Windows10Pro(64bit) can't start normally by BSoD of CRITICAL PROCESS DIED

keithgull

keithgull

Active member
Joined
Apr 9, 2022
Posts
28
Hi, I'm Kimi, Japanese.
Please advise me to solve my PC problem.
My PC can't start normally by Blue screen, error code: CRITICAL PROCESS DIED.
I tried to delete some device drivers, and start smallest system devices,
run sfc/dism command, and make iso image using MediaCreationTool21H2.exe
but I can't solve this problem.
(dism returns 0x800f081f)

I found this site, and execute SFC and SFCFix, but sfcfix crashed.
How do I do next? Please give me some advice.

Regards.
 

Attachments

hi, Thank you for replying message.
Now, I can boot in safe mode with network.
I deleted Realtek sound device drivers and hyper-v device drivers,
because I found ! marked on these devices on device manager in safe mode.
 
Last edited:
In addition, I already checked chkdsk and MdSched,
I guess that the problem wasn't caused by hardware trouble.
because I tried to boot another ssd drive in my old Windows 7 system,
Windows 7 normally started.
if the pc has something hardware trouble, I think the system crash like windows 10.
 
Hmm, could you go to the following directory and then zip up and attach any dump files:

Rich (BB code): 
%systemroot%\Minidump
 
It seems that VmComputeAgent.exe (part of Hyper-V) is being terminated prematurely, are you running Windows 10 in a virtual machine then? What security programs do you have installed e.g. Norton, BitDefender etc.
 
i don't run Windows10 on virtual machine, run on real hardware. but I installed Hyper-V before for VMware or other virtual machine software. And, I installed Norton security before, but I uninstalled Norton security a month ago. Currently I only use Windows Defender.
Does it caused this problem that I uninstalled Norton Security before?
 
keithgull said:
Does it caused this problem that I uninstalled Norton Security before?
Click to expand...
There possibly could still be remnants of Norton remaining, could you please run the official Norton Removal tool? Please be careful and make sure you remove Norton and not allow the tool to install it again.

keithgull said:
but I installed Hyper-V before for VMware or other virtual machine software.
Click to expand...
You don't need Hyper-V to run VMWare and other virtual machines. Could you please disable it by following these instructions?
 
I ran Norton Removal tool, and Uninstalled Norton Security completely. and, I removed Hyper-V in Windows Option application page.
Finally, I restarted Windows10, I could recover pc to state before I can't boot normally.
but this pc can't update by Windows update, so I did windows update of trouble shooting menu, I can't fix this problem.

Trouble shooting returns:
IsPostback_RC_PendingUpdates
IsPostback: False
Problem with BITS service :
The requested service has already been started. More help is available by typing NET HELPMSG 2182.

I tried again to stop services wuauserv, cryptSvc, bits, msiserver, and renamed SoftwareDistribution, catroot2 folder,
and started 4 services,
but It didn't change this situation.
Additionally, I did dism/sfc, but It didn't change.
 
Additionally, I checked wuauserv service, I started wuauserv from windows service panel, but this service turn to disabled in a minute.
What could I do in order to run windows update normally?
 
I ran DISM/SFC, I attached these results.

DISM:
Dism /Online /Cleanup-Image /ScanHealth
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /RestoreHealth

Dism returns this error code: 0x800f081f

SFC:
sfc /scannow

SFC returns:
"Windows Resource Protection found corrupt files but was unable to fix some
of them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log"
 

Attachments

Rich (BB code): 
2022-04-19 20:58:54, Info                  CSI    0000037b [SR] Cannot repair member file [l:11]'MsSense.exe' of Windows-SenseClient-Service, version 10.0.19041.1503, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2022-04-19 20:58:54, Info                  CSI    00000375 [SR] Cannot repair member file [l:8]'sshd.exe' of OpenSSH-Server-Components-Onecore, version 10.0.19041.964, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2022-04-19 20:58:54, Info                  CSI    0000036f [SR] Cannot repair member file [l:14]'AppVClient.exe' of Microsoft-Windows-AppManagement-AppVSystem, version 10.0.19041.1320, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2022-04-19 20:58:54, Info                  CSI    00000369 [SR] Cannot repair member file [l:9]'VSSVC.exe' of Microsoft-Windows-VssService, version 10.0.19041.1503, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2022-04-19 20:58:54, Info                  CSI    00000361 [SR] Cannot repair member file [l:44]'DiagnosticsHub.StandardCollector.Service.exe' of Microsoft-Windows-DiagnosticsHub-StandardCollector, version 10.0.19041.1466, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2022-04-19 20:58:54, Info                  CSI    00000359 [SR] Cannot repair member file [l:17]'SearchIndexer.exe' of WindowsSearchEngine, version 7.0.19041.1526, arch Host= amd64 Guest= x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2022-04-19 20:58:54, Info                  CSI    0000034c [SR] Cannot repair member file [l:12]'WmiApSrv.exe' of Microsoft-Windows-WMI-Core, version 10.0.19041.1320, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2022-04-19 20:58:54, Info                  CSI    00000340 [SR] Cannot repair member file [l:16]'AgentService.exe' of Microsoft-Windows-AppManagement-UEVService, version 10.0.19041.1526, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

