BSOD while playing d3 on new computer

yrag · 26 May 2012

hi guys,

really need your help on this... its my new computer and its drivng mad trying to troubleshoot the problem.. i previously thought it was a ram problem... ran memtest86+ and it showed erroors... however one day later i tried runing it again but it didnt show errors anymore... i ran it for 6 hours and then 10 passes

the followin is my system spec

i5 3570k
gigabyte z77x d3h
corsair vengence cl9 1600 2x4GB
sapphire 7850 OC edd
corsair txm 650 PSU
500gb WD blue HDD
win 7 ulti 64bit - fresh install.. i have already installed win7 and all the drivers before

i ran the smart test on the HDD and couple of tests on the harddisk and found no problems..

attached is my last 2 BSOD minidump files...

i hope someone can take a look at it and make some sense from it... thx a million

edit1: this does not only happen while im playing diablo3. it happened once while i was using google c hrome..altho 90% of the time i am playing diablo on the PC.

yrag · 26 May 2012

hi guys can anymody help me?????
i really need your help

usasma · 26 May 2012

Please provide this info for a complete analysis: https://www.sevenforums.com/crashes-d...tructions.html

Only known problem driver that I can see is AppleCharger.sys
Please uninstall that from your system to see if it stops the BSOD's

Try a memory test: Memory Diagnostics
Try Driver Verifier according to these directions: Driver Verifier Settings

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:


