longhorn系统下的minidump文件
使用kd进行分析时,总出现符号错误,如下:
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Signature :
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
Revision : 0x0000
我尝试过的方法:
1. 分别在winxp和longhorn系统下,安装retail和check版的longhorn符号表,用kd分析。
2. 在xp下,指定microsoft的symbol服务器
kd> .sympath srv*c:\symbols*http://msdl.microsoft.com/download/symbols
结果问题依旧,只不过使用symbol服务器后,会比前者多得到一些有用的信息(似乎有一部分符号是正确的)。
另外,longhorn下引入WHEA机制报告硬件错误,看了ddk文档也不知道WHEARecord能提供什么有用的debug信息,请高手指点。
换个问题:大家通过下面的信息能看出什么问题吗?
----------------------------------------------------------------
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
WHEA_UNCORRECTABLE_ERROR (124)
A fatal hardware error has occurred. Parameter 1 identifies the type of error
source that reported the error. Parameter 2 holds the address of the
WHEA_ERROR_RECORD structure that describes the error conditon.
Arguments:
Arg1: 0000000000000000, MCA_ASSERT
Arg2: fffffa800885f030, Address of WHEA_ERROR_RECORD structure
Arg3: 00000000f6002000, High 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
Arg4: 0000000000000853, Low 32 bits of MCi_STATUS MSR for the MCA bank that had
the error
Debugging Details:
------------------
WHEA_ERROR_RECORD: !errrec fffffa800885f030
!errrec fffffa800885f030
Error Record @ FFFFFA800885F030
*************************************************************************
*** ***
*** ***
*** 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: pshed!_WHEA_ERROR_RECORD_HEADER ***
*** ***
*************************************************************************
... ...
FRU Text : CPER????
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x124
PROCESS_NAME: Test.exe
CURRENT_IRQL: f
LAST_CONTROL_TRANSFER: from 0000000000000000 to fffff80001643d10
STACK_TEXT:
fffff800`03667c18 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+43d10
fffff800`01643d10 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 46259a4f
SYMBOL_NAME: nt+43d10
FAILURE_BUCKET_ID: X64_0x124_nt+43d10
BUCKET_ID: X64_0x124_nt+43d10
Followup: MachineOwner
俺是在系统变量里设置_NT_SYMBOL_PATH为C:\WINDOWS\Symbols;SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
一般不会出错的
信息太少,几乎没法分析,加载正确的symbols试试