The KERNEL_SECURITY_CHECK_FAILURE error is a Windows Blue Screen of Death (BSOD) that normally appears when Windows detects corruption or an inconsistency in a critical kernel data structure.

The associated Windows bug check is:

Bug Check: 0x00000139
Stop Code: KERNEL_SECURITY_CHECK_FAILURE

Microsoft describes bug check 0x139 as indicating that the Windows kernel detected corruption of a critical data structure. The corruption can originate from faulty or incompatible drivers, memory corruption, driver programming errors, unstable hardware, or other low-level system problems.

A typical system may display:

Your device ran into a problem and needs to restart.

Stop code: KERNEL_SECURITY_CHECK_FAILURE

Windows deliberately stops the system when this happens because continuing to execute after critical kernel structures have been corrupted could cause further instability or data loss.

What Does KERNEL_SECURITY_CHECK_FAILURE Mean?

The Windows kernel is the core component of the operating system. It manages critical functions including:

• Memory management
• Hardware communication
• Device drivers
• CPU scheduling
• Processes and threads
• Interrupt handling
• Security mechanisms
• Kernel-mode services

Kernel-mode drivers operate with very high privileges. A defective driver can therefore overwrite or incorrectly manipulate memory used by Windows itself.

When Windows detects that an important kernel structure has become corrupted or an internal security check has failed, Windows may intentionally halt with:

KERNEL_SECURITY_CHECK_FAILURE

The stop is therefore often the result of corruption being detected, rather than necessarily the exact moment when the original corruption occurred.

This distinction is important when troubleshooting.

Technical Meaning of Bug Check 0x139

Microsoft assigns the KERNEL_SECURITY_CHECK_FAILURE bug check the hexadecimal value:

0x00000139

The bug check contains four parameters.

Parameter 1 identifies the type of corruption detected.

Parameter 2 contains the address of the trap frame associated with the exception.

Parameter 3 contains the address of the exception record.

Parameter 4 is reserved.

For technicians analyzing memory dumps, Parameter 1 can be especially valuable because it identifies the class of security or structural violation detected.

Microsoft documents numerous possibilities, including stack-based buffer overruns, corrupted LIST_ENTRY structures, invalid parameters, illegal array indexing, invalid object reference counts, unsafe writes and other corruption conditions.

Common Causes of KERNEL_SECURITY_CHECK_FAILURE

There is no single cause for every 0x139 crash. The following are among the most common areas to investigate.

1. Faulty or Incompatible Device Drivers

Device drivers are one of the first things to investigate.

Possible offenders include:

• Graphics drivers
• Wi-Fi drivers
• Ethernet drivers
• Bluetooth drivers
• Storage/NVMe drivers
• SATA/AHCI/RAID drivers
• USB drivers
• Audio drivers
• Chipset drivers
• Printer drivers
• VPN/filter drivers
• Security software drivers

A recently installed or updated driver should receive particular attention.

Microsoft specifically recommends checking whether new device drivers or system services were added shortly before the bug check started occurring.

2. Corrupted or Defective RAM

Memory corruption can produce symptoms that resemble driver corruption.

Possible RAM-related causes include:

• Physically defective RAM
• Poorly seated RAM modules
• Mixed or incompatible modules
• Incorrect memory timings
• Aggressive XMP/EXPO settings
• RAM overclocking
• Motherboard compatibility problems

If crashes occur randomly and different drivers appear responsible each time, memory instability becomes particularly important to investigate.

3. Corrupted Windows System Files

Damaged Windows components can contribute to system instability.

Corruption may occur following:

• Interrupted Windows Updates
• Unexpected shutdowns
• Disk errors
• Failed upgrades
• Malware
• Storage corruption
• Improper system modifications

Windows includes DISM and System File Checker tools that should be used before considering a Windows reinstall.

4. Windows Update or Driver Update Problems

If KERNEL_SECURITY_CHECK_FAILURE started immediately after an update, investigate what changed.

This might include:

