Hello, My Windows 7 desktop sometimes crashes. I located a memory dump and analyzed it with the Windows Debugger. Could someone help solve this issue. I analyzed a few dumps, but this one I don't understand. Thanks in advance. Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\062009-21091-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: *** Invalid *** **************************************************************************** * Symbol loading may be unreliable without a symbol search path. * * Use .symfix to have the debugger choose a symbol path. * * After setting your symbol path, use .reload to refresh symbol locations. * **************************************************************************** Executable search path is: ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Windows 7 Kernel Version 7100 MP (4 procs) Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7100.0.x86fre.winmain_win7rc.090421-1700 Machine Name: Kernel base = 0x82c47000 PsLoadedModuleList = 0x82d8f810 Debug session time: Sat Jun 20 17:35:08.310 2009 (GMT+2) System Uptime: 0 days 2:13:20.637 ********************************************************************* * Symbols can not be loaded because symbol path is not initialized. * * * * The Symbol Path can be set by: * * using the _NT_SYMBOL_PATH environment variable. * * using the -y <symbol_path> argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ........ WARNING: Whitespace at end of path element 3: kd> .reload Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntkrnlpa.exe *** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe Loading Kernel Symbols ............................................................... ................................................................ .................................................. Loading User Symbols Loading unloaded module list ........ 3: kd> !analyze -v 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 * * * ******************************************************************************* THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea) The device driver is spinning in an infinite loop, most likely waiting for hardware to become idle. This usually indicates problem with the hardware itself or with the device driver programming the hardware incorrectly. If the kernel debugger is connected and running when watchdog detects a timeout condition then DbgBreakPoint() will be called instead of KeBugCheckEx() and detailed message including bugcheck arguments will be printed to the debugger. This way we can identify an offending thread, set breakpoints in it, and hit go to return to the spinning code to debug it further. Because KeBugCheckEx() is not called the .bugcheck directive will not return bugcheck information in this case. The arguments are already printed out to the kernel debugger. You can also retrieve them from a global variable via "dd watchdog!g_WdBugCheckData l5" (use dq on NT64). On MP machines it is possible to hit a timeout when the spinning thread is interrupted by hardware interrupt and ISR or DPC routine is running at the time of the bugcheck (this is because the timeout's work item can be delivered and handled on the second CPU and the same time). If this is the case you will have to look deeper at the offending thread's stack (e.g. using dds) to determine spinning code which caused the timeout to occur. Arguments: Arg1: 85a4fc08, Pointer to a stuck thread object. Do .thread then kb on it to find the hung location. Arg2: 00000000, Pointer to a DEFERRED_WATCHDOG object. Arg3: 00000000, Pointer to offending driver name. Arg4: 00000000, Number of times "intercepted" bugcheck 0xEA was hit (see notes). Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for atikmdag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmdag.sys *** WARNING: Unable to verify timestamp for dxgmms1.sys *** ERROR: Module load completed but symbols could not be loaded for dxgmms1.sys ***** Kernel symbols are WRONG. Please fix symbols to do analysis. ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ************************************************************************* *** *** *** *** *** Your debugger is not using the correct symbols *** *** *** *** In order for this command to work properly, your symbol path *** *** must point to .pdb files that have full type information. *** *** *** *** Certain .pdb files (such as the public OS symbols) do not *** *** contain the required information. Contact the group that *** *** provided you with these symbols if you need this command to *** *** work. *** *** *** *** Type referenced: nt!_KPRCB *** *** *** ************************************************************************* ADDITIONAL_DEBUG_TEXT: Use '!findthebuild' command to search for the target build information. If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols. MODULE_NAME: dxgkrnl FAULTING_MODULE: 82c47000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 49ee8dc4 FAULTING_THREAD: 85a4fc08 DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_FAULT CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0xEA CURRENT_IRQL: 0 LAST_CONTROL_TRANSFER: from 926b0efc to 82d22f28 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. ab9e3934 926b0efc 000000ea 85a4fc08 00000000 nt+0xdbf28 ab9e3978 926ac68c ab9e39c4 00000000 926a4f92 dxgkrnl+0x11efc ab9e39a0 92227a21 ab9e39c4 00000000 00000000 dxgkrnl+0xd68c ab9e39f0 92221c0a 9232c00f ab9e3a8c 00000bb8 atikmdag+0x27a21 ab9e3a10 92333e45 85cd4001 ab9e3a28 9232c00f atikmdag+0x21c0a ab9e3a68 9233aaac 8545c008 9232c00f ab9e3a8c atikmdag+0x133e45 ab9e3a9c 9233d0fc 8545c008 0000000a 925a2cb8 atikmdag+0x13aaac ab9e3ac8 92341f39 8545c008 8545c008 8545c140 atikmdag+0x13d0fc ab9e3adc 9233a99e 8545c008 925a2cb8 0000000a atikmdag+0x141f39 ab9e3af0 9232952f 8545c008 00000000 8545c008 atikmdag+0x13a99e ab9e3b04 9233345c 8545c008 00000000 85d6a010 atikmdag+0x12952f ab9e3b20 92329ae5 8545c008 ab9e3b40 922035f1 atikmdag+0x13345c ab9e3b2c 922035f1 8545c008 85a36940 00000000 atikmdag+0x129ae5 ab9e3b40 9220e194 00000000 c0000001 85a36940 atikmdag+0x35f1 ab9e3b70 9220f259 85c0a000 85c0a000 82c156ee atikmdag+0xe194 ab9e3b84 92724a71 00000000 8696b008 85c0a000 atikmdag+0xf259 ab9e3ba8 92725e45 87593788 8696b008 00000000 dxgkrnl+0x85a71 ab9e3bd0 9272d022 8696b008 8696b008 9164d07e dxgkrnl+0x86e45 ab9e3bec 9275c92c 00000000 00000000 ab9e3cb0 dxgkrnl+0x8e022 ab9e3c64 92783cd9 fffffcfb 0007cf63 00000000 dxgmms1+0x692c ab9e3c90 92763993 87593788 ab9e3cb0 00000102 dxgmms1+0x2dcd9 ab9e3d28 927884b7 00000000 82c78a3e 87593788 dxgmms1+0xd993 ab9e3d3c 92788573 87593788 00000000 85a4fc08 dxgmms1+0x324b7 ab9e3d50 82e41bc3 87593788 8437aad0 00000000 dxgmms1+0x32573 ab9e3d90 82d04e29 927884f4 87593788 00000000 nt+0x1fabc3 00000000 00000000 00000000 00000000 00000000 nt+0xbde29 STACK_COMMAND: .thread 0xffffffff85a4fc08 ; kb FOLLOWUP_IP: dxgkrnl+11efc 926b0efc ?? ??? SYMBOL_STACK_INDEX: 1 SYMBOL_NAME: dxgkrnl+11efc FOLLOWUP_NAME: MachineOwner IMAGE_NAME: dxgkrnl.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- Certifications: MCSA 2003 MCSE 2003

Shadowman123,It looks like it says 'Graphic Driver' and'THREAD_STUCK_IN_DEVICE_DRIVER_M (100000ea)The device driver is spinning in an infinite loop, most likely waiting forhardware to become idle. This usually indicates problem with the hardwareitself or with the device driver programming the hardware incorrectly.'So, what video card do you have and what driver do you have installed on it?

An ATI HD4800, with the lastest driver download a week ago from the AMD site.Certifications: MCSA 2003 MCSE 2003

shadowtheman123,Has this only happened since the new driver install?

No, also before that driver install.But after that new ATI driver is started to crash more often. Is it useful to upload the MSPReports and post the link here? Certifications: MCSA 2003 MCSE 2003