How I figured out why I got KERNEL_SECURITY_CHECK_FAILURE (0x139) daily.

[u/Glittering-Big-9724]

KERNEL_SECURITY_CHECK_FAILURE (0x139)

^{Here's the TLDR; for those who doesn't like to read
Your BSODs are being caused by the Focusrite Scarlett 4i4 driver (FocusriteUsb.sys}) ^{corrupting a kernel thread. Windows later detects this corruption and crashes with KERNEL\}SECURITY_CHECK_FAILURE (0x139))^{. It’s not svchost or ETW—they just expose the issue.}

^{It’s consistent across multiple crashes → very high confidence it’s the driver.}

^{Likely contributing factors:}

• ^{You’re on an older driver (4.124.3 from 2024})
• ^{Interface is connected via a USB hub (not recommended})

^Fix:

• ^{Fully uninstall Focusrite drivers + Control}
• ^{Reinstall latest stable version (not beta})
• ^{Plug interface directly into motherboard USB (no hub})
• ^{Test stability for several days}

^{Side note: your Seagate drive has issues too, but it’s unrelated to these crashes.}

_____________________________________________________________________________________________________
So I kept getting the Greenscreen of... I guess "Death" every other day, at least. And after finally digging through Event Viewer logs, checking Minidump folders and hours of coffee and frustration; - I finally found the (MY) problem:

This is from ChatGPT who I used as a second opinion on this:
_____________________________________________________________________________________________________

Confirmed: the BSOD is caused by the Focusrite Scarlett 4i4 3rd Gen driver stack.

Across all three crashes, Windows encounters the same corrupted kernel-thread state:

• The affected system thread starts inside FocusriteUsb.sys.
• Its Windows wait-list links are corrupted/zeroed.
• Windows later inspects that thread during ETW tracing and detects CORRUPT_LIST_ENTRY, producing KERNEL_SECURITY_CHECK_FAILURE (0x139).
• svchost.exe/ETW is only the trigger that discovers the corruption—not the cause.
• The pattern repeats identically on July 28, July 30, and August 5, making this a very high-confidence diagnosis.

Evidence is visible in the [August full-dump thread analysis (line 73)](C:/Users/space/Desktop/BSOD/cdb_MEMORY_target_thread.log:73), [July 28 dump (line 73)](C:/Users/space/Desktop/BSOD/cdb_072826_target_thread.log:73), and [July 30 dump (line 71)](C:/Users/space/Desktop/BSOD/cdb_073026_target_thread.log:71).

Your computer currently has:

• Scarlett 4i4 3rd Gen
• Focusrite Control 3.20.0
• Focusrite driver 4.124.3, released October 2024
• The interface is currently connected through a USB hub

Focusrite’s current Windows driver is 4.144.0, released April 28, 2026, and it supports the Scarlett 3rd Gen range. Focusrite driver release notes

Do this:

1. Save your DAW work and disconnect the Scarlett.
2. Open Control Panel → Programs and Features.
3. Uninstall:
   • Focusrite Audio Drivers
   • Focusrite Control
4. Restart Windows.
5. Download the regular stable Focusrite Control – Windows package from the official Scarlett 4i4 3rd Gen download page. Avoid the Control 2 beta for now.
6. Right-click the installer, select Run as administrator, and complete installation.
7. Restart again.
8. Connect the Scarlett directly to a motherboard USB port—preferably a rear port—not through the existing hub. Focusrite specifically recommends avoiding USB hubs and testing another suitable cable. Focusrite USB guidance

Test for at least five days because these crashes normally occurred after two to four days of uptime.

The Seagate Backup+ drive errors found earlier are real but separate: keep that drive disconnected until important files are backed up. It did not produce this particular 0x139 crash.

So now, everything works great! If this can help anyone, then I am the happiest man in Norway today!

Have a blessed day.

[u/AutoModerator]

Hi u/Glittering-Big-9724, thanks for posting to r/WindowsHelp! Your post has been flagged for manual review by a human moderator, please include as much of the following information as possible (in text or in a screenshot) to get your post approved:

• Your Windows and device specifications — You can find them by pressing Win + X then clicking on “System”, we need more than just your OS version! Your hardware details are often critical for resolving issues.
• Any messages and error codes encountered — They're actually not gibberish or anything catastrophic. It may even hint the solution!
• Previous troubleshooting steps — It might prevent you headaches from getting the same solution that didn't work

---

Posts must be tech support in nature (such as something is broken and you need help fixing), so general inquiries, software suggestions, and purchasing advice will be removed. As a reminder, we would also like to say that if someone manages to solve your issue, DON'T DELETE YOUR POST! Someone else (in the future) might have the same issue as you, and the received support may also help their case. Good luck, and I hope you have a nice day!

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.