My Windows laptop crashes with a "Critical Process Died" BSOD and won't start normally or in Safe Mode. Running SFC /scannow or any of the DISM commands I've tried from the recovery environment results in an error. CHKDSK completed successfully with both /f and /f /r. What else should I try to repair Windows or determine whether a clean reinstall is necessary?
4 Answers
If you’re running the commands from Windows Recovery Environment, the Windows partition may not be C:. Open Command Prompt, run diskpart, then list volume, and identify the partition containing the Windows folder. After exiting DiskPart, run SFC against that actual drive, for example: sfc /scannow /offbootdir=D: /offwindir=D:Windows. Replace D: with the correct drive letter.
Since the system won’t boot at all, use a Windows installation USB and choose Repair your computer > Troubleshoot > Command Prompt. You can run the offline SFC command there, and DISM may also need the installation media as a source. Be careful to identify the correct Windows partition first with diskpart and list volume.
After backing up important files, a clean Windows installation is a reasonable next step if offline repairs still fail. Create the installer USB on another computer and reinstall from it. Since CHKDSK passed but Windows and Safe Mode both fail, the problem could be badly corrupted system files, a damaged registry or boot driver, or failing hardware.
I backed up my files with robocopy, so I’m going ahead with a fresh Windows installation unless the hardware tests reveal a problem first.
It’s also worth testing the RAM with MemTest86 or MemTest86+. Create a bootable USB, test each memory module separately, and let it complete several passes. Faulty RAM can cause recurring critical-process crashes and may make repair commands fail.
That explains a lot—I may have been targeting the wrong drive letter in the recovery environment.