Code:
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80042214e0, fffff88010116ae4, 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+c3bae4 )
Followup: MachineOwner
---------
3: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80042214e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff88010116ae4, 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+c3bae4
fffff880`10116ae4 4883ec28 sub rsp,28h
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`063dba48 fffff880`078b8000 : 00000000`00000116 fffffa80`042214e0 fffff880`10116ae4 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`063dba50 fffff880`0788b867 : fffff880`10116ae4 fffffa80`055bb000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`063dba90 fffff880`078b7e0f : fffffa80`ffffd84d ffffffff`fffe7960 fffffa80`042214e0 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`063dbb40 fffff880`07986ec1 : fffffa80`03ff66e0 00000000`00000080 00000000`00000000 fffffa80`055b7010 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`063dbbc0 fffff800`03535fee : 00000000`0270af5f fffffa80`055e98c0 fffffa80`03c5a9e0 fffffa80`055e98c0 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`063dbc00 fffff800`0328c5e6 : fffff800`03410e80 fffffa80`055e98c0 fffff800`0341ecc0 fffff880`01667cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`063dbc40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+c3bae4
fffff880`10116ae4 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+c3bae4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4e99233b
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
BSOD BugCheck: VIDEO_TDR_FAILURE (0x116)
This indicates that an attempt to reset the display driver and recover from a timeout has failed causing the system exception which created by blue screen for you. The default timeout value should be around 5 seconds.
Code:
CPUID: "Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz"
MaxSpeed: 3300
CurrentSpeed: 3310
You don't seem to be overclocking anything though, your cpu cycles in at around 3.30 Ghz which is where it should be. The driver it's pointing to here is at
nvlddmkm.sys, which is your nVidia graphics driver.
Make sure that you have the most updated nVidia drivers.
Overheating and powersupply issues could be possible causes for this particular stop error (0x116). This is a less common stop error to see, but most of the time i've seen it, it was due to overheating. I would check your internal core temps to make sure that they aren't too high. To check for heating problems on your GPU I would suggest a program called
CPU-Z which is available here:
http://www.cpuid.com/softwares/cpu-z.html
You can also do a
GPU Stress test here:
http://www.ozone3d.net/benchmarks/fur/
Check for any warnings in device manager under the display area, and also your event viewer.
If we don't find an issue here, I would suggest that you also try running System File Checker to see if there's any corrupt system files. To use it, open command prompt and type this in:
This should repair any corrupted system file entries.
Last resort would be to do a reinstall for that particular driver. Make sure you reboot after uninstall, boot the machine back up, then reinstall, and reboot once more for changes to take effect when the system starts again. A good program to use for uninstalling drivers would be a program called
Driver Sweeper.