【现象】
1、Windows XP系统启动后，大概15S后就蓝屏，蓝屏代码：BugCheck 8E, {c0000005, 8057d60c, f798b9cc, 0}
2、进入安全模式，能够正常启动并使用，不会蓝屏。
3、附件为核心转存的DUMP信息，请各位大大们指点一下，如能把分析方法告知，不胜感激。
4、DUMP文件见2楼。
【DUMP文件内容】
Kernel Summary Dump File: Only kernel address space is available
Symbol search path is: SRV*D:\Program Files (x86)\Debugging Tools for Windows (x86)\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows XP Kernel Version 2600 (Service Pack 3) MP (2 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer EmbeddedNT SingleUserTS
Built by: 2600.xpsp_sp3_qfe.090206-1316
Machine Name:
Kernel base = 0x804dd000 PsLoadedModuleList = 0x805694c0
Debug session time: Sat Dec 31 15:38:51.750 2011 (GMT+8)
System Uptime: 0 days 0:00:48.437
Loading Kernel Symbols
...............................................................
.........................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 8E, {c0000005, 8057d60c, f798b9cc, 0}
Page bfea not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
Probably caused by : ntkrnlmp.exe ( nt!HvpGetCellMapped+5f )
KERNEL_MODE_EXCEPTION_NOT_HANDLED (8e)
This is a very common bugcheck. Usually the exception address pinpoints
the driver/function that caused the problem. Always note this address
as well as the link date of the driver/image that contains this address.
Some common problems are exception code 0x80000003. This means a hard
coded breakpoint or assertion was hit, but this system was booted
/NODEBUG. This is not supposed to happen as developers should never have
hardcoded breakpoints in retail code, but ...
If this happens, make sure a debugger gets connected, and the
system is booted /DEBUG. This will let us see why this breakpoint is
happening.
Arguments:
Arg1: c0000005, The exception code that was not handled
Arg2: 8057d60c, The address that the exception occurred at
Arg3: f798b9cc, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
Page bfea not present in the dump file. Type ".hh dbgerr004" for details
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
PEB is paged out (Peb.Ldr = 7ffd700c). Type ".hh dbgerr001" for details
