Windows 10: BSOD mostly ATTEMPTED_EXECUTE_OF_NO_EXECUTE_MEMORY

The new files did not contain any newer mini-dump files. Looks like the recent crashes did not create mini-dumps.

There is also a problem with one of the earlier dumps that I can't actually run an analysis because the symbols file is not available - there is nothing I can do about that except wait for Microsoft to upload them.

 

I don't really understand what you mean with "wait for Microsoft to upload them" shouldn't the files be on my computer? I am kinda confused^^

Edit:
In Bluescreenview i can see the new two Bluescreens so they should have created a dump, shouldn't they?

 

Sorry, did not mean to confuse you - these are specific symbol files that BSOD analysts obtain from Microsoft to debug and interpret the memory dump files. Nothing to do with your PC.

Looking back at the log files, you may have uploaded the same one as you previously provided.

 

You don't need to apologize *chuckle.
But you may be right I do not understand the upload tool from this stie very good maybe i reuploaded the same one. I just did a new one this second and will try to upload this =)

 

Hi DeGab,

Apologies for bumping in, but this is just to explain that a symbol is simply a signature for drivers. Symbols are files that Windbg (the program used for analyzing a dump) uses to recognize what a file of the system (like ntoskrnl.exe and win32k.sys) is. With these files we could go quite in-depth and obtain various of information. As an example, driver developers use them to track down why their drivers crash the system and what happens so they can fix the issue.

I'll leave it further to philc43 *Smile

 

Hey Axe, Thanks for your explanation =)

I hope anyone of you can find something within the files i provided. Some days ago i was so annoyed by my computer that i was on the edge of buying a new one and selling mine for parts. This here is kind of my last attempt to fix my computer without investing alot of money in it. I think i also forgot to mention that i went to a computerstore with my computer and they did test all the components, so they should be fine.

Edit:
Here again the newest files

 

Just to let you know I have tried a number of times to get more information from your files but I am not able to do anything because Microsoft still seem to have a problem on their symbol server and I can't run the debug program.

 

Thanks for the update philc, then i guess i have to be patient for the time being. How long do you think will it take Microsoft to fix this?

 

Seeing that there is no development on the side of microsoft i will try something i wanted to try for a longer time now. I am going to install Windows 7 just to try it out.

Edit:
one last File sample for reference later.

Edit 2:
After running into several Problems when installing windows 7 i stopped trying atm

 

What stage are you at now? The MS problem is now fixed so we can debug the crash files again.

Your last crash showed:

Code: ffffe501`5abf6520 fffff80a`afef17d8Unable to load image \SystemRoot\System32\drivers\rt640x64.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for rt640x64.sys *** ERROR: Module load completed but symbols could not be loaded for rt640x64.sys rt640x64+0x17d8 ffffe501`5abf5970 fffff80a`ae4a81bcUnable to load image \SystemRoot\system32\DRIVERS\ndisrfl.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ndisrfl.sys *** ERROR: Module load completed but symbols could not be loaded for ndisrfl.sys ndisrfl+0x81bc[/quote] Same drivers as before!

 

Thanks for the Update!
I reinstalled windows 10 again several times after switching the mainboard with my father`s Mainboard and ran into the same Problems again. We switched the RAM again just to be sure, same problems. So the last component which could be broken is the CPU. I switched out the Mainboard to use my old CPU and RAM for now, Its working fine with the old components and i will send my CPU to intel the day after tomorrow. If the problems persist after recieving the new/repaired CPU i will write again here

 

Well seems like the problem really was the CPU thanks again for the help *Smile