How to Fix CRITICAL_OBJECT_TERMINATION BSOD (0x000000F4) on Windows

By ErrorFix · Updated October 27, 2026 · 8 min read

What error 0x000000F4 means

Windows relies on a handful of processes it simply cannot run without — the best known are csrss.exe (the Client/Server Runtime Subsystem) and wininit.exe (the Windows Initialization Process). When one of these critical processes is terminated unexpectedly, Windows has no safe way to keep going, so it halts with CRITICAL_OBJECT_TERMINATION, stop code 0x000000F4. The name describes exactly what happened: a critical object — a process — was terminated.

What makes this blue screen different from a driver crash is the range of causes. A driver bug can kill a critical process, but so can a hard drive that stops responding mid-read, system files that are corrupted, memory that returns garbage, a loose drive cable, or a Windows update that broke something at boot. That is why the fix order here starts with the drive and the system files rather than with driver rollbacks. Work through the steps in order and the crash usually reveals itself: if chkdsk finds bad sectors, the drive is the story; if SFC repairs files, corruption was the story; if the memory test fails, RAM was the story.

Common causes

• Failing hard drive or SSD: when the drive cannot deliver the files a critical process needs, the process dies and Windows halts. Bad sectors and worn-out SSDs are the top hardware cause.
• Corrupted Windows system files: a failed update or sudden shutdown can damage the files that critical processes depend on, so they crash at load.
• Bad RAM: defective memory corrupts the data critical processes read, terminating them without warning.
• Loose or failing drive connection: a SATA cable that has worked loose, or an NVMe drive not seated firmly, starves Windows of files at boot.
• Buggy Windows update: a cumulative update that lands just before the crashes begin is a prime suspect — it can break the boot-time processes directly.

How to fix error 0x000000F4 — step by step

Work through these fixes in order. If the crashes started right after an update, step 5 alone may end them; if they happen at startup, start with steps 2 and 6.

1. Boot into Safe Mode and check whether the PC is stable. Interrupt the boot process three times in a row (hold the power button during the Windows logo) to reach the Recovery screen. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 for Safe Mode. Safe Mode loads only Microsoft's own drivers and a minimal set of processes. If the PC is stable here, a third-party driver or startup program is a likely suspect. If it still crashes in Safe Mode, the drive or system files are more likely at fault — move straight to steps 2 and 3.
2. Check the system drive for errors with chkdsk. Open an admin Terminal (right-click Start > Terminal (Admin)) and run chkdsk C: /f /r. Windows will offer to schedule the scan for the next restart — accept, then restart so the scan runs before Windows loads. The /f flag fixes file-system errors and /r locates bad sectors and recovers readable data. A scan that reports bad sectors or a large number of repaired clusters is a strong sign the drive is failing; back up your files immediately even if the crashes stop.
3. Repair system files with SFC and DISM. In an admin Terminal, first run sfc /scannow and let it finish — it repairs protected Windows files, including the ones critical processes depend on. Then run DISM /Online /Cleanup-Image /RestoreHealth, which repairs the component store that SFC draws from. If SFC reported corruption it could not fix, run it again after DISM completes. Restart and use the PC normally to see whether the crashes stop.
4. Test the RAM for errors. Press Win + R, type mdsched.exe, and run the Windows Memory Diagnostic, choosing "Restart now and check for problems." Let it complete — any reported error means a memory stick is defective. If you have two sticks, test them one at a time to find the bad one; a single bad stick can terminate critical processes at random, which is why the crashes may look unpredictable. For a deeper check, MemTest86 from a USB drive runs multiple passes.
5. Uninstall the most recent Windows update. If the crashes began within a day or two of an update, that update is the prime suspect. Open Settings > Windows Update > Update history > Uninstall updates, find the most recent cumulative update, and uninstall it. Restart and use the PC for a day. If crashes stop, pause updates for a few weeks (Settings > Windows Update > Pause updates) so the same broken update does not reinstall itself before Microsoft fixes it.
6. Reseat the drive and check its health. Shut the PC down, unplug it, and open the case. Reseat the drive firmly — push a SATA drive's data and power cables fully home, or remove and reinsert an NVMe drive in its slot and tighten its screw. A loose connection is a surprisingly common cause of startup-only 0x000000F4 crashes. Then check drive health with CrystalDiskInfo (free): a "Good" status rules the drive out, while "Caution" or "Bad" means the drive should be replaced before you spend time on anything else. Clone it to a new drive rather than reinstalling from scratch if you can.

Did this fix it? Quick checklist

• No more 0x000000F4 crashes after normal use for a few days
• chkdsk completed with no bad sectors or unrepairable damage
• SFC and DISM both completed without unrepairable corruption
• Memory diagnostic passed with zero errors

If crashes continue after all six steps, open Event Viewer (Win + X > Event Viewer), go to Windows Logs > System, and look for BugCheck entries around each crash — the parameters often name the terminated process, which tells you whether to suspect a driver, a service, or the drive. As a last resort, back up your files and try a clean Windows install; if the blue screen survives a clean install on a healthy drive with good RAM, the motherboard or power supply becomes the suspect and a repair shop is the next step.