描述:
今天在跑备份的时候(Symantec veritas NUB6.0),机器挂死。Symantec公司师无解,无奈只好自己分析dump,分析出来的结果是好像vsp。sys这个驱动,但我不敢确定,所以请大家帮忙看看(这个现象出现了一个出现了4次,都没有解决)
minidup文件分析如下
oading Dump File [C:\Documents and Settings\e000234\桌面\backup issue\Mini120809-02.dmp]Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*c:\localsymbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows Server 2003 Kernel Version 3790 (Service Pack 2) MP (2 procs) Free x86 compatibleProduct: Server, suite: TerminalServer SingleUserTSBuilt by: 3790.srv03_sp2_gdr.080813-1204Machine Name:Kernel base = 0x80800000 PsLoadedModuleList = 0x808a6ea8Debug session time: Tue Dec 8 11:16:59.984 2009 (GMT+8)System Uptime: 0 days 0:28:28.765Loading Kernel Symbols.................................................................................................................Loading User SymbolsLoading unloaded module list.....******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 80, {4f4454, 0, 0, 0}
Probably caused by : ntkrpamp.exe ( nt!KiTrap02+136 )
Followup: MachineOwner---------
1: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
NMI_HARDWARE_FAILURE (80)This is typically due to a hardware malfunction. The hardware supplier shouldbe called.Arguments:Arg1: 004f4454Arg2: 00000000Arg3: 00000000Arg4: 00000000
Debugging Details:------------------
CUSTOMER_CRASH_COUNT: 2
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0x80
PROCESS_NAME: bpbkar32.exe
CURRENT_IRQL: 2
LAST_CONTROL_TRANSFER: from 80a60df7 to 80827c83
STACK_TEXT: f772d2cc 80a60df7 00000080 004f4454 00000000 nt!KeBugCheckEx+0x1bf772d31c 8088a74e 00000000 80897818 8089a9ca hal!HalHandleNMI+0x1a5f772d31c 80a5e3f0 00000000 80897818 8089a9ca nt!KiTrap02+0x136f772d3a0 f78b2d40 ff180010 00000000 00000000 hal!KeAcquireSpinLockRaiseToSynch+0x20WARNING: Frame IP not in any known module. Following frames may be wrong.f772d3a4 ff180010 00000000 00000000 00000000 0xf78b2d40f772d3a8 00000000 00000000 00000000 00000000 0xff180010
STACK_COMMAND: kb
FOLLOWUP_IP: nt!KiTrap02+1368088a74e ff0dd0a98980 dec dword ptr [nt!KiAbiosPresent+0x4c (8089a9d0)]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: nt!KiTrap02+136
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 48a2ac75
FAILURE_BUCKET_ID: 0x80_nt!KiTrap02+136
BUCKET_ID: 0x80_nt!KiTrap02+136
请帮忙分析一下
谢谢
关键是找到NMI中断前CPU所处的状态。不妨尝试执行!pcr看一下CPU的状态;
f772d3a4 ff180010 00000000 00000000 00000000 0xf78b2d40
f772d3a8 00000000 00000000 00000000 00000000 0xff180010
最后两个返回地址(0xf78b2d40、0xff180010)对应不到任何模块么?
尝试.reload; ln 0xf78b2d40
如果需要我帮忙,那么请把转储文件发到我的信箱,需要亲自看一下...