• Windows cumulative update
• Feature update
• GPU driver
• Chipset package
• Storage driver
• Network driver
• BIOS/firmware update

Do not automatically assume that Windows Update itself is defective. An update can expose an existing incompatibility in an older third-party driver.

5. Graphics Driver Problems

GPU drivers operate deeply within Windows and are common suspects in crashes occurring during:

• Gaming
• Video playback
• Rendering
• GPU acceleration
• Sleep/wake
• External monitor connection
• High GPU workloads

Systems using NVIDIA, AMD or Intel graphics should use drivers appropriate for the exact hardware and Windows version.

6. Storage Problems

SSD, NVMe or hard-drive problems can indirectly cause BSOD errors if Windows reads corrupted system or driver data.

Check for:

• SSD health warnings
• NVMe firmware problems
• File-system corruption
• Bad sectors
• Loose SATA cables
• Storage-controller driver problems

7. Overclocking or Unstable BIOS Settings

CPU, GPU or memory overclocking can create memory corruption even when Windows appears stable during ordinary use.

Temporarily disable:

• CPU overclocking
• GPU overclocking
• RAM overclocking
• XMP/EXPO
• Undervolting
• Custom memory timings

Load BIOS/UEFI optimized defaults and test again.

8. Third-Party Security Software

Antivirus, endpoint security, encryption and monitoring products sometimes install kernel-level drivers.

If crashes started immediately after installing or upgrading such software, temporarily uninstall the product for testing.

Simply disabling an antivirus interface may not unload its kernel drivers, so a proper uninstall can be necessary for a meaningful test.

9. Newly Installed Hardware

Microsoft recommends removing recently added hardware when troubleshooting recurring stop-code errors.

Examples include:

• RAM
• Graphics cards
• USB devices
• Wi-Fi adapters
• PCIe cards
• Storage devices
• Docking stations

Disconnect unnecessary peripherals and retest the system.

Solution 1: Restart and Determine Whether the Error Repeats

A single isolated BSOD does not necessarily indicate a permanent hardware failure.

Restart the computer and observe it.

If the same error occurs repeatedly, begin systematic troubleshooting.

Record:

• Stop code
• Time of crash
• Application running
• Hardware connected
• Recent updates
• Recently installed software
• Driver changes

Patterns can dramatically reduce troubleshooting time.

Solution 2: Disconnect Recently Added Hardware

Shut down the computer and temporarily disconnect unnecessary devices.

Keep only essential hardware such as:

• Keyboard
• Mouse
• Primary monitor

If new RAM, GPU, storage or PCIe hardware was installed shortly before the crashes began, test without it where practical.

Microsoft includes removal of recently added hardware among its primary BSOD troubleshooting steps.

Solution 3: Boot Windows in Safe Mode

If Windows repeatedly crashes during normal startup, boot into Safe Mode.

You can normally reach Windows Recovery Environment through:

Settings → System → Recovery → Advanced startup → Restart now

Then select:

Troubleshoot → Advanced options → Startup Settings → Restart

Select:

Safe Mode

or:

Safe Mode with Networking

Safe Mode loads a reduced set of drivers and services.

If the computer remains stable in Safe Mode but crashes during a normal boot, investigate third-party drivers, startup applications and services.

Solution 4: Check Device Manager

Press:

Windows + X

Select:

Device Manager

Look for devices displaying:

• Yellow warning icon
• Unknown Device
• Driver error
• Device initialization problem

Pay particular attention to:

• Display adapters
• Network adapters
• Storage controllers
• System devices
• Sound devices
• USB controllers

Microsoft recommends checking Device Manager for devices showing warning indicators during BSOD troubleshooting.

Solution 5: Update Device Drivers

Obtain appropriate drivers from:

• PC/laptop manufacturer
• Motherboard manufacturer
• GPU manufacturer
• Windows Update

For branded laptops and desktops, OEM-provided chipset, storage, power-management and firmware packages may be preferable where the manufacturer specifically validates them for that system.

Avoid random third-party "driver updater" websites.

