Microsoft (R) Windows Debugger Version 10.0.20153.1000 AMD64Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\Chenb\Desktop\101020-13859-01.dmp]Mini Kernel Dump File: Only registers and stack trace are available************* Path validation summary **************Response Time (ms) LocationDeferred srv*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**************************************************************************** ****** ****** 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 10 Kernel Version 18362 MP (8 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSEdition build lab: 18362.1.amd64fre.19h1_release.190318-1202Machine Name:Kernel base = 0xfffff801`78c00000 PsLoadedModuleList = 0xfffff801`790460f0Debug session time: Sat Oct 10 08:41:12.118 2020 (UTC + 8:00)System Uptime: 0 days 22:37:17.284Unable to load image \SystemRoot\system32\ntoskrnl.exe, Win32 error 0n2*** WARNING: Unable to verify timestamp for ntoskrnl.exe**************************************************************************** ****** ****** 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.Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.Run !sym noisy before .reload to track down problems loading symbols............................................................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list................................************* Symbol Loading Error Summary **************Module name Errorntoskrnl The system cannot find the file specifiedYou 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 -vnt+0x1c2990:fffff801`78dc2990 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffd400`c61bec20=00000000000000ef