Blue screen bluescreen 1055 bccode 116

Umbra18 · 14 Mar 2015

Hello there people. I have been getting this error for a few days now and its starting to get annoying. Ive looked around the internet for any answers but couldnt find any help there. Ive attached SF diagnostic tool results can someone please help me with that?

Arc · 15 Mar 2015

A stop 0x116 is a display failure, which may be caused due to a number of reasons on an old branded desktop PC.

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 - The only power supply calculator trusted by PSU manufacturers and computer enthusiasts

Also let us know the wattage of the installed PSU.

Stress test the Graphics Card using Furmark.

Video Card - Stress Test with Furmark

Take a screenshot of the furmark window before closing it. Upload the screenshot for us. Also let us know if you have experienced any crash/BSOD and/or artifacts during the test.

Let us know the results.
________________________________________

Code:

BugCheck 116, {fffffa800dfe4010, fffff8800886cf38, 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+7a3f38 )

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: fffffa800dfe4010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800886cf38, 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+7a3f38
fffff880`0886cf38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`08746230)]

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.17237 (debuggers(dbg).140716-0327) amd64fre

STACK_TEXT:  
fffff880`02eefa48 fffff880`08b38134 : 00000000`00000116 fffffa80`0dfe4010 fffff880`0886cf38 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02eefa50 fffff880`08b0b867 : fffff880`0886cf38 fffffa80`0acfb000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02eefa90 fffff880`08b37f43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`0dfe4010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02eefb40 fffff880`0803803d : fffffa80`07126010 00000000`00000080 00000000`00000000 fffffa80`0aba6410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02eefbc0 fffff800`0331173a : 00000000`0263bbbc fffffa80`0a96ba00 fffffa80`0698f9e0 fffffa80`0a96ba00 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02eefc00 fffff800`030668e6 : fffff880`03089180 fffffa80`0a96ba00 fffff880`030940c0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02eefc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+7a3f38
fffff880`0886cf38 48ff25f192edff  jmp     qword ptr [nvlddmkm+0x67d230 (fffff880`08746230)]

SYMBOL_NAME:  nvlddmkm+7a3f38

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  54d3b001

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`080c9000 fffff880`08adb000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Thu Feb 05 23:31:37 2015 (54D3B001)
    CheckSum:         009D4DDE
    ImageSize:        00A12000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4