how to fix ERROR stop code :CRITICAL_PROCESS_DEAD(0Xef)

Question

I have follow the steps given:

The first step is to confirm whether the error occurs consistently at boot or only intermittently during use. If it happens immediately at startup, boot into the Windows Recovery Environment (WinRE) by interrupting the boot sequence three times (power off during the spinning dots). From WinRE, run Command Prompt and execute:

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

This will check and repair system files in the offline image. Follow up with:

DISM /Image:C:\ /Cleanup-Image /RestoreHealth

to repair component store corruption.

to repair component store corruption.

When i type the prompt DISM /Image:C:\ /Cleanup-Image /RestoreHealth, it shows error 87

Answer 1

Hi. I'm David, and I'm happy to help you.

---

DISM error 87 usually means the command syntax is incorrect or not supported in the environment you're running it.

---

You may need to adjust the command syntax slightly. I'll guide you through that. But first, could you confirm whether Windows starts correctly in Safe Mode with Networking?

https://support.microsoft.com/en-us/windows/windows-startup-settings-1af6ec8c-4d4a-4b23-adb7-e76eef0b847f

At the "Startup settings" step, press 5 or F5 to start Windows in Safe Mode with Networking.

---

If Windows starts in Safe Mode with Networking, see if your computer created minidump files.

These files are in C:\Windows\Minidump.

(If you don't have a Minidump folder, check if it is in the plural Minidumps.)

Copy any files you have to your desktop and store them in a ZIP file. Then, upload the ZIP file to the cloud (OneDrive), choose to share it, and get the link.

Then, post the link to the ZIP file here so I can have a look.

---

Looking forward to your reply.

Feel free to ask any questions you may have.

Answer 2

When i type in this: DISM /image:D:\ /cleanup-image /restorehealth

It shows Error 2

Answer 3

Error 87 with DISM usually indicates a syntax problem or that the command is not valid in the current environment.

For a CRITICAL_PROCESS_DIED (0xEF) stop error where the system does not boot normally, the supported approach is:

1. Boot into Windows Recovery Environment (WinRE).
   • If needed, start WinRE from Windows installation media, then select Repair your computer → Troubleshoot → Advanced options → Command Prompt.
2. Identify the correct system volume letter in WinRE.
   • In Command Prompt, run:

          BCDEdit
     

   • In the Windows Boot Loader section, note the drive letter shown next to osdevice (for example, D:). This is the system volume to use in later commands. Do not assume it is C: in WinRE.
3. Run Check Disk on the system volume.
   • Replace D: with the osdevice drive letter from the previous step:

          CHKDSK /f D:
     

4. Run System File Checker (SFC) in offline mode against the same volume.
   • Again, replace D: with the correct drive letter:

          SFC /scannow /offbootdir=D:\ /offwindir=D:\Windows
     

5. Run DISM /Cleanup-Image /RestoreHealth against the same offline image.
   • Use the same drive letter as above:

          DISM /image:D:\ /cleanup-image /restorehealth
     

   • Error 87 can occur if the path after /image: is wrong, missing the backslash, or points to a drive that does not contain a valid Windows image. Using the correct D:\ (or whatever osdevice is) avoids this.
6. If DISM reports issues found and fixed, repeat the SFC scan:

      SFC /scannow /offbootdir=D:\ /offwindir=D:\Windows
   

If the stop error persists even after successful SFC and DISM repairs, follow the advanced startup troubleshooting guidance for Windows boot issues, including checking for pending.xml and related registry entries, or collecting a memory dump for deeper analysis.

---

References:

• Use Windows Recovery Environment (WinRE) to troubleshoot common startup issues
• Advanced troubleshooting for Windows startup issues
• DISM Operating System Package (.cab or .msu) Servicing Command-Line Options
• Windows Stop Error - #0x000000EF "Critical Process Died"
• Use the System File Checker tool to repair missing or corrupted system files