*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800a54c4e0, fffff8800f1e1cf8, 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+119cf8 )
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: fffffa800a54c4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f1e1cf8, 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+119cf8
fffff880`0f1e1cf8 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`0525a9c8 fffff880`04a62000 : 00000000`00000116 fffffa80`0a54c4e0 fffff880`0f1e1cf8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0525a9d0 fffff880`04a61d0a : fffff880`0f1e1cf8 fffffa80`0a54c4e0 fffffa80`09e74d50 fffffa80`07cde010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0525aa10 fffff880`04b08f07 : fffffa80`0a54c4e0 00000000`00000000 fffffa80`09e74d50 fffffa80`07cde010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0525aa40 fffff880`04b32b75 : 00000000`ffffffff 00000000`00000997 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0525ab20 fffff880`04b312bb : 00000000`00000102 00000000`00000000 00000000`00000997 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0525ab50 fffff880`04b042c6 : ffffffff`ff676980 fffffa80`07cde010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0525abf0 fffff880`04b30e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`09938168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0525ad00 fffff800`02d2334a : 00000000`06b17f7e fffffa80`07ce8610 fffffa80`06d22b30 fffffa80`07ce8610 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0525ad40 fffff800`02a73946 : fffff800`02bfee80 fffffa80`07ce8610 fffff800`02c0ccc0 00000000`00000246 : nt!PspSystemThreadStartup+0x5a
fffff880`0525ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+119cf8
fffff880`0f1e1cf8 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+119cf8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4c37918e
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`0f0c8000 fffff880`0fd59e00 nvlddmkm T (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Sat Jul 10 03:15:58 2010 (4C37918E)
CheckSum: 00CA10CD
ImageSize: 00C91E00
Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4