BSOD / Driver failure in video games 0x000000C4

Go through this

is it bad to run multiple antivirus programs?
The Assumptions You Make About Your Slow PC (and Why They're Probably Wrong)

STOP 0x116: VIDEO_TDR_ERROR troubleshooting

I'll look into both when I get time next, as of posting this; the problem happened twice within 5 minutes of each other. It didn't BSOD, but artifacted then refreshed and I was able to continue the game.

if it bsod upload the new dumps

here is a new BSOD log, just occured.

Before this one I adjusted my video TDDR timeout, got the problem within 5 minutes.

Then I updated to NVIDIA's most recent driver just got WHQL this week, happened again in about 5 minutes, but it did BSOD.

I'm going to put MSI afterburner on to monitor GPU temperature while I play. I also looked into my power supply, ASUS's wattage calculator suggest minimum of 700 watts and I am using 750 watt supply (700 sounds high to me, but maybe I'm getting out of touch).

have you over clocked your GPU?

Code:

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8009b1f010, fffff88005238b10, ffffffffc000009a, 4}

Unable to load image \SystemRoot\system32\DRIVERS\nvlddmkm.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for nvlddmkm.sys
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+993b10 )

Followup: MachineOwner
---------

2: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8009b1f010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88005238b10, The pointer into responsible device driver module (e.g. owner tag).
Arg3: ffffffffc000009a, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000004, Optional internal context dependent data.

Debugging Details:
------------------


FAULTING_IP: 
nvlddmkm+993b10
fffff880`05238b10 4055            push    rbp

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

STACK_TEXT:  
fffff880`0336ea48 fffff880`02d36000 : 00000000`00000116 fffffa80`09b1f010 fffff880`05238b10 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`0336ea50 fffff880`02d09867 : fffff880`05238b10 fffffa80`08a1e000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0336ea90 fffff880`02d35e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`09b1f010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`0336eb40 fffff880`02c37ec1 : fffffa80`095279a0 00000000`00000080 00000000`00000000 fffffa80`08989410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`0336ebc0 fffff800`03123e5a : 00000000`02057714 fffffa80`08a31060 fffffa80`066d4040 fffffa80`08a31060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`0336ec00 fffff800`02e7dd26 : fffff800`02fffe80 fffffa80`08a31060 fffff800`0300dcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`0336ec40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+993b10
fffff880`05238b10 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+993b10

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  50b97852

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

Followup: MachineOwner
---------

I have not over-clocked it myself, I think it may have a small 'factory over-clock' on it but I doubt that would be the problem.

Temperatures never got above 57C, even when the problem occured, so I don't think it is heat.

I did have a slight issue with the new 310.70 drivers, so I am going to reinstall them. While I am at it, I am going to reinstall the two programs that cause this, because after some testing, I cannot get it to happen in other games.

I originally ignored the posibility of it being game related because it included artifacting, not just graphical glitches.

-card I am using; MSI USA ? Graphics Card - N560GTX-Ti Twin Frozr II

new BSOD happened.

this one happened seconds after loading a game. the artifacting happened twice while loading, which is new because previously it happened only "in-game".

problem is that the .dmp is almost 500MB in size, so i cannot upload it and all my viewer will tell me about it is that it is 0x00000116

here you go

Bug Check 0x116: VIDEO_TDR_ERROR (Windows Debuggers)

well I thought the pci slot switch fixed this issue, but it has happened again. I will do a driver reinstall again, but I get the feeling the graphics card or motherboard is at fault. I don't want to do another RMA as MSI support is horrible, and the graphics card already got RMA'd a few moths ago.