BSOD over past few days at random times

indo · 13 May 2010

Hello,

This is a newish computer (Built in July 2009) and up until a few days ago I haven't had any issues with it. For whatever reason though, while I was playing the Starcraft 2 beta, it crashed to BSOD and had to restart. The event viewer was largely unhelpful in figuring out the problem, so I went ahead and ran a few utilities to make sure my computer is running as well as I think it could be (CCleaner, Spybot, etc., just to get rid of junk). All seemed fine until last night when I went to shut down my computer and it blue screened again, with once again an unhelpful event file entry.

I only have the minidump from last night's crash (when I shut down my system), as when I ran the utilities to clean up my comp the minidump from the first crash was deleted. Hopefully someone can help me out with this... Your time is much appreciated.

My potentially relevant system information:
Motherboard: ASUS Crosshair III Formula AM3 AMD 790FX ATX AMD Motherboard
CPU: AMD Phenom II X4 945 Deneb 3.0GHz
RAM: mushkin 4GB (2 x 2GB) 240-Pin DDR3 SDRAM DDR3 1600 (PC3 12800) // 7-7-6-18, 1T @ 1.85v
Power Supply: CORSAIR CMPSU-750TX 750W
Hard Drive: Western Digital Caviar Black WD6401AALS 640GB w/ 32MB cache
Graphics Card: EVGA 896-P3-1170-AR GeForce GTX 275
Sound Card: Auzentech X-Fi Forte

Here is the WhoCrashed log for last night's 'Computer Shutdown' BSOD:

Code:

On Wed 5/12/2010 3:31:46  AM your computer crashed
This was likely caused by the following module:  ntoskrnl.exe
Bugcheck code: 0x1000007E  (0xFFFFFFFFC0000005, 0xFFFFF80002AED38D, 0xFFFFF880031C40E8,  0xFFFFF880031C3950)
Error: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M
Dump file:  C:\Windows\Minidump\051210-21372-01.dmp
file path: C:\Windows\system32\ntoskrnl.exe
product:  Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel &  System
The crash took place in a standard Microsoft module. Your system  configuration may be incorrect, possibly the culprit is in another driver on  your system which cannot be identified at this time.

Thanks!
indo

usasma · 13 May 2010

This is the second Starcraft2 issue I've seen today - I wonder if there's an issue with the beta? I'd check their forums to see if it's the problem.

BUT there is a driver on your system that's known to cause BSOD's - so I'd suggest that you replace the ASACPI.SYS driver (dated from 2005) with the most recent one available for your system from the Asus website ( ASUSTeK Computer Inc.-Support- download_item_mkt ). It'll be listed under the Utilities section and is known as the "ATK0110 driver for WindowsXP/Vista/Win7 32&64-bit" .

The memory dump points to a memory corruption as the issue - so I'd try this free memory test just to rule that out: Memory Diagnostics (read the details at the link).

More info on the STOP 0x7E error here: BSOD Index (Please note the "Usual causes" listed at the top of that section).

Beyond that, I'd wait and see if there were further BSOD's. If so, post the memory dump files and we'll move on from there.

Summary of the BSOD:

Code:

Built by: 7600.16539.amd64fre.win7_gdr.100226-1909
Debug session time: Wed May 12 23:30:41.009 2010 (GMT-4)
System Uptime: 1 days 12:41:50.336
BugCheck 1000007E, {ffffffffc0000005, fffff80002aed38d, fffff880031c40e8, fffff880031c3950}
Probably caused by : memory_corruption ( nt!MiGetNextNode+31 )
PROCESS_NAME:  explorer.exe
BUGCHECK_STR:  0x7E

indo · 13 May 2010

Thank you for looking into my problem, I really appreciate it.

From my various searches on the SC2 beta forums I haven't found anything relating to a problem like mine. Since the first BSOD I had came while I was playing SC2, I thought it was something to do with the beta but I've played several games since and haven't had any issues. I figured it was something other than the game when I was BSODing on computer shutdown, during a session I didn't even run SC2 on.

I updated the driver you suggested, and now I'm going to run memtest. I'll update this thread later today with what I find.

Thanks so much!

indo · 13 May 2010

Nearly 3 completed memtest passes and no errors yet. Lets hope it stays that way while I run it for a few more hours.

indo · 13 May 2010

Alright, after 7 passes of memtest86+, I think it's safe to say that there's a very very small chance that my RAM is the problem. If I crash again I'll upload the dumps and we'll go from there. Thanks again!