Update graphics, network and storage drivers from the manufacturer, remove recently installed security or system utilities, run sfc /scannow with DISM, test memory with mdsched.exe, and check the drive with chkdsk.

KERNEL_SECURITY_CHECK_FAILURE, explained

KERNEL_SECURITY_CHECK_FAILURE is raised when a kernel integrity check fails, for example a linked list in memory has been overwritten. Windows stops immediately because continuing could corrupt data or open a security hole.

It became common after upgrades from older Windows versions, when old drivers kept running on the new kernel. Today it is most often triggered by outdated drivers (especially network, graphics and antivirus), unstable memory or corrupted system files.

What you'll see

  • Blue screen with “Stop code: KERNEL_SECURITY_CHECK_FAILURE”.
  • Crashes under load, while gaming, or when waking from sleep.
  • Started after a Windows upgrade or a new driver.

What causes KERNEL_SECURITY_CHECK_FAILURE

  • Outdated or incompatible drivers.
  • Third-party antivirus or system tools hooking into the kernel.
  • Faulty or overclocked RAM.
  • Corrupted system files or disk errors.

How to fix it

  1. Update key driversInstall the latest graphics (NVIDIA/AMD/Intel), chipset, network and storage drivers from the manufacturer's site.
  2. Remove conflicting softwareUninstall third-party antivirus, VPNs and tuning utilities installed before the crashes began. If the PC crashes before you can do anything, start Safe Mode: Shift + Restart → Troubleshoot → Advanced options → Startup Settings → Restart → 4. Three failed boots in a row also bring up these menus.
  3. Repair system filesRun DISM and SFC (commands below) and restart.
  4. Test memoryRun mdsched.exe. Disable XMP/EXPO or any overclock while testing.
  5. Check the driveRun chkdsk C: /scan and check the SSD maker's tool for firmware updates.
  6. Find the exact driverAfter the next restart, look in C:\Windows\Minidump. Loading the latest .dmp file in WinDbg and running !analyze -v typically names the guilty driver; BlueScreenView is a simpler alternative.

Command

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

Run in an elevated Command Prompt (Run as administrator). DISM can take 10–20 minutes; run sfc after it finishes, then restart.

How to confirm the fix: The PC survives the workload that used to crash it (gaming, sleep/wake) for several days.

Stop it happening again

Keep drivers current from official sources and avoid running more than one security product.