求解频繁蓝屏问题，下面是dump分析。
Microsoft (R) Windows Debugger Version 10.0.14321.1024 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\Minidump\080118-33343-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: srv*
Executable search path is:
Unable to load image \SystemRoot\system32\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 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 14393.1593.amd64fre.rs1_release.170731-1934
Machine Name:
Kernel base = 0xfffff800`57a09000 PsLoadedModuleList = 0xfffff800`57d07040
Debug session time: Wed Aug 1 21:08:26.044 2018 (UTC + 8:00)
System Uptime: 0 days 0:32:54.768
Unable to load image \SystemRoot\system32\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
............................
************* Symbol Loading Error Summary **************
Module name Error
ntoskrnl 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 0000004E
Arguments 00000000`00000099 00000000`00053564 00000000`00000003 0a000000`0004e8a6
RetAddr : Args to Child
: Call Site
fffff800`57b838eb : 00000000`0000004e 00000000`00000099 00000000`00053564 00000000`00000003 : nt+0x14f870
00000000`0000004e : 00000000`00000099 00000000`00053564 00000000`00000003 0a000000`0004e8a6 : nt+0x17a8eb
00000000`00000099 : 00000000`00053564 00000000`00000003 0a000000`0004e8a6 00000000`00000000 : 0x4e
00000000`00053564 : 00000000`00000003 0a000000`0004e8a6 00000000`00000000 ffffffff`ffffff00 : 0x99
00000000`00000003 : 0a000000`0004e8a6 00000000`00000000 ffffffff`ffffff00 00000000`00000000 : 0x53564
0a000000`0004e8a6 : 00000000`00000000 ffffffff`ffffff00 00000000`00000000 ffff9d02`fed899c0 : 0x3
00000000`00000000 : ffffffff`ffffff00 00000000`00000000 ffff9d02`fed899c0 00000000`00000009 : 0x0a000000`0004e8a6
