The KERNEL_SECURITY_CHECK_FAILURE bug check (0x00000139) means Windows detected corruption of a critical kernel data structure. This often points to faulty or incompatible drivers, system services, or sometimes hardware.
For a home Windows 11 gaming system, use these steps to narrow down and fix the issue:
- Check the stop code details
- When the black/blue screen appears, note any additional stop code text or module name shown at the bottom (for example, a driver name like
nvlddmkm.sys). - This can indicate which driver or component is failing.
- Look for patterns in Event Viewer
- Open Event Viewer → Windows Logs → System.
- Look for Critical or Error events at the exact time of the restart.
- If a specific driver or service is repeatedly mentioned, update or temporarily remove it.
- Update or roll back recently changed drivers The 0x139 error is commonly caused by driver bugs, especially around LIST_ENTRY corruption and kernel synchronization objects.
- Update GPU drivers (NVIDIA/AMD/Intel) from the vendor’s official tool or site.
- Update chipset, storage, and network drivers from the laptop manufacturer.
- If the crashes started after a specific driver update, roll that driver back from Device Manager.
- Remove or update recently installed software
- If any new software, overclocking tools, RGB/overlay utilities, or anti-cheat components were installed around the time the crashes began, uninstall or update them.
- Games with kernel-level anti-cheat can trigger BSODs if their drivers misbehave.
- Use Device Manager to find faulty devices
- Open Device Manager and look for any device with a yellow exclamation mark.
- Open its Properties → Events/General tab and check for errors.
- Update or disable the problematic device and test if the BSODs stop.
- Scan for malware and file corruption
- Run a full scan with Windows Security.
- Run
sfc /scannowin an elevated Command Prompt to repair system files.
- Analyze crash dumps (advanced) If comfortable with debugging tools:
- Configure Windows to create a memory dump.
- Use WinDbg and the
!analyzeextension to inspect the 0x139 crashes and see which driver or list structure is being corrupted. The parameter 1 value helps narrow the cause (for example,3indicates LIST_ENTRY corruption).
- General BSOD troubleshooting
- If the issue started after a Windows update, check for any newer cumulative updates that might contain fixes.
- If no software/driver cause can be found and the problem persists, test hardware (RAM, storage) and consider a repair install or reset of Windows while keeping personal files.
If the system continues to restart only when gaming, focus on GPU drivers, game-related anti-cheat drivers, and any overclocking or performance-tuning tools.
References: