Solved BSOD while playing Diablo 3, multiple errors (latest: 0x000000fc)

xHitsu · Jun 17, 2012

new pc
spec:
intel 7k-3770k
asrock z77 extreme 4
g skill ripjaws-z 12800/1600mhz CL9 4GB x 4
ocz 120GB vertex 3 ssd
w.d 500GB black
asus 2gb GTX670 DCII
seasonic m12II modular 750W
corsair h100 cpu cooler
fractal design core 3000 black casing
window 7 pro SP1 oem

everytime i play d3... after awhile it would crash. been seeing quite a number of different error code. i formatted my ssd twice. i updated the firmware on my ssd too. tried getting all the updated drivers. what else am i missing?

xHitsu · Jun 17, 2012

just crashed again while playing Diablo 3.
the following attached is the minidump i got.

usasma · Jun 17, 2012

We've seen a number of BSOD issues with SSD's. Here's the information that I've compiled so far:

There's not a whole bunch available to test SSD's. The "easiest" test is to remove the SSD, install a platter-based hard drive, install Windows and test for stability that way.

Here's some suggestions:
- Update the SSD's firmware to the latest available version (VERY IMPORTANT!!!)
- Update the motherboard controllers drivers to the latest available version from the controller manufacturer (NOT the mobo manufacturer unless you can't find any on the controller manufacturer's website)
- Slow the memory (RAM) down to the next slower speed (I've only seen one person who claimed that this worked for them).
- Use any manufacturer's utilities that you may have. If you don't have any, then try this free one (I haven't used it myself): Crystal Dew World
- Update chipset and storage controller drivers to the latest available from the manufacturer of the device (not the manufacturer of the motherboard). Be sure to update ALL controllers on the motherboard!
....NOTE: Recently (Nov 2011) we had BSOD issues with the Marvell 91xx controller and an SSD. You may have to switch controllers also.-
Replace the SSD with a platter based hard drive and see if that stops the BSOD's. If it does, then it's likely that there's a problem with the SSD OR an incompatibility with your system.
It's my opinion that SSD's aren't reliable enough (with current hardware) to be used on a system that needs to work reliably. Until I see reliability I will not recommend, nor will I use, SSD's for critical applications.
06 Dec 2011 - This post tends to confirm issues with certain SSD chipsets and certain controllers - [SOLVED] cant find the cause of BSOD F4 - Tech Support Forum
29 May 2012 - The frequency of BSOD's with SSD's seems to have been decreasing over the last several months. It may be approaching time to re-evaluate my stand on their suitability for use in production systems.

Intel HD graphics is disabled. Is this deliberate? If so, why?
Please ensure that you re-enable it and then update the drivers. Feel free to disable it again after updating the drivers.
FYI - we have seen issues with the VIRTU software at times. Please update it, the latest version is available from here: lucidlogix with GPU Solution

Samsung GT-I9100 cannot start ( USB\\VID_04E8&PID_6860\\0019EEEC0E758E - most likely the Samsung Galaxy S II). Please uninstall this software from your system and physically remove the device. Feel free to reinstall the latest, Win7 compatible version once the system is stabilized.

Razer Lycosa drivers date from 2008 - and these older drivers are known to cause BSOD's on some Win7 systems. Please update them immediately!

Audio drivers date from 2009, please update them from the manufacturer's website.

There were 4 memory dumps
They cited 4 different BSOD error codes
And blamed 2 different causes.

This is most likely a hardware error. They (hardware errors) are usually caused by one of these things:
- borked (broken) hardware (several different procedures used to isolate the problem device)
- overclocking - You'll know if you're overclocking or not. If uncertain we can suggest things to check.
- compatibility issues (addressed in this post)
- low-level driver problems (addressed in this post)
- or even malware (scanned for when we ask for hardware diagnostics from Initial Hardware Diagnostics or Hardware Diagnostics ).

If the problems continue after trying all of the above things, please post back and we'll start with some diagnostic tests.

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
HECIx64.sys      Wed Nov 09 19:52:25 2011 (4EBB2049)
ISCTD64.sys      Tue Aug 23 13:32:39 2011 (4E53E437)
IntcDAud.sys     Tue Dec 06 06:23:07 2011 (4EDDFB1B)
Lycosa.sys       Fri Jan 18 03:51:42 2008 (4790689E)
MBfilt64.sys     Thu Jul 30 23:40:32 2009 (4A7267B0)
MpFilter.sys     Fri Mar 09 06:05:26 2012 (4F59E3F6)
RTKVHD64.sys     Tue Jan 31 05:55:06 2012 (4F27C88A)
SaiK0CC3.sys     Wed Apr 21 12:58:14 2010 (4BCF2EA6)
SaiU0CC3.sys     Wed Apr 21 12:58:08 2010 (4BCF2EA0)
VirtuWDDM.sys    Thu May 24 12:00:34 2012 (4FBE5B22)
WPRO_41_2001.sys Mon Nov 07 16:04:48 2011 (4EB847F0)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
asahci64.sys     Wed Sep 21 05:42:57 2011 (4E79B1A1)
asmthub3.sys     Fri Mar 04 02:55:10 2011 (4D709ADE)
asmtxhci.sys     Fri Mar 04 02:54:59 2011 (4D709AD3)
dump_iaStor.sys  Tue Nov 29 22:39:19 2011 (4ED5A567)
iaStor.sys       Tue Nov 29 22:39:19 2011 (4ED5A567)
igdkmd64.sys     Mon Mar 19 19:31:54 2012 (4F67C1EA)
ikbevent.sys     Tue Jan 03 19:35:09 2012 (4F039EBD)
imsevent.sys     Tue Jan 03 19:35:31 2012 (4F039ED3)
iusb3hcs.sys     Fri Jan 27 04:37:23 2012 (4F227053)
iusb3hcs.sys     Mon Feb 27 05:58:49 2012 (4F4B61E9)
iusb3hub.sys     Fri Jan 27 04:35:25 2012 (4F226FDD)
iusb3hub.sys     Mon Feb 27 05:56:50 2012 (4F4B6172)
iusb3xhc.sys     Fri Jan 27 04:35:28 2012 (4F226FE0)
iusb3xhc.sys     Mon Feb 27 05:56:53 2012 (4F4B6175)
k57nd60a.sys     Tue May 10 00:42:30 2011 (4DC8C236)
nvhda64v.sys     Tue Jan 17 07:45:46 2012 (4F156D7A)
nvlddmkm.sys     Wed Apr 04 03:41:05 2012 (4F7BFB11)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061712-11154-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jun 16 22:45:56.465 2012 (UTC - 4:00)
System Uptime: 0 days 0:06:55.277
BugCheck 1A, {41201, fffff68000003880, 82e000036c189d25, fffffa8013268830}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+13c82 )
BUGCHECK_STR:  0x1a_41201
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  chrome.exe
FAILURE_BUCKET_ID:  X64_0x1a_41201_nt!_??_::FNODOBFM::_string_+13c82
Bugcheck code 0000001A
Arguments 00000000`00041201 fffff680`00003880 82e00003`6c189d25 fffffa80`13268830
BiosVersion = P1.30
BiosReleaseDate = 04/18/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3500
CurrentSpeed: 3500
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061712-11637-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sat Jun 16 22:38:29.342 2012 (UTC - 4:00)
System Uptime: 0 days 0:56:34.155
BugCheck D1, {10, 2, 0, fffff88004d263d8}
*** WARNING: Unable to verify timestamp for VirtuWDDM.sys
*** ERROR: Module load completed but symbols could not be loaded for VirtuWDDM.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 : dxgmms1.sys ( dxgmms1!VidSchiSignalRegisteredEvent+40 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xD1
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xD1_dxgmms1!VidSchiSignalRegisteredEvent+40
Bugcheck code 000000D1
Arguments 00000000`00000010 00000000`00000002 00000000`00000000 fffff880`04d263d8
BiosVersion = P1.30
BiosReleaseDate = 04/18/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3500
CurrentSpeed: 3500
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061712-11762-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jun 17 02:02:27.096 2012 (UTC - 4:00)
System Uptime: 0 days 0:25:40.908
BugCheck FC, {fffff88007597b60, 8000000354811963, fffff88007597960, 0}
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+438fc )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xFC
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0xFC_nt!_??_::FNODOBFM::_string_+438fc
Bugcheck code 000000FC
Arguments fffff880`07597b60 80000003`54811963 fffff880`07597960 00000000`00000000
BiosVersion = P1.30
BiosReleaseDate = 04/18/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3500
CurrentSpeed: 3500
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061712-12152-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jun 17 00:48:15.394 2012 (UTC - 4:00)
System Uptime: 0 days 0:18:26.207
BugCheck 1E, {ffffffffc0000005, fffff80002f86b21, 0, a8}
Probably caused by : ntkrnlmp.exe ( nt!ObpCloseHandleTableEntry+51 )
BUGCHECK_STR:  0x1E_c0000005_R
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  MsMpEng.exe
FAILURE_BUCKET_ID:  X64_0x1E_c0000005_R_nt!ObpCloseHandleTableEntry+51
Bugcheck code 0000001E
Arguments ffffffff`c0000005 fffff800`02f86b21 00000000`00000000 00000000`000000a8
BiosVersion = P1.30
BiosReleaseDate = 04/18/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3500
CurrentSpeed: 3500
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

xHitsu · Jun 17, 2012

i'm gonna do what you have highlighted and try see if it works.
Thanks for your time.

xHitsu · Jun 17, 2012

now it's pointing down to 1 error code.
i've uploaded the minidump.
hopefully this will help to pin point what went wrong.

usasma · Jun 17, 2012

Audio drivers still date from 2009. Don't fret over them, but do update them if you haven't.

First thing to try is running Driver Verifier according to these instructions: Driver Verifier Settings

Next is to start with the free diagnostics from here: Hardware Diagnostics

The following info is just FYI, I've already addressed the issues that I saw in the above paragraphs

- Further info on BSOD error messages available at: http://www.carrona.org/bsodindx.html
- Info on how to troubleshoot BSOD's (DRAFT): http://www.carrona.org/userbsod.html
- How I do it: http://www.carrona.org/howidoit.html

3RD PARTY DRIVERS PRESENT IN THE DUMP FILES

Code:

[font=lucida console]
HECIx64.sys      Wed Nov 09 19:52:25 2011 (4EBB2049)
ISCTD64.sys      Tue Aug 23 13:32:39 2011 (4E53E437)
IntcDAud.sys     Tue Dec 06 06:23:07 2011 (4EDDFB1B)
Lycosa.sys       Tue Sep 07 23:01:26 2010 (4C86FC86)
MBfilt64.sys     Thu Jul 30 23:40:32 2009 (4A7267B0)
MpFilter.sys     Fri Mar 09 06:05:26 2012 (4F59E3F6)
RTKVHD64.sys     Tue Jan 31 05:55:06 2012 (4F27C88A)
SaiBus.sys       Mon Jan 23 12:29:11 2012 (4F1D98E7)
SaiK0CC3.sys     Mon Sep 19 08:41:43 2011 (4E773887)
SaiMini.sys      Mon Jan 23 12:29:11 2012 (4F1D98E7)
SaiU0CC3.sys     Mon Sep 19 08:41:38 2011 (4E773882)
VKbms.sys        Thu Sep 30 12:16:33 2010 (4CA4B7E1)
VirtuWDDM.sys    Sun Apr 22 12:20:30 2012 (4F942FCE)
WPRO_41_2001.sys Mon Nov 07 16:04:48 2011 (4EB847F0)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
asahci64.sys     Wed Sep 21 05:42:57 2011 (4E79B1A1)
asmthub3.sys     Fri Mar 04 02:55:10 2011 (4D709ADE)
asmtxhci.sys     Fri Mar 04 02:54:59 2011 (4D709AD3)
b57nd60a.sys     Thu Feb 09 22:32:25 2012 (4F348FC9)
cpuz135_x64.sys  Wed Sep 21 04:23:41 2011 (4E799F0D)
dump_iaStor.sys  Tue Nov 29 22:39:19 2011 (4ED5A567)
iaStor.sys       Tue Nov 29 22:39:19 2011 (4ED5A567)
igdkmd64.sys     Mon Mar 19 19:31:54 2012 (4F67C1EA)
ikbevent.sys     Tue Jan 03 19:35:09 2012 (4F039EBD)
imsevent.sys     Tue Jan 03 19:35:31 2012 (4F039ED3)
iusb3hcs.sys     Mon Feb 27 05:58:49 2012 (4F4B61E9)
iusb3hub.sys     Mon Feb 27 05:56:50 2012 (4F4B6172)
iusb3xhc.sys     Mon Feb 27 05:56:53 2012 (4F4B6175)
mshidkmdf.sys    Mon Jul 13 20:06:24 2009 (4A5BCC00)
nvhda64v.sys     Tue Jan 17 07:45:46 2012 (4F156D7A)
nvlddmkm.sys     Wed Apr 04 03:41:05 2012 (4F7BFB11)
[/font]

Code:

[font=lucida console]
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061712-10935-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jun 17 10:40:40.254 2012 (UTC - 4:00)
System Uptime: 0 days 0:09:51.879
BugCheck A, {2200, e, 0, fffff80001eac090}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiIpiProcessRequests+60 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiIpiProcessRequests+60
Bugcheck code 0000000A
Arguments 00000000`00002200 00000000`0000000e 00000000`00000000 fffff800`01eac090
BiosVersion = P1.70
BiosReleaseDate = 06/06/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3500
CurrentSpeed: 3500
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\John\_jcgriff2_\dbug\__Kernel__\061712-11668-01.dmp]
Built by: 7601.17835.amd64fre.win7sp1_gdr.120503-2030
Debug session time: Sun Jun 17 10:27:05.580 2012 (UTC - 4:00)
System Uptime: 0 days 0:03:49.392
BugCheck A, {300000000, 2, 0, fffff800030a5c82}
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : ntkrnlmp.exe ( nt!KiProcessExpiredTimerList+72 )
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  System
FAILURE_BUCKET_ID:  X64_0xA_nt!KiProcessExpiredTimerList+72
Bugcheck code 0000000A
Arguments 00000003`00000000 00000000`00000002 00000000`00000000 fffff800`030a5c82
BiosVersion = P1.70
BiosReleaseDate = 06/06/2012
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3500
CurrentSpeed: 3500
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

