1062
win10最近突然頻繁藍屏 顯示critical process died
試過重新插拔並清理內存與硬盤 更新驅動 運行chkdsk和自檢 均無效果 以下為dump記錄：
Loading Dump File [C:\Windows\Minidump\051317-30937-01.dmp]
Loading Dump File [C:\Windows\Minidump\051317-30937-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Mini Kernel Dump File: Only registers and stack trace are available
************* Symbol Path validation summary **************
************* Symbol Path validation summary **************
Response Time (ms) Location
Response Time (ms) Location
Deferred Deferred srv*srv*
Symbol search path is: Symbol search path is: srv*
srv*
Executable search path is:
Executable search path is:
Unable to load image Unable to load image \SystemRoot\system32\ntoskrnl.exe\SystemRoot\system32\ntoskrnl.exe, , Win32 error 0n2Win32 error 0n2
*** WARNING: Unable to verify timestamp for *** WARNING: Unable to verify timestamp for ntoskrnl.exentoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exentoskrnl.exe
Windows 10 Kernel Windows 10 Kernel Version 14393Version 14393 MP MP (8 procs) (8 procs) Free x64
Free x64
Product: Product: WinNtWinNt, suite:, suite: TerminalServer TerminalServer SingleUserTS SingleUserTS
Built by: 14393.1198.amd64fre.rs1_release_sec.170427-1353
Built by: 14393.1198.amd64fre.rs1_release_sec.170427-1353
Machine Name:Machine Name:
Kernel base = 0xfffff800`0f819000 PsLoadedModuleList = 0xfffff800`0fb18000
Kernel base = 0xfffff800`0f819000 PsLoadedModuleList = 0xfffff800`0fb18000
Debug session time: Sat May 13 16:31:13.432 2017 (UTC + 10:00)
Debug session time: Sat May 13 16:31:13.432 2017 (UTC + 10:00)
System Uptime: 0 days 0:43:56.071System Uptime: 0 days 0:43:56.071
Unable to load image Unable to load image \SystemRoot\system32\ntoskrnl.exe\SystemRoot\system32\ntoskrnl.exe, , Win32 error 0n2Win32 error 0n2
*** WARNING: Unable to verify timestamp for *** WARNING: Unable to verify timestamp for ntoskrnl.exentoskrnl.exe
*** ERROR: Module load completed but symbols could not be loaded for *** ERROR: Module load completed but symbols could not be loaded for ntoskrnl.exentoskrnl.exe
Loading Kernel Symbols
Loading Kernel Symbols
..
Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
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.
Run !sym noisy before .reload to track down problems loading symbols.
............................................................................................................................
................................................................................................................................
........................................................................................................
Loading User Symbols
Loading User Symbols
Loading unloaded module list
.Loading unloaded module list
...............
************* Symbol Loading Error Summary **************
************* Symbol Loading Error Summary **************
Module name Error
Module name Error
ntoskrnl The system cannot find the file specifiedntoskrnl 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.
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 deliver callback, Unable to deliver callback, 3131
*******************************************************************************
*******************************************************************************
* *
* *
* Bugcheck Analysis *
* Bugcheck Analysis *
* *
* *
*******************************************************************************
*******************************************************************************
Use Use !analyze -v !analyze -v to get detailed debugging information.
to get detailed debugging information.
BugCheck BugCheck EFEF, {, {ffff8d834b9da800ffff8d834b9da800, , 00, , 00, , 00}
}
***** ***** KernelKernel symbols are WRONG. Please fix symbols to do analysis.
symbols are WRONG. Please fix symbols to do analysis.
">ETW minidump data unavailable
ETW minidump data unavailable
"><Unable to get <Unable to get nt!KiCurrentEtwBufferOffsetnt!KiCurrentEtwBufferOffset>>"><Unable to get <Unable to get nt!KiCurrentEtwBufferBasent!KiCurrentEtwBufferBase>>*************************************************************************
*** ***
*** ***
*** 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: *************************************************************************
*** ***
*** ***
*** 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!_EPROCESS nt!_EPROCESS ***
*** ***
*************************************************************************
***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: *************************************************************************
*** ***
*** ***
*** 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!_EPROCESS nt!_EPROCESS ***
*** ***
*************************************************************************
***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: *************************************************************************
*** ***
*** ***
*** 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!_EPROCESS nt!_EPROCESS ***
*** ***
*************************************************************************
***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: *************************************************************************
*** ***
*** ***
*** 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 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: *************************************************************************
*** ***
*** ***
*** 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 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: *************************************************************************
*** ***
*** ***
*** 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 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: *************************************************************************
*** ***
*** ***
*** 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 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: *************************************************************************
*** ***
*** ***
*** 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 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: *************************************************************************
*** ***
*** ***
*** 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!_EPROCESS nt!_EPROCESS ***
*** ***
*************************************************************************
***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** 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: *************************************************************************
*** ***
*** ***
*** 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 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: *************************************************************************
*** ***
*** ***
*** 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.
最後更新：2017-05-13 15:41:27
上一篇：
背景圖片設置問題
下一篇： win7無法使用自動更新
- win10下遇到了https://support.microsoft.com/zh
- 惠普電腦重裝過後，微軟殺毒提示有病毒，這個正常嘛，這是個什麼目錄？？&
- 你好，我的筆記本電腦win10自帶的應用商店下載，總是顯示我這邊出錯，請問解決方法！
- Windows 無法對計算機進行啟動到下一個安裝階段的準備。要安裝
- 右鍵用戶文件夾屬性後在安全中發現未知的賬戶S
- win10藍屏問題
- win10應用商店無法更新，錯誤代碼0x80246007
- 我的Windows Defender不能啟動
- 怎麼查看Windows 更新代理的情況？
- Windows10 Pro 平板設備，希望取消睡眠喚醒後的滑動解鎖。
相關內容
- 你的設備已過期，並缺少重要的安全和質量更新，因此存在風險。讓我們帶你重回正軌，這樣
- Microsoft store 無法聯網，顯示Microsoft Store需要聯網，你似乎沒有聯網
- 設備以遷移 由於僅部分匹配或匹配不明確，因此無法遷移設備
- 由於在創建轉儲期間出錯，創建轉儲文件失敗。
- 發生臨時 DNS 錯誤
- 應用商店，在我們這邊發生問題，無法使你登陸，錯誤代碼: 0xD000000D
- 照相機不可用，錯誤代碼：0xA00F4244(0xC00DABE0)
- 應用商店打開異常提示“清單中指定了未知的布局”
- 自定義掃描Windows defender裏麵的設備性能和運行狀況 黃色感歎號問題
- windows預口體驗成員內口版本遇到問題需要重啟
熱門內容
- windows10 點開此電腦後，有兩個顯示硬盤盤符的目錄是怎麼回事?
- windows 10 專業版無法下載中文語言包
- KB4056892
- win10不能共享文件夾
- 在Surfacebook上用Windows to go 1703版本，更新後重啟藍屏，無法進入係統
- windows10 1709版本更新失敗，錯誤0x8007001f
- microdoft visual c++ 2015 redistributable
- WIN10 Insider Preview 17025更新失敗，錯誤代碼0x80096004
- 計算機管理服務 出現一個內部錯誤（INVALID
- 關於控製麵板中的安全和維護內提示Windows defender 防病毒已關閉的問題