BSOD ATTEMPTED EXECUTE OF NOEXECUTE MEMORY at Random times

Exod · Apr 9, 2015

I've been having this problem for a week now, i tried running memtest86 to diagnose Ram but the display does not show the test once it starts it show half the stats, the other half is hidden in mi right side screen. Only once it showed correctly and determined Errors with Tests 13 - hammering with both sticks. Now i am not able do determine which stick is faulty, because i cant run the test or see results properly.

This are my specs:
https://pcpartpicker.com/user/zpam/builds/#view=PBr7YJ

The error persists while listening to music (buzzing sound until it restarts), downloading things from steam or more likely while left idle. Never while gaming or doing heavy tasks, only light individual things as mentioned. I've had instances once BSOD reaches 100% in order to restart, it wont do it at all, staying like that for ever until i do it manually.

Now that i think of it, my PC would freeze and BSOD on me with buzzing sounds quite repeatedly when i had it build. But it stopped eventually, but now the problem has returned quite worse, i think it might always had been a faulty PSU (Corsair RM 850) or Ram (Patriot Viper 3 16GB (2 x 8GB) DDR3-1866 Memory).

I hope that this dump file shows some answers , please help thanks in advance.

Exod · Apr 9, 2015

Ok, i noticed the posting instructions, i downloaded the tool to create the zip file i need to upload, but it does not create any zip file in my desktop, even running it as administrator, all goes correct but it doesn't create any zip file. What am i doing wrong?

blueelvis · Apr 10, 2015

Exod said:
Ok, i noticed the posting instructions, i downloaded the tool to create the zip file i need to upload, but it does not create any zip file in my desktop, even running it as administrator, all goes correct but it doesn't create any zip file. What am i doing wrong?

Have you tried running it in Safe Mode?

If it is still not working, kindly go to the below path and ZIP up all the contents or the Dump files -
"C:\Windows\Minidumps". You might need to copy up the dump files to some other directory before Zipping them up else you might get a Permissions Denied error. Upload this ZIP file as well with your next post so that it could be analysed.

Also, run the below tool and upload the ZIP file generated by the tool with your next post -
MSINFO Zipper - OMG Debugging!!!

Let me know how it goes ^_^

-Pranav

Exod · Apr 11, 2015

blueelvis said:
Have you tried running it in Safe Mode?

If it is still not working, kindly go to the below path and ZIP up all the contents or the Dump files -
"C:\Windows\Minidumps". You might need to copy up the dump files to some other directory before Zipping them up else you might get a Permissions Denied error. Upload this ZIP file as well with your next post so that it could be analysed.

Also, run the below tool and upload the ZIP file generated by the tool with your next post -
MSINFO Zipper - OMG Debugging!!!

Let me know how it goes ^_^

-Pranav

Thanks i finally could do it with MSINFO, for some reason i had no dice with DM Log Collector even in safe mode. Please forgive my delay, i was off with college, BSOD's are now even more frequent, here are the corespondent files please help me

View attachment 60340
View attachment 60339

blueelvis · Apr 14, 2015

Hi Exod ^_^,

Don't worry about being late. Even I am in college so I know the hard stuff we need to go through

I have analysed your dump files and below has been provided an analysis of the same for informative purposes :-

ATTEMPTED_EXECUTE_OF_NOEXECUTE_MEMORY (fc)
An attempt was made to execute non-executable memory. The guilty driver is on the stack trace (and is typically the current instruction pointer). When possible, the guilty driver's name (Unicode string) is printed on the bugcheck screen and saved in KiBugCheckDriver.

Sadly, since we are analysing a minidump file, the information stored in the variable is not complete

. Furthermore, the dump file failed to capture the faulty driver in the stack as well.

Below is a list of 3rd party drivers present on your system -

Code:

