Microsoft (R) Windows Debugger Version 6.10.0003.233 X86Copyright (c) Microsoft Corporation. All rights reserved.Loading Dump File [C:\Users\baishuai\Desktop\030620-9078-01.dmp]Mini Kernel Dump File: Only registers and stack trace are availableSymbol search path is: *** Invalid ******************************************************************************** Symbol loading may be unreliable without a symbol search path. ** Use .symfix to have the debugger choose a symbol path. ** After setting your symbol path, use .reload to refresh symbol locations. *****************************************************************************Executable search path is: ********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************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.exeWindows 7 Kernel Version 17763 MP (12 procs) Free x64Product: WinNt, suite: TerminalServer SingleUserTSBuilt by: 17763.1.amd64fre.rs5_release.180914-1434Machine Name:Kernel base = 0xfffff800`490a3000 PsLoadedModuleList = 0xfffff800`494bc6f0Debug session time: Fri Mar 6 21:03:35.061 2020 (GMT+8)System Uptime: 3 days 1:55:29.832********************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************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.exeLoading Kernel Symbols.........................................................................................................................................................................................................Loading User SymbolsLoading unloaded module list...........................******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************Use !analyze -v to get detailed debugging information.BugCheck 13A, {11, ffff9c851a202100, ffff9c8542578810, 0}Unable to load image \SystemRoot\system32\DRIVERS\sysdiag.sys, Win32 error 0n2*** WARNING: Unable to verify timestamp for sysdiag.sys*** ERROR: Module load completed but symbols could not be loaded for sysdiag.sys***** Kernel symbols are WRONG. Please fix symbols to do analysis.**************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command 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!_KPRCB ****** ******************************************************************************************************************************************************** ****** ****** Your debugger is not using the correct symbols ****** ****** In order for this command 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!_KPRCB ****** ************************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ ******************************************************************************************************************************************** Symbols can not be loaded because symbol path is not initialized. ** ** The Symbol Path can be set by: ** using the _NT_SYMBOL_PATH environment variable. ** using the -y <symbol_path> argument when starting the debugger. ** using .sympath and .sympath+ **********************************************************************Probably caused by : ntoskrnl.exe ( nt+1b6a50 )Followup: MachineOwner---------
uj5u.com熱心網友回復：
用著用著就藍了，下面是截屏，大佬們幫我看看把，是怎么個原因
uj5u.com熱心網友回復：
系統出問題了，重裝系統uj5u.com熱心網友回復：
我最近更新了win10的原因么
uj5u.com熱心網友回復：
也可能，win10的bug遠比win7多，用起來頭疼，進入安全模式，看看能否把最新安裝的軟體和補丁卸載掉！
uj5u.com熱心網友回復：
按f8進安全模式，把最近打的補丁卸掉，實在不行重裝系統。uj5u.com熱心網友回復：
可以進安全模式試著用360人工服務里面的工具試著修復一下 可能是更新的問題轉載請註明出處，本文鏈接：https://www.uj5u.com/caozuo/22059.html
標籤：安全技術/病毒