KERNEL_SECURITY_CHECK_FAILURE (0x00000139)? It's a Corrupted Driver or Data Structure

Your PC blue-screens with KERNEL_SECURITY_CHECK_FAILURE (stop code 0x00000139).

Why: Microsoft’s bug-check page says 0x139 “indicates that the kernel detects the corruption of a critical data structure.” A common case is LIST_ENTRY corruption, where a driver mismanaged a linked list. The page’s general troubleshooting tips point at recently added hardware, recently added or updated drivers/services, and Device Manager warnings — so start with what changed.

Fix 1: Update or roll back the driver that changed

Microsoft’s tips say to remove or update recently added drivers and services, and to update any device flagged in Device Manager.

1. Press Win + X → Device Manager.
2. Look for any device with a yellow exclamation mark (!). Right-click it → Update driver → Search automatically, or grab the current driver from the hardware maker.
3. If the crashes began right after a driver update, right-click the device → Properties → Driver → Roll Back Driver.

Network, GPU, and storage drivers are the usual culprits — get them from the vendor, not just generic Windows Update.

Fix 2: Undo recent hardware and software changes

Per Microsoft’s tips: if you recently added hardware, try removing or replacing it (or check the maker for patches). If you recently installed a low-level app (antivirus, VPN, disk/backup tools), uninstall it to test.

Fix 3: Check Event Viewer for the real culprit

The page advises checking the System Log for errors in the same time window as the blue screen.

1. Press Start, type Event Viewer, open it.
2. Go to Windows Logs → System.
3. Find the critical/error entries around the crash time — they often name the failing driver or device.

Fix 4: Repair system files, then test RAM

Open Terminal (Admin) (right-click Start) and run:

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

If it still crashes, run the Windows Memory Diagnostic: press Start, type mdsched.exe, press Enter, and choose Restart now and check for problems. Bad RAM can corrupt the structures 0x139 is catching.

FAQ

Should I run Driver Verifier? It can pinpoint a misbehaving driver, but it’s an advanced tool that can itself cause boot loops if misused. Try Fixes 1-3 first; only reach for Verifier (or a dump analysis) if you can’t identify the driver otherwise.

It only crashes during a specific app or game. That points at the driver for the hardware that app stresses — usually the GPU. Update or roll back that driver first.

Sources: Microsoft Learn — Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE