
Quote: Originally Posted by
paul129
please could someone help me? my computer has just started restarting itself with no errors or bsod just a black screen the restart. it does not go into the startup options (safe mode etc.) just a pure restart. it will do this a couple of times a night. i have included the seven forums diag tool results if it will help. thanks in advance
Paul
Hi and welcome
this one is pretty straight forward. Probable cause was your v ideo driver and specifically the nvlddmkm.sys file.
You should use their un-installer to remove all the fragments of this driver, Then download and install a fresh copy and install it
If you are overclocking stop
Let us know if you need help
Ken
Code:
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\021410-20763-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*F:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 7 Kernel Version 7600 MP (2 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02a5c000 PsLoadedModuleList = 0xfffff800`02c99e50
Debug session time: Sun Feb 14 14:21:23.742 2010 (GMT-4)
System Uptime: 0 days 2:33:54.724
Loading Kernel Symbols
...............................................................
................................................................
...........................
Loading User Symbols
Loading unloaded module list
.........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa8003c34390, fffff8800579e6c0, 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+d06c0 )
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
VIDEO_TDR_FAILURE (116)
Attempt to reset the display driver and recover from timeout failed.
Arguments:
Arg1: fffffa8003c34390, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800579e6c0, 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+d06c0
fffff880`0579e6c0 803db1899c0000 cmp byte ptr [nvlddmkm+0xa99078 (fffff880`06167078)],0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`04a809c8 fffff880`04d5acbc : 00000000`00000116 fffffa80`03c34390 fffff880`0579e6c0 00000000`00000000 : nt!KeBugCheckEx
fffff880`04a809d0 fffff880`04d5a9c6 : fffff880`0579e6c0 fffffa80`03c34390 fffffa80`0553b830 fffffa80`03714410 : dxgkrnl!TdrBugcheckOnTimeout+0xec
fffff880`04a80a10 fffff880`04c0ff07 : fffffa80`03c34390 00000000`00000000 fffffa80`0553b830 fffffa80`03714410 : dxgkrnl!TdrIsRecoveryRequired+0x1a2
fffff880`04a80a40 fffff880`04c39b75 : 00000000`ffffffff 00000000`0009078a 00000000`00000000 00000000`00000002 : dxgmms1!VidSchiReportHwHang+0x40b
fffff880`04a80b20 fffff880`04c382bb : 00000000`00000102 00000000`00000000 00000000`0009078a 00000000`00000000 : dxgmms1!VidSchiCheckHwProgress+0x71
fffff880`04a80b50 fffff880`04c0b2c6 : ffffffff`ff676980 fffffa80`03714410 00000000`00000000 00000000`00000000 : dxgmms1!VidSchiWaitForSchedulerEvents+0x1fb
fffff880`04a80bf0 fffff880`04c37e7a : 00000000`00000000 fffffa80`0428c460 00000000`00000080 fffffa80`03714410 : dxgmms1!VidSchiScheduleCommandToRun+0x1da
fffff880`04a80d00 fffff800`02d71166 : 00000000`fffffc32 fffffa80`05539b60 fffffa80`036ca040 fffffa80`05539b60 : dxgmms1!VidSchiWorkerThread+0xba
fffff880`04a80d40 fffff800`02aac486 : fffff800`02c46e80 fffffa80`05539b60 fffff800`02c54c40 fffff880`01249534 : nt!PspSystemThreadStartup+0x5a
fffff880`04a80d80 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxStartSystemThread+0x16
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_IP:
nvlddmkm+d06c0
fffff880`0579e6c0 803db1899c0000 cmp byte ptr [nvlddmkm+0xa99078 (fffff880`06167078)],0
SYMBOL_NAME: nvlddmkm+d06c0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a0c8387
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------