Code:
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010112-22495-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03211000 PsLoadedModuleList = 0xfffff800`03456670
Debug session time: Sun Jan 1 12:51:46.408 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:19.408
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80088c44e0, fffff8800f3cf9c8, 0, 2}
*** 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+1759c8 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80088c44e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f3cf9c8, 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+1759c8
fffff880`0f3cf9c8 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`0693a9c8 fffff880`0ff2e000 : 00000000`00000116 fffffa80`088c44e0 fffff880`0f3cf9c8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0693a9d0 fffff880`0ff2dd0a : fffff880`0f3cf9c8 fffffa80`088c44e0 fffffa80`085e1ab0 fffffa80`0862f010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0693aa10 fffff880`0f20ff07 : fffffa80`088c44e0 00000000`00000000 fffffa80`085e1ab0 fffffa80`0862f010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0693aa40 fffff880`0f239b75 : 00000000`ffffffff 00000000`00000435 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0693ab20 fffff880`0f2382bb : 00000000`00000102 00000000`00000006 00000000`00000435 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0693ab50 fffff880`0f20b2c6 : ffffffff`ff676980 fffffa80`0862f010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0693abf0 fffff880`0f237e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0571c678 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0693ad00 fffff800`03528fee : 00000000`02bb8b28 fffffa80`085e28c0 fffffa80`03ced040 fffffa80`085e28c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0693ad40 fffff800`0327f5e6 : fffff880`03287180 fffffa80`085e28c0 fffff880`032920c0 fffff880`01437cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`0693ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+1759c8
fffff880`0f3cf9c8 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+1759c8
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
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010112-22245-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03206000 PsLoadedModuleList = 0xfffff800`0344b670
Debug session time: Sun Jan 1 12:55:21.628 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:18.517
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800644f4e0, fffff8800f37a9c8, 0, 2}
*** 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+1759c8 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa800644f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f37a9c8, 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+1759c8
fffff880`0f37a9c8 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`028de9c8 fffff880`0fed9000 : 00000000`00000116 fffffa80`0644f4e0 fffff880`0f37a9c8 00000000`00000000 : nt!KeBugCheckEx
fffff880`028de9d0 fffff880`0fed8d0a : fffff880`0f37a9c8 fffffa80`0644f4e0 fffffa80`0852d6c0 fffffa80`08611010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`028dea10 fffff880`0ff7ff07 : fffffa80`0644f4e0 00000000`00000000 fffffa80`0852d6c0 fffffa80`08611010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`028dea40 fffff880`0ffa9b75 : 00000000`ffffffff 00000000`000003eb 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`028deb20 fffff880`0ffa82bb : 00000000`00000102 00000000`00000006 00000000`000003eb 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`028deb50 fffff880`0ff7b2c6 : ffffffff`ff676980 fffffa80`08611010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`028debf0 fffff880`0ffa7e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`057e0b38 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`028ded00 fffff800`0351dfee : 00000000`0288e129 fffffa80`086128c0 fffffa80`03cd0040 fffffa80`086128c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`028ded40 fffff800`032745e6 : fffff800`033f8e80 fffffa80`086128c0 fffff800`03406cc0 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
fffff880`028ded80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+1759c8
fffff880`0f37a9c8 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+1759c8
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
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010112-22947-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0321c000 PsLoadedModuleList = 0xfffff800`03461670
Debug session time: Sun Jan 1 13:21:16.736 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:19.735
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa80088e02e0, fffff8800f3f99c8, 0, 2}
*** 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+1759c8 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa80088e02e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f3f99c8, 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+1759c8
fffff880`0f3f99c8 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`0673f9c8 fffff880`0ff58000 : 00000000`00000116 fffffa80`088e02e0 fffff880`0f3f99c8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0673f9d0 fffff880`0ff57d0a : fffff880`0f3f99c8 fffffa80`088e02e0 fffffa80`0861cab0 fffffa80`085fc010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0673fa10 fffff880`0f20ff07 : fffffa80`088e02e0 00000000`00000000 fffffa80`0861cab0 fffffa80`085fc010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0673fa40 fffff880`0f239b75 : 00000000`ffffffff 00000000`00000451 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0673fb20 fffff880`0f2382bb : 00000000`00000102 00000000`00000006 00000000`00000451 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0673fb50 fffff880`0f20b2c6 : ffffffff`ff676980 fffffa80`085fc010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0673fbf0 fffff880`0f237e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`05642c68 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0673fd00 fffff800`03533fee : 00000000`02cea524 fffffa80`0861da10 fffffa80`03ce2040 fffffa80`0861da10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0673fd40 fffff800`0328a5e6 : fffff800`0340ee80 fffffa80`0861da10 fffff800`0341ccc0 fffff880`01434384 : nt!PspSystemThreadStartup+0x5a
fffff880`0673fd80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+1759c8
fffff880`0f3f99c8 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+1759c8
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
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010112-22136-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0321e000 PsLoadedModuleList = 0xfffff800`03463670
Debug session time: Sun Jan 1 13:26:50.221 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:19.110
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8008a7e010, fffff8800f3b49c8, 0, 2}
*** 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+1759c8 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008a7e010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f3b49c8, 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+1759c8
fffff880`0f3b49c8 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`069359c8 fffff880`0ff13000 : 00000000`00000116 fffffa80`08a7e010 fffff880`0f3b49c8 00000000`00000000 : nt!KeBugCheckEx
fffff880`069359d0 fffff880`0ff12d0a : fffff880`0f3b49c8 fffffa80`08a7e010 fffffa80`08641810 fffffa80`08621010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06935a10 fffff880`0ffb9f07 : fffffa80`08a7e010 00000000`00000000 fffffa80`08641810 fffffa80`08621010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06935a40 fffff880`0ffe3b75 : 00000000`ffffffff 00000000`00000410 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06935b20 fffff880`0ffe22bb : 00000000`00000102 00000000`00000006 00000000`00000410 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06935b50 fffff880`0ffb52c6 : ffffffff`ff676980 fffffa80`08621010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06935bf0 fffff880`0ffe1e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`08131168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06935d00 fffff800`03535fee : 00000000`02a22e88 fffffa80`08642a10 fffffa80`03cd0040 fffffa80`08642a10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06935d40 fffff800`0328c5e6 : fffff880`03287180 fffffa80`08642a10 fffff880`032920c0 fffff880`01456cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`06935d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+1759c8
fffff880`0f3b49c8 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+1759c8
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
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010112-22198-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03256000 PsLoadedModuleList = 0xfffff800`0349b670
Debug session time: Sun Jan 1 13:49:30.173 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:20.172
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8008a8b010, fffff8800f3c89c8, 0, 2}
*** 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+1759c8 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008a8b010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f3c89c8, 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+1759c8
fffff880`0f3c89c8 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`069469c8 fffff880`0ff27000 : 00000000`00000116 fffffa80`08a8b010 fffff880`0f3c89c8 00000000`00000000 : nt!KeBugCheckEx
fffff880`069469d0 fffff880`0ff26d0a : fffff880`0f3c89c8 fffffa80`08a8b010 fffffa80`0864aab0 fffffa80`08613010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`06946a10 fffff880`0f20ff07 : fffffa80`08a8b010 00000000`00000000 fffffa80`0864aab0 fffffa80`08613010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`06946a40 fffff880`0f239b75 : 00000000`ffffffff 00000000`0000044d 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`06946b20 fffff880`0f2382bb : 00000000`00000102 00000000`00000006 00000000`0000044d 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`06946b50 fffff880`0f20b2c6 : ffffffff`ff676980 fffffa80`08613010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`06946bf0 fffff880`0f237e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0810a808 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`06946d00 fffff800`0356dfee : 00000000`02cbe6ee fffffa80`0864ba10 fffffa80`03cd0040 fffffa80`0864ba10 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`06946d40 fffff800`032c45e6 : fffff800`03448e80 fffffa80`0864ba10 fffff800`03456cc0 fffff880`0144a384 : nt!PspSystemThreadStartup+0x5a
fffff880`06946d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+1759c8
fffff880`0f3c89c8 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+1759c8
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
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010212-20124-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03261000 PsLoadedModuleList = 0xfffff800`034a6670
Debug session time: Mon Jan 2 11:12:11.546 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:21.545
Loading Kernel Symbols
...............................................................
................................................................
..................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8008605010, fffff8800f3a99c8, 0, 2}
*** 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+1759c8 )
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: fffffa8008605010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f3a99c8, 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+1759c8
fffff880`0f3a99c8 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`063aa9c8 fffff880`0ff08000 : 00000000`00000116 fffffa80`08605010 fffff880`0f3a99c8 00000000`00000000 : nt!KeBugCheckEx
fffff880`063aa9d0 fffff880`0ff07d0a : fffff880`0f3a99c8 fffffa80`08605010 fffffa80`0834c6c0 fffffa80`0832c010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`063aaa10 fffff880`0ffaef07 : fffffa80`08605010 00000000`00000000 fffffa80`0834c6c0 fffffa80`0832c010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`063aaa40 fffff880`0ffd8b75 : 00000000`ffffffff 00000000`000004ab 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`063aab20 fffff880`0ffd72bb : 00000000`00000102 00000000`00000006 00000000`000004ab 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`063aab50 fffff880`0ffaa2c6 : ffffffff`ff676980 fffffa80`0832c010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`063aabf0 fffff880`0ffd6e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`0619d168 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`063aad00 fffff800`03578fee : 00000000`0303e16b fffffa80`0834d8c0 fffffa80`03cd0040 fffffa80`0834d8c0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`063aad40 fffff800`032cf5e6 : fffff800`03453e80 fffffa80`0834d8c0 fffff800`03461cc0 fffff880`0144fcb0 : nt!PspSystemThreadStartup+0x5a
fffff880`063aad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+1759c8
fffff880`0f3a99c8 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+1759c8
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
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010212-22448-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`0324f000 PsLoadedModuleList = 0xfffff800`03494670
Debug session time: Mon Jan 2 12:14:03.096 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:19.096
Loading Kernel Symbols
...............................................................
................................................................
......................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8008a8a010, fffff8800f38d6e8, 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+1796e8 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008a8a010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800f38d6e8, 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+1796e8
fffff880`0f38d6e8 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`0666a9c8 fffff880`0ff24000 : 00000000`00000116 fffffa80`08a8a010 fffff880`0f38d6e8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0666a9d0 fffff880`0ff23d0a : fffff880`0f38d6e8 fffffa80`08a8a010 fffffa80`08665d50 fffffa80`08642010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0666aa10 fffff880`02fa9f07 : fffffa80`08a8a010 00000000`00000000 fffffa80`08665d50 fffffa80`08642010 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0666aa40 fffff880`02fd3b75 : 00000000`ffffffff 00000000`00000425 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0666ab20 fffff880`02fd22bb : 00000000`00000102 00000000`00000000 00000000`00000425 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0666ab50 fffff880`02fa52c6 : ffffffff`ff676980 fffffa80`08642010 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0666abf0 fffff880`02fd1e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`055d5a98 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0666ad00 fffff800`03566fee : 00000000`02b0a137 fffffa80`0866b4d0 fffffa80`03cd0040 fffffa80`0866b4d0 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0666ad40 fffff800`032bd5e6 : fffff800`03441e80 fffffa80`0866b4d0 fffff800`0344fcc0 fffff880`01243cb0 : nt!PspSystemThreadStartup+0x5a
fffff880`0666ad80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+1796e8
fffff880`0f38d6e8 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+1796e8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
-
Loading Dump File [C:\Users\Mike\Downloads\BSODDmpFiles\HenryVII\Windows_NT6_BSOD_jcgriff2\010212-25256-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\users\mike\documents\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 7601.17640.amd64fre.win7sp1_gdr.110622-1506
Machine Name:
Kernel base = 0xfffff800`03210000 PsLoadedModuleList = 0xfffff800`03455670
Debug session time: Mon Jan 2 14:23:49.754 2012 (UTC - 7:00)
System Uptime: 0 days 0:00:27.754
Loading Kernel Symbols
...............................................................
................................................................
..........................
Loading User Symbols
Loading unloaded module list
....
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8008b55010, fffff8801044f6e8, 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+1796e8 )
Followup: MachineOwner
---------
6: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8008b55010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8801044f6e8, 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+1796e8
fffff880`1044f6e8 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`0462e9c8 fffff880`04325000 : 00000000`00000116 fffffa80`08b55010 fffff880`1044f6e8 00000000`00000000 : nt!KeBugCheckEx
fffff880`0462e9d0 fffff880`04324d0a : fffff880`1044f6e8 fffffa80`08b55010 fffffa80`087cac00 fffffa80`086851f0 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`0462ea10 fffff880`0420ff07 : fffffa80`08b55010 00000000`00000000 fffffa80`087cac00 fffffa80`086851f0 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`0462ea40 fffff880`04239b75 : 00000000`ffffffff 00000000`0000062a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`0462eb20 fffff880`042382bb : 00000000`00000102 00000000`00000000 00000000`0000062a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`0462eb50 fffff880`0420b2c6 : ffffffff`ff676980 fffffa80`086851f0 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`0462ebf0 fffff880`04237e7a : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`082b4738 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`0462ed00 fffff800`03527fee : 00000000`0410c94d fffffa80`087a8060 fffffa80`03cd1040 fffffa80`087a8060 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`0462ed40 fffff800`0327e5e6 : fffff800`03402e80 fffffa80`087a8060 fffff800`03410cc0 fffff880`01443384 : nt!PspSystemThreadStartup+0x5a
fffff880`0462ed80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+1796e8
fffff880`1044f6e8 4883ec28 sub rsp,28h
SYMBOL_NAME: nvlddmkm+1796e8
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4dd73a68
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
Update the following drivers. To find driver updates, search google, check your hardware manufacturer sites, and you may use