- Software and digital services
- Operating system
KERNEL_SECURITY_CHECK_FAILURE
KERNEL_SECURITY_CHECK_FAILURE (0x139) on Windows: the kernel detected a corrupted data structure
Risk level
Medium
Proceed carefully and stop if the check is unclear.
Urgency
High
Quick answer
The Windows kernel detected that a critical data structure was corrupted and stopped. Check which driver, service or hardware you added before the first crash and look for flagged devices in Device Manager.
Safety first
Stop and check this first
- The word security in this code refers to internal kernel checks: on its own it does not mean you have a virus or that a part is faulty.
Safe checks you can perform
- Recent changes
- Device Manager
- System log and antivirus scan
Leave these tasks to a qualified professional
- Do not attempt this professional task: Analyse several dumps
- Do not attempt this professional task: Driver Verifier with special pool
What a technician must be able to justify
Technician visit
These are the steps they must carry out and show you. Tick them as they work: if steps are skipped, do not accept a part swap.
These are not instructions for opening or handling the equipment yourself. They are the checks that should support a technical conclusion.
Analyse several dumps
What they doIT support examines several dumps in WinDbg with !analyze, reads parameter 1 and compares what code was running at each stop.
They must show youparameter 1 and the module common to the dumps.
In writingwhich driver was identified and what was changed.
Driver Verifier with special pool
What they doIf the dump is not enough, they enable Driver Verifier with special pool on the suspect drivers.
They must show youthe settings and the dump obtained.
In writingthe result and that verification was turned off afterwards.
Before accepting a part or repair
Nothing has been shown yet. Do not accept a part swap based on the code alone.
Follow these steps
Note: Follow the documented order. An error code identifies the affected system, but it does not prove by itself which part has failed.
Recent changes
- Who:
- you.
- How:
- note the code, the time and which drivers, services or hardware you added in the previous days.
- Result that matters:
- whether a change lines up with the first crash.
- If one does:
- remove or update it and see if crashes stop.
- If nothing changed:
- go on to devices and logs.
- Evidence to keep:
- photo of the screen and list of changes.
Evidence: Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE · Troubleshooting Windows unexpected restarts and stop code errors
Device Manager
- Who:
- you.
- How:
- look for devices with an exclamation mark, review the events in their driver properties and choose Update driver.
- Result that matters:
- whether a device has problems.
- If one does:
- it is the main candidate.
- If not:
- check the System log.
- Evidence to keep:
- screenshot of the device and its driver version.
Evidence: Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE · Troubleshooting Windows unexpected restarts and stop code errors
System log and antivirus scan
- Who:
- you.
- How:
- in Event Viewer review Windows Logs, System, at the time of the crash; then run a full scan with your antivirus.
- Result that matters:
- whether a service or driver logged errors, or the antivirus finds something.
- If there are errors or detections:
- note them for IT support.
- If all is clean:
- the dump will be the main evidence.
- Evidence to keep:
- screenshots of the event and the scan result.
Evidence: Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE
Still not solved
If the error persists, stop here. See what the technician must do and show you.
Where this code applies
A code is meaningful only inside the right product and version context.
Primary scope
- System
- Software and digital services
- Brand
- Microsoft Windows
- Product type
- Operating system
Known code variants
- 0x00000139
- 0x139
- KERNEL SECURITY CHECK FAILURE
- STOP 0x00000139
- stop code KERNEL_SECURITY_CHECK_FAILURE
What it means
Microsoft defines 0x00000139 as the kernel detecting corruption of a critical data structure. Parameter 1 gives the type, such as a stack buffer overrun or a corrupted linked list. Common causes it lists are drivers corrupting synchronization objects or timers, or mismanaging their own lists. The corruption is not always detected when it happens, so the code alone does not point to the culprit.
Warnings and stop conditions
- Mediumeditorial warning
The word security in this code refers to internal kernel checks: on its own it does not mean you have a virus or that a part is faulty.
Evidence: Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE
Symptoms and causes
Probable causes · in order
- Driver corrupting kernel structuresCommon
This is the group of causes Microsoft describes. Confirmed by several dumps showing the same module or by Driver Verifier.
Evidence: Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE
- Recently added driver, service or hardwarePossible
Microsoft says to remove or update it and work out what changed; if crashes stop, that was the source.
Evidence: Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE
- Disk corruption from malwareLess common
Microsoft includes an antivirus scan that checks the Master Boot Record among the general steps.
Evidence: Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE
Virtual technician
Does KERNEL_SECURITY_CHECK_FAILURE still appear after these checks?
Answer a few questions to narrow down the likely cause and the safest next action. Guidance only - it never replaces a professional.
Sources and technical references
- 1
Bug Check 0x139 KERNEL_SECURITY_CHECK_FAILURE
Microsoft · 2026 · official_doc
- 2
Stop code error or bug check troubleshooting (IT professionals)
Microsoft · 2026 · official_doc
- 3
Troubleshooting Windows unexpected restarts and stop code errors
Microsoft · 2026 · official_doc
Was this entry useful?