**************************Sun Apr 12 02:34:34.188 2015 (UTC + 5:30)**************************
[COLOR=#FF0000][B][U]rsdrvx64.sys                Thu Feb 12 18:31:49 2009 (49941DBD)
pwdrvio.sys                 Tue Jun 16 07:13:45 2009 (4A36F8D1)
MBfilt64.sys                Fri Jul 31 09:10:32 2009 (4A7267B0)
LGBusEnum.sys               Tue Nov 24 07:06:48 2009 (4B0B38B0)
LGVirHid.sys                Tue Nov 24 07:06:48 2009 (4B0B38B0)
ISCTD64.sys                 Wed Nov 28 01:22:34 2012 (50B51A02)
[/U][/B][/COLOR]RTCore64.sys                Mon Mar 11 11:02:06 2013 (513D6C56)
ScpVBus.sys                 Mon May  6 03:01:26 2013 (5186CFAE)
intelppm.sys                Thu Aug 22 14:16:35 2013 (5215CFEB)
NETwew00.sys                Fri Aug 23 02:50:34 2013 (521680A2)
TeeDriverx64.sys            Thu Sep  5 23:32:18 2013 (5228C72A)
asstor64.sys                Mon Jan 27 15:00:34 2014 (52E6273A)
[U][B]e22w8x64.sys                Wed Mar 26 21:28:37 2014 (5332F92D)
bwcW8x64.sys                Thu Apr 10 21:10:24 2014 (5346BB68)
[/B][/U]RTKVHD64.sys                Tue Jul 15 16:23:15 2014 (53C5081B)
SamsungRapidDiskFltr.sys    Tue Sep 16 14:23:25 2014 (5417FA85)
SamsungRapidFSFltr.sys      Tue Sep 16 14:23:46 2014 (5417FA9A)
nvhda64v.sys                Thu Oct  9 22:32:27 2014 (5436BFA3)
VBoxAswDrv.sys              Wed Feb 18 23:43:19 2015 (54E4D63F)
nvlddmkm.sys                Fri Mar 13 21:09:56 2015 (550304CC)
nvvadarm.sys                Thu Mar 19 14:13:20 2015 (550A8C28)
aswMonFlt.sys               Fri Mar 20 17:13:56 2015 (550C07FC)
aswRvrt.sys                 Fri Mar 20 17:13:59 2015 (550C07FF)
aswHwid.sys                 Fri Mar 20 17:14:25 2015 (550C0819)
aswSnx.sys                  Fri Mar 20 17:14:43 2015 (550C082B)
aswRdr2.sys                 Fri Mar 20 17:14:46 2015 (550C082E)
aswVmm.sys                  Fri Mar 20 17:27:07 2015 (550C0B13)
aswSP.sys                   Fri Mar 20 17:27:29 2015 (550C0B29)
aswStm.sys                  Fri Mar 20 17:29:44 2015 (550C0BB0)

Kindly update the drivers highlighted in RED. I have provided links above for the information.
If you are still facing problem, kindly follow the below canned speech (Thanks usasma!) regarding the Killer Network Driver as they are known to cause problems.

At times the Killer Network Manager may cause BSOD problems:

NOTE1:Link thanks to blueelvis (15Oct2014): https://forum-en.msi.com/index.php?topic=178064.0 This is a method for removing all the network software and only installing the driver. Perfect for those issues that can't be resolved any other way!

NOTE2: See this link first: BSOD while playing on msi gt70 dragon edition 2 (thanks to kaelaan) It appears that the Killer Service problem was solved with the latest release of the Qualcomm versions of the drivers (so try updating to a version dated from later in 2014).
The Qualcomm Atheros Killer Service/KillerNetManager is known to cause BSOD's. Please follow the workaround instructions here:

First, open the Run dialog (Win + R keys) and type in "services.msc" (without the quotes) and press Enter
Scroll down and locate the "Qualcomm Atheros Killer Service" and right click on it. Select "Stop"
Right click on it again and this time select "Properties"
In the dropdown box for "Startup type", select "Disabled", then click on the "OK" button at the bottom of the window

Next, open Task Manager (right click on TaskBar and select "Task Manager")
Click on the "More details" dropdown (if present)
Click on the "Startup" tab
Scroll down and locate the "KillerNetManager" entry, right click on it and select "Disable"
There may also be an Install Shield (with the Killer gaming K next to it), if so Right click on it and select "Disable"
Finally, restart the system in order for the changes to take affect.

At times the Killer Network Manager will continue to load. If so, it's usually listed in the MSINFO32...Software Environment...Startup Programs section. If it is, please try this:

It may be that the instructions aren't stopping everything.
In some cases, there's a program running out of the Program Files/Program Files (x86) directory.
"c:\program files\qualcomm atheros\killer network manager\killer~1.exe" (NOTE: killer~1.exe is most likely killernetmanager.exe)
In other cases, there's a program running out of c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe (the long string of letters and numbers may change)

Here's some things to try
1) Please see if there are any entries in the Startup tab of Task Manager that are related to Qualcomm/Atheros/Killer Network Manager (and NOT the card itself) and disable them (please let us know what you find) Be careful as the wrong selection can disable the network card.
2) Check in "msconfig" for any entries that aren't in the Startup tab of Task Manager. Let us know if you find any Qualcomm/Atheros/Killer entries there (we'll disable them differently if they are there).
3) Locate the "c:\program files\qualcomm atheros\killer network manager\killer~1.exe" and rename the .exe to .BAD (the killer~1 is actually a filename that starts with killer and ends with .exe) There will be an error in event viewer, but it'll stop the bugger from loading.
4) Locate the "c:\windows\installer\{Long string of letters, numbers, and dashes}\networkmanager.exe_130c27d738f34c89bddf21bcfd74b56d.exe" entry and rename the last .exe to .BAD (the long string of letters and numbers may change)

Just FYI - here are the MSI workaround instructions: MSI USA - Online Technical Support FAQ

Click to expand...
If you are still facing problems, kindly turn on Driver Verifier using this **GUIDE** and let the Driver Verifier crash the system for a few times. Once your system has crashed for a few times, kindly re run the Diagnostic Utility and upload a freshly created ZIP file with your next post.

Let me know how it goes ^_^

-Pranav

Exod · Apr 18, 2015

Oh man thank you so much, ive been approaching my final tests and was quite busy. Suddenly the error stopped, could it be that windows update solved the problem by itself? I did not update any driver manually. So far its been a week, i have left my PC idle, playing music, downloading things or even while gaming and the is no BSOD sign.

Many thanks friend, i'll let you know if my problem persists

blueelvis · Apr 22, 2015

Hi Exod ^_^,

Yes, it is very much possible that the issue has been solved by a Windows Update. Please monitor your system and let me know in case you face any further difficulties ^_^

-Pranav

BSOD ATTEMPTED EXECUTE OF NOEXECUTE MEMORY at Random times

Exod

New Member

My Computer

System One

Exod

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

Exod

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One

Exod

New Member

My Computer

System One

blueelvis

OMG Debugger!

My Computer

System One