Random crashes playing any games or graphic intense operations

beoroahstan · 06 Jun 2013

I am running a quad sli setup, and for the past 6 months I have had no issues. No when playing games like Wow or crysis, I get random crashes. I'm trying to figure out if it is a hard ware issue or a heat issue.

I do not overclock anything, and I recently reduced my sli from quad to triple to try to reduce heat by opening more flows in my custom case. The errors in the who crashed did go from : NVIDIA Corporation SYSTEM_THREAD_EXCEPTION_NOT_HANDLED_M in a quad config to a NVIDIA Corporation VIDEO_TDR_ERROR in a triple sli config. I did update all drivers and bios, but I'm still getting these random crashes with dumps.

Arc · 06 Jun 2013

A stop 0x116 is a display/graphics related error, and a big lot of a computer's hardware/software environment is responsible for it.

Stress test the Graphics Card using Furmark.
Video Card - Stress Test with Furmark

Test your RAM modules for possible errors.
How to Test and Diagnose RAM Issues with Memtest86+
Run memtest for at least 8 passes, preferably overnight.

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
At least 30% extra is safe.

Is the computer hot? Report us the heat of the computer after a couple of hours of your normal usage. Upload a screenshot of the summery tab of Speccy.

let us know the results.
_____________________________________________________________________________
BSOD ANALYSIS:

Code:

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

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa8015f624e0, fffff8800650aed0, ffffffffc000009a, 4}

*** 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+8e9ed0 )

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

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

VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8015f624e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800650aed0, 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+8e9ed0
fffff880`0650aed0 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`05727a48 fffff880`0675f054 : 00000000`00000116 fffffa80`15f624e0 fffff880`0650aed0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`05727a50 fffff880`06732867 : fffff880`0650aed0 fffffa80`14659000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`05727a90 fffff880`0675ee63 : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`15f624e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`05727b40 fffff880`0483803d : fffffa80`157b9710 00000000`00000080 00000000`00000000 fffffa80`14641410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`05727bc0 fffff800`03b74ede : 00000000`02a2f112 fffffa80`146a1060 fffffa80`0d017b30 fffffa80`146a1060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`05727c00 fffff800`038c7906 : fffff800`03a51e80 fffffa80`146a1060 fffff800`03a5fcc0 fffff8a0`00226bc0 : nt!PspSystemThreadStartup+0x5a
fffff880`05727c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+8e9ed0
fffff880`0650aed0 4055            push    rbp

SYMBOL_NAME:  nvlddmkm+8e9ed0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  518fe8f9

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`05c21000 fffff880`06702000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Mon May 13 00:39:45 2013 (518FE8F9)
    CheckSum:         00AB6DED
    ImageSize:        00AE1000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4