Why does Marathon crash after BattlEye check?

BattlEye can conflict with USB audio drivers and some BIOS configurations. Unplugging Focusrite devices and enabling Secure Boot resolves for many users.

Does Marathon work on Linux or Steam Deck?

No. BattlEye blocks Proton. Marathon does not run on Linux or Steam Deck.

← All Error Codes

Marathon BattlEye Launch Crash

Q: How do I fix Marathon BattlEye launch crash?

Unplug USB audio interfaces like Focusrite Scarlett. Enable Secure Boot in BIOS. Run uninstall_battleye.exe in the game folder, verify files in Steam, reboot.

The game shows "running" in Steam but closes immediately after BattlEye install or check. Some users see KERNEL_SECURITY_CHECK_FAILURE BSOD.

⚠ Workarounds Available
← Check Live Server Status

Quick Fix

Unplug USB audio interfaces (e.g. Focusrite Scarlett). Enable Secure Boot in BIOS. Run uninstall_battleye.exe in the game folder, then verify files in Steam.

Step-by-Step Fixes

[PC] Unplug USB audio interfaces (e.g. Focusrite Scarlett 4i4) — BattlEye conflict confirmed fix for multiple users
[PC] Enable Secure Boot in BIOS — hidden requirement on older systems
[PC] Run uninstall_battleye.exe in C:\Program Files (x86)\Steam\steamapps\common\Marathon\battleye, then verify game files in Steam and reboot
[PC] Device Manager: disable MIDI and audio devices temporarily
[PC] Clean GPU drivers using DDU (Display Driver Uninstaller), then run sfc /scannow

What Causes BattlEye?

BattlEye is kernel-level anti-cheat that can conflict with certain hardware drivers (especially USB audio interfaces) and BIOS settings. Older systems may require Secure Boot. Bungie is investigating; when reporting, include your Bungie.net name, PC/GPU specs, and overlay info.

Related Errors

Still Not Fixed?

Submit a ticket or check official status:

→ Marathon Help — Submit a ticket
→ @BungieHelp — Official status updates
→ Live server status — MarathonStatus.com