Kernel_system_check_failure

Phatx87 · May 30, 2014

Kernel_security_check_failure

Hello guys, first time posting on this site to bare with me, I believe i have the correct information here for you guys to interpret but it seems my problem is not very consistent and only happens about 2 times a week depending on how much I am on. I notice that it seems (but not confirmed) to be triggered when playing games as I play league of legends with my friends and it likes to crash at the most intense moments lol. Any advice would be much appreciated thanks in advance!!!!

Phatx87 · May 30, 2014

Not sure if this is important or not either but ive also seen this same crash once when i went to restart my computer, but only once im pretty sure.

Phatx87 · May 31, 2014

Ok another crash and this one has a different name to it, "System_Service_exception". Im starting to think im either bad luck or maybe there is a problem with my current windows config. Is that possible?

Phatx87 · May 31, 2014

Am I missing information on my post? seems other people with the same exact problems r getting replies and ill be happy to provide any further information at request, thanks again guys

Phatx87 · Jun 1, 2014

Well I guess no one is going to reply to this, was worth a shot I guess, oh well

Phatx87 · Jun 3, 2014

Another crash....PLEASE HELP =)

IAssassinII · Jun 4, 2014

No one seems to want to respond to these questions. I'm having a similar problem man.

Phatx87 · Jun 5, 2014

