Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\Windows_NT6_BSOD_jcgriff2\022011-22900-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols;srv*e:\symbols
*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.x86fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0x8280a000 PsLoadedModuleList = 0x82952810
Debug session time: Sun Feb 20 11:57:30.521 2011 (GMT-5)
System Uptime: 0 days 0:02:25.768
Loading Kernel Symbols
...............................................................
................................................................
................
Loading User Symbols
Loading unloaded module list
.....
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: 860ab008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: 8dd06176, The pointer into responsible device driver module (e.g. owner tag).
Arg3: 00000000, Optional error code (NTSTATUS) of the last failed operation.
Arg4: 00000002, Optional internal context dependent data.
Debugging Details:
------------------
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
FAULTING_IP:
nvlddmkm+ee176
8dd06176 55 push ebp
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
8987fb74 8cec492c 00000116 860ab008 8dd06176 nt!KeBugCheckEx+0x1e
8987fb98 8cec574b 8dd06176 00000000 00000002 dxgkrnl!TdrBugcheckOnTimeout+0x8d
8987fbbc 8e5bd92c 00000000 00000102 860e0748 dxgkrnl!TdrIsRecoveryRequired+0xb8
8987fc34 8e5e7a32 fffffcfb 000023e4 00000000 dxgmms1!VidSchiReportHwHang+0x3c0
8987fc5c 8e5e8153 00000000 00000000 00000000 dxgmms1!VidSchiCheckHwProgress+0x68
8987fc98 8e5c48f0 8987fc90 86139970 86139a70 dxgmms1!VidSchiWaitForSchedulerEvents+0x1b1
8987fd28 8e5e94b7 860e0748 828463f1 860e0748 dxgmms1!VidSchiScheduleCommandToRun+0xaa
8987fd3c 8e5e9573 860e0748 00000000 86101c48 dxgmms1!VidSchiRun_PriorityTable+0xf
8987fd50 82a1866d 860e0748 926a71e8 00000000 dxgmms1!VidSchiWorkerThread+0x7f
8987fd90 828ca0d9 8e5e94f4 860e0748 00000000 nt!PspSystemThreadStartup+0x9e
00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x19
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+ee176
8dd06176 55 push ebp
SYMBOL_NAME: nvlddmkm+ee176
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4cb9dbec
FAILURE_BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: 0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------