[/FONT]

xHitsu · Jun 18, 2012

ok.. i figured there's too much to handle for me right now. My friend came in today and help me out.

1st of all. i tried enabling driver verifier and constantly got this error code 0x000000c9. they said it's a I/O thingy. so i slowly unplug everything and i still cant boot up to windows at all cos they din give me the option to boot in safe mode or anything.

currently my friend and i reformat the ssd and install window 7 again. we installed driver by driver (restarting after each). and everything seem to be working fine now. but i'm running on 1 ram at the moment. gotta work tomorrow so i figure that i would leave it that way for now. gonna continue trying ram by ram until it's all clear.

gonna upload my Perfmon. It would be nice if you could tell me what "#UNKNOWN" is.

usasma · Jun 18, 2012

Looks like this: Intel Smart Connect Technology
Intel Smart Connect Technology.

A driver for that "thing" is on your mobo page here: ASRock > Products > Z77 Extreme4

xHitsu · Jun 22, 2012

apparently the problem was a RAM. changed with the shop a new pack and now it's working fine

Solved BSOD while playing Diablo 3, multiple errors (latest: 0x000000fc)

xHitsu

New member

My Computer

xHitsu

New member

My Computer

usasma

Mr. Cranky Pants

My Computer

xHitsu

New member

My Computer

xHitsu

New member

My Computer

usasma

Mr. Cranky Pants

My Computer

xHitsu

New member

My Computer

usasma

Mr. Cranky Pants

My Computer

xHitsu

New member

My Computer

Similar threads