none
系统老是蓝屏的快吐血了,发dmp上来。希望有热心的高手帮忙分析下。谢谢 RRS feed

  • 问题


  • Microsoft (R) Windows Debugger Version 6.11.0001.402 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\Documents and Settings\Ryanwang.WICRESOFT\My Documents\New Folder (2)\Mini022809-04.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: *** Invalid ***
    ****************************************************************************
    * Symbol loading may be unreliable without a symbol search path.           *
    * Use .symfix to have the debugger choose a symbol path.                   *
    * After setting your symbol path, use .reload to refresh symbol locations. *
    ****************************************************************************
    Executable search path is:
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt, suite: TerminalServer SingleUserTS Personal
    Machine Name:
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055b6a0
    Debug session time: Sat Feb 28 16:12:24.657 2009 (GMT+8)
    System Uptime: 0 days 0:27:32.012
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Unable to load image ntoskrnl.exe, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for ntoskrnl.exe
    *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exe
    Loading Kernel Symbols
    ...............................................................
    .................................................
    Loading User Symbols
    Loading unloaded module list
    .............
    *** WARNING: Unable to verify timestamp for hal.dll
    *** ERROR: Module load completed but symbols could not be loaded for hal.dll
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9C, {0, 8054e5f0, cc0000ff, 20040189}

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    Probably caused by : ntoskrnl.exe ( nt+5c56e )

    Followup: MachineOwner
    ---------

    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 error
    Arguments:
    Arg1: 00000000
    Arg2: 8054e5f0
    Arg3: cc0000ff
    Arg4: 20040189

    Debugging Details:
    ------------------

    ***** Kernel symbols are WRONG. Please fix symbols to do analysis.

       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
       ----------------------------------------------------------------
       1100110000000000000000001111111100100000000001000000000110001001


    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.

    OVER  - Error Overflow
            Indicates that a machine check error occurred while the results of a
            previous error were still in the error-reporting register bank (that
            is, the VAL bit was already set in the IA32_MCi_STATUS register).
            the processor sets the OVER flag and software is responsible for
            clearing it.  Enabled errors are written over disabled errors, and
            uncorrected errors are written over corrected errors.  Uncorrected
            errors are not written over previous valid uncorrected errors.

    MISCV - IA32_MCi_MISC Register Valid
            Indicates that the IA32_MCi_MISC register contains additional
            information regarding the error.  When clear, this flag indicates
            that the IA32_MCi_MISC register is either not implemented or does
            not contain additional information regarding the error.

    ADDRV - IA32_MCi_ADDR register valid
            Indicates that the IA32_MCi_ADDR register contains the address where
            the error occurred.

    MEMHIRERR - Memory Hierarchy Error   {TT}CACHE{LL}_{RRRR}_ERR
            These errors match the format 0000 0001 RRRR TTLL



       Concatenated Error Code:
       --------------------------
       _VAL_OVER_MISCV_ADDRV_MEMHIRERR_89

       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.
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!KPRCB                                      ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    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: nt!_KPRCB                                     ***
    ***                                                                   ***
    *************************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************
    *********************************************************************
    * Symbols can not be loaded because symbol path is not initialized. *
    *                                                                   *
    * The Symbol Path can be set by:                                    *
    *   using the _NT_SYMBOL_PATH environment variable.                 *
    *   using the -y <symbol_path> argument when starting the debugger. *
    *   using .sympath and .sympath+                                    *
    *********************************************************************

    ADDITIONAL_DEBUG_TEXT: 
    Use '!findthebuild' command to search for the target build information.
    If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

    MODULE_NAME: nt

    FAULTING_MODULE: 804d8000 nt

    DEBUG_FLR_IMAGE_TIMESTAMP:  48a4023c

    BUGCHECK_STR:  0x9C_GenuineIntel

    CUSTOMER_CRASH_COUNT:  4

    DEFAULT_BUCKET_ID:  COMMON_SYSTEM_FAULT

    LAST_CONTROL_TRANSFER:  from 806f0faf to 8053456e

    STACK_TEXT: 
    WARNING: Stack unwind information not available. Following frames may be wrong.
    8054e5c8 806f0faf 0000009c 00000000 8054e5f0 nt+0x5c56e
    8054e6f4 806edcae 80042000 00000000 00000000 hal+0x3faf
    00000000 00000000 00000000 00000000 00000000 hal+0xcae


    STACK_COMMAND:  kb

    FOLLOWUP_IP:
    nt+5c56e
    8053456e 5d              pop     ebp

    SYMBOL_STACK_INDEX:  0

    SYMBOL_NAME:  nt+5c56e

    FOLLOWUP_NAME:  MachineOwner

    IMAGE_NAME:  ntoskrnl.exe

    BUCKET_ID:  WRONG_SYMBOLS

    Followup: MachineOwner
    ---------



    2009年3月3日 1:34

