Computer freezing 0x00000116

Hamiro · 28 May 2015

Computer freezes when I start playing League of Legends then crashes then turns back on and it also happen when I was browsing on the web.

Arc · 02 Jun 2015

Hi Hamiro.

A stop 0x116 is a display/graphics related issue.

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. Also set the BIOS to default, too.
How To Clear CMOS (Reset BIOS)

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 .

Uninstall the installed display driver using Display Driver Uninstaller. Then install and older stable version, say 350.12 WHWL. NVIDIA DRIVERS GeForce Game Ready Driver for Grand Theft Auto V WHQL

When the new driver is installed, 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.
_______________________________________________________________

Code:

BugCheck 116, {fffffa800a394170, fffff8800506081c, 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+82981c )

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: fffffa800a394170, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800506081c, 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+82981c
fffff880`0506081c 48ff25ed22ecff  jmp     qword ptr [nvlddmkm+0x6ebb10 (fffff880`04f22b10)]

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.17336 (debuggers(dbg).150226-1500) amd64fre

STACK_TEXT:  
fffff880`065d1a48 fffff880`0534f134 : 00000000`00000116 fffffa80`0a394170 fffff880`0506081c ffffffff`c000009a : nt!KeBugCheckEx
fffff880`065d1a50 fffff880`05322867 : fffff880`0506081c fffffa80`09989000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`065d1a90 fffff880`0534ef43 : fffffa80`ffffd846 ffffffff`fffe7960 fffffa80`0a394170 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`065d1b40 fffff880`02cca03d : fffffa80`0ae2b560 00000000`00000080 00000000`00000000 fffffa80`09938010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`065d1bc0 fffff800`04320456 : 00000000`02fcb676 fffffa80`099ab060 fffffa80`06995b10 fffffa80`099ab060 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`065d1c00 fffff800`040782c6 : fffff800`04205e80 fffffa80`099ab060 fffff800`04213cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`065d1c40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16


STACK_COMMAND:  .bugcheck ; kb

FOLLOWUP_IP: 
nvlddmkm+82981c
fffff880`0506081c 48ff25ed22ecff  jmp     qword ptr [nvlddmkm+0x6ebb10 (fffff880`04f22b10)]

SYMBOL_NAME:  nvlddmkm+82981c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  55515e64

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`04837000 fffff880`052f2000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
    Image name: nvlddmkm.sys
    Timestamp:        Tue May 12 07:29:00 2015 (55515E64)
    CheckSum:         00A86612
    ImageSize:        00ABB000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4

Hamiro · 05 Jun 2015

My computer crashed again after removing old drivers and installing the 350.12 WHQL, it was the same stop code 0x116. I went ahead and ran the Furmark stress test after and the gpu temperature hit 95 degrees C but no artifacts appeared and the computer did not crash. This is an alienware x51 and the case is very small, not sure if these temperatures are normal for this case but they seem pretty high. Should I try going for even older drivers or is this most likely the video card itself. http://speccy.piriform.com/results/a...NcwNNFfZuYcEpu

Arc · 05 Jun 2015

Open the computer. Clean the inside carefully. Clean all the air vents and fan grills so that the computer can blow the hot air out efficiently. Before re-seating things, apply new thermal paste.

See how it goes. Let us know.