How to Fix KERNEL_SECURITY_CHECK

What the error means: Windows runs integrity checks on critical kernel data structures. When one of those checks fails — something in protected memory is not what it should be — Windows stops immediately rather than continuing with corrupted data. The blue screen is the safety mechanism working, not the fault itself.

The underlying cause is nearly always one of three things: a faulty or outdated driver (most common), failing RAM, or corrupted system files. The steps below identify which, cheapest test first.

If you cannot boot into Windows

Start here. Force a shutdown three times during startup — hold the power button as Windows begins loading — and the Recovery Environment opens on the fourth attempt.

From there: Troubleshoot → Advanced options → Startup Settings → Restart, then press 5 for Safe Mode with Networking. If Windows runs normally in Safe Mode, a driver or a startup program is responsible — which is genuinely useful information, and it narrows everything below.

System Restore, in the same Advanced options menu, is the fastest fix if the crashes started recently and a restore point exists.

1. Undo whatever changed

These crashes rarely begin spontaneously. If it started after a specific event, reverse that first:

A new driver — roll it back in Device Manager: right-click the device → Properties → Driver → Roll Back Driver.
New hardware — remove it and test.
A Windows update — uninstall it under Settings → Windows Update → Update history → Uninstall updates.
New antivirus or a VPN client — both install kernel-level drivers and both are recurring causes. Uninstall properly with the vendor's removal tool, not just from the app list.
Overclocking — reset CPU, GPU and memory to stock, including any XMP or EXPO memory profile. An unstable memory profile produces exactly this error.

2. Repair system files

Open Command Prompt or Terminal as Administrator and run these in order, letting each finish:

sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

The second sfc is deliberate — DISM repairs the component store that sfc draws its replacement files from, so running it again afterwards can fix what the first pass could not.

Then check the disk:

chkdsk /f /r C:

It will ask to schedule at the next restart. Say yes. The /r pass is slow on a large drive — leave it running.

3. Test the memory

Faulty RAM is the most common hardware cause. Press Windows and search for Windows Memory Diagnostic, then restart and let it run. Any error at all means a bad module.

Windows Memory Diagnostic is not thorough. If it passes and you still suspect memory, MemTest86 from a USB stick is the real test — run it for several passes, ideally overnight.

If you have more than one stick, test them one at a time. That identifies which module is at fault, and a single bad stick can simply be removed.

4. Update drivers, properly

Get drivers from the manufacturer, not from Windows Update and not from a driver-updater utility. Those utilities are a common cause of this exact crash.

Graphics — from NVIDIA, AMD or Intel directly. For a persistent GPU-related crash, remove the existing driver with DDU in Safe Mode before installing.
Chipset and storage — from your motherboard or laptop manufacturer's support page for your exact model.
Anything with a warning triangle in Device Manager.

5. Find the culprit driver by name

If it still crashes, stop guessing. Windows writes a dump file at C:\Windows\Minidump naming the driver that failed.

Open it with WhoCrashed or BlueScreenView, both free, and read the driver name it reports. That single line usually ends the investigation — search the name, and it identifies the device or the software.

Driver Verifier is the heavier option: run verifier as Administrator, select standard settings for non-Microsoft drivers, and reboot. It deliberately stresses drivers until the faulty one crashes and is named. Be careful — it can make the machine unbootable, so know how to reach Safe Mode and run verifier /reset before starting.

6. Last resorts

Reset this PC, keeping your files — Settings → System → Recovery. Replaces Windows without wiping documents.
A clean install if the reset does not hold.
Hardware repair. If a clean install still crashes, the fault is physical — memory, storage, motherboard or power supply.

FAQs

Is it a virus?

Rarely, though malware with kernel drivers can cause it. Run a full scan, but investigate drivers and memory first.

Can a failing SSD cause this?

Yes. Corrupted system files on a dying drive produce it. Check the drive's SMART health with CrystalDiskInfo.

Why only when gaming?

Load exposes marginal hardware. That pattern points at the GPU driver, memory under load, or an inadequate power supply.

Does the stop code tell me the cause?

Only the category. The dump file in C:\Windows\Minidump is what names the specific driver.