Kernel Security Check Failure: Fixes That Work

A “Kernel Security Check Failure” is a Windows Blue Screen of Death (BSOD) stop code that appears when the operating system’s core (the kernel) detects a violation in its own security or integrity checks. This typically points to corrupted system files, outdated or faulty drivers, or incompatible software, and it can often be fixed by running built-in Windows repair tools, updating drivers, or removing recently installed programs.

What Does This Error Mean?

The kernel is the deepest layer of Windows, managing memory, processes, and hardware communication. During normal operation, it constantly verifies that critical data structures haven’t been tampered with or corrupted. When the kernel finds something unexpected—like a driver writing to the wrong memory region or a system file being altered—it halts the system to prevent further damage. The “Kernel Security Check Failure” stop code (0x00000139) is one of several messages Windows uses to signal this internal inconsistency.

This error is not a hardware failure notification by itself. It simply tells you that the kernel’s security checks failed. The underlying cause could be software-related (most common), a driver bug, or, less frequently, failing RAM or a dying hard drive. Because the kernel interacts with everything, the list of possible triggers is broad, but the troubleshooting steps follow a logical order from least to most invasive.

Common Causes and Triggers

Understanding what typically triggers this error helps you decide where to start. The most frequently reported causes include:

Corrupted system files: A failed Windows update, sudden power loss, or disk errors can leave essential files damaged.
Outdated or buggy drivers: Especially graphics card drivers, network adapters, and storage controllers. Third-party antivirus or firewall drivers are also notorious for causing this specific stop code.
Incompatible software: Recently installed applications, particularly those that hook deep into the system like system utilities, overclocking tools, or virtual machine software.
Failing hardware: Faulty RAM (random access memory) or a failing SSD/HDD can cause data corruption that the kernel detects.
Overclocking or incorrect BIOS settings: Unstable CPU or memory overclocks can lead to data corruption and this exact error.

If the error started after a specific event (like installing new software or connecting a new device), that event is your biggest clue.

How to Fix the Error: Step-by-Step

Work through these fixes in order. Each one addresses a common cause, and you can test after each step by using your PC normally. If the error doesn’t return, you’re done.

Run the Windows Memory Diagnostic. Type “Windows Memory Diagnostic” in the Start menu and select it. Choose “Restart now and check for problems.” This will test your RAM for errors. If it finds any, you likely need to replace the faulty stick.
Run System File Checker (SFC) and DISM. Open Command Prompt as administrator. Type sfc /scannow and press Enter. After it finishes, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This repairs corrupted system files. Restart your PC afterward.
Update your drivers. Open Device Manager (right-click the Start button). Expand categories like “Display adapters,” “Network adapters,” and “Storage controllers.” Right-click each device and select “Update driver” > “Search automatically for drivers.” Also check your motherboard manufacturer’s website for chipset driver updates.
Uninstall recently installed software. Go to Settings > Apps > Installed apps. Sort by install date. Uninstall anything you added right before the errors started. This includes driver update tools and system optimizers.
Run a disk check. Open Command Prompt as administrator and type chkdsk /f /r. You’ll be prompted to schedule it for the next restart. Do so, then restart. This checks for and fixes disk errors.
Disable overclocking. If you overclock your CPU, GPU, or RAM, revert to default settings in your BIOS/UEFI. Even a mild overclock can cause instability.
Check for Windows updates. Go to Settings > Windows Update and install any pending updates. Microsoft often releases fixes for known BSOD causes.

If the error persists after all these steps, the issue is likely hardware-related. Try reseating your RAM sticks (remove and reinsert them) and checking all cable connections. If you have multiple RAM sticks, try booting with only one at a time to isolate a faulty module.

Using Blue Screen Dump Files for Diagnosis

When a BSOD occurs, Windows creates a minidump file that contains information about what was running at the moment of the crash. Analyzing this file can pinpoint the exact driver or process responsible. You can view these files using the built-in “Reliability Monitor” (search for it in the Start menu) or by using the “Event Viewer” under Windows Logs > System. Look for events with the source “BugCheck” and note the parameter details. While interpreting the raw dump file requires specialized tools like WinDbg (a free Microsoft tool), the Reliability Monitor often shows a readable summary of which application or driver was likely at fault. This can save you hours of guesswork by telling you exactly which driver to update or roll back.

When to Suspect Hardware Failure

If the error appears randomly, regardless of what you’re doing, and especially if it happens during boot or while idle, hardware becomes a more likely culprit. RAM is the most common hardware cause. A faulty stick can corrupt data in memory, which the kernel then detects. Hard drive issues can also cause this, as corrupted files on disk are loaded into memory. Less common but possible are failing power supplies (causing unstable voltage) and overheating components. If you’ve exhausted all software fixes, consider running a hardware diagnostic tool provided by your PC or motherboard manufacturer. Many manufacturers include a built-in diagnostic in the BIOS/UEFI that you can access by pressing a specific key during startup (often F12 or Del).

Preventing Future Occurrences

Once you’ve fixed the immediate problem, a few habits can reduce the chance of it returning:

Keep Windows and all drivers updated, but avoid installing driver updates from third-party “driver booster” apps—always use the manufacturer’s site or Windows Update.
Install a reliable antivirus and keep it updated, but only run one real-time security suite at a time.
Shut down your PC properly instead of holding the power button.
If you use a laptop, ensure proper ventilation to prevent overheating.
Periodically run sfc /scannow and chkdsk as preventive maintenance.

Frequently Asked Questions

Is Kernel Security Check Failure a virus?

No, it’s not a virus itself. It’s a Windows stop code indicating a system integrity check failed. However, a severe malware infection could potentially corrupt system files and cause this error. If you suspect malware, run a full scan with Windows Defender or a reputable third-party antivirus.

Can this error be caused by a faulty GPU?

Yes, a failing graphics card or its driver can cause this error. The kernel communicates with the GPU driver constantly, and a buggy or corrupted driver can trigger the security check failure. Try updating your GPU driver, or if the error started after a driver update, roll back to the previous version.

Will I lose my files if I fix this error?

No, the fixes described here—system file checker, disk check, driver updates—do not delete your personal files. However, if the underlying cause is a failing hard drive, you could lose data. It’s always wise to back up important files regularly, especially if you’re experiencing BSODs.

How long does it take to fix this error?

It depends on the cause. Simple fixes like running SFC and updating drivers can take 30 minutes to an hour. If you need to replace faulty hardware, it could take days to order a replacement. The step-by-step approach usually resolves it within a few hours of troubleshooting.

Should I just reinstall Windows?

Reinstalling Windows is a last resort. It will definitely fix any software-related cause, but it won’t fix faulty hardware. If you’ve tried all the steps above and the error persists, a clean install is worth trying before buying new hardware, but first rule out RAM and disk issues with the diagnostics mentioned earlier.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →