STOP 0x000000F4
CRITICAL_OBJECT_TERMINATION
A process or thread essential to Windows was terminated. Very close cousin of CRITICAL_PROCESS_DIED — and in practice it points at storage problems even more often: a drive that briefly stopped responding takes the critical process down with it.
Likely causes, most common first
- A failing or intermittently disconnecting drive (SATA cable, failing SSD)
- Outdated SSD firmware or storage drivers
- Corrupted system files
- Third-party antivirus killing a protected process
How to fix it
1. Check drive, cable and firmware moderate
- Check drive health with the maker's tool; back up important files first.
- Desktop PC: reseat or replace the drive's SATA cable.
- Update the SSD's firmware with the maker's utility.
- Update storage/chipset drivers from your PC or motherboard maker.
2. Repair system files easy
- In an admin terminal run: sfc /scannow, then DISM /Online /Cleanup-Image /RestoreHealth
- Run: chkdsk C: /f and confirm for next reboot.
The four parameters on the blue screen
Windows shows four hex numbers with this stop code. Here's what each means — our analyzer decodes them automatically from your dump file.
| Parameter 1 | Type that terminated: 3 = process, 6 = thread |
| Parameter 2 | The process or thread object |
| Parameter 3 | Name of the process |
| Parameter 4 | Explanatory message address |
Got a crash dump? Get your verdict in seconds
Drop the .dmp file into our analyzer — it runs entirely in your browser. No upload, no size limit, no account.
Analyze my dump file →