Important drivers to check include:

1. Chipset
2. GPU
3. Storage/NVMe
4. Network
5. Wi-Fi/Bluetooth
6. Audio
7. USB/Thunderbolt
8. OEM system drivers

Solution 6: Roll Back a Recently Updated Driver

If the problem started immediately after a driver update:

Open:

Device Manager → Device → Properties → Driver

Select:

Roll Back Driver

if available.

Alternatively, uninstall the problematic driver and install a known stable version from the hardware manufacturer.

Solution 7: Install Windows Updates

Open:

Settings → Windows Update

Select:

Check for updates

Install applicable security, quality and driver updates and restart the computer.

Microsoft includes installing current Windows Updates among its standard BSOD troubleshooting recommendations.

Solution 8: Repair Windows with DISM

Open Terminal (Admin) or Command Prompt (Admin).

Run:

DISM /Online /Cleanup-Image /ScanHealth

Then:

DISM /Online /Cleanup-Image /RestoreHealth

Allow the operation to complete.

Restart Windows if required.

Solution 9: Run System File Checker

After DISM, open an elevated Command Prompt and execute:

sfc /scannow

System File Checker scans protected Windows files and attempts to repair corrupted versions.

After completion, restart Windows.

If SFC reports repaired files, monitor the system to determine whether the BSOD returns.

Solution 10: Check the File System

Open Command Prompt as Administrator and run:

chkdsk C: /scan

For deeper repair when file-system problems are detected, CHKDSK may require an offline scan during restart.

Do not immediately assume that every KERNEL_SECURITY_CHECK_FAILURE means the drive is defective. Check SSD/HDD health separately if storage problems are suspected.

Solution 11: Test the RAM

Press:

Windows + R

Enter:

mdsched.exe

Select:

Restart now and check for problems

Windows will restart and perform a memory diagnostic.

Microsoft recommends Windows Memory Diagnostic as one of its advanced troubleshooting steps for recurring stop errors.

For intermittent problems, technicians may also perform longer memory testing with dedicated memory-diagnostic utilities.

If multiple RAM modules are installed and errors continue, advanced troubleshooting can include testing modules individually.

Solution 12: Disable XMP/EXPO and Overclocking

Enter BIOS/UEFI setup and temporarily restore default settings.

Disable:

• XMP
• EXPO
• CPU overclock
• GPU overclock
• Memory overclock
• Custom voltage settings

Run the computer at standard specifications.

If crashes disappear, instability in the previous configuration is likely.

Solution 13: Check BIOS/UEFI and Firmware

Check your computer or motherboard manufacturer's support page for:

• BIOS/UEFI updates
• SSD/NVMe firmware
• Thunderbolt firmware
• Docking-station firmware
• Chipset updates

Do not interrupt a BIOS update.

For laptops, ensure AC power is connected and follow the manufacturer's firmware-update instructions exactly.

Solution 14: Check Event Viewer

Press:

Windows + R

Enter:

eventvwr.msc

Navigate to:

Windows Logs → System

Look around the exact time of the BSOD.

Useful entries can include errors associated with:

• Disk
• Storage
• Display drivers
• Device drivers
• Hardware
• Services
• WHEA
• Unexpected shutdowns

Microsoft recommends examining the System log for errors occurring around the time of the bug check.

Do not assume Kernel-Power Event ID 41 identifies the root cause. It commonly records that Windows restarted without a clean shutdown; the actual failure may have happened earlier.

Solution 15: Locate Windows Minidump Files

Windows may create crash dumps in:

C:\Windows\Minidump

You may see files similar to:

082926-12345-01.dmp

Larger dumps may also be stored at:

C:\Windows\MEMORY.DMP

Dump analysis is one of the most effective ways to investigate recurring BSOD problems.

Solution 16: Analyze the Dump with WinDbg

Advanced users and IT technicians can use Microsoft WinDbg.

After opening the dump, one of the primary commands is:

!analyze -v

Review information such as:

• Bugcheck code
• Bugcheck parameters
• Failure bucket
• Stack trace
• Loaded modules
• Suspected driver/module

For KERNEL_SECURITY_CHECK_FAILURE specifically, the first bug-check parameter can provide valuable information about the type of corruption Windows detected.

Microsoft recommends examining multiple dumps when possible because recurring patterns can help identify the responsible component.

Important Diagnostic Warning

If WinDbg mentions:

ntoskrnl.exe

do not automatically conclude that the Windows kernel itself is defective.

The kernel may simply be where corruption was detected.

A third-party driver or unstable hardware may have damaged memory earlier.

Solution 17: Use Driver Verifier – Advanced Users Only

Windows includes Driver Verifier for detecting problematic kernel-mode drivers.

Run:

verifier

However, Driver Verifier intentionally stresses drivers and can cause additional BSODs when it detects driver violations.

Therefore:

Driver Verifier should normally be used by experienced technicians who know how to recover the computer if Windows enters a crash loop.

To disable Driver Verifier from an elevated command prompt:

verifier /reset

Then restart Windows.

Microsoft notes that Driver Verifier, including special-pool techniques, can sometimes help identify the driver responsible for certain forms of corruption associated with bug check 0x139.

Solution 18: Perform a Clean Boot

A clean boot can help determine whether third-party software is involved.

Press:

Windows + R

Enter:

msconfig

Open the Services tab.

Select:

Hide all Microsoft services

Then disable nonessential third-party services for diagnostic purposes.

Also review:

Task Manager → Startup apps

Disable unnecessary startup programs temporarily.

Restart and test.

If the BSOD disappears, re-enable components systematically until the problematic software is identified.

Solution 19: Uninstall Recently Installed Software

If the BSOD began after installing:

• Antivirus
• VPN client
• Hardware monitoring software
• RGB software
• System optimization utility
• Virtualization software
• Backup software
• Disk encryption software
• Driver utility

temporarily uninstall it and test again.

Programs containing kernel-level drivers deserve particular attention.

Solution 20: Use System Restore

If the system previously worked correctly, System Restore may reverse problematic system changes.

Press:

Windows + R

Enter:

rstrui.exe

Choose a restore point created before the BSOD started.

System Restore can be particularly useful when the problem began following a driver, application or system configuration change.

Solution 21: Check Free Disk Space

Ensure the Windows system drive has sufficient free space.

Microsoft recommends maintaining approximately 10–15% free disk space as a general troubleshooting guideline because Windows and applications require free space for temporary files, paging and other operations.

Extremely low disk space can create additional problems that complicate BSOD troubleshooting.

Solution 22: Scan for Malware

Run a complete scan using Windows Security or another trusted security product.

Malware capable of manipulating system files or kernel-level components can potentially cause instability.

However, KERNEL_SECURITY_CHECK_FAILURE should not automatically be interpreted as evidence of malware. Driver and memory problems are generally more useful starting points.

Solution 23: Check SSD/HDD Health

If crashes are accompanied by:

• File corruption
• Slow startup
• Disk errors
• Missing files
• Application corruption
• I/O errors
• SMART warnings

investigate storage health.

Back up important data before performing extensive testing on a potentially failing drive.

Solution 24: Check Physical RAM Installation

If the desktop or laptop allows user-serviceable RAM:

1. Shut down Windows.
2. Disconnect AC power.
3. Follow the manufacturer's safety instructions.
4. Reseat the memory modules.
5. Test again.

For multiple modules, technicians may test one module at a time where supported.

If one particular module or slot consistently produces failures, hardware service may be required.

Solution 25: Check System Temperatures and Stability

Although temperature is not unique to bug check 0x139, unstable hardware can contribute to memory corruption.

Check:

• CPU temperature
• GPU temperature
• Fan operation
• Dust buildup
• Power supply stability
• Laptop cooling system

If crashes occur only under gaming or heavy workloads, hardware stability deserves additional investigation.

Recommended Troubleshooting Order

For most users, use this sequence:

