Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsKERNEL_SECURITY_CHECK_FAILURE is Windows 11 stop code 0x00000139. It means the kernel detected corruption in a critical data structure, not that one particular part is automatically defective. A bad driver is a common suspect, but recently added hardware, damaged Windows components, or other software can trigger the same crash. Work through the fixes in order: remove recent hardware, boot Safe Mode if necessary, check drivers, install Windows updates, free storage, repair the component store with DISM followed by SFC, and use System Restore when the failures began after a change.
If the blue screen returns repeatedly, preserve the minidumps and compare the bug-check parameter, event log, and implicated modules before replacing hardware. The first parameter is especially useful: a value of 3 identifies a corrupted LIST_ENTRY, but it still does not by itself identify which driver or device performed the damaging write.
As an Amazon Associate I earn from qualifying purchases.
What KERNEL_SECURITY_CHECK_FAILURE (0x139) actually means
Microsoft defines bug check 0x00000139 as a condition in which the Windows kernel detects corruption of a critical data structure. Kernel code manages memory, threads, drivers, timers, linked lists, and security-sensitive bookkeeping. When an integrity check finds that one of those structures no longer has a valid layout or relationship, Windows stops rather than continue with potentially unsafe state.
The stop code is therefore a finding, not a component-level diagnosis. The first bug-check parameter identifies the class of integrity failure. Parameter 1 value 3 means a corrupted LIST_ENTRY. Other values represent checks involving items such as a stack buffer, virtual-function table, invalid parameter, bounds, or control transfer. Record the parameter shown on the blue screen or in the dump; it gives useful direction, but the rest of the dump is needed to identify a responsible module.
#1 Best Overall
Corruption can be detected after the original bad write. For example, a driver may damage a linked list and the kernel may not notice until a later operation walks that list. The driver named near the crash is consequently a lead, not conclusive proof. This timing explains why uninstalling an apparently unrelated recent change can solve the problem.
First response: capture clues before changing the system
When Windows is still usable, write down the exact stop-code text, the hexadecimal code, the parameter 1 value, and the time of each crash. Note what happened immediately beforehand: a new device, driver package, update, game, security product, virtual-machine component, or firmware change. Also record whether a particular workload, such as waking from sleep, gaming, transferring files, or connecting a peripheral, reliably triggers the failure.
- Save important work and copy essential files to another drive or cloud location before repeated troubleshooting.
- Photograph the blue screen if it disappears too quickly to read.
- Do not repeatedly force power-off while Windows is writing files unless the machine is completely unresponsive; abrupt interruptions can create additional file-system problems.
- Keep the computer connected to reliable power during updates and component repairs.
These observations let you distinguish a change-related crash from a workload-sensitive failure. If the crash began directly after one change, reverse that change before making several unrelated modifications.
Recommended Free Tools
Use this repair sequence in order
1. Undo recently added hardware
Shut down Windows completely, disconnect the power, and remove hardware installed immediately before the crashes began. This includes expansion cards, USB devices, docks, storage devices, memory modules, and replacement adapters. Reconnect only the hardware required to start Windows, then test the same workload that previously failed.
If removing the device stops the crashes, install the latest driver or firmware supplied for that exact model and Windows 11 edition. If no compatible update exists, leave the device disconnected or replace it. Do not keep testing an unstable device in a way that risks data loss. A device that is essential to the computer may require the manufacturer’s support process rather than a generic driver.
2. Start Windows 11 in Safe Mode
Safe Mode loads a limited set of drivers and services, making it useful when normal startup crashes. From the sign-in screen, hold Shift while selecting Power > Restart. If Windows will not reach that screen, interrupt startup two or three times by turning the computer off during the spinning-logo phase; Windows should enter the Recovery Environment on the next boot.
In the Recovery Environment select Troubleshoot > Advanced options > Startup Settings > Restart. Press 4 for Safe Mode or 5 for Safe Mode with Networking. If you can reach the desktop normally, the equivalent path is Settings > System > Recovery > Advanced startup > Restart now, followed by the same Startup Settings choices.
Use Safe Mode to remove a recently installed driver or application, inspect Device Manager, and run the repair commands below. If the machine is stable in Safe Mode but crashes during normal startup, a driver or startup service is more likely than a basic Windows kernel file. Safe Mode is a diagnostic state; it does not repair the underlying cause by itself.
3. Inspect Device Manager and roll back the suspect driver
Right-click Start and open Device Manager. Expand categories that match the timing of the failure, such as Display adapters, Network adapters, Storage controllers, Bluetooth, sound, and Universal Serial Bus controllers. A yellow warning icon indicates a detected device or driver problem, but a device without an icon can still be involved in memory corruption.
- Open the device’s Properties and read the status message on the General tab.
- On the Driver tab, note the provider, date, and version.
- If the failure began after an update, choose Roll Back Driver when Windows offers it.
- Otherwise choose Update Driver and let Windows search, or install a current Windows 11 package from the device manufacturer.
- If updating does not help, choose Uninstall device, select the option to remove the driver package only when you are certain it is the problematic package, and restart. Windows may reinstall a basic driver.
- For a nonessential device, use Disable device temporarily and test. Re-enable it after the test if it is not implicated.
Never disable storage or boot-critical hardware casually. If disabling a device makes the system unbootable, return to Safe Mode or the Recovery Environment and undo the change.
4. Install current Windows 11 updates
Open Settings > Windows Update, select Check for updates, install all applicable updates, and restart when requested. Run the check again after the restart until Windows reports that no further updates are available. Updates can contain fixes for Windows components and inbox drivers, so this step is worthwhile even when Device Manager reports that every driver is current.
If an update itself preceded the crashes, use Settings > Windows Update > Update history to identify it. Remove a recently installed quality update only as a recovery measure, then check for a newer replacement. A rollback should be tied to the timeline and testing result, not used as a permanent substitute for a compatible driver.
5. Free enough storage for Windows to operate
Windows and applications need working space for paging, temporary files, update staging, and crash dumps. Microsoft suggests keeping roughly 10% to 15% of a drive free. Check Settings > System > Storage and remove unnecessary temporary files, old installers, or unused applications. Empty the Recycle Bin only after confirming that it contains nothing you need.
Do not delete arbitrary folders under C:Windows or C:Program Files. If the system drive is nearly full, move personal files to another disk, uninstall large applications, or expand the storage device. Restart after freeing space and observe whether updates and normal workloads complete without another stop code.
6. Repair the Windows component store, then system files
Open Terminal (Admin) or Command Prompt (Admin) by right-clicking Start and choosing the administrator option. Approve the User Account Control prompt. Run the commands in this order:
DISM.exe /Online /Cleanup-image /RestorehealthWait for DISM to finish. It may appear to pause at a percentage while checking or repairing the component store. Do not close the window or power off the computer. When DISM completes, run:
sfc /scannowMicrosoft’s sequence places DISM before SFC because SFC relies on the component store as a source for replacement files. SFC reports whether it found and repaired integrity violations, found violations it could not repair, or found no violations. Restart after both commands and test again. If either command reports an error, record the exact text rather than repeatedly running it without addressing the reported condition.
7. Use System Restore or another recovery option after a recent change
If the crashes began after a driver, application, update, or other system change, open Settings > System > Recovery and review the available recovery choices. System Restore can return system files, drivers, and settings to an earlier restore point without deliberately deleting personal documents. Choose a restore point dated before the first failures and review the affected-program list when Windows presents it.
When Windows cannot boot normally, enter the Recovery Environment and choose Troubleshoot > Advanced options > System Restore. If no suitable restore point exists, use the recovery option that matches your situation, such as uninstalling the latest update or starting from a backup. A reset or reinstall is a last resort after personal data is backed up and hardware and driver causes have been considered.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →If the computer crashes before you can sign in
Start with the Recovery Environment procedure above rather than repeatedly attempting a normal boot. Select Safe Mode and perform the Device Manager, update, storage, and component-repair checks there. If Safe Mode also crashes, disconnect every nonessential peripheral, remove recently added internal hardware, and try the built-in recovery options.
When the machine can remain powered on only briefly, prioritize data protection and evidence collection. Photograph the stop screen, note the parameter, and copy any accessible files. A bootable Windows recovery drive can provide access to troubleshooting tools when the installed system is unusable. If encryption is enabled, have the recovery key available before attempting offline recovery.
A crash that occurs before the Windows logo, during firmware initialization, or immediately after adding a physical component points more strongly toward hardware or firmware than an ordinary startup driver. In that situation, follow the device or motherboard manufacturer’s diagnostic process and avoid random parts replacement.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Memory Integrity warnings: do not disable protection casually
Windows may display a message that a driver cannot load because Memory integrity blocked it. Memory integrity is a virtualization-based security feature; on a secured-core PC, turning it off removes part of the machine’s protected state. First obtain a compatible driver through Windows Update or from the hardware or software manufacturer, then restart and test.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Only consider disabling Memory integrity as a deliberate, temporary compatibility decision when you understand the security trade-off and have no supported driver. The setting is under Windows Security > Device security > Core isolation details. Record the original state, make the smallest possible change, and restore protection as soon as a compatible driver is available. Turning the feature off is not a routine treatment for every 0x139 crash.
Best Value
- Windows 11's new user experience, from reworked Start menu and Settings app to voice input
- The brand-new Windows 365 option for running Windows 11 as a Cloud PC, accessible from anywhere
- Major security and privacy enhancements that leverage the latest PC hardware
- Expert insight and options for installation, configuration, deployment, and management – from the individual to the enterprise
- Getting more productivity out of Windows 11's built-in apps and advanced Microsoft Edge browser
How to tell whether the cause is a driver, hardware, or software
Use timing, repeatability, dump evidence, and isolation together. No single clue proves responsibility because corruption may be detected later than the write that caused it.
| Candidate | Clues that raise its probability | Useful test |
|---|---|---|
| Device driver | Crashes began after a driver update, occur during one device’s workload, or disappear in Safe Mode. | Roll back, update, disable, or uninstall the affected device and repeat the workload. |
| New hardware or firmware | Failure started immediately after installation or stops when the device is removed. | Shut down, remove the new component, and test with the previous configuration. |
| Windows component corruption | Updates fail, system files report integrity violations, or several unrelated functions behave abnormally. | Run DISM first and SFC second, then restart and retest. |
| Other software | Crashes follow a particular application or service and do not occur in Safe Mode. | Uninstall or roll back that software, then test without its startup service. |
| Unresolved hardware fault | Failures continue in Safe Mode after recent changes are removed, or recur under varied workloads. | Preserve dumps and use the manufacturer’s hardware diagnostics or qualified support. |
This comparison is a prioritization method, not a substitute for evidence. Buying replacement memory, a disk, or a motherboard before isolating the trigger can waste money and leave the real driver problem untouched.
Advanced diagnosis with dumps and event logs
For recurring crashes, make sure Windows is configured to save small memory dumps and keep the resulting files instead of deleting them during cleanup. Compare more than one dump. Look for the same parameter 1 value, repeated modules, and a consistent call-stack pattern. Also inspect Event Viewer > Windows Logs > System around the crash time for device, driver, storage, or update errors.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallMicrosoft’s debugging tools, including WinDbg, can open a dump and run the !analyze command. Advanced users or support technicians can then inspect the bug-check parameters, stack, loaded modules, and any driver-verifier evidence. A module named in a report is an investigative lead; confirm it by checking its version, update history, and whether disabling the related device changes the crash pattern.
Keep an incident log containing the dump filename, date, workload, parameter 1, recent changes, and each troubleshooting action. This prevents circular testing and gives a technician enough context to reproduce the failure. If dumps are not being created, check that the system drive has free space and that the paging-file configuration has not been disabled.
Verify the repair and prevent a recurrence
After each meaningful change, restart normally and perform the workload that previously triggered the crash. Do not make five changes at once: you would not know which action helped or which one introduced a new problem. Once the computer is stable, install only compatible drivers, keep Windows updated, and leave adequate free space for updates and dumps.
- Reconnect removed hardware one device at a time, testing between additions.
- Keep the successful driver version and note why it was selected.
- Re-enable Memory integrity after replacing an incompatible driver.
- Retain at least the latest few minidumps until the issue is conclusively resolved.
- Create a restore point before major driver or application changes when System Protection is available.
If 0x139 returns despite these steps, stop treating each crash as an isolated event. Preserve the dumps, compare the parameter and modules, and escalate with the incident log. Persistent kernel corruption requires evidence-based diagnosis; a sequence of random reinstalls or hardware purchases can obscure the original cause.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
