Solved BSOD when I'm away from my pc for more than 4 hours-dxgkrnl.sys driver

[psychotron]

041412-23228-01.dmp 4/14/2012 1:16:27 PM 0x00000116 fffffa80`10b414e0 fffff880`01007ae4 00000000`00000000 00000000`0000000d dxgkrnl.sys dxgkrnl.sys+5d000 x64 ntoskrnl.exe+7cc80 C:\Windows\Minidump\041412-23228-01.dmp 6 15 7601 306,376

Problem signature:
Problem Event Name: BlueScreen
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 1033

Additional information about the problem:
BCCode: 116
BCP1: FFFFFA8010B414E0
BCP2: FFFFF88001007AE4
BCP3: 0000000000000000
BCP4: 000000000000000D
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1


I will attach BSOD Dump and File collection results only if I have to.

From reading on google it looks to be related to ATI driver and Direct X, but not sure. Happens ONLY when I'm away from my pc for more than 4 hours. Sometimes utorrent is running, sometimes not, BSOD has happened in both instances every night I go to sleep since this issue started. I'm trying to remember what I installed or updated about the time these BSOD started but I can only say I updated my ATI driver, regualr windows updates and a adobe flash update. No new installed programs or games I can think of. Happened when both Chrome and Firefox was installed as browser, I used Chrome but switched back to FF for privacy issues, so I know it's not browser related.

Revert to old ATI drivers?

 

[JMH]

Nice nebula starbreaker & welcome,

"BCCode: 116 is 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

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

 

[psychotron]

Well thank you, and thank you.

Nice nebula starbreaker & welcome,

"BCCode: 116 is 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

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

Sorry for late reply and thank yous.

I have something called Probe II installed, it came with my ASUS crosshair 4 formula mobo, a temp and voltage gauge program. I do remember the alarm going off a few times in the recent month or two but I remember the CPU, mobo, NB and SB being normal and one being a bit high like 54 Celcuis. I do try to clean inside box once a month but maybe I need to do a more thorough one. I will do that and run pc overnight for a week and see results. I will also check for liquid issues since I'm using a H50 cpu cooler in conjunction with an 8 fan set-up. Second option will be reverting back to old ATI video drivers, I have Radeon HD 6950.

Will post back solution.

 

[JMH]

We await your report.
Good luck!

 

[psychotron]

Solved:Bad Video Card Driver Version

I had the latest ATI drivers for my XFX Radeon HD6950 2 GB video card, they were the 12.3 version of Catalyst suite. I reverted back two versions to 12.1 and now have no BSOD issues.

I have ran my pc 24/7 for the last week and it has not shut down on it's own, no BSOD and no errors. Being my pc shut down almost every other night since March I can assume my issue is solved. Why the 12.3, and possibly the 12.2 drivers cause BSOD on my pc I have no idea. I guess the newest isn't always the best.

OVER AND OUT.

 

[writhziden]

The 12.3 drivers have been causing issues on systems. I actually had some when I first installed it yesterday myself. A restart cleared my issues, but given the locking up I was experiencing, I am not too surprised to see they are causing problems on other people's systems. And you are correct, newest drivers are not always the best. That is why technical experts actually warn against doing driver updates as a routine maintenance task. When it comes to driver updates, if it ain't broke, don't fix it; if your current drivers are not causing problems, there is no reason to update them.