Marathon Error Codes & Fixes

Individual Error Code Pages

Dedicated fix guides for each error. Use these for targeted troubleshooting and SEO-friendly deep links.

Connection & Network Errors

W:8:80090305 Connection Timeout (Most Common)

Server connection timeout — your handshake request exceeded the server's time limit. Extremely common during peak Server Slam traffic.

• Restart the Marathon application to generate a new authentication token. Post-restart waits are usually brief.
• If it repeats: flush DNS (ipconfig /flushdns on PC), switch to wired Ethernet, retry.

PAPRIKA Connection / Server Error

General server-side connection failure, often during high-traffic windows. One of the most searched errors during Server Slam.

• Restart the game and retry — usually self-resolving.
• Check live server status to confirm servers are up.
• If persistent: check your network, disable VPN, switch to wired Ethernet.

Weasel "Could Not Connect" — Recurring Kicks

Red screen error, kicks you every 45–60 seconds. Primarily affected PC/Steam users on wired connections. Bungie deployed a server-side patch (~Feb 27, 2026).

• Update the game — restart your client to download Bungie's patch.
• Restart your router and PC — temporary fix until patch is applied; worked 3+ hours for many community reports.
• Flush DNS: ipconfig /flushdns in admin Command Prompt.
• Set DNS to 8.8.8.8 / 8.8.4.4 (Google) or 1.1.1.1 (Cloudflare).
• Disable VPN and firewall temporarily; use wired Ethernet.
• Primarily seen in EU players (ISP-related per Bungie). If it persists, report at Marathon Help.

Buzzard Lost Connection

Indicates a dropped connection to Marathon servers, often caused by network instability or routing issues between you and Bungie's infrastructure.

• Switch to wired Ethernet — Wi-Fi interference is the most common cause.
• Disable VPN if active.
• Restart the game and your router.
• Flush DNS: ipconfig /flushdns on PC; clear alternate MAC on Xbox.
• If repeated: check for ISP packet loss using tracert to Bungie's servers.

Ginger / Currant Packet Loss / Network Interruption

Host-to-client interruption from packet loss, Wi‑Fi instability, or ISP routing issues. If you disconnect mid-run, the game includes reconnection logic and inventory rollback.

• Switch to wired Ethernet — the most effective fix for both codes.
• Disable VPN if active.
• Restart your router; check for firmware updates.
• Disable QoS or traffic shaping on your router if enabled.

Marmot Server-Side Failure

Server-side connection failure, typically seen during high-load periods or when Bungie's backend is under stress.

• Restart the game and wait 2–5 minutes before retrying.
• Check live server status for active incidents.
• Follow @BungieHelp for real-time updates during outages.

Centipede Connectivity / Firewall Block

Connection error often related to network configuration, firewall rules, or antivirus blocking Marathon's required ports.

• Add Marathon as a firewall exception in Windows Defender and any antivirus.
• Disable VPN if active.
• Restart your router; switch to wired Ethernet.
• Check that required ports for Bungie services are not blocked by your ISP or router.

Stingray Connection Error

General connectivity error. Seen alongside authentication and server handshake failures.

• Restart the game.
• Flush DNS (ipconfig /flushdns) and reset Winsock (netsh winsock reset).
• Ensure no firewall or VPN is blocking Marathon.
• Wired Ethernet over Wi-Fi.

CAT Authentication Failure

Authentication error during login or session handshake. Often appears at launch or after a server restart.

• Restart the game completely — most common fix.
• If on PC: restart Steam as Administrator.
• Check Bungie.net to confirm your account is in good standing.
• If repeated: clear Steam download cache (Steam → Settings → Downloads → Clear download cache) and restart.

Nightingale CDN / Config Download Failure

Failed to download configuration files from Bungie's CDN. On Xbox often appears as a "Checking for Updates" loading bar that times out.

• Change DNS: Use Cloudflare (1.1.1.1) or Google (8.8.8.8) instead of your ISP default.
• Xbox: Power cycle (unplug 5+ min) or clear alternate MAC address in network settings.
• PC: Run ipconfig /flushdns and netsh winsock reset in admin Command Prompt, then reboot.
• Temporarily disable antivirus/firewall to test — Kaspersky is a known culprit (see Salak below).

