UQAT,
читать дальше »
Microsoft (R) Windows Debugger Version 6.10.0003.233 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\dump\Minidump\Mini112608-02.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: C:\symbols
Executable search path is: C:\symbols
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 Server 2008/Windows Vista SP1 Kernel Version 6001 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0x81a00000 PsLoadedModuleList = 0x81b17c70
Debug session time: Wed Nov 26 16:01:42.105 2008 (GMT+3)
System Uptime: 0 days 2:54:47.969
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
........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 101, {30, 0, 803d1120, 1}
*** WARNING: Unable to verify timestamp for sptd.sys
*** ERROR: Module load completed but symbols could not be loaded for sptd.sys
*** WARNING: Unable to verify timestamp for CLASSPNP.SYS
*** ERROR: Module load completed but symbols could not be loaded for CLASSPNP.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 ***
*** ***
*************************************************************************
Probably caused by : ntkrnlpa.exe
Followup: MachineOwner
---------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 00000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 00000000, 0.
Arg3: 803d1120, The PRCB address of the hung processor.
Arg4: 00000001, 0.
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 ***
*** ***
*************************************************************************
MODULE_NAME: nt
FAULTING_MODULE: 81a00000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 47918b12
BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT_4_PROC
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: WRONG_SYMBOLS
CURRENT_IRQL: 0
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
81af58bc 81ab8321 00000101 00000030 00000000 nt+0xcd163
81af58f0 81ab802d 93ef601b 000000d1 81af59b0 nt+0xb8321
81af5900 81ab7cc0 badb0d00 81af8920 81dd0cc9 nt+0xb802d
81af59b0 8061fb3e 8061f982 81af59c8 00040000 nt+0xb7cc0
81af5a00 8062026a 0000001f 8061f84e 81af5a24 sptd+0x14b3e
81af5a30 8061a5e3 01000001 85baba38 85a53728 sptd+0x1526a
81af5a48 8061bf6d 00000103 85bfffb0 85410008 sptd+0xf5e3
81af5a74 8061e8c4 85bab980 81af5acc 8061b8ec sptd+0x10f6d
81af5ad4 85718210 85718008 81af5ae4 00000000 sptd+0x138c4
81af5afc 87dbf264 85b53b70 85bfff90 85b53ab8 0x85718210
81af5b10 87dbf45d 85b53b70 85bfffa8 00000000 CLASSPNP+0x4264
81af5b28 87dbf2af 85b53b70 85a71324 81b34cc0 CLASSPNP+0x445d
81af5b48 81a3a598 85b53ab8 00000000 81af5bb8 CLASSPNP+0x42af
81af5b68 81ab6d00 81b34ca0 02b34c44 1e5c88d4 nt+0x3a598
81af5c88 81ab68c0 81af5cd0 8583f502 81af5cd8 nt+0xb6d00
81af5ce8 81ab6483 00000000 00000000 000a3d0b nt+0xb68c0
81af5d50 81ab4f9d 00000000 0000000e 00000000 nt+0xb6483
81af5d54 00000000 0000000e 00000000 00000000 nt+0xb4f9d
STACK_COMMAND: .bugcheck ; kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntkrnlpa.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
---------
