CRITICAL_PROCESS_DIED Troubleshooting

Question

Last week, my desktop running Windows 10 bluescreened with the error message "CRITICAL_PROCESS_DIED." I am able to boot my computer and log in, but once I log in, the computer bluescreens with the same error message within about twenty seconds. I have not installed any new hardware recently beyond a USB cable I did not yet plug in to a device. However, power was cut to the computer suddenly during a snow storm a few days before the bluescreen first occurred. I suspect that my windows installation is somehow corrupted, and that has characterized my approach in trying to resolve the issue. Here is what I have already done:

1. First, I entered the Windows 10 recovery environment. I used the startup repair option, but this did nothing to resolve the issue. I tried to boot into safe mode or to boot from a restore point, but both of these options did nothing (i.e. they just restarted my computer).
2. Second, since the Windows 10 recovery environment wasn't working, I made a Windows 10 installation media using my laptop which runs Windows 10, and I booted my computer with this loaded on a USB drive. I tried repairing my installation with this installation media with mixed results. For one, I was able to access the recovery environment in a working state -- I tried system restore, and I got a dialogue box informing me I had no restore points. I was able to access the command prompt. There did not seem to be an option to boot into safe mode. I also once again activated startup repair, but this didn't resolve the issue (i.e. the computer still bluescreened about fifteen seconds after logging in).
3. Third, while using my installation media to repair the installation, I opened command prompt in the recovery environment to try and run some commands I know are often used to resolve corruption. First I tried running "sfc /scannow," but this operation failed with the message "Windows Resource Protection could not perform the requested operation. Then I tried running DISM to fix my installation using my installation media as a source. My exact command was "dism /image:C:\ /cleanup-image /restorehealth /source:I:\sources\install.esd:1 /limitaccess." This seemed promising at first, as DISM loaded and the progress bar ticked up. However, it stalled at around 25% completion and failed with error 1726 ("The remote procedure call failed. An error occurred closing a servicing component in the image. Wait a few minutes and try running the command again"). So I waited ten minutes and tried running the command again. It failed at 4% completion with the same error. I did this two more times with the same result. On the next time, it failed with a new error message -- error 433 (a device which does not exist was specified).

I am out of ideas. It would be very helpful if I could boot into safe mode, but as stated above, my computer fails to boot into safe mode from the recovery environment as the option does nothing, and it does not seem like I can boot into safe mode from the recovery environment while I am accessing the recovery environment using the "repair this installation" option with my installation media. Is there some way I can boot into safe mode while having my installation media loaded? Are there other commands I could try running from the command prompt in the recovery environment? I feel like I've come to a brick wall.

Answer 1

Aaron,

I tried to copy over my files onto another one of my drives through file explorer as well as xcopy, but both ran into errors. I have ordered a SATA III to USB adapter and will use this to attempt to move my files onto my other computer. I think reinstalling Windows is my only option at this point, and if that fails, I will probably just go see a computer technician. Thanks for your guidance.

Answer 2

Reinstalling Windows only affects your C drive and windows.old only saves personal data, application data is not retained.

Regarding your SSD question, yes, you can just remove it and back it up on another device, provided your data files are not protected or Bitlocker enabled.

Regarding your question about using command prompt to backup your data, yes, you can, you can refer to the following link:

Rescue Files when Windows Won't Start - Microsoft Community

I look forward to your feedback.

Answer 3

Aaron,

Thank you for getting back to me. I entered the recovery environment using the USB installation media and ran "chkdsk C: F." It deleted an orphan file segment but could only run through the first stage of the process before running into two unspecified errors. I have attached a picture of the output below (sorry it's not a screenshot).

I then restarted my computer after removing the USB installation media and tried to boot into safe mode. It still didn't work. Then I tried to boot normally and the blue screen still occurred.

I will try the custom installation of Windows 10 from my installation media, but I have two questions before I attempt this procedure:

1. From what I understand, this process takes all personal files and applications on my C: drive and moves it into a windows.old folder that I can then recover from once a new windows installation is installed. Is there a danger that my personal files and applications might get overwritten by this process? I ask this question because while I have free space on my C: drive, I don't know the size of the new Windows 10 installation. Also, does this procedure touch drives beyond my C: drive? Should I disconnect my other drives so that there isn't a risk of loss?
2. You stated that I might need to remove my hard disk to backup onto another computer. My C: drive is one of those thin SSDs that you slot directly onto the motherboard of the computer. If I were to backup this drive, would I remove it and get some sort of adapter to allow another computer to interface with it?

Another question I have regarding file backup: I can access file explorer from the command prompt in the recovery environment using the USB installation media. Could I just copy and paste the contents of my C: drive into one of my external drives to act as a backup without loss of my personal files and applications?

I will try the custom installation, but at this point, I am wondering if there might be physical damage to certain sectors of my C: drive which might explain these unspecified errors. I guess we will see. Sorry for the abundance of questions; this is all new to me.

Answer 4

Hello, MatthewZW

Welcome to the Microsoft community.

Thank you for your feedback. Based on your description and the operations that have been performed, it seems that your recovery partition may be corrupted at the moment and there is a big chance that there is a hardware problem. Here are some options for troubleshooting:

1. You can use the USB installation media again to try to enter the command prompt in the recovery environment and enter the following command:

chkdsk C: /F

Disclaimer: Running chkdsk checks the file system and file system metadata of the volume for logical and physical errors. To avoid causing unnecessary trouble, please follow the above steps step by step and do not interrupt or cancel during the run, and make a backup of important data.

2. If this method does not work, you can try to see if you can enter the BIOS and try to reinstall Windows.

 How to: Perform a Custom Installation of Windows 11 and Windows 10 - Microsoft Community

For file backup you may need to remove your hard disk and backup on another computer.

If you can't install Windows or you are experiencing problems, then it is a problem with your hardware and you are advised to contact a professional computer repairer for assistance.

I look forward to your feedback which will help me pinpoint your problem.

Best Regards,

Aaron| Microsoft Community Support Specialist