BSOD mostly ATTEMPTED_EXECUTE_OF_NO_EXECUTE_MEMORY

DeGab · 11 May 2017

Here are the new files =)

philc43 · 11 May 2017

OK, the new files from today indicate that it is still the same two drivers that are causing trouble. I can see that the Realtek one is a newer version but it has not helped.

Please try the versions on the motherboard website for both the Audio and the Intel Management Engine Drivers:

https://www.msi.com/Motherboard/supp...river&Win10 64

DeGab · 11 May 2017

Thanks for the answer, i will try em as soon as i get home. Just wanted to say that i downloaded the tool for my motherboard to update all the drivers the day before yesterday and it should have updated all of them then. Will nonetheless try to update the ones you said in like half an hour or so

Update:
I did install the new drivers and then it asked me to restart, so i did. As soon as i got to the desktop I got a BSOD

Update2:

Got Another one here are the new files

philc43 · 11 May 2017

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.

DeGab · 11 May 2017

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?

philc43 · 11 May 2017

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.

DeGab · 11 May 2017

You don't need to apologize

.
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 =)

axe0 · 12 May 2017

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 :)

DeGab · 12 May 2017

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

philc43 · 14 May 2017

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.