Microsoft (R) Windows Debugger Version 10.0.17763.168 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [F:\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 (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff801`1ea9b000 PsLoadedModuleList = 0xfffff801`1eeb6ad0
Debug session time: Tue Feb 26 14:39:43.224 2019 (UTC + 8:00)
System Uptime: 0 days 0:05:48.285
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntkrnlmp.exe -
Loading Kernel Symbols
.....................................Page 20013cfc6 too large to be in the dump file.
Page 20013cfc5 too large to be in the dump file.
..........................
................................................................
................................................................
...........
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000000`00cd4018). Type ".hh dbgerr001" for details
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.
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 0000009F
Arguments 00000000`00000003 ffff9604`e9f2a080 ffffb009`4203ec20 ffff9604`f0716730
RetAddr : Args to Child : Call Site
fffff801`1ed6ce06 : 00000000`0000009f 00000000`00000003 ffff9604`e9f2a080 ffffb009`4203ec20 : nt!KeBugCheckEx
fffff801`1ed6cd12 : ffff9604`f31204e0 ffff9604`f8f0e0e0 00000000`000000fe ffffbe00`81bcf180 : nt!ObIsKernelHandle+0x9a6
fffff801`1eb52659 : ffff9604`f3120518 ffff9604`f66ee000 ffff9604`f3120558 fffff801`00000002 : nt!ObIsKernelHandle+0x8b2
fffff801`1eb535a7 : 00000000`00000008 00000000`00989680 ffff9604`f66ee080 00000000`00000019 : nt!PsIsHostSilo+0x349
fffff801`1ec552a5 : f5ff7bfb`fdfffbff ffffbe00`81bcf180 ffffb009`46572b80 ffff9604`e90bfd00 : nt!IofCallDriver+0x527
fffff801`1ec55090 : 00000000`0000330c fffff801`1ea05ae6 00000000`0510c070 00000000`00000000 : nt!KeSynchronizeExecution+0x5ce5
fffff801`1ec54955 : 00000000`3b98d880 fffff801`1ec50401 00000000`00005b07 ffffb009`46572b80 : nt!KeSynchronizeExecution+0x5ad0
fffff801`1ec50401 : 00000000`00005b07 ffffb009`46572b80 ffff9604`e90bfd00 ffffb009`46572b80 : nt!KeSynchronizeExecution+0x5395
00007ffc`3b18125a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeSynchronizeExecution+0xe41
00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`3b18125a