Step 1: Record the stop code and when the crash occurs.

Step 2: Remove recently installed hardware.

Step 3: Undo recently installed drivers or software.

Step 4: Install appropriate Windows and device-driver updates.

Step 5: Run DISM.

DISM /Online /Cleanup-Image /RestoreHealth

Step 6: Run SFC.

sfc /scannow

Step 7: Test RAM.

mdsched.exe

Step 8: Check Event Viewer.

Step 9: Check disk/storage health.

Step 10: Disable overclocking/XMP/EXPO temporarily.

Step 11: Analyze Windows minidumps.

Step 12: Use Driver Verifier only when advanced driver diagnostics are necessary.

This order avoids immediately reinstalling Windows when a driver or hardware problem may be identifiable.

KERNEL_SECURITY_CHECK_FAILURE After a Windows Update

If the BSOD began immediately after Windows Update:

1. Install any subsequent available updates.
2. Check for updated OEM drivers.
3. Update chipset and storage drivers.
4. Check the GPU driver.
5. Review Update History.
6. Roll back a recently changed driver if appropriate.
7. Use System Restore if necessary.
8. Analyze the dump before removing updates indiscriminately.

KERNEL_SECURITY_CHECK_FAILURE While Gaming

If the computer crashes primarily during games, investigate:

• GPU driver
• GPU overclock
• CPU overclock
• RAM/XMP stability
• GPU temperature
• CPU temperature
• Power supply
• Game anti-cheat/kernel drivers
• Overlay software
• RGB/monitoring utilities

Return CPU, GPU and RAM to stock settings before performing further diagnostics.

KERNEL_SECURITY_CHECK_FAILURE During Startup

If Windows crashes before reaching the desktop:

1. Enter Windows Recovery Environment.
2. Start Safe Mode.
3. Remove recently installed drivers/software.
4. Use System Restore.
5. Run Startup Repair where appropriate.
6. Test memory.
7. Check storage.
8. Analyze available crash dumps.

KERNEL_SECURITY_CHECK_FAILURE After Installing RAM

If the error started after a RAM upgrade:

1. Confirm motherboard/laptop compatibility.
2. Reseat the RAM.
3. Disable XMP/EXPO.
4. Load BIOS defaults.
5. Run memory diagnostics.
6. Test individual modules.
7. Test the original RAM again.

If the original memory works normally but the new memory repeatedly causes crashes, compatibility or defective RAM becomes a strong suspect.

When Should You Reinstall Windows?

A clean Windows installation should generally not be the first troubleshooting step.

Consider reinstalling Windows only after reasonable checks of:

• Drivers
• RAM
• Storage
• Windows system files
• Recent software
• Firmware
• Crash dumps

A reinstall cannot repair physically defective RAM, an unstable CPU, failing storage or another hardware fault.

If the BSOD returns immediately on a clean Windows installation, hardware or a subsequently installed driver should be investigated carefully.

Frequently Asked Questions (FAQ)

1. What is KERNEL_SECURITY_CHECK_FAILURE?

It is a Windows stop error indicating that the kernel detected corruption or violation involving a critical data structure.

Its bug check code is:

0x00000139

2. Is KERNEL_SECURITY_CHECK_FAILURE a virus?

Not necessarily.

The error is more commonly investigated as a driver, memory, hardware or system-corruption problem. Malware scanning is still reasonable as part of broader troubleshooting.

3. Can faulty RAM cause KERNEL_SECURITY_CHECK_FAILURE?

Yes. Unstable or defective memory can corrupt data used by the Windows kernel and drivers.

Run Windows Memory Diagnostic and consider deeper RAM testing if crashes continue.

4. Can a driver cause this BSOD?

Yes.

Kernel-mode driver problems are an important cause to investigate, particularly if the BSOD began after installing or updating hardware or drivers.

5. Why does KERNEL_SECURITY_CHECK_FAILURE happen after a driver update?

The new driver might contain a defect, be incompatible with another component or expose an existing hardware/driver problem.

