How to fix the KERNEL_SECURITY_CHECK_FAILURE (0x00000139) blue screen
This stop code means Windows detected that a critical data structure had been corrupted and stopped to protect itself. Incompatible drivers, corrupt system files or bad memory are the usual causes. Jump to your situation below or work through the methods in order.
By Neeraj Singh ~11 min Updated Jun 2026 87% found this helpful
Error message
KERNEL_SECURITY_CHECK_FAILURE. Stop code 0x00000139. The kernel detected the corruption of a critical data structure.
Summary
KERNEL_SECURITY_CHECK_FAILURE (stop code 0x00000139) means a Windows integrity check found a critical data structure corrupted, and rather than continue in an unsafe state, the kernel stopped. This is a safety check firing, so the real cause is whatever corrupted that structure: most often an incompatible or outdated driver, corrupt system files, or faulty RAM, and sometimes disk corruption or a problem program. The fix works through those: update or roll back drivers (the minidump can name one), repair system files with SFC and DISM, test memory, and check the disk. It often appears after an upgrade or a driver update, so undoing a recent change is a good early step.
What this error means
Windows constantly checks that key internal data structures are intact. When one of these security checks finds a structure has been overwritten or corrupted, continuing could cause data loss or worse, so the kernel deliberately stops with this code.
The check is a symptom, not the disease. Something corrupted the structure, and that is usually an incompatible driver writing where it should not, corrupt system files, or memory returning bad data. Working through drivers, system files and RAM finds and removes the actual cause.
Common causes
An incompatible or outdated driver.
Corrupt system files.
Faulty or failing RAM.
A recent Windows upgrade or driver update.
Disk corruption on the system drive.
A problem application interfering at a low level.
Malware that altered system components.
Expert insight
“KERNEL_SECURITY_CHECK_FAILURE is Windows catching something corrupting its insides and refusing to carry on. It is a symptom, so I chase the cause through the usual three: drivers, system files and memory. The minidump often names a driver, so I update or roll it back, then run DISM and SFC to repair the system, then MemTest86 if it is still going. It loves to show up after an upgrade, so undoing a recent driver or update is always worth an early try.”
Manager, Tech Support & Operations · 19+ years fixing Windows and system errors
✓ How to fix it
Method 1
Read the crash for a driver
1Open the minidump in C:\Windows\Minidump with BlueScreenView, or note any module on the screen.
2It can name the driver involved.
3Target that driver next.
Method 2
Update or roll back drivers
1Update your drivers from the device or PC maker, or roll back any driver updated just before the crashes.
2An incompatible driver, often after an upgrade, is a common cause.
3Remove a newly added device to test.
Method 3
Repair system files
1Run DISM /Online /Cleanup-Image /RestoreHealth then SFC /scannow from an elevated prompt.
2This repairs corrupt system files that can trigger the stop code.
3Reboot and watch for the crash.
Method 4
Test your memory
1Run Windows Memory Diagnostic (mdsched.exe) or MemTest86.
2Reseat or replace any failing stick.
3Bad RAM can corrupt the structures behind this check.
Method 5
Check the disk
1Run chkdsk /f /r on the system drive to find and repair disk errors.
2Disk corruption can damage the data this check protects.
3Reboot and watch.
Method 6
Boot into Safe Mode if it keeps crashing
1If the PC will not stay up, let it fail twice so it enters the Recovery environment, then choose Troubleshoot, Advanced options, Startup Settings, and pick Safe Mode with Networking.
2Safe Mode loads only basic drivers, so you can work on the fix without the crash recurring.
3From there, update or roll back drivers and run the repairs below.
KERNEL_SECURITY_CHECK_FAILURE is a safety check, so chase the cause through drivers, system files and memory. Read the minidump for a driver and update or roll it back, then run DISM and SFC, then test RAM. Because it often follows an upgrade, undoing a recent driver or update early is worthwhile.
Frequently asked questions
What does KERNEL_SECURITY_CHECK_FAILURE mean?
Stop code 0x00000139 means Windows detected that a critical internal data structure was corrupted and stopped to stay safe. An incompatible driver, corrupt system files or bad RAM is usually the cause.
How do I fix it?
Read the minidump for a named driver and update or roll it back, run DISM and SFC to repair system files, test your RAM, and check the disk with chkdsk.
It started after a Windows upgrade
Roll back the driver or uninstall the update that coincided with the crashes. This stop code commonly appears after an upgrade leaves an incompatible driver in place.
Could bad RAM cause it?
Yes. Faulty memory can corrupt the data structures this check protects. Run Windows Memory Diagnostic or MemTest86 and replace any failing module.
How do I read the crash dump?
Open the minidump files in C:\Windows\Minidump with a free tool such as BlueScreenView, which lists the driver involved in the crash.
Should I check my disk?
Yes, if drivers, system files and RAM are clean. Run chkdsk /f /r on the system drive, since disk corruption can damage the data this security check guards.
Still not working?
If drivers, system files, RAM and the disk all check out, enable Driver Verifier on third-party drivers to force a hidden offender into the next dump, and run a malware scan in case a threat altered system components. You can also submit your error to us for a tailored fix.
