How to Fix KERNEL SECURITY CHECK FAILURE Error on Windows 11 (BSOD Guide)

The KERNEL SECURITY CHECK FAILURE error (stop code 0x00000139) is one of the most persistent Windows 11 BSOD crashes. It appears randomly during gaming, after waking from sleep, right after a Windows update, or even on a clean install. Many users also see ntoskrnl.exe listed in the crash log, which adds to the confusion.

This guide explains exactly why the error occurs, how to read the crash report to find the real cause, and which fixes actually work including the BIOS-level steps that Windows reinstalls cannot touch.

Why KERNEL_SECURITY_CHECK_FAILURE Appears on Windows 11

Windows 11 triggers stop code 0x00000139 when the kernel detects that a critical data structure has been corrupted. This is a self-protection mechanism, the system crashes on purpose to prevent silent data loss.

The most common causes are:

• A driver writes to memory it does not own
• RAM delivers unstable or incorrect data under load
• An SSD or NVMe controller corrupts data before it reaches Windows
• CPU overclocking or aggressive boost settings destabilize kernel memory
• Third-party software installs a low-level driver that conflicts with Windows 11 security features like VBS or Secure Boot

The error can appear alongside other rotating BSOD codes such as IRQL_NOT_LESS_OR_EQUAL or SYSTEM_SERVICE_EXCEPTION when a faulty driver produces different symptoms on each crash.

Ntoskrnl.exe appears in crash logs because it detects the corruption, not because it caused it. The real culprit is almost always a third-party driver or unstable hardware.

Step 1: Read the Crash Report First (Find the Real Cause)

Before changing anything, identify what Windows already recorded about the crash.

Option A: Use BlueScreenView (Fastest)

1. Download BlueScreenView from NirSoft
2. Run the tool, it reads minidump files automatically from C:\Windows\Minidump
3. Look at the Caused By Driver column
4. Note the filename (example: nvlddmkm.sys = Nvidia driver, aswSP.sys = Avast)

Option B: Check Event Viewer

1. Press Win + X and select Event Viewer
2. Go to Windows Logs > System
3. Filter for Critical events near the crash time
4. Look for error source names that match a driver or service

The driver name from this step tells you exactly where to focus. If the dump points to a graphics driver, go to Step 3. If it points to an audio or RGB driver, go to Step 4. If the dump is inconclusive, continue from Step 2.

Step 2: Disable XMP or DOCP in BIOS

Unstable RAM is the single most common cause of KERNEL_SECURITY_CHECK_FAILURE on Windows 11. XMP and DOCP profiles push RAM above its rated JEDEC speed and voltage, which can corrupt kernel memory even on high-quality kits.

What to do:

1. Restart your PC
2. Enter BIOS (usually DEL or F2 at startup)
3. Find Memory or Overclocking settings
4. Set XMP / DOCP / EXPO to Disabled
5. Save and exit

Run the system for 24 to 48 hours. If the crashes stop, RAM instability was the cause. You can try re-enabling XMP at a lower speed profile or increase DRAM voltage slightly for stability.

Step 3: Update or Roll Back Your Graphics Driver

A corrupt or incompatible graphics driver is the second most common cause. This applies to both Nvidia and AMD cards.

To update:

1. Open Device Manager (Win + X)
2. Expand Display adapters
3. Right-click your GPU and select Update driver
4. Choose Search automatically

To roll back if the crash started after a driver update:

1. Right-click your GPU in Device Manager
2. Select Properties > Driver tab
3. Click Roll Back Driver

For a clean reinstall, use DDU (Display Driver Uninstaller) in Safe Mode before installing the new driver. A clean graphics driver install resolves most cases described in the blue screen after installing graphics driver guide.

Step 4: Remove Problem Software With Low-Level Drivers

Some software installs kernel-mode drivers that conflict with Windows 11 security features. These are among the hardest crashes to trace because the software name never appears in the dump.

Temporarily uninstall the following categories:

• RGB control software: Aura Sync, Mystic Light, iCUE, Armoury Crate
• Audio enhancement tools: Nahimic, Sonic Studio, DTS Sound Unbound
• Third-party antivirus: Avast, AVG, Kaspersky, McAfee
• Hardware monitoring tools: HWiNFO64, MSI Afterburner, NZXT CAM
• Virtual machine software: VMware, VirtualBox, Hyper-V (if enabled)

Restart after each removal and test for 30 minutes before uninstalling the next item. This isolates which application is responsible.

Step 5: Use Driver Verifier to Identify the Faulty Driver