Ya i dont get it, would really like to get some feedback and possible solutions, but i guess a reformat is the only step and then sending back my Mobo.... = (

Phatx87 · Jun 6, 2014

well another crash....and another file to attach, not that i think anyone is going to look at it lol

Phatx87 · Jun 6, 2014

And now another one...

usasma · Jun 7, 2014

There just aren't that many people who do BSOD analysis, so at times we get a bit overwhelmed!

I check topics from the oldest to the latest - as time allows. Right now I'm working on those not responded to from 2 days ago. I do this by looking at the last reply date. Yours seems to have slipped through the cracks here. In the future, if you haven't received a reply within 48 hours, please PM someone for assistance (FYI - now that I've responded to this topic, I'll bbe notified by email if anyone replies).

IAssassinII - You're welcome to hang out here to see what we do. But, I'd suggest that you start your own topic so that you can get individual assistance that relates directly to your problem.

I'll start on the analysis now - and will post my results in another post.........

usasma · Jun 7, 2014

You have a NETGEAR WNDA3100v2 N600 Wireless Dual Band USB Adapter and it's drivers date from as early as 2007:

I do not recommend using wireless USB network devices. Especially in Win8/8.1 systems.
These wireless USB devices have many issues with Win7 and later - using Vista drivers with them is almost sure to cause a BSOD.
Should you want to keep using these devices, be sure to have Win8/8.1 drivers - DO NOT use Vista drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

The drivers for this device aren't installed:

PCI Simple Communications Controller PCI\VEN_8086&DEV_8C3A&SUBSYS_78181462&REV_04\3&11583659&0&B0 The drivers for this device are not installed.

This is most likely the Intel Management Engine Interface. Please download and install the latest, Win8.1 compatible version from the manufacturer's website

At times the Killer Network Manager may cause BSOD problems:

NOTE: See this link first: http://www.eightforums.com/bsod-cra...msi-gt70-dragon-edition-2-a-4.html#post358413 (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.

Click to expand...

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

Click to expand...

Click to expand...

MSI Afterburner (along with Riva Tuner and EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys). Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting. Feel free to resume the overclock once the system has been stabilized.

Please uninstall the Western Digital software. The wdcsam64.sys driver dates from 2008 and is known to cause BSOD's on some Windows systems

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

scmndisp.sys Wed Jan 17 02:48:03 2007 (45ADD4B3)
Netgear Neutral Wireless Solution
http://www.carrona.org/drivers/driver.php?id=scmndisp.sys

wdcsam64.sys Wed Apr 16 04:39:08 2008 (4805BB2C)
Western Digital SCSI Arcitecture Model (SAM) WDM driver [br] 2008 driver version has known BSOD issues in Windows
http://www.carrona.org/drivers/driver.php?id=wdcsam64.sys

bcmwlhigh664.sys Tue Apr 19 03:13:08 2011 (4DAD3604)
Broadcom 802.11 USB Network Adapter Driver
http://www.carrona.org/drivers/driver.php?id=bcmwlhigh664.sys

Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web. Removing some drivers may make the system unstable - so if you're unable to find updates, post back for info on the one's that can/cannot be safely removed.

Finally, one of the memory dumps blames hardware, so if the above doesn't stop the BSOD's, then please start with these free hardware diagnostics: Hardware Diagnostics

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Fri Jun  6 03:18:20.374 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\060614-94937-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 1:47:24.051[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )[/B]
BugCheck [B]139, {3, fffff8007e634820, fffff8007e634778, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000139]KERNEL_SECURITY_CHECK_FAILURE (139)[/url]
Arguments: 
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: fffff8007e634820, Address of the trap frame for the exception that caused the bugcheck
Arg3: fffff8007e634778, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x139_3_nt!KiFastFailDispatch[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.7
  BIOS Release Date             12/02/2013
  Manufacturer                  MSI
  Product Name                  MS-7818
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri Jun  6 01:28:36.218 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\060614-95296-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 10:55:18.516[/B]
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by :[B]hardware ( afd+4c5cd )[/B]
BugCheck [B]3B, {c000001d, fffff803c5f27c41, ffffd0002183f9d0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c000001d, Exception code that caused the bugcheck
Arg2: fffff803c5f27c41, Address of the instruction which caused the bugcheck
Arg3: ffffd0002183f9d0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  KillerService.
FAILURE_BUCKET_ID: [B]IP_MISALIGNED[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.7
  BIOS Release Date             12/02/2013
  Manufacturer                  MSI
  Product Name                  MS-7818
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 31 03:27:42.981 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\053114-13921-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]0 days 11:17:25.658[/B]
*** WARNING: Unable to verify timestamp for aswSnx.sys
*** ERROR: Module load completed but symbols could not be loaded for aswSnx.sys
Probably caused by :[B]aswSnx.sys ( aswSnx+306c8 )[/B]
BugCheck [B]3B, {c0000005, fffff800eda268f7, ffffd00022c94bf0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800eda268f7, Address of the instruction which caused the bugcheck
Arg3: ffffd00022c94bf0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  raidcall.exe
FAILURE_BUCKET_ID: [B]0x3B_aswSnx+306c8[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.7
  BIOS Release Date             12/02/2013
  Manufacturer                  MSI
  Product Name                  MS-7818
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri May 30 16:09:22.052 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\053014-13484-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]1 days 16:14:56.729[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )[/B]
BugCheck [B]139, {3, ffffd000204e05c0, ffffd000204e0518, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000139]KERNEL_SECURITY_CHECK_FAILURE (139)[/url]
Arguments: 
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd000204e05c0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd000204e0518, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
PROCESS_NAME:  LoLLauncher.ex
FAILURE_BUCKET_ID: [B]0x139_3_nt!KiFastFailDispatch[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.7
  BIOS Release Date             12/02/2013
  Manufacturer                  MSI
  Product Name                  MS-7818
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed May 28 23:52:49.243 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\052814-16093-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]5 days 8:32:46.734[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!KiFastFailDispatch+d0 )[/B]
BugCheck [B]139, {3, ffffd00025dfc630, ffffd00025dfc588, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x00000139]KERNEL_SECURITY_CHECK_FAILURE (139)[/url]
Arguments: 
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd00025dfc630, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd00025dfc588, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
BUGCHECK_STR:  0x139
DEFAULT_BUCKET_ID:  LIST_ENTRY_CORRUPT
PROCESS_NAME:  Battle.net.exe
FAILURE_BUCKET_ID: [B]0x139_3_nt!KiFastFailDispatch[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.7
  BIOS Release Date             12/02/2013
  Manufacturer                  MSI
  Product Name                  MS-7818
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri May 23 15:01:02.295 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\052314-13437-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]2 days 11:00:35.971[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!PspReturnQuota+45 )[/B]
BugCheck [B]3B, {c0000005, fffff800544a1765, ffffd00023ea6dc0, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c0000005, Exception code that caused the bugcheck
Arg2: fffff800544a1765, Address of the instruction which caused the bugcheck
Arg3: ffffd00023ea6dc0, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  raidcall.exe
FAILURE_BUCKET_ID: [B]0x3B_nt!PspReturnQuota[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.7
  BIOS Release Date             12/02/2013
  Manufacturer                  MSI
  Product Name                  MS-7818
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Wed May 21 03:58:24.220 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\052114-16062-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]2 days 10:06:50.898[/B]
Probably caused by :[B]ntkrnlmp.exe ( nt!SwapContext_PatchLdMxCsr+ae )[/B]
BugCheck [B]3B, {c0000096, fffff80333d5831b, ffffd00185a75d30, 0}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000003B]SYSTEM_SERVICE_EXCEPTION (3b)[/url]
Arguments: 
Arg1: 00000000c0000096, Exception code that caused the bugcheck
Arg2: fffff80333d5831b, Address of the instruction which caused the bugcheck
Arg3: ffffd00185a75d30, Address of the context record for the exception that caused the bugcheck
Arg4: 0000000000000000, zero.
BUGCHECK_STR:  0x3B
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  Steam.exe
FAILURE_BUCKET_ID: [B]0x3B_nt!SwapContext_PatchLdMxCsr[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.7
  BIOS Release Date             12/02/2013
  Manufacturer                  MSI
  Product Name                  MS-7818
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon May 12 13:42:04.207 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\051214-14140-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]6 days 16:32:29.882[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]hardware ( nvlddmkm+1c88b4 )[/B]
BugCheck [B]D1, {0, 6, 1, fffff801a91f78b4}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url]
Arguments: 
Arg1: 0000000000000000, memory referenced
Arg2: 0000000000000006, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff801a91f78b4, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]IP_MISALIGNED_nvlddmkm.sys[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.7
  BIOS Release Date             12/02/2013
  Manufacturer                  MSI
  Product Name                  MS-7818
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon May  5 21:08:40.513 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\050514-8828-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]1 days 7:04:08.191[/B]
*** ERROR: Module load completed but symbols could not be loaded for afd.sys
Probably caused by :[B]afd.sys ( afd+4a9fb )[/B]
BugCheck [B]D1, {fffff800e65dd618, 2, 0, fffff800e664a9fb}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url]
Arguments: 
Arg1: fffff800e65dd618, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff800e664a9fb, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  NetworkManager
FAILURE_BUCKET_ID: [B]AV_afd+4a9fb[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.7
  BIOS Release Date             12/02/2013
  Manufacturer                  MSI
  Product Name                  MS-7818
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Tue Apr 22 23:24:50.288 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\042214-7500-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].16452.amd64fre.winblue_gdr.131030-1505
System Uptime:[B]10 days 2:17:01.963[/B]
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by :[B]nvlddmkm.sys ( nvlddmkm+1f36bf )[/B]
BugCheck [B]D1, {ffffffff8d4805c3, e, 1, fffff80001e106bf}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x000000D1]DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)[/url]
Arguments: 
Arg1: ffffffff8d4805c3, memory referenced
Arg2: 000000000000000e, IRQL
Arg3: 0000000000000001, value 0 = read operation, 1 = write operation
Arg4: fffff80001e106bf, address which referenced memory
BUGCHECK_STR:  AV
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]AV_nvlddmkm+1f36bf[/B]
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Fri Jun  6 03:18:20.374 2014 (UTC - 4:00)**************************
[COLOR=RED][B]scmndisp.sys                Wed Jan 17 02:48:03 2007 (45ADD4B3)[/B][/COLOR]
[COLOR=RED][B]wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)[/B][/COLOR]
[COLOR=RED][B]bcmwlhigh664.sys            Tue Apr 19 03:13:08 2011 (4DAD3604)[/B][/COLOR]
AcpiCtlDrv.sys              Tue Jul 17 13:07:16 2012 (50059BC4)
ISCTD64.sys                 Tue Nov 27 14:52:34 2012 (50B51A02)
iocbios2.sys                Mon Jan  7 12:53:11 2013 (50EB0B87)
ICCWDT.sys                  Wed Jan 23 03:46:01 2013 (50FFA349)
bwcW8x64.sys                Wed Feb 13 12:25:48 2013 (511BCC9C)
e22w8x64.sys                Wed Mar 20 17:24:01 2013 (514A28F1)
intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
NETwew00.sys                Thu Aug 22 17:20:34 2013 (521680A2)
nvhda64v.sys                Thu Nov 28 08:38:09 2013 (52974741)
aswHwid.sys                 Tue Apr  8 11:43:26 2014 (5344191E)
aswRdr2.sys                 Thu Apr 17 07:02:56 2014 (534FB4E0)
aswMonFlt.sys               Thu Apr 17 07:04:01 2014 (534FB521)
aswRvrt.sys                 Thu Apr 17 07:04:41 2014 (534FB549)
aswVmm.sys                  Thu Apr 17 07:04:55 2014 (534FB557)
aswSnx.sys                  Mon May  5 04:04:42 2014 (5367461A)
aswSP.sys                   Mon May  5 04:11:11 2014 (5367479F)
aswStm.sys                  Mon May  5 04:11:48 2014 (536747C4)
RTKVHD64.sys                Wed May 14 06:28:52 2014 (53734564)
rzudd.sys                   Mon May 19 02:43:44 2014 (5379A820)
nvlddmkm.sys                Mon May 19 19:08:44 2014 (537A8EFC)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Sat May 31 03:27:42.981 2014 (UTC - 4:00)**************************
rzudd.sys                   Tue Apr  8 22:28:33 2014 (5344B051)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Fri May 23 15:01:02.295 2014 (UTC - 4:00)**************************
MBfilt64.sys                Thu Jul 30 23:40:32 2009 (4A7267B0)
RTKVHD64.sys                Mon Oct 21 02:38:20 2013 (5264CBDC)
rzudd.sys                   Fri Nov 15 01:34:51 2013 (5285C08B)
nvlddmkm.sys                Tue Mar  4 06:07:52 2014 (5315B408)
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
**************************Mon May 12 13:42:04.207 2014 (UTC - 4:00)**************************
aswRvrt.sys                 Fri Oct  4 03:48:58 2013 (524E72EA)
aswRdr2.sys                 Fri Oct 11 07:11:37 2013 (5257DCE9)
aswVmm.sys                  Mon Dec  9 02:04:51 2013 (52A56B93)
aswSnx.sys                  Tue Jan 21 12:11:09 2014 (52DEAA2D)
aswMonFlt.sys               Tue Jan 21 12:11:16 2014 (52DEAA34)
aswSP.sys                   Tue Jan 21 12:17:55 2014 (52DEABC3)
aswStm.sys                  Tue Jan 21 12:18:41 2014 (52DEABF1)
[/font]

