Starcraft 2 BSOD reboot error

Code:

BugCheck A, {fffff0800ad189c0, 2, 0, fffff80002a98ef2}

Probably caused by : memory_corruption

Code:

Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

memory_corruption doesn't necessary mean that a RAM module is faulty, it can also point to a object which corrupted the RAM at the time of the crash, for instance a corrupted driver or program. Paging files and the CPU caches can also be causes.

Follow these steps -

Test for any corrupted drivers, by running Driver Verifier for least 24 hours, stop the test if a BSOD occurs before this time frame. Driver Verifier will place stress on the drivers within your system, which will cause corrupted drivers to crash and hopefully be pinpointed.

• Driver Verifier - Enable and Disable

Memory:

• RAM - Test with Memtest86+

Run Memtest86+ for least 7-8 passes, and preferrly overnight as it can take a while to fully complete.

Test each RAM stick individually, if an error is found then move the same RAM stick into the next DIMM slot and test again, if errors are found for the same RAM stick in every available slot then you have a faulty RAM module. On the other hand, if no errors are found in the next slot or the other slots for the same RAM module, then you have a faulty DIMM slot.

Test each RAM stick and every motherboard DIMM slot available.

Remove the graphics card too, just to make sure the Video RAM of the card is not causing any problems; only follow this step if your motherboard has a onboard graphics chip or you have an alternative card.

Code:

BugCheck A, {fffff0800ad189c0, 2, 0, fffff80002a98ef2}

Probably caused by : memory_corruption

Code:

Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

The latest .dmp file I could find was dated to yesterday, and is the same crash as listed above.

Have you completed the memory test with MemTest86+?

Have you looked for BIOS updates for your motherboard?

Code:

American Megatrends Inc. 1610, 7/14/2009

X BlueRobot,

I haven't been able to run Memtest yet because I am working 12 hour night shifts right now and have been dreading it horribly. A few months back I seem to remember Memtest as being the worst part of the trouble shooting requiring a boot disk, a computer disassemble and a solid night per stick of ram. I am almost considering buying a few newer sticks of ram and seeing if they solve the problem then just taking them back before dealing with Memtest again lol

I will work on updating my motherboard drivers and bios tomorrow and let you know if I can crash it. If I can I will devote my entire weekend to Memtest.

Also will driver verifier document something new in Grab All or does it make a separate log somewhere I need to attach?

Thanks,
Kyle

It was create a another .dmp file, if it does find any corrupted or misbehaving drivers.

Code:

BugCheck A, {fffff0800ad189c0, 2, 0, fffff80002a98ef2}

Probably caused by : memory_corruption

Code:

Usual causes:  Kernel mode driver, System Service, BIOS, Windows, Virus scanner, Backup tool, compatibility

The latest crash (listed above) was dated as 3rd December, is this the latest dump saved?

Has Driver Verifier found anything yet?

Test the CPU and Power Supply with OCCT:

• NVIDIA/AMD Video Card - Test with OCCT

Here's the Grab All from the previous post. Happened at approximately about 1530 hours on 12/08/12.