Driver Verifier forces every driver to prove it behaves correctly. A faulty driver crashes immediately and reveals its name in the BSOD.

Enable Driver Verifier:

1. Press Win + R, type verifier, and press Enter
2. Select Create standard settings
3. Select Select drivers from a list
4. Check only non-Microsoft drivers (uncheck everything with Microsoft in the Provider column)
5. Click Finish and restart

What to expect:

• A new BSOD appears within minutes or hours
• The crash screen names the actual faulty driver
• Note the driver filename

To disable Driver Verifier after finding the driver:

1. Boot into Safe Mode
2. Open Command Prompt as administrator
3. Run: verifier /reset
4. Restart normally

Once you have the driver name, search for an updated version from the hardware manufacturer’s website.

Step 6: Run SFC and DISM to Repair System Files

Corrupt Windows system files can trigger kernel security violations even without a driver or hardware problem.

Run SFC first:

1. Open Command Prompt as administrator
2. Run:

sfc /scannow

3. Wait for the scan to complete, do not close the window
4. Restart if SFC reports repaired files

Run DISM if SFC finds unrepairable files:

DISM /Online /Cleanup-Image /RestoreHealth

This pulls replacement files directly from Windows Update. An internet connection is required.

Step 7: Update SSD or NVMe Firmware

Outdated storage firmware can corrupt memory silently before Windows detects it. This step is separate from updating the storage driver in Device Manager.

What to do:

1. Identify your SSD model (open Device Manager > Disk drives)
2. Visit the manufacturer’s website (Samsung, WD, Seagate, Kingston, Crucial)
3. Download and run the official firmware update tool
4. Restart after the update completes

This step matters most for NVMe drives on systems running Windows 11 24H2.

Step 8: Run Advanced RAM Testing

Windows Memory Diagnostic misses many real RAM failures. Use MemTest86 for a definitive test.

How to use MemTest86:

1. Download MemTest86 and create a bootable USB using their tool
2. Restart and boot from the USB
3. Let the test run for at least 4 full passes (this takes several hours)
4. Any error even one means the RAM is faulty or running at an unsafe speed

If errors appear with XMP disabled, the RAM itself may be failing. Test sticks one at a time to identify which module is bad.

Step 9: Reset CPU Overclocking and Undervolting

PBO, manual overclocks, and CPU undervolting profiles can destabilize kernel memory under load or during boost transitions.

What to reset:

1. Enter BIOS
2. Load Optimized Defaults or reset CPU settings manually
3. Disable PBO (Precision Boost Overdrive) on AMD systems
4. Remove any Intel XTU or ThrottleStop undervolting profiles
5. Save and exit

Test the system under CPU load using Cinebench or Prime95 for at least 30 minutes.

When Hardware Replacement Is the Only Fix

Consider physical hardware replacement only after all software steps fail.

Hardware is likely faulty if:

• Driver Verifier shows no specific driver
• XMP is disabled and crashes continue
• MemTest86 reports errors after multiple passes
• Firmware updates do not help

Likely faulty components at this stage:

• RAM module (test sticks individually)
• Motherboard memory controller
• NVMe or SSD controller
• GPU (if dump consistently points to a display driver with no software fix)

A related issue that can occur alongside hardware instability is LiveKernelEvent errors causing screen flickering, which often shares the same driver or hardware root cause.

Related BSOD Errors on Windows 11

If the steps above do not resolve the crash, the underlying issue may be producing a different stop code on each restart. These guides cover the most common related errors:

• ntkrnlmp.exe Blue Screen Error in Windows 10 and 11: A kernel-level crash that shares causes with KERNEL_SECURITY_CHECK_FAILURE
• How to Fix ntoskrnl.exe BSOD Errors in Windows 11: Explains what ntoskrnl.exe reports and how to trace the real driver
• BSOD With Different BugCheck Strings in Windows 11: Covers rotating stop codes from a single root cause
• DPC_WATCHDOG_VIOLATION Fix Windows 10: Common on Ryzen systems and often triggered by the same drivers
• How to Fix CRITICAL_SERVICE_FAILED on Windows 11: Appears when a core service driver fails at boot
• How to Fix Blue Screen After Installing Graphics Driver: Covers GPU-specific BSOD crashes step by step

If crashes are producing unexpected shutdowns without a visible stop code, check the system rebooted without cleanly shutting down error guide for Event Viewer diagnosis steps.

For a full set of diagnostic utilities, see Best Windows Troubleshooting Tools for Common Errors.

FAQs