How to Fix Marathon Crashing on PC — Every Error Code and Solution

Marathon just dropped and your PC is already fighting for its life. If you’re dealing with Marathon crashing on PC, blue screens of death, frozen mouse cursors, or a wall of cryptic error codes, you’re not alone — this launch is rough. Here’s every known Marathon crashing PC fix so you can actually play the game.

TL;DR — Quick Fixes

• BSOD / Kernel Crash: Unplug Focusrite/Scarlett audio interfaces or disable their MIDI driver in Device Manager
• Mouse cursor frozen: Disable Discord Clips, Steam Overlay, and close OBS
• Game won’t launch: Run as Administrator, verify game files on Steam
• Error W:8:80090305: Restart Marathon completely to refresh your auth token
• Error broccoli: Update GPU drivers (clean install with DDU)
• Error marmot: Verify game file integrity through Steam
• Black screen on launch: Press Alt+Enter to force windowed mode
• Xbox “Checking for Updates” loop: Change DNS to 1.1.1.1 or 8.8.8.8

If the quick fixes didn’t solve it, keep reading for the full breakdown of every Marathon crash scenario and how to fix it.

1. BattlEye Causing Blue Screen of Death (BSOD)

This is the worst one. BattlEye, Marathon’s anti-cheat system, operates at the kernel level. For some players — especially those with Focusrite Scarlett USB audio interfaces — it causes an instant blue screen or full system crash.

The fix:

• Unplug your Focusrite/Scarlett interface before launching Marathon. Yes, seriously. This is a known kernel-level conflict between BattlEye and the Focusrite USB audio driver.
• If you need your audio interface connected, go to Device Manager → Sound, video and game controllers, find your Focusrite device, expand it, and disable the MIDI driver specifically. Restart your PC afterward.
• This also applies to some other USB audio devices. If you’re getting BSODs, unplug any external audio hardware and test.

Bungie is aware of this issue. Expect a patch, but for now this workaround is your only option.

2. Mouse Cursor Freezing or Locking Up

Your mouse randomly stops responding mid-match? This is a hardware cursor conflict. Multiple apps fight Marathon for cursor control, and the game loses.

The fix:

• Discord Clips is the #1 cause. Go to Discord Settings → Clips → Disable completely. The Clipping feature grabs hardware cursor access and conflicts directly with Marathon.
• Disable Steam Overlay: Steam → Settings → In Game → uncheck “Enable the Steam Overlay while in-game.”
• Close OBS, Streamlabs, or any screen capture software before launching.
• If you use Discord overlay, disable that too — or switch to Discord in your browser.
• Lower your mouse polling rate to below 1000Hz. Some high-end gaming mice at 2000Hz+ cause input conflicts with BattlEye.

3. Marathon Won’t Launch at All

You click Play on Steam, BattlEye loads briefly, and then… nothing. The game silently crashes before even showing a window.

The fix:

• Run as Administrator. Right-click Marathon in Steam → Manage → Browse Local Files. Find the Marathon .exe, right-click → Properties → Compatibility → check “Run this program as an administrator.”
• Verify game files: Steam → Library → Marathon → Properties → Installed Files → Verify Integrity of Game Files. This catches any corrupted downloads.
• Legacy CPU issue: If your CPU is pre-2016 (no AVX2 support), Marathon will not launch. You’ll see exception code 0xc000001d in Event Viewer. Unfortunately, there’s no fix — the game requires modern instruction sets.
• Try launching in windowed mode by adding -windowed to your Steam launch options.

4. Every Marathon Error Code Explained

Here’s what each error code means and how to fix it:

Error Code W:8:80090305

What it means: Server connection timeout. Your authentication token expired.
Fix: Fully close Marathon (check Task Manager) and relaunch. This generates a fresh auth token. If it persists, restart your router and try again during off-peak hours.

Error Code Broccoli

What it means: GPU not detected or driver crash mid-game.
Fix: Update your GPU drivers immediately. For the cleanest result, use DDU (Display Driver Uninstaller) to completely remove old drivers, then install fresh ones from Nvidia or AMD’s website. Don’t use GeForce Experience auto-update — download manually.

Error Code Marmot

What it means: Corrupted game files.
Fix: Steam → Library → Marathon → Properties → Installed Files → Verify Integrity of Game Files. If this doesn’t work, uninstall and reinstall completely.

Error Code Ginger / Paprika

What it means: General server-side errors. Bungie’s backend is struggling under launch load.
Fix: Wait and retry. These are not your fault. Check @BungieHelp on X for server status updates.

Error Code Nightingale

What it means: Account-level issue. Bungie is investigating these on a case-by-case basis.
Fix: File an appeal directly at Bungie.net. There’s no local fix for this one.

5. AMD GPU Texture Issues (RX 500 Series)

If you’re on an AMD RX 560, 570, 580, or 590, you’re probably seeing broken, invisible, or flickering textures. This is a known driver compatibility issue with the RX 500 series and Marathon’s rendering pipeline.

The fix:

• Do a clean install of AMD Adrenalin drivers. Use AMD’s cleanup utility first, then install the latest version.
• Bungie has confirmed they’re working on a dedicated fix for RX 500 series GPUs. This is a temporary workaround.
• If textures are still broken after a driver reinstall, lower Texture Quality to Medium in Marathon’s settings.

6. Xbox “Checking for Updates” Timeout

Marathon on Xbox Series X|S sometimes gets stuck on “Checking for Updates” and never loads.

The fix:

• Change your DNS to Cloudflare (1.1.1.1) or Google (8.8.8.8). Go to Settings → Network → Advanced Settings → DNS Settings → Manual.
• Power cycle your console: Hold the power button for 10 seconds, unplug for 30 seconds, plug back in.
• Clear alternate MAC address: Settings → Network → Advanced Settings → Alternate MAC Address → Clear.

7. Black Screen on Launch

Marathon loads but you’re staring at a black screen with audio playing in the background.

The fix:

• Press Alt+Enter to switch to windowed mode. This forces the game to render to a window and usually fixes the black screen.
• If that doesn’t work, check that your monitor is set as the primary display in Windows Settings → Display.
• Disable any G-Sync or FreeSync temporarily to test.

Still Not Working?

If none of these fixes solved your Marathon crashing issue:

• Make sure Windows is fully updated (Windows Update → Check for updates)
• Disable any antivirus real-time scanning temporarily
• Close every background app — especially RGB software like iCUE, Razer Synapse, or NZXT CAM
• Check that you have at least 16 GB of RAM — Marathon is hungry
• Monitor your GPU temperatures with HWMonitor. Overheating causes silent crashes

Marathon’s launch is messy, but Bungie will be patching aggressively over the next few weeks. Bookmark this page — we’ll update it as new fixes drop.

You might also like:

• How to Fix High Ping in Any Game
• How to Reduce Input Lag for PC Gaming
• Best Free PC Games in 2026
• How to Fix Marathon Crashing and Not Launching on PC (2026)