What is 0x00000139?
KERNEL_SECURITY_CHECK_FAILURE (0x00000139) is a critical-severity fault affecting the Windows operating system. The kernel detected corruption of security-critical data structures. Another common trigger is driver conflict (typically anticheat or antivirus). Work through the steps below in order.
Common Causes
- Driver conflict (typically anticheat or antivirus)
- Kernel stack overflow
- Corruption of system files
Step-by-Step Fix Guide
-
1
Enable memory integrity protection in Windows Security
Begin with Enable memory integrity protection in Windows Security; it's the step that resolves 0x00000139 for the largest share of reported cases.
-
2
Uninstall foreign antivirus
Not every case resolves on the first try; the steps that follow cover rarer windows instability situations.
-
3
Repair corrupted files with DISM and SFC
"Repair corrupted files with DISM and SFC" targets corruption of system files, one of the documented causes of 0x00000139.
Commands & Diagnostics
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
Frequently Asked Questions
Driver conflict (typically anticheat or antivirus) accounts for the majority of 0x00000139 reports; kernel stack overflow and corruption of system files come up less often but are documented.
Most 0x00000139 reports resolve after "Enable memory integrity protection in Windows Security". The rest of the guide above is there for the cases that don't.
Treat 0x00000139 as urgent — it's flagged critical severity, meaning repeated occurrences risk data loss or hardware damage.
You shouldn't need to. Work through the guide above first — a reinstall is only worth considering if none of those steps help.
Sometimes. Microsoft regularly releases patches that fix known BSOD triggers including 0x00000139. Make sure Windows is fully up to date via Settings → Windows Update before attempting more advanced fixes.
Still Need Help?
Search our full database of 535+ documented PC errors for more solutions and step-by-step repair guides.
Search Error Database