*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800cbdb010, fffff8800f4247a0, ffffffffc000009a, 4}
Unable to load image 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
---------
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800cbdb010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f4247a0, 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`0f4247a0 48ff25f94eedff jmp qword ptr [nvlddmkm+0x87a6a0 (fffff880`0f2f96a0)]
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`02ab8a48 fffff880`04b53134 : 00000000`00000116 fffffa80`0cbdb010 fffff880`0f4247a0 ffffffff`c000009a : nt!KeBugCheckEx
fffff880`02ab8a50 fffff880`04b26867 : fffff880`0f4247a0 fffffa80`0c1dd000 00000000`00000000 ffffffff`c000009a : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`02ab8a90 fffff880`04b52f43 : fffffa80`ffffd846 00000000`00000000 fffffa80`0cbdb010 00000000`00000000 : dxgkrnl!DXGADAPTER::Reset+0x2a3
fffff880`02ab8b40 fffff880`04a3803d : fffffa80`07651bb0 00000000`00000080 00000000`00000000 fffffa80`0c129410 : dxgkrnl!TdrResetFromTimeout+0x23
fffff880`02ab8bc0 fffff800`0376d73a : 00000000`031f69fc fffffa80`0b932b50 fffffa80`069a0990 fffffa80`0b932b50 : dxgmms1!VidSchiWorkerThread+0x101
fffff880`02ab8c00 fffff800`034c28e6 : fffff880`037d7180 fffffa80`0b932b50 fffff880`037e1fc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`02ab8c40 00000000`00000000 : fffff880`02ab9000 fffff880`02ab3000 fffff880`02ab8460 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+9a57a0
fffff880`0f4247a0 48ff25f94eedff jmp qword ptr [nvlddmkm+0x87a6a0 (fffff880`0f2f96a0)]
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
---------
2: kd> lmvm nvlddmkm
start end module name
fffff880`0ea7f000 fffff880`0f70d000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: 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