computer constantly restarts critical process died since windows update

This problem appeared for me after restarting my PC two afternoons ago and I've run every test possible and finally have a solution.

I have a 2019 Alienware Area-51m for reference. The problem after lots of diagnostics and fix attempts is from Alienware control panel. I think they recently pushed through some fatal updates to cause this stop code.

My solution is to go 'CMD+R', type 'msconfig' and hit 'Enter'. Go to the tab 'Services' and at the bottom check the 'Hide all Microsoft Services' checkbox. In the list of services, disable everything named Alienware or AWCC (you might also need to disable some Dell services if you have them, but try AWCC first). The three services in my case are: "AlienwareSupportAssist Remediation", "AWCCService", and "Alienware Client Management Service". As I type this, I've hit about 90mins without the forced reset/crash.
Be aware that if lighting, FX, performance and fan profiles are important to you, this will disable them to default firmware behaviour.

If this doesn't work, I'll mention that during my tests/diagnostics, I happened to see an issue with hard drive diagnostics encountering a problem with the partition table half of the time. The recovery environment's repair tool would fix it, but it would appear again after running diagnostics again 2-3 times. This meant I'd have to buy a new SSD and re-install windows on it as a fix (even had the SSD ready to be ordered in my basket). Hopefully you can avoid spending money too.

Cheers!

Hi,

Are you able to access Windows, or do you get a BSOD (Blue Screen of Death) right when you try to start the Windows screen?

If it is a laptop or desktop, if possible, could you provide the laptop model or your desktop configuration?

Thanks

The stop code CRITICAL_PROCESS_DIED (0x000000EF) indicates that a critical Windows system process has failed or become corrupted. This often appears as a blue screen and forces an automatic restart to protect system integrity.

For home Windows systems where this started after a recent update and causes frequent restarts, use these general troubleshooting steps:

1. Remove recent hardware or drivers
   • If any new hardware or device drivers were added around the time of the problem, remove or disconnect the hardware and/or uninstall or roll back the driver.
   • This helps identify whether a new device or driver is triggering the failure.
2. Boot into Safe Mode
   • Start the PC in Safe Mode to see if the error still occurs with only essential drivers and services loaded.
   • If the system is stable in Safe Mode, the cause is likely a third‑party driver, service, or software installed recently.
3. Check Event Viewer
   • Open Event Viewer and review the System log for critical errors that occur just before each CRITICAL_PROCESS_DIED stop.
   • Use those entries to identify any specific driver, service, or component that is failing.
4. Run System File Checker
   • Open an elevated Command Prompt and run:

          sfc /scannow
     

   • This scans for and repairs missing or corrupted Windows system files that can cause critical processes to fail.
5. Check Device Manager
   • Open Device Manager and look for devices marked with an exclamation point (!).
   • For any such device, review its events and update, disable, or uninstall the driver as appropriate.
6. Check for firmware/BIOS and hardware issues
   • Verify whether an updated system BIOS or firmware is available from the PC or motherboard manufacturer and apply it if appropriate.
   • Run the hardware diagnostics provided by the system manufacturer to rule out hardware faults.
7. Scan for malware
   • Run a full antivirus scan, ensuring the tool checks the disk thoroughly, including the boot area, as disk corruption from malware can cause system bug checks.
8. Ensure Windows is fully updated and has enough disk space
   • Install any pending Windows updates once the system is stable enough to do so.
   • Ensure there is sufficient free disk space (typically at least 10–15% of the system drive) so Windows can create necessary files and logs.

If the problem persists and occurs frequently, advanced analysis with crash dumps and a debugger (WinDbg) is typically required to identify the exact process or thread that is failing and why.

References:

• Bug check 0xEF: CRITICAL_PROCESS_DIED
• Troubleshooting Windows unexpected restarts and stop code errors