receive this error every 30-40 mins stop code: CRITICA_PROCESS_DIED (0xEF)

Question

I get this error stop code: CRITICA_PROCESS_DIED (0xEF) abd my system reboots

Answer 1

The stop code CRITICAL_PROCESS_DIED (0xEF) means a critical Windows system process is terminating, so Windows forces a restart to protect system integrity.

Without debugging tools, use these general troubleshooting steps:

1. Check what changed recently
   • If new hardware was added, temporarily remove or replace it and see if the crashes stop.
   • If new drivers or software (especially low‑level tools like antivirus, tuning, or hardware utilities) were installed or updated recently, uninstall or roll them back and test.
2. Check Event Viewer
   • Press Win+X → Event Viewer.
   • Go to Windows Logs → System.
   • Look for Critical or Error events at the same time as the blue screen.
   • Note any device, driver, or service that appears repeatedly and update, disable, or remove it.
3. Update firmware and drivers
   • From the PC or motherboard manufacturer, install the latest BIOS/UEFI and firmware.
   • Update chipset, storage, graphics, and network drivers from the OEM, not only Windows Update.
4. Run hardware diagnostics
   • Use the diagnostics tools provided by the PC manufacturer (often available in firmware/boot menu or as a downloadable tool) to test memory, disk, and other components.
5. Scan for malware
   • Run a full antivirus scan, including boot sectors/Master Boot Record if the tool supports it, because disk corruption from malware can cause bug checks.
6. Repair system files
   • Open Command Prompt as administrator.
   • Run:

          sfc /scannow
     

   • Wait for completion and follow any instructions. This repairs missing or corrupted Windows system files that can trigger CRITICAL_PROCESS_DIED.
7. Check Device Manager
   • Press Win+X → Device Manager.
   • Look for any device with a yellow exclamation mark.
   • Open its properties → Events tab to see errors, then update or reinstall the driver.

If comfortable with debugging and you have memory dump files, the cause can be narrowed further using WinDbg and the !analyze, !process, or !thread commands as described in the documentation.

If the problem started right after a specific Windows Update and persists after the steps above, consider uninstalling that update from Settings → Windows Update → Update history → Uninstall updates, or using System Restore to roll back to a point before the issue, if available.

---

References:

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

Answer 2

Please check to see if your PC is producing any minidump files, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.