328
頻繁出現0x000000ef錯誤（CRITICAL
Win10係統筆記本電腦，已購買並使用1年，昨天開始不斷出現CRITICAL_PROCESS_DIED藍屏問題。通常都是在連續使用了2-3個小時後發生的。發生時機不定，正在遊戲時和待機時都發生過。
最新一次出錯時，事件查看器記錄下以下信息：事件1001，BugCheck。計算機已經從檢測錯誤後重新啟動。檢測錯誤: 0x000000ef (0xffffe001915327c0, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)。已將轉儲的數據保存在: C:\WINDOWS\Minidump\101917-7875-01.dmp。報告 ID: ab15e3b3-510c-4d3f-96bb-ea8dd3c7a987。請問這是什麼原因導致的呢？有什麼解決方法嗎？
以下為最後一次出錯後，WinDbg分析記錄的.dmp文件結果。
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 10 Kernel Version 10586 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 10586.1106.amd64fre.th2_release.170904-1742
Machine Name:
Kernel base = 0xfffff800`18000000 PsLoadedModuleList = 0xfffff800`182ddc70
Debug session time: Thu Oct 19 16:52:00.402 2017 (UTC + 8:00)
System Uptime: 0 days 1:50:27.225
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 Symbols
Loading unloaded module list
..........
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
Use !analyze -v to get detailed debugging information.
BugCheck EF, {ffffe001915327c0, 0, 0, 0}
ETW minidump data unavailable
Probably caused by : ntkrnlmp.exe ( nt!PspCatchCriticalBreak+a4 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffe001915327c0, Process object or thread object
Arg2: 0000000000000000, If this is 0, a process died. If this is 1, a thread died.
Arg3: 0000000000000000
Arg4: 0000000000000000
Debugging Details:
------------------
ETW minidump data unavailable
DUMP_CLASS: 1
DUMP_QUALIFIER: 400
BUILD_VERSION_STRING: 10586.1106.amd64fre.th2_release.170904-1742
SYSTEM_MANUFACTURER: Terrans Force
SYSTEM_PRODUCT_NAME: T5-SKYLAKE
SYSTEM_SKU: Not Applicable
SYSTEM_VERSION: Not Applicable
BIOS_VENDOR: American Megatrends Inc.
BIOS_VERSION: 1.05.07
BIOS_DATE: 10/12/2015
BASEBOARD_MANUFACTURER: Terrans Force
BASEBOARD_PRODUCT: T5-SKYLAKE
BASEBOARD_VERSION: Not Applicable
DUMP_TYPE: 2
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_P1: ffffe001915327c0
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
PROCESS_NAME: svchost.exe
CRITICAL_PROCESS: svchost.exe
EXCEPTION_RECORD: 000000000010005f -- (.exr 0x10005f)
Cannot read Exception record @ 000000000010005f
EXCEPTION_CODE: (NTSTATUS) 0x90d04040 - <Unable to get error code text>
ERROR_CODE: (NTSTATUS) 0x90d04040 - <Unable to get error code text>
CPU_COUNT: 8
CPU_MHZ: a20
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 5e
CPU_STEPPING: 3
CPU_MICROCODE: 6,5e,3,0 (F,M,S,R) SIG: 49'00000000 (cache) 49'00000000 (init)
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xEF
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: DESKTOP-5RBDJV4
ANALYSIS_SESSION_TIME: 10-19-2017 17:22:48.0445
ANALYSIS_VERSION: 10.0.15063.468 amd64fre
LAST_CONTROL_TRANSFER: from fffff8001863d670 to fffff80018142a00
STACK_TEXT:
ffffd000`210463b8 fffff800`1863d670 : 00000000`000000ef ffffe001`915327c0 00000000`00000000 00000000`00000000 : nt!KeBugCheckEx
ffffd000`210463c0 fffff800`1843b6c8 : 00000000`00000000 ffffe001`90d04360 00000000`00000001 fffff800`18003dda : nt!PspCatchCriticalBreak+0xa4
ffffd000`21046400 fffff800`1843bc8d : ffffe001`915327c0 ffffe001`915327c0 ffffe001`90d04360 00000000`00000000 : nt!PspTerminateAllThreads+0x74
ffffd000`21046460 fffff800`184c2694 : ffffe001`915327c0 00000000`c0000005 ffffe001`915327c0 ffffe001`90d04040 : nt!PspTerminateProcess+0x101
ffffd000`210464a0 fffff800`1814d2a3 : ffffe001`915327c0 ffffe001`90d04040 ffffd000`21046590 fffff800`183bbea0 : nt!NtTerminateProcess+0x9c
ffffd000`21046510 fffff800`181458f0 : fffff800`18008318 00000000`00000000 00000000`00000000 ffffd000`21047a00 : nt!KiSystemServiceCopyEnd+0x13
ffffd000`210466a8 fffff800`18008318 : 00000000`00000000 00000000`00000000 ffffd000`21047a00 00000000`00000003 : nt!KiServiceLinkage
ffffd000`210466b0 fffff800`18007954 : 00000000`0010005f ffffd000`21047030 00000000`00000000 fffff801`00000003 : nt!KiDispatchException+0x614
ffffd000`21047000 fffff800`1814334b : ffffe001`90d04040 fffff800`00000005 00000000`00000000 ffffd000`21047a80 : nt!KiRaiseException+0x1ac
ffffd000`210478c0 fffff800`1814d2a3 : ffffe001`00000000 00000000`000010a8 ffffe001`90d04040 00000000`00000000 : nt!NtRaiseException+0x7b
ffffd000`21047a00 00007ffb`568edb89 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
0000005d`17b7ecf0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffb`568edb89
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 79773ef5e5670fa5f4c11f4b30f9ea18989b1b3b
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 32d4ffe0d4b7bc28b26b206ee9b280a047ef82ff
THREAD_SHA1_HASH_MOD: b28610981796779b4ac02f58898fde25728a775c
FOLLOWUP_IP:
nt!PspCatchCriticalBreak+a4
fffff800`1863d670 cc int 3
FAULT_INSTR_CODE: 5c8b48cc
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: nt!PspCatchCriticalBreak+a4
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: nt
IMAGE_NAME: ntkrnlmp.exe
DEBUG_FLR_IMAGE_TIMESTAMP: 59ae2ed4
IMAGE_VERSION: 10.0.10586.1106
BUCKET_ID_FUNC_OFFSET: a4
FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_90d04040_nt!PspCatchCriticalBreak
BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_90d04040_nt!PspCatchCriticalBreak
PRIMARY_PROBLEM_CLASS: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_90d04040_nt!PspCatchCriticalBreak
TARGET_TIME: 2017-10-19T08:52:00.000Z
OSBUILD: 10586
OSSERVICEPACK: 1106
SERVICEPACK_NUMBER: 0
OS_REVISION: 0
SUITE_MASK: 784
PRODUCT_TYPE: 1
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS Personal
OS_LOCALE:
USER_LCID: 0
OSBUILD_TIMESTAMP: 2017-09-05 12:57:56
BUILDDATESTAMP_STR: 170904-1742
BUILDLAB_STR: th2_release
BUILDOSVER_STR: 10.0.10586.1106.amd64fre.th2_release.170904-1742
ANALYSIS_SESSION_ELAPSED_TIME: a42
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xef_svchost.exe_bugcheck_critical_process_90d04040_nt!pspcatchcriticalbreak
FAILURE_ID_HASH: {19d725da-2385-f669-d6af-7c8b1d409888}
Followup: MachineOwner
---------
最後更新：2017-10-19 18:03:22
上一篇：
無法更改c盤users下的文件名
下一篇： Kaspersky Internet Security Suite/Anti
- 你的設備已過期，並缺少重要的安全和質量更新，因此存在風險。讓我們帶你重回正軌，這樣
- 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 防病毒已關閉的問題