KERNEL_SECURITY_CHECK_FAILURE (0x139): Windows Found Its Own Data Corrupted
In plain English
If your PC shows 0x139, Windows is saying it found corruption inside protected kernel data. That points to something deeper than one app freezing.
First safe step
Note what changed right before the first crash: the last driver update, Windows update, SSD or hard drive issue, USB device, antivirus change, or BIOS setting change. That timing is the lead for everything on this page.
Software first, in this order. RAM is the last suspect, tested on its own page.
If your PC shows 0x139, Windows is saying it found corruption inside protected kernel data. That points to something deeper than one app freezing. If you want the bigger map of blue screen errors, start with the Blue and Black Screen Stop Codes pillar.
On this page, the focus is the two common non-RAM paths, drivers and storage. A bad, wrong, or half-removed driver can damage data as Windows moves it through the kernel. Disk or file system problems can do the same, especially if the crash started after an update, a new device, or a drive problem.
We'll start with the most recent change, then work through safe driver rollback and disk checks. If the pattern looks more like a driver blue screen than failing memory, you may also want the driver crash page for 0x0A. If you already suspect memory, go to the separate RAM test page for 0x1A for that path.
What KERNEL_SECURITY_CHECK_FAILURE (0x139) means
KERNEL_SECURITY_CHECK_FAILURE with stop code 0x139 means Windows caught damage in data the kernel depends on to run safely. In plain English, the system found that one of its own protected structures no longer looked valid, so it stopped on purpose instead of continuing and risking worse corruption.
This usually points to a low-level problem such as a bad driver, a storage problem, or file system damage. It is not the same as a normal app crash. If your blue screen started after a device driver change, a new accessory, sleep or wake problems, or a recent update, that timing matters. If the crashes happen around sleep or resume, compare the pattern with the sleep and wake crash page for 0x9F. If another stop code mentions a driver reaching memory it should not, see the driver crash page for 0x0A.
This page focuses on the driver and disk side of 0x139. If you already suspect memory, random crashes under load, or several different stop codes, use the separate RAM test page for 0x1A for that path instead of repeating those checks here.
Your first safe step is simple, note what changed right before the first crash. Think about the last driver update, Windows update, SSD or hard drive issue, USB device, antivirus change, or BIOS setting change. If the blue screen began right after patching, read what to do first after a blue screen appears right after an update before you start removing things at random.
1 Check what changed right before the crash Free
Start with the last thing that changed. A new graphics, Wi-Fi, chipset, storage, or antivirus driver matters more than a random guess, because 0x139 often starts right after one bad low-level change. The same goes for a Windows update, a new external SSD, a USB hub, a dock, or anything you plugged in shortly before the first blue screen.
Write down exactly what you see on the crash screen before you restart. Keep the stop code KERNEL_SECURITY_CHECK_FAILURE and 0x139, and note any named file such as a .sys driver. If the crash began right after Patch Tuesday or another update, see what to do first after a blue screen appears right after an update. If it happens mostly during sleep, wake, or shutdown, compare it with the sleep and wake crash page for 0x9F.
A short list on paper helps. Mark the date of the first crash, the last driver or app you installed, any update that was still pending, and any device you connected that day. If Windows Update looked frozen and you forced a restart, check how long to wait when Windows Update seems stuck, because an interrupted update can leave driver files half-changed.
If the PC crashes before you can sign in normally, don't keep retrying the same boot over and over. Go straight to how to get into Safe Mode when Windows will not boot, then come back here and continue with the driver checks first. If later signs point more toward memory than drivers or storage, use the separate RAM test page for 0x1A instead of guessing.
2 Fix the driver side first Free
Start with the newest driver, not every driver on the PC. Open Device Manager, find the hardware you changed or updated, then check display, storage, network, and chipset devices first. Those four groups are common triggers for KERNEL_SECURITY_CHECK_FAILURE 0x139, especially if the crash began during startup, gaming, file copying, or waking from sleep.
In Device Manager, right-click the suspect device and open Properties. On the driver tab, try Roll Back Driver first if it is available. If rollback is grayed out, use Disable device as a short test, or choose Uninstall device, restart, and let Windows reload a basic driver. If the blue screen names a .sys file, match that file to the related device before changing anything else.
If the problem started right after Patch Tuesday or another system update, do not use a driver-updater app. Those tools often install the wrong package or a generic one, which can make kernel corruption worse. Instead, check your PC maker or motherboard maker for a newer Windows 10 or Windows 11 driver, especially for graphics, storage controller, Wi-Fi, Ethernet, and chipset parts. If the crash appeared right after an update and you are still sorting out the timing, see what to do first after a blue screen appears right after an update.
Power-related timing can narrow this down. If 0x139 happens mostly when the PC sleeps, wakes, docks, or undocks, the pattern overlaps with the sleep and wake crash page for 0x9F. If another stop code starts appearing after you remove one driver, compare it with the driver crash page for 0x0A. If driver cleanup does not stop the crashes, the next branch is storage on this page, and later, if needed, the separate RAM test page for 0x1A.
3 Check the drive and file system for corruption Free
If the driver steps did not stop 0x139, check the drive next. A failing SSD or HDD can damage Windows files or file-system records, and that can make protected kernel data look corrupted. This angle is more likely if the PC has become very slow, boots take much longer than usual, or Windows keeps dropping into repair screens.
If Windows still starts, back up your personal files first before you do anything stressful to the drive. Focus on documents, photos, and anything you cannot replace. If the crashes started right after patching, it can also help to read what to do first after a blue screen appears right after an update, because update timing can overlap with drive trouble.
Then open Command Prompt as administrator and run SFC first. Type SFC /scannow and let it finish. After that, run a file-system check with chkdsk C: /f. If Windows says the drive is in use and asks to schedule the scan at restart, type Y, restart, and let the check complete.
Pay attention to what happens next. If the scan finds errors once and the PC becomes stable, the problem may have been file-system damage. If errors keep coming back, boots stay slow, files go missing, or you hear clicking or grinding from a hard drive, suspect the drive itself. If crashes mostly happen during sleep or wake instead, that points back toward the sleep and wake crash page for 0x9F. If Windows will not stay up long enough to run these checks, use how to get into Safe Mode when Windows will not boot and run the checks there.
✓ Crashes gone? You can stop here.
4 If Windows still crashes, use Safe Mode and the recovery path Free
If Windows keeps crashing before you can finish the checks above, use Safe Mode as a repair doorway. It is there to help you remove the change that broke normal startup, not to prove the problem is gone. If you need the boot steps, follow how to get into Safe Mode when Windows will not boot first, then come back here.
Once you are in, start with System Restore if you have a restore point from before the first 0x139 crash. If the problem started right after Patch Tuesday or another update, try uninstalling the latest quality update from recovery options, or see what to do first after a blue screen appears right after an update if you are not sure whether the update is still installing or actually broken. If the crash lines up with sleep, wake, dock, or undock, compare your symptoms with the sleep and wake crash page for 0x9F.
If restore or update removal does not help, remove the newest suspect driver from Device Manager while you are still in Safe Mode. That is often enough to get one stable normal boot so you can install the correct driver afterward. If your blue screen named a driver file or looked more like a direct driver overreach than storage corruption, check the driver crash page for 0x0A for the matching pattern.
Stop chasing software fixes if crashes keep returning after rollback, restore, and file-system repair, especially if the PC also has slow boots, repair loops, missing files, or drive noises. At that point, a failing SSD or HDD becomes more likely, and repeated blue screens with no clear driver can also point toward memory trouble. For the memory side, go to the separate RAM test page for 0x1A.
5 When to suspect RAM, and where to go next
Bad RAM can still be part of a 0x139 crash, but this page stops short of the full memory test. For that, go to the separate MEMORY_MANAGEMENT page and follow its RAM checks there.
If the driver and disk fixes here did not stop the crashes, move on to the 0x1A page and then compare it with the related stop-code pages. That keeps the RAM path in one place instead of repeating it here.
By this point, you have ruled out the most common driver and storage causes of KERNEL_SECURITY_CHECK_FAILURE. What remains is the narrower set of memory-related causes, which belong on the other page.
Frequently asked questions
What should I do if 0x139 happened only once?
Write down the date and what had changed, back up files you cannot replace, and use the PC normally. If it happens again, start with the newest change from that note instead of guessing.
Will reinstalling Windows fix KERNEL_SECURITY_CHECK_FAILURE?
It can remove a bad driver or damaged Windows files, but it will not fix failing RAM or a failing drive. Try the driver, disk, and RAM paths first, so you do not reinstall and then meet the same crash.
The short version
If the crashes have stopped, use the PC normally for a few days before you call it fixed. Keep your note of what changed and what you rolled back or repaired. If 0x139 returns with the same timing, that timing is still useful information.
If it keeps crashing after the driver and disk work here, stop swapping drivers at random. Move on to the separate RAM test page for 0x1A, and keep that note if you later take the PC to a repair shop. Save the test result with your note of the first crash.
Different number on screen?
Type it exactly as it appears and get the plain-English answer.
Pop-up telling you to call?
That is a scam. Microsoft never asks you to phone a number.