Microsoft (R) Windows Debugger Version 6.11.0001.404 X86 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\011313-26218-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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Windows 7 Kernel Version 7601 (Service Pack 1) UP Free x86 compatible Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0x82c0f000 PsLoadedModuleList = 0x82d4f230 Debug session time: Sun Jan 13 13:35:11.240 2013 (GMT+1) System Uptime: 0 days 0:23:53.350 ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Unable to load image ntoskrnl.exe, Win32 error 0n2 *** WARNING: Unable to verify timestamp for ntoskrnl.exe *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe Loading Kernel Symbols ............................................................... ................................................................ ............................. Loading User Symbols Mini Kernel Dump does not contain unloaded driver list Unable to load image 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 117, {84c9a008, 905bb26c, 0, 0} *** WARNING: Unable to verify timestamp for mssmbios.sys *** ERROR: Module load completed but symbols could not be loaded for mssmbios.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 *** *** *** ************************************************************************* Unable to load image atikmpag.sys, Win32 error 0n2 *** WARNING: Unable to verify timestamp for atikmpag.sys *** ERROR: Module load completed but symbols could not be loaded for atikmpag.sys ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* Probably caused by : atikmpag.sys ( atikmpag+726c ) Followup: MachineOwner --------- kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* VIDEO_TDR_TIMEOUT_DETECTED (117) The display driver failed to respond in timely fashion. (This code can never be used for real bugcheck). Arguments: Arg1: 84c9a008, Optional pointer to internal TDR recovery context (TDR_RECOVERY_CONTEXT). Arg2: 905bb26c, The pointer into responsible device driver module (e.g owner tag). Arg3: 00000000, The secondary driver specific bucketing key. Arg4: 00000000, Optional internal context dependent data. Debugging Details: ------------------ ***** 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 *** *** *** ************************************************************************* ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* ********************************************************************* * 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 argument when starting the debugger. * * using .sympath and .sympath+ * ********************************************************************* 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. FAULTING_MODULE: 82c0f000 nt DEBUG_FLR_IMAGE_TIMESTAMP: 4f7e427e FAULTING_IP: atikmpag+726c 905bb26c ?? ??? DEFAULT_BUCKET_ID: GRAPHICS_DRIVER_TDR_TIMEOUT TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b CUSTOMER_CRASH_COUNT: 1 BUGCHECK_STR: 0x117 CURRENT_IRQL: 0 STACK_TEXT: WARNING: Stack unwind information not available. Following frames may be wrong. 8d2b89b4 929d15b8 00000000 905bb26c 86ce5390 dxgkrnl+0x81a5e 8d2b8a20 929d097e 00000000 00000001 84c9a008 dxgkrnl+0x825b8 8d2b8a40 92a0c92c 00000000 00000000 8d2b8b04 dxgkrnl+0x8197e 8d2b8ab8 92a33c1d fffffcfb 000162d8 00000000 dxgmms1+0x692c 8d2b8ae4 92a36e20 86ce5390 8d2b8b04 00000102 dxgmms1+0x2dc1d 8d2b8b64 92a37523 875ff000 86c7f9d0 875fff70 dxgmms1+0x30e20 8d2b8bdc 92a37e99 86ce5390 00000001 86c7f9d0 dxgmms1+0x31523 8d2b8d18 92a38141 00c7f9d0 86c7fdd0 8d2b8d3c dxgmms1+0x31e99 8d2b8d28 92a383de 86c7f9d0 82c3dfc5 86ce5390 dxgmms1+0x32141 8d2b8d3c 92a38485 86ce5390 00000000 87101d48 dxgmms1+0x323de 8d2b8d50 82df750a 86ce5390 92ebb6a3 00000000 dxgmms1+0x32485 8d2b8d90 82c98879 92a38406 86ce5390 00000000 nt+0x1e850a 00000000 00000000 00000000 00000000 00000000 nt+0x89879 STACK_COMMAND: .bugcheck ; kb FOLLOWUP_IP: atikmpag+726c 905bb26c ?? ??? SYMBOL_NAME: atikmpag+726c FOLLOWUP_NAME: MachineOwner MODULE_NAME: atikmpag IMAGE_NAME: atikmpag.sys BUCKET_ID: WRONG_SYMBOLS Followup: MachineOwner --------- kd> lmvm atikmpag start end module name 905b4000 905fb000 atikmpag T (no symbols) Loaded symbol image file: atikmpag.sys Image path: atikmpag.sys Image name: atikmpag.sys Timestamp: Fri Apr 06 03:10:22 2012 (4F7E427E) CheckSum: 00048245 ImageSize: 00047000 Translations: 0000.04b0 0000.04e4 0409.04b0 0409.04e4 Mini Kernel Dump does not contain unloaded driver list