Help with minidump debugging (BSOD)

[Habitats]

Hello

I've been getting a bunch of BSOD's (under high system load, games/benchmark/booting etc), probably due to GPU's not getting sufficient power as a result of a plausible faulty PSU. I've not been able to debug these dump files myself, because the debugging tools refuses to install on my system (completely different story here).

Either way, I've attached 3 dump files that should probably yield the same result. I'd be forever thankful if some of you could extract some useful information from either.

Since my display shuts off every BSOD I've been unable to take a picture of the actual BSOD, however, I received this error when I got back in Windows:

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 1044

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA800B0D0350
BCP2: FFFFF88003DB18F0
BCP3: 0000000000000000
BCP4: 0000000000000002
OS Version: 6_1_7601
Service Pack: 1_0
Product: 256_1

Thanks in advance.

 

[JMH]

Hello Habitats,

I note your Asacpi.sys is 2005.

The pre 2009 version of this driver is a known BSOD cause.

Please visit this link: Asus tek computer inc. -support- drivers and download p7p55d le

ASUSTeK Computer Inc. -Support- Drivers and Download P7P55D LE
ASUSTeK Computer Inc. - Motherboards- ASUS P5K-VM

Scroll down to the utilities category, then scroll down to the "atk0110 driver for windowsxp/vista/windows 7 32&64-bit" (it's about the 12th item down).

Download and install it.

Go to c:\windows\system32\drivers to check and make sure that the asacpi.sys file is date stamped from 2009 or 2010 (notbefore).

FYI...
Your problem / crash was caused by Stop 0x116.
Please read through the following carefully.

"It's not a true crash, in the sense that the bluescreen was initiated only because the combination of video driver and video hardware was being unresponsive, and not because of any synchronous processing exception".

Since Vista, the "Timeout Detection and Recovery" (TDR) components of the OS video subsystem have been capable of doing some truly impressive things to try to recover from issues which would have caused earlier OSs like XP to crash.

As a last resort, the TDR subsystem sends the video driver a "please restart yourself now!" command and waits a few seconds.

If there's no response, the OS concludes that the video driver/hardware combo has truly collapsed in a heap, and it fires off that stop 0x116 BSOD.

If playing with video driver versions hasn't helped, make sure the box is not overheating.

Try removing a side panel and aiming a big mains fan straight at the motherboard and GPU.

Run it like that for a few hours or days - long enough to ascertain whether cooler temperatures make a difference.

If so, it might be as simple as dust buildup and subsequently inadequate cooling.

I would download cpu-z and gpu-z (both free) and keep an eye on the video temps Let us know if you need help

http://www.sevenforums.com/crash-lo...op-0x116-video_tdr_error-troubleshooting.html

 

[Habitats]

Thank you very much for taking the time to go over it.

When I woke up this morning my computer had BSOD'd again, and so I tried to shut it back on. Then out of nowhere the GPU sparked and I could see smoke coming out of my case.

Now my motherboard and GPU is useless, however, the CPU/RAM seems to have gotten away without a scratch.

Bottom line. Whatever it was causing this error, it is probably related to this. My guess is the motherboard.

 

[JMH]

Habitats,
Ouch!
:shock: