The Problem
Your PC blue-screens with the stop code KERNEL_SECURITY_CHECK_FAILURE. It might happen while gaming, waking from sleep, plugging in a USB device, or seemingly at random.
This stop code means a kernel-level integrity check failed — Windows found that a critical data structure was corrupted. In practice, the cause is almost always one of three things: an incompatible or outdated driver, failing RAM, or corrupted system files. Old drivers written before Windows 11's stricter memory-integrity enforcement are the single most common trigger.
Quick Checks Before You Start
- Did you just install new hardware or a peripheral? Unplug it and see if the crashes stop.
- Did the crashes start after a specific program install? Especially VPNs, antivirus tools, or anything with its own driver — uninstall it first.
- Crashing before you can do anything? Boot into safe mode: how to enter Safe Mode in Windows 11.
Step 1: Find the Failing Driver
Windows usually logs which driver caused the crash.
- Press
Win + R, typeeventvwr.msc, press Enter. - Go to Windows Logs > System and look for Error or Critical entries at the crash time. A BugCheck entry (Event ID 1001) may name a
.sysfile. - Search that filename online — it maps to a specific driver (e.g.,
nvlddmkm.sys= NVIDIA graphics,netwtw*.sys= Intel Wi-Fi). - Update that driver from the manufacturer's website, or if the crashes began after updating it, roll it back in Device Manager > right-click device > Properties > Driver > Roll Back Driver.
No obvious culprit? Update the big three anyway: graphics, chipset, and network drivers. See how to update outdated drivers.
Step 2: Repair System Files
- Right-click Start > Terminal (Admin).
- Run:
sfc /scannow - Then:
DISM /Online /Cleanup-Image /RestoreHealth - Restart. Full walkthrough: repair Windows 11 system files with SFC and DISM.
Step 3: Test Your RAM
Kernel structures live in RAM — a failing stick corrupts them and triggers this exact stop code.
- Press
Win + R, typemdsched.exe, press Enter, and choose Restart now and check for problems. - Let both passes finish and check the result notification after reboot.
- If errors appear, or crashes continue despite a clean result, run MemTest86 from a USB stick overnight — it's far more thorough.
- Disable any XMP/EXPO memory profile in BIOS while testing; unstable profiles cause this stop code even on healthy RAM.
The related MEMORY_MANAGEMENT blue screen guide covers RAM isolation in more detail.
Step 4: Check the Disk
- In Terminal (Admin), run:
Confirm withchkdsk C: /f /rYto schedule it on next restart, then reboot and let it complete. - Verify overall drive health with check SSD and hard drive health.
Step 5: Uninstall Recent Updates or Roll Back
If the crashes began right after a Windows update:
- Open Settings > Windows Update > Update history > Uninstall updates.
- Remove the most recent quality update and restart.
- The full rollback procedure — including uninstalling a bad feature update — is in fix Windows 11 after a bad update.
If nothing above stops the crashes, back up your files and do a repair install: reinstall Windows without losing data.
Different stop code? See the general blue screen troubleshooting guide, or the specific guides for DPC_WATCHDOG_VIOLATION and VIDEO_TDR_FAILURE.
Related guides
How to Fix PFN_LIST_CORRUPT in Windows 11
PFN_LIST_CORRUPT means Windows' index of physical memory pages was damaged. Test the RAM first, then the storage driver — here is the order that works.
How to Fix BAD_POOL_HEADER in Windows 11
BAD_POOL_HEADER means a driver corrupted Windows' kernel memory pool. Track down the driver, antivirus, or RAM stick behind it with these ordered checks.
How to Fix KMODE_EXCEPTION_NOT_HANDLED in Windows 11
KMODE_EXCEPTION_NOT_HANDLED means a kernel-mode program hit an error nothing caught. Find the driver behind it and stop the crashes with these ordered checks.
How to Fix KERNEL_DATA_INPAGE_ERROR in Windows 11
KERNEL_DATA_INPAGE_ERROR means Windows could not read data back from the drive. Read the sub-code, test the disk and cable, and fix the real cause.
Fix SYSTEM_THREAD_EXCEPTION_NOT_HANDLED in Windows 11
This blue screen usually names the driver that crashed, right on the screen. Read that .sys file, roll the driver back, and stop the reboot loop for good.