My Windows laptop crashes with a "Critical Process Died" BSOD and won't start normally or even in Safe Mode. SFC /scannow fails, and the DISM commands I've tried also return errors. I ran chkdsk C: /f and chkdsk C: /f /r, and both completed without finding a problem. Is there anything else I should try from the recovery environment before reinstalling Windows?
3 Answers
When you use the recovery Command Prompt, Windows may not be mounted as drive C:. First run diskpart, then list volume, and identify the partition containing the Windows folder. Exit DiskPart and run SFC against that actual drive, for example: sfc /scannow /offbootdir=D: /offwindir=D:Windows. Replace D: with the correct letter. Running SFC against the wrong drive can make it appear to fail or scan the recovery environment instead.
It’s also worth testing the RAM from a bootable USB with MemTest86 or MemTest86+. Test each memory module separately and let it run several passes. Faulty RAM can cause repeated critical-process crashes even when chkdsk reports that the drive is fine.
Since neither normal mode nor Safe Mode works, and both SFC and DISM are failing, a clean Windows installation is a reasonable next step—especially after backing up your data. Create an installation USB on another computer, boot from it, and use the recovery tools first if you still want to attempt offline repairs. If those don’t work, reinstall Windows after confirming your important files are safely backed up.
That makes sense—I hadn’t realized the drive letters could change in the recovery environment. I’ve already backed up my files with robocopy, so I may try this once and then move on to a clean installation if it still fails.