我测试用的机器蓝屏了，dump文件提取后，Windbg分析结果如下:
/////////////////////////////////////////////////////////////////////////////////////////////////////////////Microsoft (R) Windows Debugger Version 6.10.0003.233 X86Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Documents and Settings\dhp\桌面\dump\Mini112508-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: SRV*e:\symbols*http://msdl.microsoft.com/download/symbolsExecutable search path is: Windows XP Kernel Version 2600 (Service Pack 3) MP (8 procs) Free x86 compatibleProduct: WinNt, suite: TerminalServer SingleUserTSBuilt by: 2600.xpsp.080413-2111Machine Name:Kernel base = 0xe0ba3000 PsLoadedModuleList = 0xe0c29720Debug session time: Wed Nov 26 07:35:56.109 2008 (GMT+8)System Uptime: 0 days 0:02:47.718Loading Kernel Symbols............................................................................................................Loading User SymbolsLoading unloaded module list..............******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck 9C, {0, f6076050, b2000040, 800}
Probably caused by : ntkrpamp.exe ( nt!KiIpiStallOnPacketTargets+27 )
Followup: MachineOwner---------
3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************
MACHINE_CHECK_EXCEPTION (9c)A fatal Machine Check Exception has occurred.KeBugCheckEx parameters; x86 Processors If the processor has ONLY MCE feature available (For example Intel Pentium), the parameters are: 1 - Low 32 bits of P5_MC_TYPE MSR 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of P5_MC_ADDR MSR 4 - Low 32 bits of P5_MC_ADDR MSR If the processor also has MCA feature available (For example Intel Pentium Pro), the parameters are: 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the error IA64 Processors 1 - Bugcheck Type 1 - MCA_ASSERT 2 - MCA_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing MCA. 3 - MCA_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing MCA. 4 - MCA_FATAL FW reported a fatal MCA. 5 - MCA_NONFATAL SAL reported a recoverable MCA and we don't support currently support recovery or SAL generated an MCA and then couldn't produce an error record. 0xB - INIT_ASSERT 0xC - INIT_GET_STATEINFO SAL returned an error for SAL_GET_STATEINFO while processing INIT event. 0xD - INIT_CLEAR_STATEINFO SAL returned an error for SAL_CLEAR_STATEINFO while processing INIT event. 0xE - INIT_FATAL Not used. 2 - Address of log 3 - Size of log 4 - Error code in the case of x_GET_STATEINFO or x_CLEAR_STATEINFO AMD64 Processors 1 - Bank number 2 - Address of MCA_EXCEPTION structure 3 - High 32 bits of MCi_STATUS MSR for the MCA bank that had the error 4 - Low 32 bits of MCi_STATUS MSR for the MCA bank that had the errorArguments:Arg1: 00000000Arg2: f6076050Arg3: b2000040Arg4: 00000800
Debugging Details:------------------
NOTE: This is a hardware error. This error was reported by the CPU via Interrupt 18. This analysis will provide more information about the specific error. Please contact the manufacturer for additional information about this error and troubleshooting assistance.
This error is documented in the following publication:
- IA-32 Intel(r) Architecture Software Developer's Manual Volume 3: System Programming Guide
Bit Mask:
MA Model Specific MCA O ID Other Information Error Code Error Code VV SDP ___________|____________ _______|_______ _______|______ AEUECRC| | | | LRCNVVC| | | | ^^^^^^^| | | | 6 5 4 3 2 1 3210987654321098765432109876543210987654321098765432109876543210 ---------------------------------------------------------------- 1011001000000000000000000100000000000000000000000000100000000000
VAL - MCi_STATUS register is valid Indicates that the information contained within the IA32_MCi_STATUS register is valid. When this flag is set, the processor follows the rules given for the OVER flag in the IA32_MCi_STATUS register when overwriting previously valid entries. The processor sets the VAL flag and software is responsible for clearing it.
UC - Error Uncorrected Indicates that the processor did not or was not able to correct the error condition. When clear, this flag indicates that the processor was able to correct the error condition.
EN - Error Enabled Indicates that the error was enabled by the associated EEj bit of the IA32_MCi_CTL register.
PCC - Processor Context Corrupt Indicates that the state of the processor might have been corrupted by the error condition detected and that reliable restarting of the processor may not be possible.
BUSCONNERR - Bus and Interconnect Error BUS{LL}_{PP}_{RRRR}_{II}_{T}_err These errors match the format 0000 1PPT RRRR IILL
Concatenated Error Code: -------------------------- _VAL_UC_EN_PCC_BUSCONNERR_0
This error code can be reported back to the manufacturer. They may be able to provide additional information based upon this error. All questions regarding STOP 0x9C should be directed to the hardware manufacturer.
BUGCHECK_STR: 0x9C_GenuineIntel
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT
PROCESS_NAME: System
LAST_CONTROL_TRANSFER: from e0b87bfb to e0bc5f33
STACK_TEXT: f6076028 e0b87bfb 0000009c 00000000 f6076050 nt!KeBugCheckEx+0x1bf6076154 e0b82c52 f6072d70 00000000 00000000 hal!HalpMcaExceptionHandler+0xddf6076154 e0bcdf81 f6072d70 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4af623dbc8 e0bc7545 000000f7 0a752921 c06211d8 nt!KiIpiStallOnPacketTargets+0x27f623dbe8 e0bd3fac c423b000 00000000 00000001 nt!KeFlushSingleTb+0xc3f623dc74 e0bb04bd c423c000 01001000 00000000 nt!MmSetAddressRangeModified+0x12ef623dcf0 e0bb08b5 00001000 00000000 00000001 nt!CcFlushCache+0x319f623dd34 e0bb30cb fcd02090 e0c30820 fccccb30 nt!CcWriteBehind+0x119f623dd7c e0c0476d fcd02090 00000000 fccccb30 nt!CcWorkerThread+0x12ff623ddac e0c9bf64 fcd02090 00000000 00000000 nt!ExpWorkerThread+0xeff623dddc e0c120de e0c0467e 00000000 00000000 nt!PspSystemThreadStartup+0x3400000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
STACK_COMMAND: kb
FOLLOWUP_IP: nt!KiIpiStallOnPacketTargets+27e0bcdf81 833a00 cmp dword ptr [edx],0
SYMBOL_STACK_INDEX: 3
SYMBOL_NAME: nt!KiIpiStallOnPacketTargets+27
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrpamp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 4802516a
FAILURE_BUCKET_ID: 0x9C_GenuineIntel_nt!KiIpiStallOnPacketTargets+27
BUCKET_ID: 0x9C_GenuineIntel_nt!KiIpiStallOnPacketTargets+27
3: kd> .threadImplicit thread is now fccccb303: kd> !thread fccccb30GetPointerFromAddress: unable to read from e0c2e134THREAD fccccb30 Cid 0004.0020 Teb: 00000000 Win32Thread: 00000000 RUNNING on processor 3Not impersonatingGetUlongFromAddress: unable to read from e0c2e1ccOwning Process fcccea00 Image: SystemAttached Process N/A Image: N/Affdf0000: Unable to get shared dataWait Start TickCount 10321 Context Switch Count 1886 ReadMemory error: Cannot get nt!KeMaximumIncrement value.UserTime 00:00:00.000KernelTime 00:00:00.000Start Address nt!ExpWorkerThread (0xe0c0467e)Stack Init f623e000 Current f623d544 Base f623e000 Limit f623b000 Call 0Priority 13 BasePriority 13 PriorityDecrement 0 DecrementCount 16ChildEBP RetAddr Args to Child f6076028 e0b87bfb 0000009c 00000000 f6076050 nt!KeBugCheckEx+0x1b (FPO: [5,0,0])f6076154 e0b82c52 f6072d70 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd (FPO: [0,65,4])f6076154 e0bcdf81 f6072d70 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a (FPO: TSS 28:0)f623dbc8 e0bc7545 000000f7 0a752921 c06211d8 nt!KiIpiStallOnPacketTargets+0x27 (FPO: [1,0,0])f623dbe8 e0bd3fac c423b000 00000000 00000001 nt!KeFlushSingleTb+0xc3 (FPO: [6,3,0])f623dc74 e0bb04bd c423c000 01001000 00000000 nt!MmSetAddressRangeModified+0x12e (FPO: [2,24,4])f623dcf0 e0bb08b5 00001000 00000000 00000001 nt!CcFlushCache+0x319 (FPO: [4,24,4])f623dd34 e0bb30cb fcd02090 e0c30820 fccccb30 nt!CcWriteBehind+0x119 (FPO: [0,8,4])f623dd7c e0c0476d fcd02090 00000000 fccccb30 nt!CcWorkerThread+0x12f (FPO: [Non-Fpo])f623ddac e0c9bf64 fcd02090 00000000 00000000 nt!ExpWorkerThread+0xef (FPO: [1,6,0])f623dddc e0c120de e0c0467e 00000000 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo])00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16
3: kd> dt nt!_KTHREAD fccccb30 +0x000 Header : _DISPATCHER_HEADER +0x010 MutantListHead : _LIST_ENTRY [ 0xfccccb40 - 0xfccccb40 ] +0x018 InitialStack : 0xf623e000 +0x01c StackLimit : 0xf623b000 +0x020 Teb : (null) +0x024 TlsArray : (null) +0x028 KernelStack : 0xf623d544 +0x02c DebugActive : 0 '' +0x02d State : 0x2 '' +0x02e Alerted : [2] "" +0x030 Iopl : 0 '' +0x031 NpxState : 0xa '' +0x032 Saturation : 0 '' +0x033 Priority : 13 '' +0x034 ApcState : _KAPC_STATE +0x04c ContextSwitches : 0x75e +0x050 IdleSwapBlock : 0 '' +0x051 Spare0 : [3] "" +0x054 WaitStatus : 0 +0x058 WaitIrql : 0 '' +0x059 WaitMode : 0 '' +0x05a WaitNext : 0 '' +0x05b WaitReason : 0x13 '' +0x05c WaitBlockList : 0xfccccba0 _KWAIT_BLOCK +0x060 WaitListEntry : _LIST_ENTRY [ 0x0 - 0xe0c1d204 ] +0x060 SwapListEntry : _SINGLE_LIST_ENTRY +0x068 WaitTime : 0x2851 +0x06c BasePriority : 13 '' +0x06d DecrementCount : 0x10 '' +0x06e PriorityDecrement : 0 '' +0x06f Quantum : 6 '' +0x070 WaitBlock : [4] _KWAIT_BLOCK +0x0d0 LegoData : (null) +0x0d4 KernelApcDisable : 0 +0x0d8 UserAffinity : 0xff +0x0dc SystemAffinityActive : 0 '' +0x0dd PowerState : 0 '' +0x0de NpxIrql : 0 '' +0x0df InitialNode : 0 '' +0x0e0 ServiceTable : 0xe0c28700 +0x0e4 Queue : 0xe0c30820 _KQUEUE +0x0e8 ApcQueueLock : 0 +0x0f0 Timer : _KTIMER +0x118 QueueListEntry : _LIST_ENTRY [ 0xfbbb5138 - 0xfccccec0 ] +0x120 SoftAffinity : 0xff +0x124 Affinity : 0xff +0x128 Preempted : 0 '' +0x129 ProcessReadyQueue : 0 '' +0x12a KernelStackResident : 0x1 '' +0x12b NextProcessor : 0x3 '' +0x12c CallbackStack : (null) +0x130 Win32Thread : (null) +0x134 TrapFrame : (null) +0x138 ApcStatePointer : [2] 0xfccccb64 _KAPC_STATE +0x140 PreviousMode : 0 '' +0x141 EnableStackSwap : 0x1 '' +0x142 LargeStack : 0 '' +0x143 ResourceIndex : 0x1 '' +0x144 KernelTime : 5 +0x148 UserTime : 0 +0x14c SavedApcState : _KAPC_STATE +0x164 Alertable : 0 '' +0x165 ApcStateIndex : 0 '' +0x166 ApcQueueable : 0x1 '' +0x167 AutoAlignment : 0 '' +0x168 StackBase : 0xf623e000 +0x16c SuspendApc : _KAPC +0x19c SuspendSemaphore : _KSEMAPHORE +0x1b0 ThreadListEntry : _LIST_ENTRY [ 0xfcccca68 - 0xfccccf58 ] +0x1b8 FreezeCount : 0 '' +0x1b9 SuspendCount : 0 '' +0x1ba IdealProcessor : 0x3 '' +0x1bb DisableBoost : 0 ''3: kd> .processImplicit process is now fcccea003: kd> dt nt!_EPROCESS fcccea00 +0x000 Pcb : _KPROCESS +0x06c ProcessLock : _EX_PUSH_LOCK +0x070 CreateTime : _LARGE_INTEGER 0x0 +0x078 ExitTime : _LARGE_INTEGER 0x0 +0x080 RundownProtect : _EX_RUNDOWN_REF +0x084 UniqueProcessId : 0x00000004 +0x088 ActiveProcessLinks : _LIST_ENTRY [ 0xfc08ca00 - 0xe0c2f8b8 ] +0x090 QuotaUsage : [3] 0 +0x09c QuotaPeak : [3] 0 +0x0a8 CommitCharge : 7 +0x0ac PeakVirtualSize : 0x6bc000 +0x0b0 VirtualSize : 0x1e3000 +0x0b4 SessionProcessLinks : _LIST_ENTRY [ 0x0 - 0x0 ] +0x0bc DebugPort : (null) +0x0c0 ExceptionPort : (null) +0x0c4 ObjectTable : 0xe1003e68 _HANDLE_TABLE +0x0c8 Token : _EX_FAST_REF +0x0cc WorkingSetLock : _FAST_MUTEX +0x0ec WorkingSetPage : 0x93c6 +0x0f0 AddressCreationLock : _FAST_MUTEX +0x110 HyperSpaceLock : 0 +0x114 ForkInProgress : (null) +0x118 HardwareTrigger : 0 +0x11c VadRoot : 0xfccce838 +0x120 VadHint : 0xfccce838 +0x124 CloneRoot : (null) +0x128 NumberOfPrivatePages : 3 +0x12c NumberOfLockedPages : 0 +0x130 Win32Process : (null) +0x134 Job : (null) +0x138 SectionObject : (null) +0x13c SectionBaseAddress : (null) +0x140 QuotaBlock : 0xe0c2f960 _EPROCESS_QUOTA_BLOCK +0x144 WorkingSetWatch : (null) +0x148 Win32WindowStation : (null) +0x14c InheritedFromUniqueProcessId : (null) +0x150 LdtInformation : (null) +0x154 VadFreeHint : 0xfc1ab3f0 +0x158 VdmObjects : (null) +0x15c DeviceMap : 0xe1003150 +0x160 PhysicalVadList : _LIST_ENTRY [ 0xfccceb60 - 0xfccceb60 ] +0x168 PageDirectoryPte : _HARDWARE_PTE +0x168 Filler : 0 +0x170 Session : (null) +0x174 ImageFileName : [16] "System" +0x184 JobLinks : _LIST_ENTRY [ 0x0 - 0x0 ] +0x18c LockedPagesList : (null) +0x190 ThreadListHead : _LIST_ENTRY [ 0xfccce804 - 0xfbb7ed5c ] +0x198 SecurityPort : 0xe19e3898 +0x19c PaeTop : 0xf6394020 +0x1a0 ActiveThreads : 0x48 +0x1a4 GrantedAccess : 0x1f0fff +0x1a8 DefaultHardErrorProcessing : 1 +0x1ac LastThreadExitStatus : 0 +0x1b0 Peb : (null) +0x1b4 PrefetchTrace : _EX_FAST_REF +0x1b8 ReadOperationCount : _LARGE_INTEGER 0x7a +0x1c0 WriteOperationCount : _LARGE_INTEGER 0x1de +0x1c8 OtherOperationCount : _LARGE_INTEGER 0xdae +0x1d0 ReadTransferCount : _LARGE_INTEGER 0x107b30 +0x1d8 WriteTransferCount : _LARGE_INTEGER 0x337e00 +0x1e0 OtherTransferCount : _LARGE_INTEGER 0x6eb94 +0x1e8 CommitChargeLimit : 0 +0x1ec CommitChargePeak : 0x5d1 +0x1f0 AweInfo : (null) +0x1f4 SeAuditProcessCreationInfo : _SE_AUDIT_PROCESS_CREATION_INFO +0x1f8 Vm : _MMSUPPORT +0x238 LastFaultCount : 0 +0x23c ModifiedPageCount : 0x7bb +0x240 NumberOfVads : 5 +0x244 JobStatus : 0 +0x248 Flags : 0x40800 +0x248 CreateReported : 0y0 +0x248 NoDebugInherit : 0y0 +0x248 ProcessExiting : 0y0 +0x248 ProcessDelete : 0y0 +0x248 Wow64SplitPages : 0y0 +0x248 VmDeleted : 0y0 +0x248 OutswapEnabled : 0y0 +0x248 Outswapped : 0y0 +0x248 ForkFailed : 0y0 +0x248 HasPhysicalVad : 0y0 +0x248 AddressSpaceInitialized : 0y10 +0x248 SetTimerResolution : 0y0 +0x248 BreakOnTermination : 0y0 +0x248 SessionCreationUnderway : 0y0 +0x248 WriteWatch : 0y0 +0x248 ProcessInSession : 0y0 +0x248 OverrideAddressSpace : 0y0 +0x248 HasAddressSpace : 0y1 +0x248 LaunchPrefetched : 0y0 +0x248 InjectInpageErrors : 0y0 +0x248 VmTopDown : 0y0 +0x248 Unused3 : 0y0 +0x248 Unused4 : 0y0 +0x248 VdmAllowed : 0y0 +0x248 Unused : 0y00000 (0) +0x248 Unused1 : 0y0 +0x248 Unused2 : 0y0 +0x24c ExitStatus : 259 +0x250 NextPageColor : 0xec8c +0x252 SubSystemMinorVersion : 0 '' +0x253 SubSystemMajorVersion : 0 '' +0x252 SubSystemVersion : 0 +0x254 PriorityClass : 0x2 '' +0x255 WorkingSetAcquiredUnsafe : 0 '' +0x258 Cookie : ??Memory read error fcccec583: kd> kvChildEBP RetAddr Args to Child f6076028 e0b87bfb 0000009c 00000000 f6076050 nt!KeBugCheckEx+0x1b (FPO: [5,0,0])f6076154 e0b82c52 f6072d70 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd (FPO: [0,65,4])f6076154 e0bcdf81 f6072d70 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x4a (FPO: TSS 28:0)f623dbc8 e0bc7545 000000f7 0a752921 c06211d8 nt!KiIpiStallOnPacketTargets+0x27 (FPO: [1,0,0])f623dbe8 e0bd3fac c423b000 00000000 00000001 nt!KeFlushSingleTb+0xc3 (FPO: [6,3,0])f623dc74 e0bb04bd c423c000 01001000 00000000 nt!MmSetAddressRangeModified+0x12e (FPO: [2,24,4])f623dcf0 e0bb08b5 00001000 00000000 00000001 nt!CcFlushCache+0x319 (FPO: [4,24,4])f623dd34 e0bb30cb fcd02090 e0c30820 fccccb30 nt!CcWriteBehind+0x119 (FPO: [0,8,4])f623dd7c e0c0476d fcd02090 00000000 fccccb30 nt!CcWorkerThread+0x12f (FPO: [Non-Fpo])f623ddac e0c9bf64 fcd02090 00000000 00000000 nt!ExpWorkerThread+0xef (FPO: [1,6,0])f623dddc e0c120de e0c0467e 00000000 00000000 nt!PspSystemThreadStartup+0x34 (FPO: [Non-Fpo])00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x163: kd> kChildEBP RetAddr f6076028 e0b87bfb nt!KeBugCheckEx+0x1bf6076154 e0b82c52 hal!HalpMcaExceptionHandler+0xddf6076154 e0bcdf81 hal!HalpMcaExceptionHandlerWrapper+0x4af623dbc8 e0bc7545 nt!KiIpiStallOnPacketTargets+0x27f623dbe8 e0bd3fac nt!KeFlushSingleTb+0xc3f623dc74 e0bb04bd nt!MmSetAddressRangeModified+0x12ef623dcf0 e0bb08b5 nt!CcFlushCache+0x319f623dd34 e0bb30cb nt!CcWriteBehind+0x119f623dd7c e0c0476d nt!CcWorkerThread+0x12ff623ddac e0c9bf64 nt!ExpWorkerThread+0xeff623dddc e0c120de nt!PspSystemThreadStartup+0x3400000000 00000000 nt!KiThreadStartup+0x163: kd> ln e0b87bfb(e0b87b1e) hal!HalpMcaExceptionHandler+0xdd | (e0b87d0e) hal!HalHandleNMI//////////////////////////////////////////////////////////////////////////////////////////////////////////
以上结果查了一下Intel的手册也没分析出来具体原因。google了一下，说是电源、内存、CPU或者硬盘可能有缺陷。对它们也进行了各种检测和压力测试，没发现问题。哪位大侠帮忙看看，有什么办法找到蓝屏的原因。