none
Windows Server 2012 R2 出现反复蓝屏问题,如何解决? RRS feed

  • 问题

  • Loading Dump File [C:\Users\s1517\Desktop\MEMORY\MEMORY.DMP]
    Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.


    ************* Path validation summary **************
    Response                         Time (ms)     Location
    Deferred                                       srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Symbol search path is: srv*c:\symbols*http://msdl.microsoft.com/download/symbols
    Executable search path is: 
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that     ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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!_MMPTE_TRANSITION                          ***
    ***                                                                   ***
    *************************************************************************
    Windows 8.1 Kernel Version 9600 MP (2 procs) Free x64
    Product: LanManNt, suite: TerminalServer SingleUserTS
    Built by: 9600.16404.amd64fre.winblue_gdr.130913-2141
    Machine Name:
    Kernel base = 0xfffff803`c7489000 PsLoadedModuleList = 0xfffff803`c774d990
    Debug session time: Tue Jul 28 03:33:16.771 2020 (UTC + 8:00)
    System Uptime: 94 days 3:54:38.620
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that     ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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!_MMPTE_TRANSITION                          ***
    ***                                                                   ***
    *************************************************************************
    Loading Kernel Symbols
    ...............................................................
    ................................................................
    ..........
    Loading User Symbols

    Loading unloaded module list
    .....

    ************* Symbol Loading Error Summary **************
    Module name            Error
    ntkrnlmp               The system cannot find the file specified

    You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the command that caused symbols to be loaded.
    You should also verify that your symbol search path (.sympath) is correct.
    For analysis of this file, run !analyze -v
    1: kd> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Bugcheck Analysis                                    *
    *                                                                             *
    *******************************************************************************

    PAGE_FAULT_IN_NONPAGED_AREA (50)
    Invalid system memory was referenced.  This cannot be protected by try-except.
    Typically the address is just plain bad or it is pointing at freed memory.
    Arguments:
    Arg1: ffffe0000bf6e000, memory referenced.
    Arg2: 0000000000000001, value 0 = read operation, 1 = write operation.
    Arg3: fffff800021cb400, If non-zero, the instruction address which referenced the bad memory
    address.
    Arg4: 0000000000000000, (reserved)

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

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



    *************************************************************************

    KEY_VALUES_STRING: 1

        Key  : Analysis.CPU.Sec
        Value: 2

        Key  : Analysis.DebugAnalysisProvider.CPP
        Value: Create: 8007007e on DESKTOP-R09NQ1M

        Key  : Analysis.DebugData
        Value: CreateObject

        Key  : Analysis.DebugModel
        Value: CreateObject

        Key  : Analysis.Elapsed.Sec
        Value: 120

        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 81

        Key  : Analysis.System
        Value: CreateObject


    ADDITIONAL_DEBUG_TEXT:  
    You can run '.symfix; .reload' to try to fix the symbol path and load symbols.

    WRONG_SYMBOLS_TIMESTAMP: 52341cf4

    WRONG_SYMBOLS_SIZE: 781000

    FAULTING_MODULE: fffff803c7489000 nt

    BUGCHECK_CODE:  50

    BUGCHECK_P1: ffffe0000bf6e000

    BUGCHECK_P2: 1

    BUGCHECK_P3: fffff800021cb400

    BUGCHECK_P4: 0

    WRITE_ADDRESS: *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that     ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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!_MMPFN                                     ***
    ***                                                                   ***
    *************************************************************************
    *************************************************************************
    ***                                                                   ***
    ***                                                                   ***
    ***    Either you specified an unqualified symbol, or your debugger   ***
    ***    doesn't have full symbol information.  Unqualified symbol      ***
    ***    resolution is turned off by default. Please either specify a   ***
    ***    fully qualified symbol module!symbolname, or enable resolution ***
    ***    of unqualified symbols by typing ".symopt- 100". Note that     ***
    ***    enabling unqualified symbol resolution with network symbol     ***
    ***    server shares in the symbol path may cause the debugger to     ***
    ***    appear to hang for long periods of time when an incorrect      ***
    ***    symbol name is typed or the network symbol server is down.     ***
    ***                                                                   ***
    ***    For some commands 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!_MMPTE                                     ***
    ***                                                                   ***
    *************************************************************************
    Unable to get size of nt!_MMPTE - probably bad symbols
     ffffe0000bf6e000 

    MM_INTERNAL_CODE:  0

    STACK_TEXT:  
    ffffd000`2224ddf8 fffff803`c75ebfd8 : 00000000`00000050 ffffe000`0bf6e000 00000000`00000001 ffffd000`2224dfe0 : nt!KeBugCheckEx
    ffffd000`2224de00 fffff803`c74ea0fd : 00000000`00000001 ffffe000`0905c040 ffffd000`2224dfe0 ffffe000`0bf5d000 : nt!CcTestControl+0x81a0
    ffffd000`2224dea0 fffff803`c75e0f2f : 00000000`00000001 ffffe000`0bf6e000 00000000`00010f00 ffffd000`2224dfe0 : nt!ExReleasePushLockEx+0x85d
    ffffd000`2224dfe0 fffff800`021cb400 : 00000000`00010fe8 6c336352`2f325954 ffffd000`2224e298 ffffd000`2224e290 : nt!setjmpex+0x1f2f
    ffffd000`2224e170 fffff800`021cb345 : ffffc000`021c4095 ffffe000`0bf6dff8 00000000`00000010 ffffc000`021c4138 : srv+0x76400
    ffffd000`2224e1a0 fffff800`021daae7 : ffffe000`0bf48010 00000000`00000000 ffffc000`021b4010 00000000`00000001 : srv+0x76345
    ffffd000`2224e1f0 fffff800`021a0cc7 : 00000000`00000000 fffff800`00010fe8 ffffe000`0bf5d010 ffffe000`0bf48010 : srv+0x85ae7
    ffffd000`2224e290 fffff800`021e07a6 : ffffc000`021b4010 00000000`00001000 ffffe000`09065db0 ffffe000`0bf48010 : srv+0x4bcc7
    ffffd000`2224e2d0 fffff800`02157d6d : ffffe000`00000000 fffff800`00000000 fffff800`00000035 ffffe000`0000f3d0 : srv+0x8b7a6
    ffffd000`2224e370 fffff800`02157c54 : fffff800`02173010 ffffe000`0bf48a80 ffffe000`0bf48010 ffffe000`00000000 : srv+0x2d6d
    ffffd000`2224e3f0 fffff800`021ad4e0 : ffffe000`0904d340 00000000`00000006 00000000`00000005 ffffe000`0bf48020 : srv+0x2c54
    ffffd000`2224e430 fffff803`c7970d2e : 00000000`00000000 ffffe000`0bf48010 00000000`00000000 ffffc000`20206f49 : srv+0x584e0
    ffffd000`2224e490 fffff803`c756cc80 : ffffe000`0905c040 ffffe000`0905c040 00000000`00000000 fffff800`00b3c99c : nt!LdrResFindResource+0x9a
    ffffd000`2224e4c0 fffff803`c75dd2c6 : fffff803`c7777180 ffffe000`0905c040 ffffe000`00f45040 00000000`00000000 : nt!SeTokenIsWriteRestricted+0x68
    ffffd000`2224e520 00000000`00000000 : ffffd000`2224f000 ffffd000`22248000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0x59d6


    STACK_COMMAND:  .thread ; .cxr ; kb

    EXCEPTION_CODE_STR:  52341CF4

    EXCEPTION_STR:  WRONG_SYMBOLS

    PROCESS_NAME:  ntoskrnl.wrong.symbols.exe

    IMAGE_NAME:  ntoskrnl.wrong.symbols.exe

    MODULE_NAME: nt_wrong_symbols

    SYMBOL_NAME:  nt_wrong_symbols!52341CF4781000

    FAILURE_BUCKET_ID:  WRONG_SYMBOLS_X64_9600.16404.amd64fre.winblue_gdr.130913-2141_TIMESTAMP_130914-082316_52341CF4_nt_wrong_symbols!52341CF4781000

    OS_VERSION:  8.1.9600.16404

    BUILDLAB_STR:  winblue_gdr

    OSPLATFORM_TYPE:  x64

    OSNAME:  Windows 8.1

    FAILURE_ID_HASH:  {22198cf8-592a-b9e1-7d73-4f84dc1bf882}

    Followup:     MachineOwner
    ---------
    2020年7月28日 7:56

全部回复

  • 您好,

    根据您提供的信息 Either you specified an unqualified symbol, or your debugger doesn't have full symbol information来看,symbol文件配置出现问题,导致无法分析出有帮助的信息。

    因为这是一个公共的论坛,为了保护你的个人隐私信息,不建议您直接上传dump信息。

    如果有Win10的机器,建议您在Microsoft Store中下载WinDbg preview这个工具,可以直接进行dump的分析,然后用这个命令看一下:!analyze -v。

    如果蓝屏问题持续出现,建议您以管理员身份打开CMD窗口运行以下指令尝试进行修复:

    sfc /scannow


    针对Windows 2008/2008R2的扩展支持将于2020年结束,之后微软将不再为其提供安全更新。点击此处或扫描二维码获取《在 Azure 上运行 Windows Server 的终极指南》,把握良机完成云迁移并实现业务现代化。

    2020年7月29日 12:52