Phatx87 · Jun 9, 2014

Thank you for looking over my thread, Had almost given up hope hahaha. OK, so far i have updated my drivers for each one specified, and I have ran Memtest without any errors (need to let it run all night just to make sure), will move on to the other diagnostic tools when i have some time. I have also removed the Killer Network Manager and under clocked my settings back to default for the time being. On a side note, Im not sure why I waited until now to mention this buy my built in sound card has actually never worked, and I was and am still in the process of buying one to use instead, but sometimes my sound (which only plays out of the right side) will cut out on me...and makes this weird noise, the only reason why i bring this up is because when my system does crash....it makes the same noise as when my sound dies. Don't know if this is related but just something i noticed. Oh and 3 days with no crashes, though unfortunately this is not necessarily abnormal, and I dont know the trigger for the crash so I cant simulate a scenario to see if it is fixed or not. Will post back in a day or two and let you know where I am at, thanks again!

Phatx87 · Jun 12, 2014

Ok so I went almost a week without any crashes....and then it happened lol. KMODE_EXCEPTION_NOT_HANDLED (dxmms1.sys). Going to do some research and see if there is anything specific with this crash, I was almost convinced it was resolved too =(

usasma · Jun 13, 2014

Still looks like a hardware problem to me.
Try removing the sound card (and any programs associated with it)

Most errors have had an nVidia video driver involved, have you run the video tests at this link: Hardware Diagnostics
Please run any tests that you haven't run before (start with the video tests).

Please remove the Western Digital software - the wdcsam64.sys driver is a known BSOD cause.
If you have already removed it, post back for instructions on how to manually remove it (not a fun thing to do, as it may stop your system from booting - that's why we prefer the uninstaller).

If unable to update the USB network device, please remove it (temporarily) and uninstall it's software to see if that helps. During this time, try using a wired internet connection - you may have to move the computer closer to the router/modem - or may have to use a very long ethernet cord in order to achieve connectivity (again, this is temporary).

Why are you using a wireless USB device when you have a built-in wireless card?

Please update these older drivers. Links are included to assist in looking up the source of the drivers. If unable to find an update, please remove (un-install) the program responsible for that driver. DO NOT manually delete/rename the driver as it may make the system unbootable! :

tapoas.sys Sun Jul 11 20:31:59 2010 (4C3A627F)
OpenVPN Virtual Network Driver
http://www.carrona.org/drivers/driver.php?id=tapoas.sys

Please note the drivers below that date from before the release of Windows 8.1 (17 Oct 2013) - check to see that each and every one is compatible w/Windows 8.1 (at the manufacturer's website). If not, you must either remove the device and it's software - or locate a Windows 8.1 compatible update on the web. Removing some drivers may make the system unstable - so if you're unable to find updates, post back for info on the one's that can/cannot be safely removed.

Killer Network Manager is still starting:

At times the Killer Network Manager may cause BSOD problems:

NOTE: See this link first: http://www.eightforums.com/bsod-cra...msi-gt70-dragon-edition-2-a-4.html#post358413 (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.

Click to expand...

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

Click to expand...

Click to expand...

Click to expand...

Analysis:
The following is for informational purposes only.

Code:

[font=lucida console]**************************Thu Jun 12 21:07:21.636 2014 (UTC - 4:00)**************************
Loading Dump File [C:\Users\John\SysnativeBSODApps\061214-121109-01.dmp]
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Built by: [B]9600[/B].17041.amd64fre.winblue_gdr.140305-1710
System Uptime:[B]3 days 21:38:18.970[/B]
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by :[B]dxgmms1.sys ( dxgmms1+518f )[/B]
BugCheck [B]1E, {ffffffffc0000005, fffff800ac01b18f, 0, ffffffffffffffff}[/B]
BugCheck Info: [url=http://www.carrona.org/bsodindx.html#0x0000001E]KMODE_EXCEPTION_NOT_HANDLED (1e)[/url]
Arguments: 
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff800ac01b18f, The address that the exception occurred at
Arg3: 0000000000000000, Parameter 0 of the exception
Arg4: ffffffffffffffff, Parameter 1 of the exception
BUGCHECK_STR:  0x1E_c0000005_R
PROCESS_NAME:  System
FAILURE_BUCKET_ID: [B]0x1E_c0000005_R_dxgmms1+518f[/B]
CPUID:        "Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz"
MaxSpeed:     3500
CurrentSpeed: [B]3500[/B]
  BIOS Version                  V1.7
  BIOS Release Date             12/02/2013
  Manufacturer                  MSI
  Product Name                  MS-7818
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
[/font]

3rd Party Drivers:
The following is for information purposes only.
Any drivers in red should be updated or removed from your system. And should have been discussed in the body of my post.

Code:

[font=lucida console]**************************Thu Jun 12 21:07:21.636 2014 (UTC - 4:00)**************************
[COLOR=RED][B]wdcsam64.sys                Wed Apr 16 04:39:08 2008 (4805BB2C)[/B][/COLOR]
[COLOR=RED][B]tapoas.sys                  Sun Jul 11 20:31:59 2010 (4C3A627F)[/B][/COLOR]
[COLOR=RED][B]bcmwlhigh664.sys            Tue Apr 19 03:13:08 2011 (4DAD3604)[/B][/COLOR]
scmndisp.sys                Mon May 28 03:51:48 2012 (4FC32E94)
AcpiCtlDrv.sys              Tue Jul 17 13:07:16 2012 (50059BC4)
ISCTD64.sys                 Tue Nov 27 14:52:34 2012 (50B51A02)
iocbios2.sys                Mon Jan  7 12:53:11 2013 (50EB0B87)
ICCWDT.sys                  Wed Jan 23 03:46:01 2013 (50FFA349)
bwcW8x64.sys                Wed Feb 13 12:25:48 2013 (511BCC9C)
e22w8x64.sys                Wed Mar 20 17:24:01 2013 (514A28F1)
intelppm.sys                Thu Aug 22 04:46:35 2013 (5215CFEB)
dump_storahci.sys           Thu Aug 22 07:40:39 2013 (5215F8B7)
tap0901.sys                 Thu Aug 22 08:40:01 2013 (521606A1)
NETwew00.sys                Thu Aug 22 17:20:34 2013 (521680A2)
TeeDriverx64.sys            Wed Nov 27 12:56:32 2013 (52963250)
nvhda64v.sys                Thu Nov 28 08:38:09 2013 (52974741)
aswHwid.sys                 Tue Apr  8 11:43:26 2014 (5344191E)
aswRdr2.sys                 Thu Apr 17 07:02:56 2014 (534FB4E0)
aswMonFlt.sys               Thu Apr 17 07:04:01 2014 (534FB521)
aswRvrt.sys                 Thu Apr 17 07:04:41 2014 (534FB549)
aswVmm.sys                  Thu Apr 17 07:04:55 2014 (534FB557)
aswSnx.sys                  Mon May  5 04:04:42 2014 (5367461A)
aswSP.sys                   Mon May  5 04:11:11 2014 (5367479F)
aswStm.sys                  Mon May  5 04:11:48 2014 (536747C4)
RTKVHD64.sys                Wed May 14 06:28:52 2014 (53734564)
rzudd.sys                   Mon May 19 02:43:44 2014 (5379A820)
nvlddmkm.sys                Mon May 19 19:08:44 2014 (537A8EFC)
[/font]

Phatx87 · Jun 13, 2014

I use the wireless adapter because I can get onto the 5G network which no other device in the house is on (so i have no interference with my connection) Ill update the drivers and Im in the process of getting a new sound card in the near future so HOPEFULLY between the drivers and the sound card it will fix my problem. I also have removed western digital from my computer not sure why it is still showing up

usasma · Jun 14, 2014

Try this to remove the Western Digital driver:

Code:
1) Create a Restore Point using System Restore
2) Create a Repair disc (Recovery Drive in Win8.1):
Win 7 - Go to Start...All Programs...Maintenance...Create a System Repair Disc
Win 8 - Press "WIN" and "R" to open the Run dialog...type "RECDISC" (without the quotes) and press ENTER
Win 8.1 - Go to the Start Screen and type in "recoverydrive" (one word, without the quotes). That will start the recovery drive process. You will need a USB drive of at least 512 mB - and all data will be erased off of it. If copying the recovery partition the drive size will be much, much larger (16 - 32 gB drive required).
3) Test the System Repair disc/Recovery Drive to make sure that you can get to the System Restore entry when you boot from the disk/drive (you may also want to try actually using System Restore to make sure that it works)
4) Download this free program (Autoruns for Windows) and use it to disable any instances of wdcsam64.sys that are starting (or any other Western Digital entries) (DO NOT DELETE - only disable by removing the checkmark in the left hand column)
5) Check in Device Manager (to include showing hidden devices from the View menu item) and ensure that any instances of wdcsam64.sys (or any other Western Digital entries) are "Uninstalled" (DO NOT DISABLE THESE).
6) Check in the Services applet (services.msc) to be sure any instances of wdcsam64.sys or any other Western Digital entries are disabled.
7) Go to C:\Windows\System32\drivers and rename the wdcsam64.sys driver to wdcsam64.BAD (search the hard drive for it if it's not in C:\Windows\System32\drivers).

In the event that the system doesn't boot:

1) Boot from the System Repair disc/Recovery Drive and use the Command Prompt option to rename wdcsam64.BAD to wdcsam64.sys

Code:

ren C:\Windows\System32\drivers\wdcsam64.BAD C:\Windows\System32\drivers\wdcsam64.sys

2) Boot from the System Repair disc/Recovery Drive and use the System Restore option to restore the system to a point before the changes were made.

Good luck!

Kernel_system_check_failure

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer

New Member

My Computer

Mr. Cranky Pants

My Computer