Consistent BSOD - KERNEL SECURITY CHECK FAILURE - (when loading escape from tarkov/other games)

Question

Never used to happen before. Started happening a couple months ago, same time around installing a new DAC and mic.

Here is the minidump - https://1drv.ms/u/c/232d48033c4c8b71/IQCd8mYgbIZSTpBYfezGGDAsAcS-xN1mtvl8tmCL3lPX7OY?e=IuWgL7

Could a support staff please take a look at this and see what may be the issue?

Answer 1

Hi,

I am afraid the link isn't working and giving me an unknown render failure.

Could you try using another cloud service?

I’m eager to hear back and work together to find a solution.

Answer 2

The minidump indicates a KERNEL_SECURITY_CHECK_FAILURE (bug check 0x139), which means the Windows kernel detected corruption of a critical data structure. In many real-world cases like this, the underlying cause is a faulty or misbehaving third‑party driver (often related to recently added hardware, overclocking/“tuning” tools, or security/monitoring software), not the game itself.

Based on similar analyzed cases in the context, the most effective next steps are:

1. Check what changed recently

• Because the issue started around the time a new DAC and microphone were installed, focus on any audio‑related drivers or vendor utilities that came with them.
• If there is a vendor control panel/“enhancement” app for the DAC or mic, temporarily uninstall it and test the games again.

2. Use the bug check 0x139 information

• Bug check 0x139 means the kernel detected corruption of a critical structure. Parameter 1 further refines the cause (for example, 3 = corrupted LIST_ENTRY, often due to a driver double‑removing or mismanaging a list entry).
• With WinDbg and the dump file, use !analyze -v and then follow the guidance in the KERNEL_SECURITY_CHECK_FAILURE article to see if a specific driver or pattern appears across multiple dumps.

3. General driver and hardware troubleshooting Follow the generic guidance for bug check 0x139:

• If any hardware was recently added (the DAC/mic), temporarily remove or disconnect it and test. If BSODs stop, reinstall with the latest drivers from the manufacturer.
• If any new device drivers or system services were installed or updated around when the crashes began, roll them back or update them to the latest versions.
• Open Event Viewer → Windows Logs → System and look for critical or error events that occur at the same time as the BSODs to identify a specific device or driver.
• Open Device Manager and check for devices with a yellow exclamation mark. For any such device, open its properties → Events tab and review for driver faults; then update or reinstall that driver.
• Run a full malware/virus scan, including a check of the Master Boot Record, as disk or system corruption from malware can also trigger kernel bug checks.

4. If the dump only shows “memory corruption” In some similar cases, minidumps only show generic memory corruption with no clear driver name. When that happens, the usual next step is to:

• Enable Driver Verifier (targeting non‑Microsoft drivers) to force faulty drivers to fail in a more visible way and produce more informative dumps.
• If Driver Verifier causes boot loops, use System Restore or Safe Mode and then reset Verifier (verifier /reset).
• Once more specific driver names appear in new dumps, update, disable, or uninstall those drivers.

5. Consider vendor utilities and “defender” services

• In similar KERNEL_SECURITY_CHECK_FAILURE cases, vendor utilities such as overclocking/tuning tools (for example, OEM “gaming” suites) or crash‑defender services have been the root cause. Disabling or uninstalling such tools has resolved BSODs.
• If any OEM audio, gaming, or “defender” services were installed with the DAC, mic, motherboard, or GPU, temporarily disable them via services.msc and test.

6. If the issue persists

• Collect several minidumps and analyze them together in WinDbg to see if the same code path or driver is always present at the time of the crash.
• Use the guidance in the KERNEL_SECURITY_CHECK_FAILURE documentation to walk any corrupted LIST_ENTRY structures and identify the driver or component that owns them.

---

References:

• Bug Check 0x139: KERNEL_SECURITY_CHECK_FAILURE
• Kernel_Security_Error BSOD. Driver Verifier causing bootloop. - Microsoft Q&A
• Please check my minidumps, BSOD and shutdowns - Microsoft Q&A
• Constant BSOD - Microsoft Q&A
• BSODs caused by ntkrnlmp.exe - Microsoft Q&A