2022-04-19 20:58:53, Info                  CSI    00000338 [SR] Cannot repair member file [l:13]'vmcompute.exe' of HyperV-Compute-Host-Service, version 10.0.19041.1526, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch

SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

The fix should repair most of your files apart from the sshd.exe, which I'll need to find the associated update for.
 

Attachments

I ran SFCFix with above zip file, I got following result.

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2022-04-20 15:02:24.337
Microsoft Windows 10 Build 19044 - amd64
Using .zip script file at C:\Users\keithgull\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\wow64_windowssearchengine_31bf3856ad364e35_7.0.19041.1526_none_f6b32ef836e5a7a7\SearchIndexer.exe
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_windows-senseclient-service_31bf3856ad364e35_10.0.19041.1503_none_1cc4636b44839085\MsSense.exe
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.19041.1320_none_2e0b8e36d4d512eb\WmiApSrv.exe
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-vssservice_31bf3856ad364e35_10.0.19041.1503_none_cf6c74d4cd2638d6\VSSVC.exe
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-d..b-standardcollector_31bf3856ad364e35_10.0.19041.1466_none_a5f2634a28b77867\DiagnosticsHub.StandardCollector.Service.exe
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..nagement-uevservice_31bf3856ad364e35_10.0.19041.1526_none_f2458cecdf83b550\AgentService.exe
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..nagement-appvsystem_31bf3856ad364e35_10.0.19041.1320_none_bdd1af332df43821\AppVClient.exe
Successfully took permissions for file or folder C:\WINDOWS\WinSxS\amd64_hyperv-compute-host-service_31bf3856ad364e35_10.0.19041.1526_none_6c49ce5c61003d76\vmcompute.exe

Successfully copied file C:\Users\keithgull\AppData\Local\niemiro\Archive\wow64_windowssearchengine_31bf3856ad364e35_7.0.19041.1526_none_f6b32ef836e5a7a7\SearchIndexer.exe to C:\WINDOWS\WinSxS\wow64_windowssearchengine_31bf3856ad364e35_7.0.19041.1526_none_f6b32ef836e5a7a7\SearchIndexer.exe.
Successfully copied file C:\Users\keithgull\AppData\Local\niemiro\Archive\amd64_windows-senseclient-service_31bf3856ad364e35_10.0.19041.1503_none_1cc4636b44839085\MsSense.exe to C:\WINDOWS\WinSxS\amd64_windows-senseclient-service_31bf3856ad364e35_10.0.19041.1503_none_1cc4636b44839085\MsSense.exe.
Successfully copied file C:\Users\keithgull\AppData\Local\niemiro\Archive\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.19041.1320_none_2e0b8e36d4d512eb\WmiApSrv.exe to C:\WINDOWS\WinSxS\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.19041.1320_none_2e0b8e36d4d512eb\WmiApSrv.exe.
The file \\?\C:\WINDOWS\WinSxS\amd64_microsoft-windows-vssservice_31bf3856ad364e35_10.0.19041.1503_none_cf6c74d4cd2638d6\VSSVC.exe is in use and must be replaced over a reboot.
Successfully copied file C:\Users\keithgull\AppData\Local\niemiro\Archive\amd64_microsoft-windows-d..b-standardcollector_31bf3856ad364e35_10.0.19041.1466_none_a5f2634a28b77867\DiagnosticsHub.StandardCollector.Service.exe to C:\WINDOWS\WinSxS\amd64_microsoft-windows-d..b-standardcollector_31bf3856ad364e35_10.0.19041.1466_none_a5f2634a28b77867\DiagnosticsHub.StandardCollector.Service.exe.
Successfully copied file C:\Users\keithgull\AppData\Local\niemiro\Archive\amd64_microsoft-windows-a..nagement-uevservice_31bf3856ad364e35_10.0.19041.1526_none_f2458cecdf83b550\AgentService.exe to C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..nagement-uevservice_31bf3856ad364e35_10.0.19041.1526_none_f2458cecdf83b550\AgentService.exe.
Successfully copied file C:\Users\keithgull\AppData\Local\niemiro\Archive\amd64_microsoft-windows-a..nagement-appvsystem_31bf3856ad364e35_10.0.19041.1320_none_bdd1af332df43821\AppVClient.exe to C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..nagement-appvsystem_31bf3856ad364e35_10.0.19041.1320_none_bdd1af332df43821\AppVClient.exe.
Successfully copied file C:\Users\keithgull\AppData\Local\niemiro\Archive\amd64_hyperv-compute-host-service_31bf3856ad364e35_10.0.19041.1526_none_6c49ce5c61003d76\vmcompute.exe to C:\WINDOWS\WinSxS\amd64_hyperv-compute-host-service_31bf3856ad364e35_10.0.19041.1526_none_6c49ce5c61003d76\vmcompute.exe.

