!求解决办法:ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe 导致的蓝屏错误 Windows Server 2019 Standard

聃 王 21 Reputation points
2022-01-06T02:02:04.343+00:00

系统为:Windows Server 2019 Standard

通过debugging tools 读取的日志信息如下:

Loading Dump File [E:\dmp\MEMORY.DMP]

Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*

Executable search path is:

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

Windows 10 Kernel Version 17763 MP (4 procs) Free x64

Product: Server, suite: TerminalServer SingleUserTS

Built by: 17763.1.amd64fre.rs5_release.180914-1434

Machine Name:

Kernel base = 0xfffff8061fc0c000 PsLoadedModuleList = 0xfffff8062002b9b0

Debug session time: Sat Jan 1 03:10:08.610 2022 (UTC + 8:00)

System Uptime: 2 days 9:33:07.065

*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -

Loading Kernel Symbols

.......................................Page 2001095ab too large to be in the dump file.

Page 2004405aa too large to be in the dump file.

........................

................................................................

.................................

Loading User Symbols

....................

Loading unloaded module list

..............*** ERROR: Module load completed but symbols could not be loaded for ntdll.dll

************* Symbol Loading Error Summary **************

Module name Error

ntkrnlmp The system cannot find the file specified

ntdll 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.

Unable to add extension DLL: kdexts

Unable to add extension DLL: kext

Unable to add extension DLL: exts

The call to LoadLibrary(ext) failed, Win32 error 0n2

"系统找不到指定的文件。" 

Please check your debugger configuration and/or network access.

The call to LoadLibrary(ext) failed, Win32 error 0n2

"系统找不到指定的文件。" 

Please check your debugger configuration and/or network access.


  • Bugcheck Analysis *

Bugcheck code 000000EF

Arguments ffffa681c68cd140 0000000000000000 0000000000000000 0000000000000000

RetAddr : Args to Child : Call Site

fffff8062041a1dd : 00000000000000ef ffffa681c68cd140 0000000000000000 00000000`00000000 : nt!KeBugCheckEx

fffff806202f497b : 0000000000000000 0000000000000000 ffffa681c68cd140 fffff806`1fcdcef8 : nt!PsSetLegoNotifyRoutine+0x5dd

fffff806201d57c8 : ffffa68100000000 0000000000000000 ffffa681c68cd140 ffffa681`c68cd418 : nt!FsRtlRegisterFltMgrCalls+0x2051b

fffff806201d5599 : ffffffffffffffff ffffa58c5ffefa80 ffffa681c68cd140 00000000`00000001 : nt!PsChargeProcessWakeCounter+0xbc8

fffff8061fdce285 : ffffa6810000026c ffffa681c89c9080 ffffa681c68cd140 00000000`00000000 : nt!PsChargeProcessWakeCounter+0x999

00007ffd6cdfeb14 : 00007ffd68d483a1 0000000000000000 0000000000000000 ffffffff`ee1e5d00 : nt!setjmpex+0x78c5

*** ERROR: Symbol file could not be found. Defaulted to export symbols for CSRSRV.dll -

00007ffd68d483a1 : 0000000000000000 0000000000000000 ffffffffee1e5d00 00000000`00000c70 : ntdll+0x9eb14

00007ffd6ce07100 : 0000000000000000 00007ffd6cea37a8 0000000c802bddd8 00000000`00200040 : CSRSRV!CsrUnhandledExceptionFilter+0x131

0000000000000000 : 00007ffd6cea37a8 0000000c802bddd8 0000000000200040 00000000`00000000 : ntdll+0xa7100

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,126 questions
0 comments No comments
{count} votes

Accepted answer
  1. Docs 15,516 Reputation points
    2022-01-06T05:21:54.113+00:00

    Please perform the following steps:

    Run the DM log collector and post a share link into this thread using one drive, drop box, or google drive:

    https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

    Make sure that the default language is English so that the logs can be scanned and read:

    https://www.tenforums.com/tutorials/3813-add-remove-change-display-language-windows-10-a.html

    https://www.tenforums.com/tutorials/136792-change-display-language-windows-10-a.html

    If possible see if the V2 log collector can run on the server.
    If it can run then it will collect additional logs useful in the troubleshooting.

    .
    .
    .
    .
    .

    Please remember to vote and to mark the replies as answers if they help.

    On the bottom of each post there is:

    Propose as answer = answered the question

    On the left side of each post there is /\ with a number: click = a helpful post
    .
    .
    .
    .
    .

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Limitless Technology 39,646 Reputation points
    2022-01-06T17:18:26.407+00:00

    Hello

    Please check the next official article from Microsoft about the BSOD Bug Check 0xEF: CRITICAL_PROCESS_DIED

    https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xef--critical-process-died

    Hope this helps with your query,

    --------
    --If the reply is helpful, please Upvote and Accept as answer--


Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.