*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800e8714e0, fffff8800f3eaa88, 0, 2}
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+14ba88 )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800e8714e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f3eaa88, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 0000000000000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 0000000000000002, Optional internal context dependent data.
Debugging Details:
------------------
FAULTING_IP:
nvlddmkm+14ba88
fffff880`0f3eaa88 4055 push rbp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`050e6988 fffff880`03e7e000 : 00000000`00000116 fffffa80`0e8714e0 fffff880`0f3eaa88 00000000`00000000 : nt!KeBugCheckEx
fffff880`050e6990 fffff880`03e7dd0a : fffff880`0f3eaa88 fffffa80`0e8714e0 fffffa80`0633dc00 fffffa80`06438410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`050e69d0 fffff880`03f24f07 : fffffa80`0e8714e0 00000000`00000000 fffffa80`0633dc00 fffffa80`06438410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`050e6a00 fffff880`03f4eb75 : 00000000`ffffffff 00000000`001be665 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`050e6ae0 fffff880`03f4d2bb : 00000000`00000102 00000000`00000000 00000000`001be665 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`050e6b10 fffff880`03f202c6 : ffffffff`ff676980 fffffa80`06438410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`050e6bb0 fffff880`03f4ce7a : 00000000`00000000 00000000`001be611 00000000`00000080 00000000`00000000 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`050e6cc0 fffff800`03365e5a : 00000000`fffffc32 fffffa80`05e80b50 fffffa80`03cd0b30 fffffa80`05e80b50 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`050e6d00 fffff800`030bfd26 : fffff800`03241e80 fffffa80`05e80b50 fffff800`0324fcc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`050e6d40 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+14ba88
fffff880`0f3eaa88 4055 push rbp
SYMBOL_NAME: nvlddmkm+14ba88
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 506b3099
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
1: kd> lmvm nvlddmkm
start end module name
fffff880`0f29f000 fffff880`0ff93000 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Wed Oct 03 00:21:13 2012 (506B3099)
CheckSum: 00CD4613
ImageSize: 00CF4000
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4