Unexpected BSOD's

So the past couple of nights I leave my PC on and get some sleep I've been waking up to Windows recovery notices.

If I could get assisstance in fixing this It would be appreciated. I've attached perfmon & minidump inside NT6 rar.

- x86 (32-bit) or x64 ? x64
- the original installed OS on the system? Y
- an OEM or full retail version? Full

- What is the age of system (hardware)? < 1 year
- What is the age of OS installation (have you re-installed the OS?) > 2 weeks

Thanks

"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

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

Uploaded a pic of my testing.

My dust insides are clean on my PC. Everything's wired correctly.

Please let me know next course of action if one is available!

FurMark is only one step in the link given. Proceed with the rest of the steps in STOP 0x116: VIDEO_TDR_ERROR troubleshooting

For FurMark, did you get any artifacts? Is 73 C where the temperature maxed out and stopped increasing?

No artifacts on Furmark, I'll troubleshoot through the rest of the log if the error happens again