BSOD when idle for a long period of time.

[paulrawr]

Hi there, I normally leave my computer on overnight so I could do things such as defragging, virus scans and sometimes downloading.

I'm running Windows 7 Ultimate x64, which I installed 3 days ago as I got a new hard drive. The system was blue screening since then, so I'm guessing it's not a faulty hard drive, OS or memory (Replaced memory and done 20 hours of memtest86+)

I bought this machine about 7 months ago, but since then I have replaced the motherboard, memory, graphics card, CPU cooler and hard drive.

It only seems to bluescreen when idle, like when all it's doing is downloading on uTorrent or has finished doing a defrag.

According to bluescreenview, it has been caused by dxgkrnl.sys, atikmpag.sys and dxgmms1.sys . It was these causing it before the reinstall as well.

 

[zigzag3143]

"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

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

 

[paulrawr]

"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

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

I've just done a couple 15 minute stress tests and the highest the GPU goes is 77. My intake fan at the front on my machine goes nearly directly onto the GPU area, so the temperature of it should be fine. There is no dust in the PC near enough as before I did the reinstall of windows, I cleaned the computer out.

Is there any chance it could be the new video driver?

 

[zigzag3143]

"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

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

I've just done a couple 15 minute stress tests and the highest the GPU goes is 77. My intake fan at the front on my machine goes nearly directly onto the GPU area, so the temperature of it should be fine. There is no dust in the PC near enough as before I did the reinstall of windows, I cleaned the computer out.

Is there any chance it could be the new video driver?

It is easy enough to test. Either re-install the newest or if that is problematic roll back to a prior version.

 

[paulrawr]

Left it running for about 7 hours last night and no BSOD, might of been driver! Leaving it while I go College and seeing if it's BSOD when I've came back.