[BSOD] Bug Check Code 0x00000116 (and 0x1000007e)

Hi I have for a few weeks now been getting some BSOD, at random events.

Now I get it very often last night when scouering the internet for clues about that could be wrong I had several possibly over 15 (windows didn't manage to minidump att BSODs)

Windows blames dxgkrnl.sys and at several times have the nvidia drivers "failed" and been restored.

BSODs occur when at complete random intervalls, when starting up windows or playing games.

Sometimes my screens goes black and gets "no signal found" and then it reboots (bsod windows reports when i get back from the reboot).
Other times as soon as it should switch from windows loading screen to windows welcome screen the monitor is just black and I hear the sounds of skype etc starting up. (There is never any problem showing the motherboard startup screen or the black windows loading screen)

When I have my dual monitor setup I don't even get a propper bluescreen only blue or browning colors. When I only use my TV I get a real bluescreen(if the screen doesn't go black first ofc).

I am also very confident that it's not a cooling issue and in some threads regarding similar issues some suggested memory issues so I ran memtest for 8+ hours when I was away and no errors had been found when I got back.

No hardware on my computer is overclocked.

Code:

Windows 7 Ultimate 64bit
Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz 
12GB RAM
GeForce 580 GTX
INTEL SS DSA2M080G2GC SCSI Disk Device + ST310003 40AS SCSI

A complete everest home edition report saved as .html is included in the .zip file.


I usually manages to fix my own mess but this time I hit a wall.
I'd appriciate any help hopefully my gfx isn't broken.

//Soda

Sodien said:

Hi I have for a few weeks now been getting some BSOD, at random events.

Now I get it very often last night when scouering the internet for clues about that could be wrong I had several possibly over 15 (windows didn't manage to minidump att BSODs)

Windows blames dxgkrnl.sys and at several times have the nvidia drivers "failed" and been restored.

BSODs occur when at complete random intervalls, when starting up windows or playing games.

Sometimes my screens goes black and gets "no signal found" and then it reboots (bsod windows reports when i get back from the reboot).
Other times as soon as it should switch from windows loading screen to windows welcome screen the monitor is just black and I hear the sounds of skype etc starting up. (There is never any problem showing the motherboard startup screen or the black windows loading screen)

When I have my dual monitor setup I don't even get a propper bluescreen only blue or browning colors. When I only use my TV I get a real bluescreen(if the screen doesn't go black first ofc).

I am also very confident that it's not a cooling issue and in some threads regarding similar issues some suggested memory issues so I ran memtest for 8+ hours when I was away and no errors had been found when I got back.

No hardware on my computer is overclocked.

Code:

Windows 7 Ultimate 64bit
Intel(R) Core(TM) i7 CPU 950 @ 3.07GHz 
12GB RAM
GeForce 580 GTX
INTEL SS DSA2M080G2GC SCSI Disk Device + ST310003 40AS SCSI

A complete everest home edition report saved as .html is included in the .zip file.


I usually manages to fix my own mess but this time I hit a wall.
I'd appriciate any help hopefully my gfx isn't broken.

//Soda

"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 STOP 0x116: VIDEO_TDR_ERROR troubleshooting