Salak Antivirus Block

Antivirus blocking Marathon's config file fetch from Bungie's servers. Confirmed link to Kaspersky on PC.

• Add Marathon as a firewall exception in Kaspersky or your antivirus software.
• Temporarily disable real-time protection to confirm the cause, then whitelist Marathon permanently.

WEAVE Connection Drop

Connection error, often appearing alongside "could not connect" or mid-session disconnects.

• Restart the game; verify your network connection is stable.
• Retry during off-peak hours if Server Slam traffic is high.

Marathon Servers Are Not Available

This message means Marathon's game servers are temporarily unreachable — either due to scheduled maintenance, an unplanned outage, or extremely high queue traffic during Server Slam.

• Check MarathonStatus.com live status to see if there's an active outage.
• Follow @BungieHelp for official status updates.
• Wait a few minutes and retry — queue-related messages clear on their own.
• Force-close and relaunch the game (especially on PS5).

Access Denied

Seen during Server Slam when an account is not yet authorized or the access queue is full.

• Make sure you have added the free Server Slam to your library on Steam or PlayStation Store before launching.
• Wait and retry — this error typically clears within a few minutes during high-traffic periods.
• On PS5: confirm PS+ is active for online play (Server Slam download is free, but online requires PS+).
• Check server status to rule out a broader outage.

Infinite "Connecting to Marathon Servers"

Authentication queue stuck. Most common on PS5 during peak traffic.

• Wait for backend stabilization (check server status).
• PS5: Force close the app from the dashboard, then relaunch.

Matchmaking / Can't Connect to a Match

• Disable cross-platform play in network settings — narrows the matchmaking pool and often resolves lockouts.
• Check that your NAT type is Open. Port forward if needed.

Steam Download "Connection Timeout" or Button Stuck

Steam store times out when downloading, or the download/install button is unresponsive.

• Add to library first — add Marathon Server Slam to your library before attempting to download.
• Restart Steam as Administrator — right‑click Steam → Run as administrator.
• Clear download cache: Steam → Settings → Downloads → Clear download cache.
• If partially installed: right‑click game in library → Properties → Local Files → Verify integrity of game files.
• Refresh the store page and retry after a few minutes.

Mouse or Input Not Working (PC)

• Streaming? Stream your whole screen — not the Marathon game window specifically.
• Steam overlay: Settings → In Game → turn off "Enable the Steam Overlay while in-game". Or: enable overlay → press Shift+Tab in-game → exit overlay.
• Discord: Disable the overlay and "Always-on game clipping", or use the Discord web version instead of the desktop app.
• Other tools: Close any screen sharing, screen capture, or screen measurement utilities.
• Mouse stops after a few seconds? Lower your mouse polling rate below 1000 Hz in your mouse software or Windows settings.
• Still stuck? Press Alt+Enter to switch to windowed mode.
• Run Steam as Administrator.
• Last resort: Restart PC; reinstall the game if needed.

Note: PS5 mouse & keyboard support is limited during Server Slam. See PS5 section below.

BattlEye Launch Crash (PC)

Game shows "running" in Steam but closes immediately after BattlEye install or check. Some users see a KERNEL_SECURITY_CHECK_FAILURE BSOD. Bungie is investigating — provide your Bungie.net name, PC/GPU specs, and active overlays when reporting.

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

Crashes (Launch, Death, Exfil)

Crashes on launch, on death, during exfil, or with certain hardware are expected during Server Slam stress testing. Report to Bungie with your DXDiag/MSInfo.

• Freeze after signing in? Disable Discord, Steam, and GeForce Experience overlays. Update GPU drivers (clean install via DDU). Right‑click marathon.exe → Properties → Compatibility → "Disable fullscreen optimizations".
• "Graphics runtime detected a crash or loss of device"? Clean install GPU drivers (DDU in Safe Mode, install latest NVIDIA/AMD). Lower graphics settings and cap FPS.
• Stuck on first mission load? Restart the game (confirmed workaround).
• Controller causing crashes? Try keyboard/mouse only and report on Bungie forums.
• OBS causing PC restarts? Avoid OBS game capture — use display capture or stream your whole screen.
• If persistent: reinstall the game.
• Report with DXDiag/MSInfo at the Marathon Help Center.

