Attached is the minidump from my crash. This system has been up and running fine since the launch of Win 7 on Oct 22nd. It seems to have occured when going to sleep mode. If someone gets time can you take a look at the minidump and give me an idea what may be the problem, thanks.
Hi and welcome
this crash was probably caused by both dxgkrnl.sys and nvlddmkm.sys. fortunately both are related to your video driver. The DXG file is the direct x component, and NVLD is the driver
I would update the video driver and at least the one driver below as it is from 2005.
since system files were involved I would run a system file check
type cmd in search>right click and run as admin>sfc /scannow
If you are overclocking stop
if you have a raid update its driver
Hope this helps
Ken J+
]
ASACPI.sys fffff880`04200000 fffff880`04208000 0x00008000 0x42476c4c 3/27/2005 9:30:36 PM
Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Users\K\Desktop\120109-34694-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\symbols*
Symbol information
Executable search path is:
Windows 7 Kernel Version 7600 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7600.16385.amd64fre.win7_rtm.090713-1255
Machine Name:
Kernel base = 0xfffff800`02e4b000 PsLoadedModuleList = 0xfffff800`03088e50
Debug session time: Tue Dec 1 14:07:49.524 2009 (GMT-5)
System Uptime: 0 days 3:53:58.443
Loading Kernel Symbols
...............................................................
................................................................
...........................................
Loading User Symbols
Loading unloaded module list
............
Unable to load image \SystemRoot\System32\drivers\dxgkrnl.sys, Win32 error 0n2
*** WARNING: Unable to verify timestamp for dxgkrnl.sys
*** ERROR: Module load completed but symbols could not be loaded for dxgkrnl.sys
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 116, {fffffa800754f4e0, fffff8800495c140, 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+e1140 )
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: fffffa800754f4e0, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT).
Arg2: fffff8800495c140, 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:
------------------
OVERLAPPED_MODULE: Address regions for 'hiber_dumpfve' and 'ENG64.SYS' overlap
FAULTING_IP:
nvlddmkm+e1140
fffff880`0495c140 803d51b4970000 cmp byte ptr [nvlddmkm+0xa5c598 (fffff880`052d7598)],0
DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_FAULT
CUSTOMER_CRASH_COUNT: 1
BUGCHECK_STR: 0x116
PROCESS_NAME: System
CURRENT_IRQL: 0
STACK_TEXT:
fffff880`06a669c8 fffff880`0455bef8 : 00000000`00000116 fffffa80`0754f4e0 fffff880`0495c140 00000000`00000000 : nt!KeBugCheckEx
fffff880`06a669d0 00000000`00000116 : fffffa80`0754f4e0 fffff880`0495c140 00000000`00000000 00000000`00000002 : dxgkrnl+0x5cef8
fffff880`06a669d8 fffffa80`0754f4e0 : fffff880`0495c140 00000000`00000000 00000000`00000002 00000000`00000000 : 0x116
fffff880`06a669e0 fffff880`0495c140 : 00000000`00000000 00000000`00000002 00000000`00000000 00000000`00000000 : 0xfffffa80`0754f4e0
fffff880`06a669e8 00000000`00000000 : 00000000`00000002 00000000`00000000 00000000`00000000 fffff880`0455bc02 : nvlddmkm+0xe1140
STACK_COMMAND: kb
FOLLOWUP_IP:
nvlddmkm+e1140
fffff880`0495c140 803d51b4970000 cmp byte ptr [nvlddmkm+0xa5c598 (fffff880`052d7598)],0
SYMBOL_STACK_INDEX: 4
SYMBOL_NAME: nvlddmkm+e1140
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nvlddmkm
IMAGE_NAME: nvlddmkm.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 4a5ce19c
FAILURE_BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
BUCKET_ID: X64_0x116_IMAGE_nvlddmkm.sys
Followup: MachineOwner
---------