全部回复

  • 这是硬件故障,检查 CPU、内存、显卡等有没有超频,有的话先恢复默认频率。同时改善一下机箱通风散热情况,检查有没有热量不能及时排出的问题。
    Alexis Zhang (Microsoft MVP 2004' 2007' 2008')
    2009年3月3日 2:27
    版主
  •   Your debugger is not using the correct symbols 
    你没有导入正确的SYMBOLS所以分析都是错误的!

    请按照以下步骤:

    首先下载windebug

     

    http://www.microsoft.com/whdc/devtools/debugging/installx86.mspx

    说下debug方法
    1.
    我的电脑,属性->高级->启动,最下面的内存调试选最后一项的全部,确定后重新启动
    2.
    蓝屏后不要急着重启,系统会保存整个内存内容,然后会自动重启
    3.
    找到C:\Windows\Minidump\

    4. 下载安装windwos debug tools, 我这有下载地址,或微软网站
    http://public.hshh.org/SysTools/debug/dbg_x86_6.6.07.5.exe
    5.
    安装后创建一个临时目录,例如 c:\temp
    6.
    启动 windbg
    7. windbg
    界面: file->symbol file path (ctrl+s) 输入:
    SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    然后确定
    8. windbg
    界面: file->open crash dump(ctrl+d),打开9. 打开例如C:\Windows\Minidump\Mini122208-01.dmp后,等待提示
    当出现 Use !analyze -v to get detailed debugging information. 字样后,在下面输入框
    !analyze -v
    10.
    等待分析完毕,可以知道什么导致的出错
    11. windbg
    使用中需要网上下载调试内容,这个速度嘛,取决于你的网络了。

    -----------------------------------------------------------------------

     

    你把敲完!analyze -v后的信息发上来!

     


    Microsoft Certified Systems Engineer 如果您觉得对您有帮助,请在“是否有帮助”点“是”;如果你觉得回复很满意,请“标记为已解答”
    2009年3月3日 3:07
  •  thanks

    :)
    ========
    Microsoft (R) Windows Debugger Version 6.11.0001.404 X86
    Copyright (c) Microsoft Corporation. All rights reserved.


    Loading Dump File [C:\WINDOWS\Minidump\Mini030709-01.dmp]
    Mini Kernel Dump File: Only registers and stack trace are available

    Symbol search path is: SRV*c:\temp*http://msdl.microsoft.com/download/symbols
    Executable search path is:
    Windows XP Kernel Version 2600 (Service Pack 2) UP Free x86 compatible
    Product: WinNt
    Built by: 2600.xpsp_sp2_gdr.080814-1233
    Machine Name:
    Kernel base = 0x804d8000 PsLoadedModuleList = 0x8055b6a0
    Debug session time: Sat Mar  7 12:39:52.075 2009 (GMT+8)
    System Uptime: 0 days 0:31:07.673
    Loading Kernel Symbols
    .

    Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
    Run !sym noisy before .reload to track down problems loading symbols.

    ..............................................................
    ................................................
    Loading User Symbols
    Loading unloaded module list
    ..............
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 9C, {0, 8054e5f0, cc0000ff, 20040189}

    Probably caused by : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

    Followup: MachineOwner
    ---------

    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 error
    Arguments:
    Arg1: 00000000
    Arg2: 8054e5f0
    Arg3: cc0000ff
    Arg4: 20040189

    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
       ----------------------------------------------------------------
       1100110000000000000000001111111100100000000001000000000110001001


    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.

    OVER  - Error Overflow
            Indicates that a machine check error occurred while the results of a
            previous error were still in the error-reporting register bank (that
            is, the VAL bit was already set in the IA32_MCi_STATUS register).
            the processor sets the OVER flag and software is responsible for
            clearing it.  Enabled errors are written over disabled errors, and
            uncorrected errors are written over corrected errors.  Uncorrected
            errors are not written over previous valid uncorrected errors.

    MISCV - IA32_MCi_MISC Register Valid
            Indicates that the IA32_MCi_MISC register contains additional
            information regarding the error.  When clear, this flag indicates
            that the IA32_MCi_MISC register is either not implemented or does
            not contain additional information regarding the error.

    ADDRV - IA32_MCi_ADDR register valid
            Indicates that the IA32_MCi_ADDR register contains the address where
            the error occurred.

    MEMHIRERR - Memory Hierarchy Error   {TT}CACHE{LL}_{RRRR}_ERR
            These errors match the format 0000 0001 RRRR TTLL



       Concatenated Error Code:
       --------------------------
       _VAL_OVER_MISCV_ADDRV_MEMHIRERR_89

       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

    LAST_CONTROL_TRANSFER:  from 806f0faf to 8053456e

    STACK_TEXT: 
    8054e5c8 806f0faf 0000009c 00000000 8054e5f0 nt!KeBugCheckEx+0x1b
    8054e6f4 806edcae 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
    8054e6f4 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x46


    STACK_COMMAND:  kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  0x9C_GenuineIntel_ANALYSIS_INCONCLUSIVE

    BUCKET_ID:  0x9C_GenuineIntel_ANALYSIS_INCONCLUSIVE

    Followup: MachineOwner
    ---------

    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    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 error
    Arguments:
    Arg1: 00000000
    Arg2: 8054e5f0
    Arg3: cc0000ff
    Arg4: 20040189

    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
       ----------------------------------------------------------------
       1100110000000000000000001111111100100000000001000000000110001001


    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.

    OVER  - Error Overflow
            Indicates that a machine check error occurred while the results of a
            previous error were still in the error-reporting register bank (that
            is, the VAL bit was already set in the IA32_MCi_STATUS register).
            the processor sets the OVER flag and software is responsible for
            clearing it.  Enabled errors are written over disabled errors, and
            uncorrected errors are written over corrected errors.  Uncorrected
            errors are not written over previous valid uncorrected errors.

    MISCV - IA32_MCi_MISC Register Valid
            Indicates that the IA32_MCi_MISC register contains additional
            information regarding the error.  When clear, this flag indicates
            that the IA32_MCi_MISC register is either not implemented or does
            not contain additional information regarding the error.

    ADDRV - IA32_MCi_ADDR register valid
            Indicates that the IA32_MCi_ADDR register contains the address where
            the error occurred.

    MEMHIRERR - Memory Hierarchy Error   {TT}CACHE{LL}_{RRRR}_ERR
            These errors match the format 0000 0001 RRRR TTLL



       Concatenated Error Code:
       --------------------------
       _VAL_OVER_MISCV_ADDRV_MEMHIRERR_89

       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

    LAST_CONTROL_TRANSFER:  from 806f0faf to 8053456e

    STACK_TEXT: 
    8054e5c8 806f0faf 0000009c 00000000 8054e5f0 nt!KeBugCheckEx+0x1b
    8054e6f4 806edcae 80042000 00000000 00000000 hal!HalpMcaExceptionHandler+0xdd
    8054e6f4 00000000 80042000 00000000 00000000 hal!HalpMcaExceptionHandlerWrapper+0x46


    STACK_COMMAND:  kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  0x9C_GenuineIntel_ANALYSIS_INCONCLUSIVE

    BUCKET_ID:  0x9C_GenuineIntel_ANALYSIS_INCONCLUSIVE

    Followup: MachineOwner
    ---------

    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd>
    Implicit thread is now 81fbf3c0
    kd> Microsoft (R) Windows Debugger Version 6.11.0001.404 X86

    2009年3月9日 2:20
  • 疑似系统文件加载出错,请先排除是否病毒破坏或可用XP光盘启动进行系统修复试试哦
    2009年3月9日 2:24
  •  感谢大家的帮助,重装了一次系统。系统仍旧不断重启蓝屏
    2009年3月16日 1:26
  •  上面说是因为CPU的问题要你联系厂家!
    但是我觉得你最好安装64位的操作系统在试试!你的CPU是64位的
    Microsoft Certified Systems Engineer 如果您觉得对您有帮助,请在“是否有帮助”点“是”;如果你觉得回复很满意,请“标记为已解答”
    2009年3月16日 6:50
  • 新装系统也蓝屏的话
     用工具检测内存是否有坏块,硬盘是否有坏道,电源替换的试试
    2009年3月18日 8:12
  • 应该对你的计算机硬件做全面体检,比如做详尽的清洁工作,然后检查一下主板元件,电源,CPU及散热器,内存,硬盘等等!必要的话对主板放电(重置CMOS参数),怀疑硬盘的话可以做一下低级格式化!
    然后重新安装系统(最好使用原版安装光盘,不建议使用论坛版系统)!
    Li Guoping
    2009年3月19日 14:47