BSOD 0x00000116

BASF8 · 06 Sep 2014

Hi, i bought a new vga and i keep getting BSODs (it happened with old vga as well, but not as much). Maybe someone can check the files and give me a hand.

This is happening mostly in games: screen goes black, loud sound on speakers, and sometimes the coolers on the vga stuck on full speed. I have to manualy reset and sometimes the fans on the case, leds and discs are on, but the cpu cooler and vga are off.

Thanks.

Arc · 08 Sep 2014

Hi BASF8.

Stop 0x116 is a display/graphics related BSOD.

Are you overclocking?
As you are getting BSODs, you should stop overclocking and run all the hardware components like CPU, GPU and RAM to their default settings.

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. Alternatively, you can publish a Speccy snapshot too: Speccy - Publish Snapshot of your System Specs .

Check if the Power Supply Unit (PSU) supplying adequate power to the computer or not.
eXtreme Power Supply Calculator
Also let us know the wattage of the PSU.

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

Let us know the results.

Code:

....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 116, {fffffa80093dd010, fffff8800fa687a0, 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+9a57a0 )

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: fffffa80093dd010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800fa687a0, 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+9a57a0
fffff880`0fa687a0 48ff25f94eedff  jmp     qword ptr [nvlddmkm+0x87a6a0 (fffff880`0f93d6a0)]

DEFAULT_BUCKET_ID:  GRAPHICS_DRIVER_TDR_FAULT

CUSTOMER_CRASH_COUNT:  1

BUGCHECK_STR:  0x116

PROCESS_NAME:  System

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

STACK_TEXT:  
fffff880`025d7a48 fffff880`02c62134 : 00000000`00000116 fffffa80`093dd010 fffff880`0fa687a0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`025d7a50 fffff880`02c35867 : fffff880`0fa687a0 fffffa80`08003000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`025d7a90 fffff880`02c61f43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`093dd010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`025d7b40 fffff880`02d3203d : fffffa80`08be4c70 00000000`00000080 00000000`00000000 fffffa80`08002410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`025d7bc0 fffff800`0356973a : 00000000`0158b88d fffffa80`07dffa00 fffffa80`0668d6f0 fffffa80`07dffa00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`025d7c00 fffff800`032be8e6 : fffff880`03174180 fffffa80`07dffa00 fffff880`0317f0c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`025d7c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+9a57a0
fffff880`0fa687a0 48ff25f94eedff  jmp     qword ptr [nvlddmkm+0x87a6a0 (fffff880`0f93d6a0)]

SYMBOL_NAME:  nvlddmkm+9a57a0

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  53b4446a

FAILURE_BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

BUCKET_ID:  X64_0x116_IMAGE_nvlddmkm.sys

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x116_image_nvlddmkm.sys

FAILURE_ID_HASH:  {1f9e0448-3238-5868-3678-c8e526bb1edc}

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

7: kd> lmvm nvlddmkm
start             end                 module name
fffff880`0f0c3000 fffff880`0fd51000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Wed Jul 02 23:12:02 2014 (53B4446A)
    CheckSum:         00C4C7C9
    ImageSize:        00C8E000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4