I've been having this problem where my computer will BSOD 10-12 seconds after the Windows loading screen disappears. I have Vista Ultimate 64-bit. Hardware specs are an 8800 GTX, 750 watt PSU powered by PC Power & Cooling, 2 150 GB Western Digital RaptorX's 10000 RPM, 1 500 GB Western Digital Caviar 7200 RPM and a ABIT IP35 PRO. I have tried uninstalling my video card drivers using Driver Cleaner and done so in safe mode. I've tried downgrading my video card drivers as well. Here is the .dmp file for the BSOD.
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8007f61010, fffffa6002c1e9b0, 0, 2}
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+109b0 )
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: fffffa8007f61010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffffa6002c1e9b0, 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+109b0
fffffa60`02c1e9b0 803d312f850000 cmp byte ptr [nvlddmkm+0x8638e8 (fffffa60`034718e8)],0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffffa60`02514a08 fffffa60`03551398 : 00000000`00000116 fffffa80`07f61010 fffffa60`02c1e9b0 00000000`00000000 : nt!KeBugCheckEx
fffffa60`02514a10 fffffa60`035511cb : fffffa60`02c1e9b0 fffffa80`07f61010 fffffa80`07c05540 fffffa80`07f61010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffffa60`02514a50 fffffa60`0350bd8a : 00000000`00000000 00000000`00000000 fffffa80`07c05540 00000000`000009db : dxgkrnl!TdrIsRecoveryRequired+0x16f
fffffa60`02514a90 fffffa60`035cc26b : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000002 : dxgkrnl!VidSchiReportHwHang+0x312
fffffa60`02514b40 fffffa60`035cae6d : fffffa80`07c05540 fffffa80`00000000 00000000`000009db fffffa80`07c05540 : dxgkrnl!VidSchiCheckHwProgress+0x7b
fffffa60`02514b70 fffffa60`035100f8 : ffffffff`ff676980 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VidSchiWaitForSchedulerEvents+0x199
fffffa60`02514bf0 fffffa60`035cac8d : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`07c05540 : dxgkrnl!VidSchiScheduleCommandToRun+0x398
fffffa60`02514d10 fffff800`020d7f73 : fffffa80`07c019a0 fffff800`01eae697 fffffa80`057a4300 fffffa80`039a8c01 : dxgkrnl!VidSchiWorkerThread+0x95
fffffa60`02514d50 fffff800`01eee526 : fffff800`01fd3680 fffffa80`07c019a0 fffff800`01fd8b80 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`02514d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+109b0
fffffa60`02c1e9b0 803d312f850000 cmp byte ptr [nvlddmkm+0x8638e8 (fffffa60`034718e8)],0
SYMBOL_NAME: nvlddmkm+109b0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4894c6af
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
fffffa60`02c0e000 fffffa60`034f6380 nvlddmkm (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Sat Aug 02 13:42:23 2008 (4894C6AF)
CheckSum: 008F28E6
ImageSize: 008E8380
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
The weird thing is that it doesn't happen every time I start-up or restart my PC, only after every 2-3 reboots; sometimes more, sometimes less.
Any ideas as to what might be causing this?
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8007f61010, fffffa6002c1e9b0, 0, 2}
*** ERROR: Module load completed but symbols could not be loaded for nvlddmkm.sys
Probably caused by : nvlddmkm.sys ( nvlddmkm+109b0 )
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: fffffa8007f61010, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffffa6002c1e9b0, 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+109b0
fffffa60`02c1e9b0 803d312f850000 cmp byte ptr [nvlddmkm+0x8638e8 (fffffa60`034718e8)],0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffffa60`02514a08 fffffa60`03551398 : 00000000`00000116 fffffa80`07f61010 fffffa60`02c1e9b0 00000000`00000000 : nt!KeBugCheckEx
fffffa60`02514a10 fffffa60`035511cb : fffffa60`02c1e9b0 fffffa80`07f61010 fffffa80`07c05540 fffffa80`07f61010 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffffa60`02514a50 fffffa60`0350bd8a : 00000000`00000000 00000000`00000000 fffffa80`07c05540 00000000`000009db : dxgkrnl!TdrIsRecoveryRequired+0x16f
fffffa60`02514a90 fffffa60`035cc26b : 00000000`00000000 00000000`00000002 00000000`00000002 00000000`00000002 : dxgkrnl!VidSchiReportHwHang+0x312
fffffa60`02514b40 fffffa60`035cae6d : fffffa80`07c05540 fffffa80`00000000 00000000`000009db fffffa80`07c05540 : dxgkrnl!VidSchiCheckHwProgress+0x7b
fffffa60`02514b70 fffffa60`035100f8 : ffffffff`ff676980 00000000`00000000 00000000`00000000 00000000`00000000 : dxgkrnl!VidSchiWaitForSchedulerEvents+0x199
fffffa60`02514bf0 fffffa60`035cac8d : 00000000`00000000 00000000`0000000f 00000000`00000080 fffffa80`07c05540 : dxgkrnl!VidSchiScheduleCommandToRun+0x398
fffffa60`02514d10 fffff800`020d7f73 : fffffa80`07c019a0 fffff800`01eae697 fffffa80`057a4300 fffffa80`039a8c01 : dxgkrnl!VidSchiWorkerThread+0x95
fffffa60`02514d50 fffff800`01eee526 : fffff800`01fd3680 fffffa80`07c019a0 fffff800`01fd8b80 00000000`00000001 : nt!PspSystemThreadStartup+0x57
fffffa60`02514d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+109b0
fffffa60`02c1e9b0 803d312f850000 cmp byte ptr [nvlddmkm+0x8638e8 (fffffa60`034718e8)],0
SYMBOL_NAME: nvlddmkm+109b0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4894c6af
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
fffffa60`02c0e000 fffffa60`034f6380 nvlddmkm (no symbols)
Loaded symbol image file: nvlddmkm.sys
Image path: \SystemRoot\system32\DRIVERS\nvlddmkm.sys
Image name: nvlddmkm.sys
Timestamp: Sat Aug 02 13:42:23 2008 (4894C6AF)
CheckSum: 008F28E6
ImageSize: 008E8380
Translations: 0000.04b0 0000.04e0 0409.04b0 0409.04e0
The weird thing is that it doesn't happen every time I start-up or restart my PC, only after every 2-3 reboots; sometimes more, sometimes less.
Any ideas as to what might be causing this?

Help
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Back to top