Platform-Specific Issues

PS5

• Can't find the game? Search "Marathon Server Slam" in the PlayStation Store.
• PS+ required? Server Slam download is free — PS+ is only needed for online play. If the store incorrectly blocks you, wait and retry or check @BungieHelp.
• Mouse & keyboard on PS5: Limited support in Server Slam. Mouse input issues are a known beta limitation — full M&K support has not been confirmed for launch.
• Freeze on loading: Force close from the dashboard and relaunch.
• Overheating: Ensure ventilation and clear dust. Limit extended sessions until further engine optimization from Bungie.

Xbox Series X|S

• Can't find the game? Search "Marathon Server Slam" in the Microsoft Store.
• "Missing Files" or tutorial crash: Hard reset (unplug power supply), then delete and reinstall from the dashboard.

PC — AMD Black Screen / Missing Textures

Buildings and environments appear invisible, black, or completely wrong — widespread on AMD Polaris GPUs (RX 560/570/580/590). Bungie has acknowledged the issue and a fix is in progress.

• Do a clean install of the latest AMD Adrenalin drivers (try both Beta and Stable channels).
• Use DDU (Display Driver Uninstaller) in Safe Mode before reinstalling drivers for best results.
• Follow @BungieHelp for patch updates.

PC — Black Screen on Launch

• Disable Discord overlay and GeForce Experience overlay.
• Right-click marathon.exe → Properties → Compatibility → "Disable fullscreen optimizations".
• Try Alt+Enter to force windowed mode.
• Update GPU drivers (clean install via DDU).

PC — Low FPS / Unplayable Performance

• Update graphics drivers to the latest stable version.
• Lower in-game graphics settings.
• Close background applications, especially overlay tools.

PC — Linux / Steam Deck / Proton

For PC BattlEye launch crashes on Windows, see the BattlEye section above.

In-Game & UI Issues

Proximity / In-Run Voice Chat Not Working

• Click the microphone icon on your player banner — required even if voice is enabled in settings.
• If still broken: disable IPv6 in your router settings to force IPv4.
• Kaspersky users: whitelist Discord — Kaspersky has been reported to block Marathon voice comms.
• Report persistent issues in the Marathon Discord feedback channels.

Username Shows "Redacted"

If your profile still isn't syncing, log into Bungie.net and verify or update your profile directly.

Can't Progress Past Registration / EULA

• Hold the confirm button until the meter fills — don't just tap it.

Premium / Collector Edition or Twitch Drops Not Showing

Pre-order bonuses and certain cosmetics unlock at full launch (March 5, 2026). Check again post-launch — this is expected behavior during Server Slam, not a bug.

Does Marathon Have Solo Play?

Marathon is a team-based extraction shooter — the primary mode is squads. Solo play options and specifics have not been fully detailed by Bungie for the full launch. Server Slam is squad-focused.

Does Server Slam Progress Carry Over to Full Game?

Bungie has not confirmed progression carryover from Server Slam. Typically, beta/test events reset at full launch — assume progress does not carry over unless Bungie explicitly states otherwise.

How to Disable Crossplay

• Go to Settings → Network (or Gameplay) in Marathon.
• Toggle off cross-platform play.
• Note: Disabling crossplay may increase matchmaking times but can resolve certain connection errors.

Quick Reference — All Error Codes

More Help & Bug Reports

For issues not covered here:

• Submit a ticket — Marathon Help Center (include Bungie.net name, PC/GPU specs, and overlay info)
• Marathon Help Community — Graphics/UI, Systems & Settings, In-Game Mechanics, Weapons, Zones
• @BungieHelp — Official real-time status and announcements
• help.bungie.net — Bungie support, name appeals, account issues