KERNEL_SECURITY_CHECK_FAILURE (0x139) GOXLR
I’m encountering a repeatable BSOD when launching or playing Marathon, specifically KERNEL_SECURITY_CHECK_FAILURE (0x139). After troubleshooting and checking system logs, this appears to be linked to a driver conflict involving BattleEye and audio interfaces.
In my case, the issue seems tied to a TC-Helicon GoXLR Mini, but I’ve also found multiple reports from other users experiencing the same crash with different audio hardware, particularly Focusrite Scarlett interfaces. The common factor across these cases is that disabling or disconnecting the audio device prevents the crash.
This suggests a broader compatibility issue between BattleEye and certain audio drivers, rather than a fault with any one device.
This is a significant concern because:
-
Audio interfaces like GoXLR and Focusrite are widely used by streamers and content creators.
-
These setups are common in the exact audience likely to be playing and promoting Marathon.
-
Currently, affected users are forced to disable or unplug core parts of their audio setup just to launch the game.
It would be worth investigating this in collaboration with BattleEye, as it appears to be a kernel-level driver interaction rather than a typical application crash.
Comments
Hello there,
Thank you very much for reaching out to us. I'm sorry to hear that you are having issues getting into the game while using your GoXLR. We've taken note of this detailed report and will continue investigating.
Please sign in to leave a comment.