Successfully pended file for replace over reboot: \\?\C:\WINDOWS\WinSxS\amd64_microsoft-windows-vssservice_31bf3856ad364e35_10.0.19041.1503_none_cf6c74d4cd2638d6\VSSVC.exe

Successfully restored ownership for C:\WINDOWS\WinSxS\wow64_windowssearchengine_31bf3856ad364e35_7.0.19041.1526_none_f6b32ef836e5a7a7\SearchIndexer.exe
Successfully restored permissions on C:\WINDOWS\WinSxS\wow64_windowssearchengine_31bf3856ad364e35_7.0.19041.1526_none_f6b32ef836e5a7a7\SearchIndexer.exe
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_windows-senseclient-service_31bf3856ad364e35_10.0.19041.1503_none_1cc4636b44839085\MsSense.exe
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_windows-senseclient-service_31bf3856ad364e35_10.0.19041.1503_none_1cc4636b44839085\MsSense.exe
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.19041.1320_none_2e0b8e36d4d512eb\WmiApSrv.exe
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-wmi-core_31bf3856ad364e35_10.0.19041.1320_none_2e0b8e36d4d512eb\WmiApSrv.exe
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-d..b-standardcollector_31bf3856ad364e35_10.0.19041.1466_none_a5f2634a28b77867\DiagnosticsHub.StandardCollector.Service.exe
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-d..b-standardcollector_31bf3856ad364e35_10.0.19041.1466_none_a5f2634a28b77867\DiagnosticsHub.StandardCollector.Service.exe
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..nagement-uevservice_31bf3856ad364e35_10.0.19041.1526_none_f2458cecdf83b550\AgentService.exe
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..nagement-uevservice_31bf3856ad364e35_10.0.19041.1526_none_f2458cecdf83b550\AgentService.exe
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..nagement-appvsystem_31bf3856ad364e35_10.0.19041.1320_none_bdd1af332df43821\AppVClient.exe
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-a..nagement-appvsystem_31bf3856ad364e35_10.0.19041.1320_none_bdd1af332df43821\AppVClient.exe
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_hyperv-compute-host-service_31bf3856ad364e35_10.0.19041.1526_none_6c49ce5c61003d76\vmcompute.exe
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_hyperv-compute-host-service_31bf3856ad364e35_10.0.19041.1526_none_6c49ce5c61003d76\vmcompute.exe
PowerCopy:: directive completed successfully.




Reboot:: directive completed successfully.




PostRebootCorruptionDetection::
No hash verification failures detected.
PostRebootCorruptionDetection:: directive completed successfully.




PostRebootRestorePermissions::
Successfully restored ownership for C:\WINDOWS\WinSxS\amd64_microsoft-windows-vssservice_31bf3856ad364e35_10.0.19041.1503_none_cf6c74d4cd2638d6\VSSVC.exe
Successfully restored permissions on C:\WINDOWS\WinSxS\amd64_microsoft-windows-vssservice_31bf3856ad364e35_10.0.19041.1503_none_cf6c74d4cd2638d6\VSSVC.exe
PostRebootRestorePermissions:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 9 datablocks.
Finish time: 2022-04-20 15:11:00.961
----------------------EOF-----------------------
 
Thank you, those files should have been successfully repaired now. I'll try and source the final file for you.
 
x BlueRobot said:
Thank you, those files should have been successfully repaired now. I'll try and source the final file for you.
Click to expand...

Excuse me, Could I ask one more question?
My PC recovered and I did windows Update,
but Windows Update Service turn to disable on running for only 1 min,
So I watched Service panel, When the service stopped, I have to restart Windows update service.
How do I solve this problem?
 
Last edited by a moderator:
SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Please find the last file attached. Afterwards, please open an elevated command prompt and then enter the following command:

Rich (BB code): 
sfc /scannow
 

Attachments

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top