xhcdrv.sys       Mon Nov 14 06:01:09 2011 (4EC0F4F5)
mvs91xx.sys      Mon Aug 08 23:05:23 2011 (4E40A3F3)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
iaStor.sys       Tue Nov 29 22:39:19 2011 (4ED5A567)
mvxxmm.sys       Mon Aug 08 23:05:06 2011 (4E40A3E2)
iusb3hcs.sys     Thu Jan 05 06:56:40 2012 (4F058FF8)
AppleCharger.sys Tue Nov 01 22:46:00 2011 (4EB0AEE8)
atikmpag.sys     Thu Apr 05 21:10:44 2012 (4F7E4294)
cpuz135_x64.sys  Fri Mar 09 03:56:55 2012 (4F59C5D7)
HECIx64.sys      Wed Nov 09 19:52:25 2011 (4EBB2049)
iusb3xhc.sys     Thu Jan 05 06:54:45 2012 (4F058F85)
atikmdag.sys     Thu Apr 05 21:48:25 2012 (4F7E4B69)
L1C62x64.sys     Wed Aug 03 02:21:09 2011 (4E38E8D5)
iusb3hub.sys     Thu Jan 05 06:54:43 2012 (4F058F83)
AtihdW76.sys     Thu Feb 23 07:30:12 2012 (4F463154)
viahduaa.sys     Tue Jan 10 06:33:14 2012 (4F0C21FA)
ViaHub3.sys      Mon Nov 14 06:01:20 2011 (4EC0F500)
TRIXX.sys        Wed Oct 06 12:14:37 2010 (4CACA06D)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052612-17238-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat May 26 05:15:40.461 2012 (UTC - 4:00)
System Uptime: 0 days 1:47:38.304
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355e4 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Origin.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`010d2770 00000000`0000ffff 00000000`00000000
BiosVersion = F8
BiosReleaseDate = 05/11/2012
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052612-12589-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat May 26 03:27:35.183 2012 (UTC - 4:00)
System Uptime: 0 days 3:51:18.401
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+c6 )
BUGCHECK_STR:  0x1a_8884
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6
Bugcheck code 0000001A
Arguments 00000000`00008884 fffffa80`04c985d0 fffffa80`034bd7a0 00000000`00000400
BiosVersion = F8
BiosReleaseDate = 05/11/2012
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

yrag · 26 May 2012

hi,

sorry i did not see the posting instructions. i have attached all the files as per the instructions.

hope u can do a more detailed analysis to find the root of the problem... for the mean time i will do the memory test and driver verifier

my system spec are as follows.

x86 (32-bit) or x64 ? x64
- the original installed OS on the system? fresh install on new computer
- an OEM or full retail version? full retail
- OEM = came pre-installed on system
- Full Retail = you purchased it from retailer
- What is the age of system (hardware)? 2 weeks
- What is the age of OS installation (have you re-installed the OS?) 2 weeks...yes i have reinstalled twice

thx usasma your a lifesaver

usasma · 27 May 2012

Only 67 updates after SP1 - most systems have 75 of more. Please visit Windows Update and get all available updates

It's looking like a hardware problem to me. Start with these free diagnostics: Initial Hardware Diagnostics (I suspect RAM - so ensure that you run the MemTest86+ according to the instructions).

First memory dump shows a significant overclock - but the rest show that you've reset the system to default values. Please remain at default values until we've finished troubleshooting and the system is stabilized again.

Everything seems to point at memory. If the memory diagnostics don't reveal anything, then try Prime95 according to the instructions at this link: Additional 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:


iaStor.sys       Tue Nov 29 22:39:19 2011 (4ED5A567)
mvs91xx.sys      Mon Aug 08 23:05:23 2011 (4E40A3F3)
mvxxmm.sys       Mon Aug 08 23:05:06 2011 (4E40A3E2)
amdxata.sys      Fri Mar 19 12:18:18 2010 (4BA3A3CA)
iusb3hcs.sys     Thu Jan 05 06:56:40 2012 (4F058FF8)
L1C62x64.sys     Wed Aug 03 02:21:09 2011 (4E38E8D5)
HECIx64.sys      Wed Nov 09 19:52:25 2011 (4EBB2049)
xhcdrv.sys       Mon Nov 14 06:01:09 2011 (4EC0F4F5)
AppleCharger.sys Tue Nov 01 22:46:00 2011 (4EB0AEE8)
atikmpag.sys     Thu Apr 05 21:10:44 2012 (4F7E4294)
cpuz135_x64.sys  Fri Mar 09 03:56:55 2012 (4F59C5D7)
iusb3xhc.sys     Thu Jan 05 06:54:45 2012 (4F058F85)
atikmdag.sys     Thu Apr 05 21:48:25 2012 (4F7E4B69)
iusb3hub.sys     Thu Jan 05 06:54:43 2012 (4F058F83)
AtihdW76.sys     Thu Feb 23 07:30:12 2012 (4F463154)
viahduaa.sys     Tue Jan 10 06:33:14 2012 (4F0C21FA)
ViaHub3.sys      Mon Nov 14 06:01:20 2011 (4EC0F500)
TRIXX.sys        Wed Oct 06 12:14:37 2010 (4CACA06D)

Code:


Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052712-11200-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat May 26 13:01:33.131 2012 (UTC - 4:00)
System Uptime: 0 days 7:45:26.974
Probably caused by : memory_corruption ( nt!MiReplenishPageSlist+c0 )
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xA
PROCESS_NAME:  Diablo III.exe
FAILURE_BUCKET_ID:  X64_0xA_nt!MiReplenishPageSlist+c0
Bugcheck code 0000000A
Arguments 00000000`00000010 00000000`00000002 00000000`00000001 fffff800`02ca6850
BiosVersion = F8
BiosReleaseDate = 05/11/2012
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052612-17238-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat May 26 05:15:40.461 2012 (UTC - 4:00)
System Uptime: 0 days 1:47:38.304
Probably caused by : ntkrnlmp.exe ( nt! ?? ::FNODOBFM::`string'+355e4 )
BUGCHECK_STR:  0x1a_41790
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  Origin.exe
FAILURE_BUCKET_ID:  X64_0x1a_41790_nt!_??_::FNODOBFM::_string_+355e4
Bugcheck code 0000001A
Arguments 00000000`00041790 fffffa80`010d2770 00000000`0000ffff 00000000`00000000
BiosVersion = F8
BiosReleaseDate = 05/11/2012
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052612-12589-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Sat May 26 03:27:35.183 2012 (UTC - 4:00)
System Uptime: 0 days 3:51:18.401
Probably caused by : memory_corruption ( nt!MiRelinkStandbyPage+c6 )
BUGCHECK_STR:  0x1a_8884
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  svchost.exe
FAILURE_BUCKET_ID:  X64_0x1a_8884_nt!MiRelinkStandbyPage+c6
Bugcheck code 0000001A
Arguments 00000000`00008884 fffffa80`04c985d0 fffffa80`034bd7a0 00000000`00000400
BiosVersion = F8
BiosReleaseDate = 05/11/2012
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052512-21278-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Thu May 24 13:54:41.218 2012 (UTC - 4:00)
System Uptime: 1 days 0:09:08.435
*** WARNING: Unable to verify timestamp for win32k.sys
*** ERROR: Module load completed but symbols could not be loaded for win32k.sys
Probably caused by : hardware_ram ( ZEROED_PAGE_CORRUPTED )
BUGCHECK_STR:  0x1a_8887
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  rundll32.exe
FAILURE_BUCKET_ID:  X64_0x1a_8887_ZEROED_PAGE_CORRUPTED
Bugcheck code 0000001A
Arguments 00000000`00008887 fffffa80`04738e00 fffffa80`04d885d0 00000000`00000205
BiosVersion = F8
BiosReleaseDate = 05/11/2012
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052412-18298-01.dmp]
Built by: 7601.17803.amd64fre.win7sp1_gdr.120330-1504
Debug session time: Wed May 23 13:44:38.609 2012 (UTC - 4:00)
System Uptime: 0 days 7:57:02.827
Probably caused by : memory_corruption ( nt!MiUnlinkPageFromLockedList+19c )
BUGCHECK_STR:  0x1a_8886
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
PROCESS_NAME:  mscorsvw.exe
FAILURE_BUCKET_ID:  X64_0x1a_8886_nt!MiUnlinkPageFromLockedList+19c
Bugcheck code 0000001A
Arguments 00000000`00008886 fffffa80`04c985d0 fffffa80`01e4e600 00000000`00000501
BiosVersion = F8
BiosReleaseDate = 05/11/2012
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3403
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\FUBAR\_jcgriff2_\dbug\__Kernel__\052212-19203-01.dmp]
Built by: 7601.17514.amd64fre.win7sp1_rtm.101119-1850
Debug session time: Mon May 21 14:39:58.007 2012 (UTC - 4:00)
System Uptime: 0 days 0:00:25.194
BugCheck F4, {3, fffffa800b6ebb30, fffffa800b6ebe10, fffff80002deadb0}
Probably caused by : wininit.exe
PROCESS_NAME:  wininit.exe
DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT
BUGCHECK_STR:  0xF4
FAILURE_BUCKET_ID:  X64_0xF4_IMAGE_wininit.exe
Bugcheck code 000000F4
Arguments 00000000`00000003 fffffa80`0b6ebb30 fffffa80`0b6ebe10 fffff800`02deadb0
BiosVersion = F6
BiosReleaseDate = 03/23/2012
CPUID:        "Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz"
MaxSpeed:     3400
CurrentSpeed: 3513
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

yrag · 28 May 2012

hi usasma...

i did the memtest according to the instructions provided by you...

after the first pass for round i found almost 100 errors... i stopped in imediatly... i fear continuing will damage the RAM....

should i continue trouble shooting following your instructions...

i guess now we can conclude its a RAM problem... but how to we further confirm if its the RAM stick problem or motherboard ram slot problem...

please advise should i continue doing the full spectrum of the memtest or just RMA the RAM sticks now

usasma · 29 May 2012

The test won't damage your RAM. BUT, the test indicates that the RAM is already damaged.
Go to step 6 or 7 (I can't recall which) in this diagnostic procedure: Memory Diagnostics
That's where you start to figure out which stick/slot is at fault.

If the RAM manufacturer will accept an RMA now, do that instead. It'll be quicker (and easier) to just return them all for a new, matching set of sticks.