Bungie Answered
PC Crash / Force Restart when BattleEye initializes (Focusrite interface connected)
When launching Marathon on Steam, the game fails during anti-cheat initialization.
PC force restart
KERNEL_SECURITY_CHECK_FAILURE
I’ve read that it could possibly be caused by my Focusrite audio interface. I was unable to test this workaround during the sever slam test launch.
1
Комментарии
Hi there,
Thanks for reporting this. Our team is aware of players experiencing crashes due to Focusrite audio interfaces and is currently investigating this issue. Our apologies for the inconvenience this is causing.
Please feel free to report any new issues post-launch in the Help Forums!
Bumping this thread because I have the same issue: Marathon / BattleEye causes a full PC crash and reboot. This is whenever my Focusrite Scarlet 18i Audio Interface is active while trying to launch the game – or turned on while the game is running. As others have noted, this weirdly wasn't an issue during the Sever Slam!
Would love to hear if there has been any progress. Audio is such an important part of the Marathon experience. Couldn't this be easily fixed by just whitelisting Focusrite Drivers on BattleEye?
Hope this gets fixed. Happy to provide more information if needed.
Bumping this as well. I literally can't start the game with my audio equipment plugged in. I'm glad I have a headset otherwise I'd not be able to hear any audio at all.
Same issue here i have a focusrite 16i16 4th gen can't play any battle eye games needs fixing asap.
Войдите в службу, чтобы оставить комментарий.