Try updating to a newer release or rolling back to the previous stable driver.

6. Why does the BSOD mention ntoskrnl.exe?

ntoskrnl.exe is a core Windows kernel component.

Its presence in a crash report does not automatically mean that ntoskrnl.exe is defective. The kernel may simply have detected corruption caused earlier by another driver or unstable hardware.

7. How do I repair corrupted Windows files?

Open Terminal or Command Prompt as Administrator and run:

DISM /Online /Cleanup-Image /RestoreHealth

followed by:

sfc /scannow

Restart Windows afterward.

8. Where are BSOD dump files stored?

Small memory dumps are normally found in:

C:\Windows\Minidump

A larger system dump may exist at:

C:\Windows\MEMORY.DMP

9. How can I identify which driver caused the crash?

Analyze the dump using WinDbg and start with:

!analyze -v

Examine the stack, modules and failure information rather than assuming that the first Windows component shown is responsible.

10. Should I use Driver Verifier?

Driver Verifier can help identify defective drivers but is intended primarily for advanced troubleshooting.

It can deliberately trigger BSODs when driver violations are detected.

To reset it:

verifier /reset

11. Can XMP cause KERNEL_SECURITY_CHECK_FAILURE?

Potentially, yes.

If XMP/EXPO makes the memory subsystem unstable, memory corruption can result. Disable XMP/EXPO temporarily and retest.

12. Can an SSD cause this error?

Storage problems can contribute indirectly through corrupted files or driver/data errors. Check the file system, drive health, firmware and storage drivers when symptoms point toward storage.

13. Why does the computer crash only while gaming?

Gaming places heavy load on the GPU, CPU, RAM and power system. Check graphics drivers, temperatures, overclocking, RAM stability and power delivery.

14. Does reinstalling Windows always fix KERNEL_SECURITY_CHECK_FAILURE?

No.

A reinstall may solve software corruption, but it will not repair defective RAM, unstable hardware or failing storage.

15. What should I do if the BSOD happens repeatedly?

Collect multiple minidumps and compare them.

Microsoft specifically recommends examining multiple dump files for recurring characteristics when diagnosing bug check 0x139.

Conclusion

KERNEL_SECURITY_CHECK_FAILURE (0x00000139) means Windows detected corruption or an invalid condition involving a critical kernel data structure.

The most productive troubleshooting areas are usually:

• Device drivers
• RAM stability
• Recent hardware/software changes
• Windows system-file corruption
• Storage health
• BIOS/firmware
• Overclocking or XMP/EXPO
• Third-party kernel-level software

For a recurring problem, do not rely only on generic fixes. Crash-dump analysis is the best way to move from guessing to evidence-based diagnosis.

Microsoft's general BSOD guidance also recommends checking recently added hardware, Safe Mode, Device Manager, Windows Update, Event Viewer, memory diagnostics and recovery options.

For advanced technical reference, see Microsoft's documentation for Bug Check 0x139: KERNEL_SECURITY_CHECK_FAILURE and its Windows blue-screen troubleshooting guide.

 

#KERNEL_SECURITY_CHECK_FAILURE #KernelSecurityCheckFailure #BSOD #BlueScreen #WindowsBSOD #Windows11 #Windows10 #WindowsError #WindowsTroubleshooting #StopCode #Error0x139 #BugCheck139 #WindowsKernel #KernelError #DriverError #DriverTroubleshooting #WindowsDrivers #DeviceDrivers #MemoryCorruption #RAMError #RAMTest #WindowsMemoryDiagnostic #SystemFileCorruption #SFC #DISM #CHKDSK #WindowsRepair #WindowsRecovery #SafeMode #DeviceManager #WindowsUpdate #DriverUpdate #DriverRollback #GraphicsDriver #NVIDIADriver #AMDDriver #IntelDriver #SSD #HardDrive #WinDbg #Minidump #CrashDump #DriverVerifier #EventViewer #SystemRestore #CleanBoot #BIOS #UEFI #WindowsSupport #ComputerRepair