none
Windows Server 2008 R2 蓝屏故障分析 RRS feed

  • 常规讨论

  • 请问一下这样的蓝屏故障是什么原因造成的呢? 谢谢。

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

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


    Loading Dump File [C:\Users\admin.gao\Desktop\MEMORY.DMP]
    Kernel Summary Dump File: Only kernel address space is 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 read NT module Base Name string at 00006b76`ffffffe8 - NTSTATUS 0xC0000147
    Missing image name, possible paged-out or corrupt data.
    *** WARNING: Unable to verify timestamp for Unknown_Module_00006b76`ffffffe8
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00006b76`ffffffe8
    Debugger can not determine kernel base address
    Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x64
    Product: Server, suite: TerminalServer DataCenter SingleUserTS
    Built by: 7601.18409.amd64fre.win7sp1_gdr.140303-2144
    Machine Name:
    Kernel base = 0xfffff800`0185b000 PsLoadedModuleList = 0xfffff800`01a9e890
    Debug session time: Fri Jun 27 16:40:33.655 2014 (UTC + 8:00)
    System Uptime: 0 days 6:42:04.537
    *********************************************************************
    * 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 read NT module Base Name string at 00006b76`ffffffe8 - NTSTATUS 0xC0000147
    Missing image name, possible paged-out or corrupt data.
    *** WARNING: Unable to verify timestamp for Unknown_Module_00006b76`ffffffe8
    *** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00006b76`ffffffe8
    Debugger can not determine kernel base address
    Loading Kernel Symbols
    Unable to read NT module Base Name string at 00006b76`ffffffe8 - NTSTATUS 0xC0000147
    Missing image name, possible paged-out or corrupt data.
    .Unable to read KLDR_DATA_TABLE_ENTRY at 00360037`002e0031 - NTSTATUS 0xC0000141

    Image path too long, possible corrupt data.
    Loading unloaded module list
    ..Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    ...Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    ..Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .Image path too long, possible corrupt data.
    .
    WARNING: .reload failed, module list may be incomplete
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    Use !analyze -v to get detailed debugging information.

    BugCheck 24, {1904fb, fffff88006bb92b8, fffff88006bb8b10, fffff80001bbaf0f}

    ***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

    *********************************************************************
    * 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+                                    *
    *********************************************************************
    *********************************************************************
    * 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 : Unknown_Image ( ANALYSIS_INCONCLUSIVE )

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


    On My Way

    2014年6月27日 14:23

全部回复

  • 你好,

    最近有没有安装什么软件或驱动?如果有的话,请卸载掉试试。此外,安全模式可以进入服务器吗?

    安全模式启动:

    1. 开机在进入Windows系统启动画面之前按下F8键 

    2. 在出现的系统高级启动选项界面, 选择安全模式, 然后按回车键

    2014年6月30日 11:32
    版主