您好,
由於時間過長,這邊將暫時歸檔,後續問題可以繼續回復此貼,
如果之後微軟產品使用過程中有其他問題,歡迎來論壇發帖。
感謝您使用微軟產品。
目前遇到的狀況:只要進行關機動作,均會產生藍屏顯示critical process die
使用Window debug tool分析Memory Dump得到以下結果
請協助分析原因
已在最高權限管理命令提示元輸入以下指令修復檔案但無效
DISM.exe /Online /Cleanup-image /Restorehealth
sfc /scannow
Microsoft (R) Windows Debugger Version 10.0.14321.1024 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [H:\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 16299 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Built by: 16299.15.amd64fre.rs3_release.170928-1534
Machine Name:
Kernel base = 0xfffff800ab20d000 PsLoadedModuleList = 0xfffff800ab574130
Debug session time: Fri Apr 6 09:21:52.345 2018 (UTC + 8:00)
System Uptime: 0 days 0:19:52.226
Loading Kernel Symbols
...............................................................
...Page 34d366 not present in the dump file. Type ".hh dbgerr004" for details
.............................................................
...........................................Page 11d559 not present in the dump file. Type ".hh dbgerr004" for details
...............
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, {ffffe08fca7a9580, 0, 0, 0}
Page 370401 not present in the dump file. Type ".hh dbgerr004" for details
Page 370401 not present in the dump file. Type ".hh dbgerr004" for details
Page 11d559 not present in the dump file. Type ".hh dbgerr004" for details
Page 11d559 not present in the dump file. Type ".hh dbgerr004" for details
Page 372286 not present in the dump file. Type ".hh dbgerr004" for details
Page 372286 not present in the dump file. Type ".hh dbgerr004" for details
Page 34d366 not present in the dump file. Type ".hh dbgerr004" for details
Page 34d366 not present in the dump file. Type ".hh dbgerr004" for details
Probably caused by : ntdll.dll ( ntdll!NtTerminateProcess+14 )
Followup: MachineOwner
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffe08fca7a9580, 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:
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 80XK
SYSTEM_SKU: LENOVO_MT_80XK_BU_idea_FM_ideapad 320-14IKB
SYSTEM_VERSION: Lenovo ideapad 320-14IKB
BIOS_VENDOR: LENOVO
BIOS_VERSION: 4WCN38WW
BIOS_DATE: 12/25/2017
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: LNVNB161216
BASEBOARD_VERSION: SDK0J40700 WIN
DUMP_TYPE: 1
BUGCHECK_P1: ffffe08fca7a9580
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
PROCESS_NAME: svchost.exe
CRITICAL_PROCESS: svchost.exe
EXCEPTION_CODE: (NTSTATUS) 0xc3c87080 - <Unable to get error code text>
ERROR_CODE: (NTSTATUS) 0xc3c87080 - <Unable to get error code text>
CPU_COUNT: 4
CPU_MHZ: b58
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 8e
CPU_STEPPING: 9
CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 7C'00000000 (cache) 7C'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xEF
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: LAPTOP-5327MES9
ANALYSIS_SESSION_TIME: 04-07-2018 13:22:01.0442
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff800ab92126f to fffff800ab382510
STACK_TEXT:
ffff9302d9576838 fffff800ab92126f : 00000000000000ef ffffe08fca7a9580 0000000000000000 0000000000000000 : nt!KeBugCheckEx
ffff9302d9576840 fffff800ab857bfd : ffffe08fca7a95c0 ffffe08fca7a9580 ffffe08fca7a9580 0000000040010004 : nt!PspCatchCriticalBreak+0xff
ffff9302d95768e0 fffff800ab66c0a8 : ffffe08f00000000 ffffe08fca7a9580 ffffe08fca7a9858 ffffe08fca7a9580 : nt!PspTerminateAllThreads+0x113421
ffff9302d9576950 fffff800ab66be91 : ffffffffffffffff ffff9302d9576a80 ffffe08fc6e42580 0000000000000001 : nt!PspTerminateProcess+0xe0
ffff9302d9576990 fffff800ab395003 : ffffe08f000030d4 ffffe08fc3c87080 ffffe08fca7a9580 0000020a7c841980 : nt!NtTerminateProcess+0xa9
ffff9302d9576a00 00007ffd3f7e0404 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13
0000003c133ffbb8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!NtTerminateProcess+0x14
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 1ee16e27f2a3bf32487936ba1484cfcaf564e2dc
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: efd501109c2111ca07b61e101773ddd7f430ba82
THREAD_SHA1_HASH_MOD: fce38ccd7b727228240c1b437cae1484437f51f9
FOLLOWUP_IP:
ntdll!NtTerminateProcess+14
00007ffd`3f7e0404 c3 ret
FAULT_INSTR_CODE: c32ecdc3
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: ntdll!NtTerminateProcess+14
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ntdll
IMAGE_NAME: ntdll.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID_FUNC_OFFSET: 14
FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c3c87080_ntdll!NtTerminateProcess
BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c3c87080_ntdll!NtTerminateProcess
PRIMARY_PROBLEM_CLASS: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c3c87080_ntdll!NtTerminateProcess
TARGET_TIME: 2018-04-06T01:21:52.000Z
OSBUILD: 16299
OSSERVICEPACK: 0
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: 2018-03-01 13:36:55
BUILDDATESTAMP_STR: 170928-1534
BUILDLAB_STR: rs3_release
BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534
ANALYSIS_SESSION_ELAPSED_TIME: 7a1
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xef_svchost.exe_bugcheck_critical_process_c3c87080_ntdll!ntterminateprocess
FAILURE_ID_HASH: {360917f2-1fa3-626d-e8c8-9c2c31c73311}
Followup: MachineOwner
2: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
CRITICAL_PROCESS_DIED (ef)
A critical system process died
Arguments:
Arg1: ffffe08fca7a9580, 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:
DUMP_CLASS: 1
DUMP_QUALIFIER: 401
BUILD_VERSION_STRING: 16299.15.amd64fre.rs3_release.170928-1534
SYSTEM_MANUFACTURER: LENOVO
SYSTEM_PRODUCT_NAME: 80XK
SYSTEM_SKU: LENOVO_MT_80XK_BU_idea_FM_ideapad 320-14IKB
SYSTEM_VERSION: Lenovo ideapad 320-14IKB
BIOS_VENDOR: LENOVO
BIOS_VERSION: 4WCN38WW
BIOS_DATE: 12/25/2017
BASEBOARD_MANUFACTURER: LENOVO
BASEBOARD_PRODUCT: LNVNB161216
BASEBOARD_VERSION: SDK0J40700 WIN
DUMP_TYPE: 1
BUGCHECK_P1: ffffe08fca7a9580
BUGCHECK_P2: 0
BUGCHECK_P3: 0
BUGCHECK_P4: 0
PROCESS_NAME: svchost.exe
CRITICAL_PROCESS: svchost.exe
EXCEPTION_CODE: (NTSTATUS) 0xc3c87080 - <Unable to get error code text>
ERROR_CODE: (NTSTATUS) 0xc3c87080 - <Unable to get error code text>
CPU_COUNT: 4
CPU_MHZ: b58
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 8e
CPU_STEPPING: 9
CPU_MICROCODE: 6,8e,9,0 (F,M,S,R) SIG: 7C'00000000 (cache) 7C'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0xEF
CURRENT_IRQL: 0
ANALYSIS_SESSION_HOST: LAPTOP-5327MES9
ANALYSIS_SESSION_TIME: 04-07-2018 13:22:21.0783
ANALYSIS_VERSION: 10.0.14321.1024 amd64fre
LAST_CONTROL_TRANSFER: from fffff800ab92126f to fffff800ab382510
STACK_TEXT:
ffff9302d9576838 fffff800ab92126f : 00000000000000ef ffffe08fca7a9580 0000000000000000 0000000000000000 : nt!KeBugCheckEx
ffff9302d9576840 fffff800ab857bfd : ffffe08fca7a95c0 ffffe08fca7a9580 ffffe08fca7a9580 0000000040010004 : nt!PspCatchCriticalBreak+0xff
ffff9302d95768e0 fffff800ab66c0a8 : ffffe08f00000000 ffffe08fca7a9580 ffffe08fca7a9858 ffffe08fca7a9580 : nt!PspTerminateAllThreads+0x113421
ffff9302d9576950 fffff800ab66be91 : ffffffffffffffff ffff9302d9576a80 ffffe08fc6e42580 0000000000000001 : nt!PspTerminateProcess+0xe0
ffff9302d9576990 fffff800ab395003 : ffffe08f000030d4 ffffe08fc3c87080 ffffe08fca7a9580 0000020a7c841980 : nt!NtTerminateProcess+0xa9
ffff9302d9576a00 00007ffd3f7e0404 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x13
0000003c133ffbb8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!NtTerminateProcess+0x14
STACK_COMMAND: kb
THREAD_SHA1_HASH_MOD_FUNC: 1ee16e27f2a3bf32487936ba1484cfcaf564e2dc
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: efd501109c2111ca07b61e101773ddd7f430ba82
THREAD_SHA1_HASH_MOD: fce38ccd7b727228240c1b437cae1484437f51f9
FOLLOWUP_IP:
ntdll!NtTerminateProcess+14
00007ffd`3f7e0404 c3 ret
FAULT_INSTR_CODE: c32ecdc3
SYMBOL_STACK_INDEX: 6
SYMBOL_NAME: ntdll!NtTerminateProcess+14
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: ntdll
IMAGE_NAME: ntdll.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 0
BUCKET_ID_FUNC_OFFSET: 14
FAILURE_BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c3c87080_ntdll!NtTerminateProcess
BUCKET_ID: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c3c87080_ntdll!NtTerminateProcess
PRIMARY_PROBLEM_CLASS: 0xEF_svchost.exe_BUGCHECK_CRITICAL_PROCESS_c3c87080_ntdll!NtTerminateProcess
TARGET_TIME: 2018-04-06T01:21:52.000Z
OSBUILD: 16299
OSSERVICEPACK: 0
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: 2018-03-01 13:36:55
BUILDDATESTAMP_STR: 170928-1534
BUILDLAB_STR: rs3_release
BUILDOSVER_STR: 10.0.16299.15.amd64fre.rs3_release.170928-1534
ANALYSIS_SESSION_ELAPSED_TIME: 6b7
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0xef_svchost.exe_bugcheck_critical_process_c3c87080_ntdll!ntterminateprocess
FAILURE_ID_HASH: {360917f2-1fa3-626d-e8c8-9c2c31c73311}
Followup: MachineOwner
鎖定的問題。 此問題已從 Microsoft 支援服務社群移轉。 您可以對其是否有幫助進行投票,但無法對問題新增註解或回覆,或進行追蹤。
您好,
由於時間過長,這邊將暫時歸檔,後續問題可以繼續回復此貼,
如果之後微軟產品使用過程中有其他問題,歡迎來論壇發帖。
感謝您使用微軟產品。
您好,
很抱歉未能及時回復您,
注意:還原出廠之前一定要記得將自己的重要資料拷貝到移動磁碟,或者上傳雲端,避免數據丟失。
這個狀況來看,您使用的賬戶應該是普通賬戶,沒有管理員權限,
這種情況是沒有辦法從Windows 10 恢復出廠的,
不過一般電腦廠家會有實體按鍵(可以問一下電腦廠家),這種實體按鍵可以直接一鍵還原出廠。
另一個辦法就是問公司管理,或者IT 人員,應該能瞭解到管理員賬戶密碼。
您好,
好的,衹有最後一個日志裏面看到,可以先放一放,
如果可以的話,試著做USB 安裝介質之後用USB 開機重灌系統,因爲您貼出的日志來看一直是有某個程式進程導致問題,不過一直沒有抓出來是哪個,
https://www.microsoft.com/zh-tw/software-download/windows10
用過USB 開機重灌系統可以避免之前安裝程式的影響。
如果之後還有問題可以繼續回復此貼,
感謝您使用微軟產品。
感謝你的回覆,另外想請教一個問題,筆電為公司所提供,個人手邊只有可供登入的密碼,之前就有想利用WIN10的回覆出場設置,但卻要求提供另一組密碼,請問可以利用PIN碼回覆出場設置值嗎?
您好,
好的,衹有最後一個日志裏面看到,可以先放一放,
如果可以的話,試著做USB 安裝介質之後用USB 開機重灌系統,因爲您貼出的日志來看一直是有某個程式進程導致問題,不過一直沒有抓出來是哪個,
https://www.microsoft.com/zh-tw/software-download/windows10
用過USB 開機重灌系統可以避免之前安裝程式的影響。
如果之後還有問題可以繼續回復此貼,
感謝您使用微軟產品。
您好,
注意一下系統安裝的軟體,盡量避免安裝使用32位元,應該可以改善,
另外,檢查虛擬記憶體,將虛擬記憶體關掉,pagefile.sys 檔清除掉。
https://dotblogs.com.tw/kay/archive/2013/10/15/124198.aspx
注意,非微軟鏈接,如有問題請聯係作者。
您貼的最後一個日志上看到 page_not_zero_0xef
這個是記憶體接觸不好,拔出來擦拭乾净,插槽也吹一下,之後單根插入測試看看。
好的我先將虛擬記憶體關掉,因為操作機型為筆記型電腦,隨意拆開會導致保固失效,如還是有同樣問題,我會到廠牌經銷那那邊請他們幫忙
如果還有問題我會再回報,謝謝!!