I've been getting frequent KERNEL_SECURITY_CHECK_FAILURE (0x139) blue screens over the past few weeks. They usually occur while I'm working in FL Studio, and I'm wondering whether my Focusrite audio interface or previously installed audio drivers could be involved. I have already removed Waves SoundGrid, Sonarworks Reference, VB-CABLE, and Voicemeeter, although some of them may still appear in older minidump files.
I also experienced a complete system freeze while playing a game. The mouse still moved, but Windows stopped responding and I had to hold the power button to shut the computer down. The games where I've noticed problems include Wuthering Waves, Palworld, Cyberpunk 2077, and Diablo 4.
My system has a Ryzen 9 5900X, Corsair Vengeance Pro SL CL16 memory, an RTX 4080 Super, an ASUS B550-F Gaming motherboard, a 1200W Thermaltake power supply, and an NZXT Kraken Elite 360 RGB cooler. I'm not very experienced with troubleshooting, so I'd appreciate help understanding what the crash dumps might indicate and what I should test first. The RAM was replaced recently, and reinstalling Windows would be difficult because this computer is used for work.
3 Answers
The first thing I’d test is the memory configuration. With two DDR4 modules, the Ryzen 9 5900X is officially rated for up to DDR4-3200. If the system is running the memory at DDR4-3600 through DOCP, that is technically an overclock and can cause intermittent crashes even when the RAM itself is new. Disable DOCP or set the memory to Auto so it runs at the motherboard’s default safe speed, then see whether the BSODs stop. If the system becomes stable, you can try a lower memory speed later.
The minidumps are useful because they can identify the crash context, but a blamed driver is not always the real cause. Since the freezes also happen during demanding games, I’d test system stability outside FL Studio: return BIOS settings to defaults, monitor CPU and GPU temperatures, check power and GPU connections, and run a few controlled memory and graphics tests. Avoid immediately reinstalling Windows; hardware and driver troubleshooting can usually be done first.
A 0x139 crash can be caused by corrupted memory, unstable RAM settings, or a driver corrupting kernel data. Replacing the RAM does not completely rule out memory instability, especially if DOCP is enabled. Run a thorough memory test and also check whether the crashes continue with the audio interface disconnected and its related software fully removed. Updating the motherboard BIOS, AMD chipset drivers, NVIDIA driver, and Focusrite driver would also be worthwhile.
I didn’t realize DDR4-3600 could count as an overclock on this CPU. My BIOS offers Auto, Manual, and DOCP, so I’ll start with Auto and test the computer before changing anything else.