蓝屏代码 0X0000008E，用windbg查了一下，内容如下。请高手指点！
Microsoft (R) Windows Debugger Version 6.6.0007.5
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\WINDOWS\Minidump\Mini090511-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*d:\temp*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
Built by: 2600.xpsp_sp3_qfe.101209-1646
Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055d720
Debug session time: Mon Sep 5 19:10:48.812 2011 (GMT+10)
System Uptime: 0 days 0:00:36.484
Loading Kernel Symbols
............................................................................................................................
Loading User Symbols
Loading unloaded module list
......
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 1000008E, {c0000005, f72ca4f5, f778cbac, 0}
Probably caused by : hardware ( Ntfs!NtfsInitializeTopLevelIrp+8b )
Followup: MachineOwner
---------
1: kd> !analyze -v
*******************************************************************************
*
*
* Bugcheck Analysis
*
*
*
*******************************************************************************
KERNEL_MODE_EXCEPTION_NOT_HANDLED_M (1000008e)
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: f72ca4f5, The address that the exception occurred at
Arg3: f778cbac, Trap Frame
Arg4: 00000000
Debugging Details:
------------------
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at "0x%08lx" referenced memory at "0x%08lx". The memory could not be "%s".
FAULTING_IP:
Ntfs!NtfsInitializeTopLevelIrp+8b
f72ca4f5 ff8958148808 dec dword ptr [ecx+8881458h]
TRAP_FRAME: f778cbac -- (.trap fffffffff778cbac)
Unable to read trap frame at f778cbac
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
BUGCHECK_STR: 0x8E
MISALIGNED_IP:
Ntfs!NtfsInitializeTopLevelIrp+8b
f72ca4f5 ff8958148808 dec dword ptr [ecx+8881458h]
LAST_CONTROL_TRANSFER: from 2ccf59f7 to f72ca4f5
STACK_TEXT:
f778cc2f 2ccf59f7 78cc50f7 000001f7 00000100 Ntfs!NtfsInitializeTopLevelIrp+0x8b
WARNING: Frame IP not in any known module. Following frames may be wrong.
f778cc3f 92a3a000 fc3cf886 76930086 00000086 0x2ccf59f7
f778cc43 fc3cf886 76930086 00000086 00000000 0x92a3a000
f778cc47 76930086 00000086 00000000 00000000 0xfc3cf886
f778cc4b 00000000 00000000 00000000 00000000 0x76930086
STACK_COMMAND: kb
FOLLOWUP_IP:
Ntfs!NtfsInitializeTopLevelIrp+8b
f72ca4f5 ff8958148808 dec dword ptr [ecx+8881458h]
SYMBOL_STACK_INDEX: 0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: hardware
DEBUG_FLR_IMAGE_TIMESTAMP: 0
SYMBOL_NAME: Ntfs!NtfsInitializeTopLevelIrp+8b
MODULE_NAME: hardware
FAILURE_BUCKET_ID: IP_MISALIGNED
BUCKET_ID: IP_MISALIGNED
Followup: MachineOwner
