KERNEL_SECURITY_CHECK_FAILURE is a blue screen that means Windows caught a data structure in kernel memory that had been corrupted. It stopped rather than continuing with memory it could not trust.
Three things cause it, in this order: a bad driver, faulty memory, and damaged system files. The order matters — driver problems are far more common than the other two combined.
Checked August 2026. Applies to Windows 11 and Windows 10 22H2.
First: when does it happen?
The pattern narrows the cause more than anything else you can do.
| When it crashes | Most likely cause |
|---|---|
| Right after installing a driver or device | That driver |
| Only under load — games, rendering, compiling | Memory, or an unstable overclock |
| Randomly, including at idle | Memory, or storage |
| Right after a Windows update | A driver incompatible with the new build |
| Only when a specific device is connected | That device’s driver |
| During boot, every time | Boot driver or file system corruption |
1. Undo the most recent change
If the crashes started at a definite point, reverse that change before doing anything else:
- A driver: Device Manager → the device → Properties → Driver → Roll Back Driver.
- A Windows update: Settings → Windows Update → Update history → Uninstall updates.
- New software: uninstall it, particularly anything with a driver — VPN clients, virtual drives, monitoring tools, anti-cheat.
- Anything at all: use a restore point from before the trouble.
2. Remove any overclock
Including XMP and EXPO memory profiles, which are factory overclocks. Load Optimized Defaults in the firmware and run at stock while you diagnose. An unstable memory profile produces exactly this stop code.
3. Test the memory
Corrupted kernel structures are what failing RAM looks like from the inside.
The built-in tool is a starting point:
- Press Win + R, type
mdsched.exe, press Enter. - Choose Restart now and check for problems.
For anything conclusive, run MemTest86 from a USB stick for at least four full passes. With more than one stick, test them individually — that identifies which one is faulty rather than only that one is.
4. Repair system files and the disk
From an elevated Command Prompt:
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
chkdsk C: /f /rchkdsk with /f /r needs a restart and can take hours on a large mechanical drive. It is worth doing once when crashes are random.
5. Find the driver responsible
The blue screen names the check, not the culprit. The crash dump names the culprit.
Read the dump
- Download WhoCrashed or BlueScreenView — both are free and read
C:WindowsMinidump. - Open the most recent dump and look for the driver file named as the probable cause.
A .sys file name is usually enough to identify the hardware: nvlddmkm.sys is NVIDIA graphics, iaStorA.sys is Intel storage, rt640x64.sys is a Realtek network adapter.
Make sure dumps are being written
If C:WindowsMinidump is empty:
- Press Win + R, run
sysdm.cpl. - Advanced → Startup and Recovery → Settings.
- Set Write debugging information to Small memory dump (256 KB).
6. Driver Verifier — advanced
Verifier stresses drivers deliberately to force the faulty one to reveal itself. It is effective and it is also the fastest way to make a machine unbootable, so read this whole section first.
Driver Verifier will cause repeated blue screens by design. Before enabling it: create a restore point, and make sure you know how to reach Safe Mode. If the machine will not boot afterwards, enter Safe Mode and run verifier /reset.
- Run
verifierfrom an elevated prompt. - Choose Create custom settings (for code developers).
- Select the standard tests, but not Low Resource Simulation.
- Choose Select driver names from a list and tick only non-Microsoft drivers.
- Restart and use the machine normally.
When it crashes, the dump names the offending driver directly. Then run verifier /reset and update or remove that driver.
7. Update the drivers that matter
Get them from the hardware manufacturer, not from Windows Update, and not from a “driver updater” utility:
- Graphics: NVIDIA, AMD or Intel directly
- Chipset: your motherboard or laptop manufacturer
- Storage: the SSD maker’s utility, which also updates firmware
- Network: the laptop or motherboard vendor
In order, what to try
- Undo whatever changed most recently.
- Remove every overclock, including XMP/EXPO.
- Run MemTest86 for four passes.
- Run DISM, SFC and chkdsk.
- Read the minidump to name the driver.
- Update or remove that driver.
- Use Driver Verifier only if the dump is inconclusive.
Frequently asked questions
What does KERNEL_SECURITY_CHECK_FAILURE mean?
Windows verified a kernel data structure and found it corrupted, so it stopped rather than continuing with untrusted memory. It is a safety mechanism, not the fault itself.
Is my hard drive failing?
Possibly, but memory and drivers are more likely. Run chkdsk and check the drive’s SMART data — see how to check SSD health.
Will reinstalling Windows fix it?
Only if the cause is software. It does nothing for failing memory or an unstable overclock. Rule out the hardware first, or you will lose a day and still be crashing.
Can I lose files?
A blue screen loses unsaved work in open applications. Saved files are not affected, unless the underlying cause is a failing drive — which is a reason to back up now rather than later.
It only happens in one game.
That usually points at the graphics driver or at memory under load, since games stress both harder than anything else. Clean-install the graphics driver at stock clocks, then test memory.
