Computer crash (kinda) after playing certain games

[Commando5551]

My computer has just recently started crashing while playing certain games. But it isn't a normal crash, instead my computer fans start running at full blast, my screens go black, and the audio sort of repeats a little.

I just have to hold the power button down for it to turn off. I've tried everything I can think of changing. I reset my overclocks, I reset the whole motherboard to defaults, I've turned all my settings down on the Nvidia control panel program, and I've disabled one of my monitors. The games that cause the crash are Battlefield 3, Dota 2 Beta, Magic: The Gathering - Duals of the Planeswalkers 2012 and Trapped Dead.

I was able the play Battlefield 3, with full settings, and Dota 2 perfectly fine a few weeks ago, no crashes or anything. But when I got Trapped Dead, it started crashing, and then I got Magic, and that crashed as well. Then Dota 2 and Battlefield 3 are causing the same crashes just this past day or two. The strange thing is that, if I make Magic not fullscreen, it stops the crashing. That's why I thought it might have been something with my dual monitor setup, but disabling a monitor didn't help. With Magic on fullscreen, the crash happens anytime after about 5 minutes of the game running, and Dota 2 has it happen about every 20 minutes.

All today I was testing the different changes that I mentioned, and only once did my computer come up with an error message after reboot. It said that there was a problem and there was an option to search for solutions, which did nothing, as well as a more info button that had this:

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: FFFFFA80074B54E0
BCP2: FFFFF8800FF74AA4
BCP3: FFFFFFFFC000009A
BCP4: 0000000000000004
OS Version: 6_1_7601
Service Pack: 1_0
Product: 768_1

Files that help describe the problem:
C:\Windows\Minidump\041912-21231-01.dmp
C:\Users\Sean\AppData\Local\Temp\WER-89747-0.sysdata.xml

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

I'm not seeing a BSOD, so I'm not sure if the BlueScreen name is correct or not. I'm sure the information I need is in that somewhere, or somewhere else on my computer, but I don't know how to read it or where to look.

Thanks for any help.

Edit: My system specs are up to date, if you need them.

 

[zigzag3143]

We do need the DMPs to be sure why

"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

 

[Commando5551]

OK, I've attached the .dmp in a .zip folder. I've also been trying other things, and it looks like just turning off the AA in Magic solves the problem as well. So it may just be a driver problem?

 

[zigzag3143]

OK, I've attached the .dmp in a .zip folder. I've also been trying other things, and it looks like just turning off the AA in Magic solves the problem as well. So it may just be a driver problem?

It is a true 116. please follow the directions.