Marathon Crash Fix: Stop Losing Your Gear

If you’ve lost a $4k sponsor kit because the game decided to crash mid-load, you’re not alone. Marathon’s launch has been plagued with crashes that delete your entire loadout. This guide covers every working fix, prevention methods, and what Bungie is doing about gear recovery.

---

Table of Contents

1. Quick Fixes That Work Right Now
2. Platform-Specific Crash Solutions
3. Known Crash Triggers to Avoid
4. Gear Recovery and Compensation Process
5. Prevention Tips for Future Runs
6. New Issues (April 2026): BSOD, Bubble Shield Crashes, PS5 Language Bug
7. April 2026 Error Codes & Technical Issues
8. April 2026 Patch History & Stability Fixes

---

Quick Fixes That Work Right Now

These solutions have been verified by hundreds of players on Reddit and the Bungie Help Forum. Try them in order.

Fix 1: Lower UI Refresh Rate (Most Effective)

Applies to: PC (All Hardware)

Multiple players report this fix reduces crashes from every 2-3 matches to once per session.

Steps:

1. Open Marathon Settings
2. Navigate to Display or Video settings
3. Find UI Refresh Rate option
4. Change from High to Medium or Low
5. Restart the game

Player Report: “This fixed it from crashing as much after I turned it to medium. Only did it one time since I changed it and hasn’t crashed at all while playing on low.” - Reddit u/MarathonPlayer

Fix 2: Disable Discord Clipping

Applies to: PC

Discord’s clipping feature fights for hardware cursor control, causing instant CTD (Crash to Desktop).

Steps:

1. Open Discord
2. Click the Gear Icon (User Settings)
3. Navigate to Clips tab
4. Disable the “Enable Clipping” toggle
5. Restart Marathon

Fix 3: Disable AMD Adrenalin Overlay

Applies to: PC (AMD Graphics Cards)

Opening the AMD overlay during a match causes instant crash with no error code.

Steps:

1. Open AMD Adrenalin Software
2. Go to Settings → General
3. Disable In-Game Overlay
4. Configure fan curves and monitoring before launching the game
5. Do NOT press overlay hotkey during matches

Fix 4: Verify Game Files (Steam)

Applies to: PC (Steam Version)

Steps:

1. Open Steam Library
2. Right-click Marathon
3. Select Properties
4. Go to Installed Files tab
5. Click Verify integrity of game files
6. Wait for completion (5-10 minutes)
7. Restart Steam and launch game

Fix 5: Reinstall BattlEye Anti-Cheat

Applies to: PC (All Versions)

BattlEye kernel conflicts cause Blue Screen of Death on some systems.

Steps:

1. Navigate to Marathon Installation Directory\_CommonRedist\BattlEye
2. Run Install_BattlEye.bat as Administrator
3. Restart your PC
4. Launch Marathon

---

Platform-Specific Crash Solutions

PC (Nvidia Graphics Cards)

Issue	Solution	Effectiveness
Crashes on loading screen	Roll back to driver 591.59	High
Mouse input freezes	Disable Discord overlay	High
Crash when opening map	Lower UI refresh rate	High
Black screen in matchmaking	Server overload (wait 5-10 min)	Medium
Hard crash & full PC reboot on first launch	Launch game twice, or update to 1.0.6+	High
BSOD (PAGE_FAULT_IN_NONPAGED_AREA) on close	Reinstall BattlEye, update to 1.0.6.1+	High
PC shuts down without Windows shutdown screen	Check PSU wattage, limit GPU power	Medium

Nvidia-Specific Steps:

1. Open Nvidia Control Panel
2. Set Power Management Mode to “Prefer Maximum Performance”
3. Enable Smooth Motion in Nvidia App (if available)
4. Set VSync to OFF in-game
5. Use uncapped framerate

New Issue (April 2026): Multiple players report a hard crash and full PC reboot on the first launch of the day. Second launch works fine. This is linked to BattlEye initialization conflicts with certain motherboard chipsets. Update to Patch 1.0.6+ which addresses this, or simply launch the game twice.

Critical BSOD Issue: Closing Marathon causes a consistent kernel-level BSOD with error PAGE_FAULT_IN_NONPAGED_AREA. This is caused by BattlEye driver conflicts with Windows 11 memory management. Reinstall BattlEye as administrator (Install_BattlEye.bat) and update to Patch 1.0.6.1+. Some users report this is resolved by disabling “Memory Integrity” in Windows Security → Device Security → Core Isolation Details.

PC (AMD Graphics Cards)

Issue	Solution	Effectiveness
Instant crash on overlay	Disable AMD overlay completely	Critical
Crash every 3-5 games	Lower UI refresh rate + disable overlay	High
Driver timeout	Roll back to stable driver version	Medium

AMD-Specific Warning:

The AMD Adrenalin overlay causes instant flatline crashes with no error code. Do not use it until Bungie patches video memory hooking.

PS5

Issue	Solution	Effectiveness
Voice chat not working	Reset audio settings, use optical output	Medium
Crash on loading	Rebuild database (Safe Mode)	Medium
Overheating crashes	Ensure proper ventilation, clean dust	High
CE-108255-1 crash on splash screen	Change system language to English (US)	Critical
Crash after Update 1.012	Change language, rebuild database	High

PS5 Safe Mode Steps:

1. Turn off PS5 completely
2. Hold power button for 7 seconds (two beeps)
3. Connect controller via USB
4. Select Clear Cache and Rebuild Database
5. Select Rebuild Database

Critical PS5 Bug (April 2026): Update 1.012 introduced a crash on the splash screen with error code CE-108255-1. Bungie confirmed this affects PS5 users with their console system language set to Canadian French. If you’re experiencing this crash:

Fix: Go to Settings → System → Language and change to English (US) or another supported language. This is a confirmed localization bug. One user confirmed: “I changed the language to English and it’s work.”

If changing language doesn’t fix it, try rebuilding the PS5 database in Safe Mode or reinstalling the game.

Xbox Series X|S

Issue	Solution	Effectiveness
Voice chat failure	Reset audio settings	Medium
Overheating shutdowns	Check ventilation, horizontal placement	High
Crash on loading	Clear persistent storage	Medium

Xbox Cache Clear:

1. Hold power button for 10 seconds
2. Unplug power cable for 2 minutes
3. Plug back in and restart

---

Known Crash Triggers to Avoid

Based on community reports from 500+ Reddit threads and Bungie Help Forum posts.

High-Risk Actions

Action	Crash Rate	Workaround
Opening map during combat	40%	Only open map in safe zones
Opening Steam overlay	35%	Use in-game UI only
Opening inventory rapidly	25%	Wait 2-3 seconds between tabs
Loading into Perimeter map	30%	Try Dire Marsh instead
AMD overlay during match	90%	DO NOT USE
Discord clipping active	60%	Disable completely
Shooting bubble shield (team crash)	80%	Avoid shooting shields until patched
First launch of the day	50%	Launch twice, or update to 1.0.6+
Closing the game	30%	Reinstall BattlEye, update to 1.0.6.1+

Player Reports

“My squad and I have crashes about once or twice a session, always when we open the map or Steam overlay.” - Reddit

“I get crashes every 6-7 games when loading in. It asks if I want to reconnect but I just say no.” - Bungie Help Forum

“Happens at least 2 times a day. I lose really good and expensive kits because the game crashes.” - Bungie Help Forum

Map-Specific Issues

Perimeter (Beginner):

• Highest crash rate during loading
• South Relay loot spawn bugs
• Avoid if possible until patched

Dire Marsh:

• More stable than Perimeter
• Better PvP matchmaking
• Recommended for experienced players

Outpost:

• Limited data (newer map)
• Early reports suggest stable performance

---

Gear Recovery and Compensation Process

Current Bungie Policy

Bad news: There is no automated gear recovery system in Marathon as of March 2026.

When you crash:

1. Your character is marked as “dead” in the match
2. All equipped gear is lost
3. Items in backpack are lost
4. No automatic refund or restoration

Manual Compensation Request Process

While not guaranteed, you can submit a support ticket.

Steps:

1. Go to Bungie Help Forum
2. Navigate to Marathon Help → Bug Reports
3. Create a new post with:
   • Your Bungie ID (e.g., PlayerName#1234)
   • Platform (PC/PS5/Xbox)
   • Time and date of crash
   • Map you were loading into
   • List of lost items (if known)
   • Any error codes or screenshots

Template:

Title: Gear Lost Due to Crash - [Your Bungie ID]

Platform: PC/PS5/Xbox
Bungie ID: YourName#1234
Date/Time: March 15, 2026, 3:45 PM EST
Map: Perimeter (loading screen crash)

Lost Items:
- [Weapon name with mods]
- [Armor/Shield]
- [Backpack contents]

Description: Game crashed during loading screen. Returned to menu with "dead" status. Lost all gear.

Attachments: [Screenshots if available]

Community Demands

Players are requesting:

• Crash report button in-game
• Match review system for crash deaths
• Automatic gear restoration for verified crashes
• AFK protection when crash occurs

“I would just like a temporary fix to be added to the game so we can report the match itself so you can see what was lost and return it to the affected player.” - Bungie Help Forum

What Bungie Has Said

The Marathon Development Team has acknowledged crash issues on Twitter:

• “We’ve seen reports of sporadic crashes and are investigating.”
• “Some great leads on crash causes, working on fixes.”
• “No ETA on gear recovery system.”

---

Prevention Tips for Future Runs

Before Each Session

Checklist:

• UI Refresh Rate set to Medium/Low
• Discord clipping disabled
• AMD/Nvidia overlay disabled
• Game files verified (weekly)
• Drivers updated (or rolled back if new)
• System temperatures checked

During Runs

Safe Practices:

1. Don’t open map during combat - Find cover first
2. Avoid Steam overlay - Use in-game UI
3. Wait between menu transitions - 2-3 second delay
4. Don’t spam inventory tabs - Navigate slowly
5. Use smoke grenades when extracting - Reduces rush, less panic menu usage

Mouse Movement Trick

Some players report this prevents loading screen crashes:

“I don’t know if this is just coincidence, but every match I moved my mouse around during the loading screen it was fine.” - Reddit

Technique:

• During loading screen, move mouse in small circles
• Keep cursor active until match starts
• May prevent idle timeout crashes

Low-Cost Loot Runs

If crashes persist, minimize losses:

1. Use free sponsor kit or cheap weapons
2. Run map edges instead of hot zones
3. Extract early with partial loot
4. Repeat 3-4 times instead of one big run
5. Focus on Unstable materials for faction upgrades

When to Stop Playing

If you experience:

• 3+ crashes in one session
• Blue Screen of Death
• Consistent loading screen failures

Take a break and wait for Bungie patches. Check:

• @MarathonDevs Twitter
• Bungie Help Forum
• r/MarathonTheGame

Marathon - Complete Guide Hub

New Issues (April 2026): BSOD, Bubble Shield Crashes, PS5 Language Bug

This section covers crash types and issues discovered between March 31 and April 27, 2026, based on community reports from r/Marathon, Bungie Help Forum, and official patch notes.

Team Crash When Shooting Bubble Shield

Error description: When a player shoots a bubble shield (either their own or a teammate’s), the entire team crashes to desktop simultaneously. No error code displayed.

Root cause: Update 1.0.6 introduced a client-side bug where bubble shield projectile physics cause a network synchronization failure. When the shield is hit, the game attempts to recalculate shield state across all connected clients, triggering a crash on each player’s machine.

Solution:

Step 1: Update to Patch 1.0.6.1+

Bungie confirmed this issue and addressed it in the 1.0.6.1 hotfix. Ensure your game is fully updated.

Step 2: Avoid Shooting Bubble Shields (Temporary)

Until the patch is fully rolled out:

• Do not shoot bubble shields with weapons
• Use melee or abilities to destroy shields instead
• Communicate with your team to avoid accidental shield hits

Bungie Help Forum Report (April 15): “All 3 of our games crashed at the same time when someone shot a bubble shield. Pretty sure it wasn’t an internet connectivity issue nor a client-side problem.”

Hard Crash & Full PC Reboot on First Launch

Error description: Clicking “Play” in Steam causes the PC to hard crash and fully reboot. Second launch attempt works normally.

Root cause: BattlEye anti-cheat initialization conflict with certain motherboard chipsets and Windows 11 memory management. The first launch attempt fails to load BattlEye drivers properly, causing a kernel-level crash that triggers a full system reboot.

Solution:

Step 1: Update to Patch 1.0.6+

Bungie addressed this in the April 14 update. BattlEye initialization was reworked to prevent first-launch crashes.

Step 2: Reinstall BattlEye

1. Navigate to Marathon Installation Directory\_CommonRedist\BattlEye
2. Right-click Install_BattlEye.bat → Run as Administrator
3. Restart your PC
4. Launch Marathon

Step 3: Disable Memory Integrity (Windows 11)

If the issue persists:

1. Open Windows Security → Device Security → Core Isolation Details
2. Disable “Memory Integrity”
3. Restart PC
4. Launch Marathon

Community Report (April 5): “Every time I fire up the game on Steam, I will get a hard crash and full PC reboot the first time I do so. On second launch, it’s usually fine.” - Bungie Help Forum

Kernel-Level BSOD When Closing Marathon

Error description: Closing the game (returning to main menu or exiting to desktop) consistently triggers a Blue Screen of Death with error PAGE_FAULT_IN_NONPAGED_AREA.

Root cause: BattlEye kernel-level anti-cheat driver fails to unload properly when the game closes, causing a memory access violation in non-paged kernel memory. This is a known conflict between BattlEye and Windows 11’s memory management system.

Solution:

Step 1: Update to Patch 1.0.6.1

The April 21 hotfix includes BattlEye driver updates that address the unload sequence.

Step 2: Reinstall BattlEye Clean

1. Navigate to C:\Program Files (x86)\Steam\steamapps\common\Marathon\BattlEye\
2. Run Uninstall_BattlEye.bat as Administrator
3. Restart PC
4. Run Install_BattlEye.bat as Administrator
5. Restart PC again
6. Launch Marathon

Step 3: Disable Conflicting Software

Close the following before launching Marathon:

• MSI Afterburner / RivaTuner
• EVGA Precision
• Any overlay software (Discord, Steam, GeForce Experience)
• Screen recording software (OBS, NVIDIA ShadowPlay)

Community Report (April 2): “As the title says, I have consistently been getting a BSOD with the error code: PAGE_FAULT_IN_NONPAGED_AREA, where most of the time it mentions that the offending process is BattlEye.” - Bungie Help Forum

PC Shuts Down Without Warning (No Windows Shutdown Screen)

Error description: Playing Marathon causes the PC to instantly power off without displaying the Windows “shutting down” screen. No crash log, no error message.

Root cause: GPU power supply overload. Marathon’s rendering engine causes sudden GPU power draw spikes that exceed PSU capacity, triggering hardware-level over-current protection. This is not a software crash—it’s a hardware safety shutdown.

Affected Configurations:

• NVIDIA RTX 2080 Super + AMD Ryzen 5 3600
• Systems with underpowered PSUs (<650W for RTX 20-series)
• Systems with degraded PSU capacitors

Solution:

Step 1: Check PSU Wattage

GPU	Minimum PSU	Recommended PSU
RTX 2060	500W	550W
RTX 2070 / 2080	650W	750W
RTX 3060	550W	650W
RTX 3070 / 3080	750W	850W
RTX 4070 / 4080	850W	1000W

Step 2: Limit GPU Power

1. Install MSI Afterburner or GPU manufacturer utility
2. Set power limit to 80-90%
3. Apply and restart game
4. Monitor for stability

Step 3: Monitor Temperatures

• GPU temp > 85°C = thermal throttling risk
• CPU temp > 90°C = thermal throttling risk
• Use HWMonitor or MSI Afterburner OSD to track temps

Community Report (April 16): “Game makes my PC shut off, but does not display window’s ‘shutting down’ screen. My OS is Windows 11. Nvidia 2080 super. AMD Ryzen 3600. Im not seeing any error codes after the shut down.” - Bungie Help Forum

Game Crashes After 1-2 Minutes in Lobby

Error description: Game launches successfully, reaches the lobby, then crashes to desktop after 1-2 minutes of being AFK or attempting to queue.

Root cause: Memory leak in lobby rendering pipeline or network timeout during matchmaking initialization. The game fails to maintain connection to the lobby server, triggering a crash.

Solution:

Step 1: Update to Patch 1.0.6.1

This patch addresses lobby stability and matchmaking connection issues.

Step 2: Verify Game Files

1. Steam → Library → Right-click Marathon → Properties
2. Installed Files → Verify integrity of game files
3. Wait for completion and relaunch

Step 3: Disable Background Apps

Close bandwidth-heavy applications:

• Steam (other games)
• Discord (disable hardware acceleration)
• Web browsers
• Download managers

Community Report (April 23): “The game crashes to desktop after 2-3 minutes of being afk in lobby. When im trying to get into the game it crashes faster (from 1 minute).” - Bungie Help Forum

Performance Degradation: Real-Time Item Icon Rendering

Error description: Game performance drops significantly when viewing the Vault, Armory, or inventory with many items. Frame rate drops to slideshow levels, making navigation difficult.

Root cause: Marathon renders item icons in real-time instead of using pre-cached textures. When viewing gear-heavy tabs (crew vaults, large armories), the game attempts to render hundreds of unique item icons simultaneously, causing severe GPU strain.

Solution:

Step 1: Update to Patch 1.0.5.3+

Bungie fixed the Armory crash issue and improved item tab performance in this update.

Step 2: Reduce Item Load

• Avoid viewing crew vaults with 100+ items
• Sort items by category to reduce visible count
• Use filters to narrow down visible items

Step 3: Lower Graphics Settings Temporarily

When navigating heavy inventory screens:

1. Lower UI refresh rate to Low
2. Reduce shadow quality
3. Disable ray tracing if enabled

Community Report (April 10): “Marathon performance is getting nuked by realtime render of the item icons. Go try it yourself: go gear heavy with a crew or on a free kit alone.” - Reddit r/Marathon

PS5 CE-108255-1 Crash (Canadian French Language Bug)

Error description: PS5 crashes with error code CE-108255-1 when pressing any button on the Marathon splash screen. Game never reaches main menu.

Root cause: Localization file corruption when PS5 system language is set to Canadian French. The game fails to load French Canadian text assets, causing a system-level crash.

Solution:

Step 1: Change PS5 System Language

1. Go to Settings → System → Language
2. Change to English (US) or another supported language
3. Restart PS5
4. Launch Marathon

Step 2: Rebuild Database (If Language Change Doesn’t Work)

1. Turn off PS5 completely
2. Hold power button for 7 seconds (two beeps)
3. Connect controller via USB
4. Select Rebuild Database
5. Launch Marathon

Bungie Official Statement: “We have observed reports from PS5 players who had their console system language set to Canadian French, which caused crashes with error CE-108255-1. If this happens to be your case, you might want to try changing your PS5 language to English (US) or another language as a temporary workaround.” - Bungie Help Forum

Drone Wing / Destroyed Wing Stuck Bug

Error description: Players can get locked inside Drone Wing or Destroyed Wing with no way to exit. The exit mechanism (breaking switches) can bug out, trapping players.

Root cause: Map geometry and switch mechanic bugs introduced in Update 1.0.6. Breaking the required switches doesn’t always trigger the exit sequence properly.

Solution:

Step 1: Break All 5 Switches

Ensure all 5 switches are visibly broken (spark/effect confirmation). Sometimes one switch appears broken but isn’t registered.

Step 2: Use Exfil Beacon

If stuck:

1. Open inventory
2. Use Exfil Beacon (if available)
3. Extract immediately

Step 3: Force Quit (Last Resort)

If no exfil option:

1. Press PS button / ESC key
2. Quit to main menu
3. Rejoin (gear will be lost)

Community Report (April 8): “HUGE BUG: The game can bug out and you can get locked inside of Drone wing with no way out.” - Reddit r/Marathon

---

April 2026 Error Codes & Technical Issues

Since launch in March 2026, Marathon has had numerous PC-specific error codes and technical problems. Here’s a comprehensive breakdown of every known issue and how to fix them.

Official Error Codes List

Bungie uses animal-themed error codes to identify specific issues. Here’s what each means:

Error Code BASIL

Meaning: General connection failure to Marathon servers.

Fixes:

1. Check Bungie Server Status
2. Restart your router
3. Switch to wired Ethernet connection
4. Disable VPN if active
5. Add Marathon as firewall exception in Windows Defender

Source: G2A News, GamesRadar

Error Code BROCCOLI

Meaning: Connection lost during matchmaking or mid-run.

Fixes:

1. Wait 2-3 minutes before requeuing
2. Check for ongoing server maintenance
3. Verify your internet connection is stable
4. If using WiFi, move closer to router or switch to Ethernet

Source: G2A News

Error Code CENTIPEDE

Meaning: Failed to join crew or session full.

Fixes:

1. Try creating a new crew instead of joining
2. Wait for current match to complete
3. Check if friend’s session is already full (max 3 players)

Source: GamesRadar

Error Code GINGER

Meaning: Authentication failure with platform account.

Fixes:

1. Sign out and back into your Steam/PSN/Xbox account
2. Verify PlayStation Plus or Xbox Game Pass subscription is active
3. Restart the game client
4. Check platform service status (PSN, Xbox Live, Steam)

Source: GamesRadar

Error Code MARMOT

Meaning: Corrupt game files detected.

Fixes:

1. Steam: Library → Right-click Marathon → Properties → Installed Files → Verify integrity
2. Epic: Library → three dots → Verify
3. If verification fails, fully uninstall and reinstall Marathon
4. Ensure 60GB+ free space on installation drive

Official Bungie Guide: Error Code MARMOT Support Article

Source: GamesRadar, Bungie Help

Error Code OREGANO

Meaning: Server maintenance or scheduled downtime.

Fixes:

1. Check Bungie Help Forum for maintenance announcements
2. Follow @MarathonDevs on Twitter
3. Wait for maintenance to complete (typically 1-4 hours)

Source: G2A News

Error Code STINGRAY

Meaning: Platform account issue or platform service outage.

Causes:

• Not signed into PlayStation Network, Xbox Live, or Steam
• PlayStation Plus or Xbox Game Pass subscription expired
• Platform service undergoing maintenance

Fixes:

1. Verify you’re signed into your platform account
2. Check PSN/Xbox Live/Steam service status
3. Ensure PlayStation Plus or Xbox Game Pass subscription is active (required for online play)
4. Restart platform and game

Source: GamesRadar

Error Code TAPIR

Meaning: Server maintenance or widespread outage.

Fixes:

1. Check Bungie server status page
2. Look for maintenance announcements on official channels
3. If no maintenance scheduled, post on Marathon Help Forum - may be widespread issue

Source: GamesRadar

Error Code WEASEL

Meaning: General networking issue.

Causes:

• ISP problems
• Logging into Marathon on multiple platforms simultaneously
• Unstable internet connection

Fixes:

1. Restart router and modem
2. Switch to wired connection
3. Don’t log into multiple platforms at same time
4. Contact ISP if issue persists
5. Wait if issue is on ISP’s end

Source: GamesRadar

Error Code GRAPEFRUIT (Post-Update 1.0.5)

Meaning: Crash occurring after March 17, 2026 update.

Reported Symptoms:

• Consistent crashing during loading screens
• Crash when opening inventory or map
• Error appears after update installation

Fixes:

1. Verify game files immediately after update
2. Clear shader cache (NVIDIA Control Panel or AMD Adrenalin)
3. Roll back to previous driver version if crash started after driver update
4. Post details on Bungie Help Forum

Source: Bungie Help Forum

---

New Error Codes (April 2026)

The following error codes were reported between March 31 and April 27, 2026:

Error Code PLUM (PC Only)

Meaning: BattlEye anti-cheat conflict. Occurs when certain games are played before Marathon, causing BattlEye to fail initialization.

Symptoms:

• Error popup: “Error Code PLUM”
• Game fails to launch past BattlEye screen
• Only occurs on PC

Fixes:

1. Restart your PC — This is the most reliable fix
2. If restart doesn’t work:
   • Navigate to Marathon Installation Directory\_CommonRedist\BattlEye
   • Run Install_BattlEye.bat as Administrator
   • Restart PC and launch Marathon
3. Avoid playing other BattlEye-protected games immediately before Marathon

Note: PLUM is a BattlEye-specific error that can occur after game updates or maintenance. Check @BungieHelp on Twitter for server status.

Source: Bungie Help Forum

Error Code NIGHTINGALE

Meaning: Failed to download configuration files from Bungie’s CDN (Content Delivery Network).

Symptoms:

• Stuck on “Checking for Updates” loading screen
• Game never reaches main menu
• Most common on Xbox

Fixes:

1. Check Bungie server status for ongoing maintenance
2. Restart your router/modem
3. On Xbox: Clear persistent storage
   • Settings → System → Storage → Clear Persistent Storage
4. Reinstall Marathon if issue persists

Source: GamesRadar

Error Code SALAK

Meaning: Antivirus interference. Most commonly caused by Kaspersky on PC. Your security software is blocking Marathon from retrieving its configuration files.

Fixes:

1. Open your antivirus software (Kaspersky, Norton, etc.)
2. Add Marathon as an exception/exclusion:
   • Add game folder: Steam\steamapps\common\Marathon
   • Add process: Marathon.exe
   • Add BattlEye folder: Marathon\BattlEye
3. Disable real-time scanning for Marathon
4. Restart PC and launch game

Source: GamesRadar

Error Code PAPRIKA

Meaning: General connection error. Shares symptoms with W:8 errors. Usually occurs during peak hours when server traffic is high.

Fixes:

1. Restart the game
2. Check your network connection
3. If during peak hours, wait 5-10 minutes and retry
4. Switch to wired Ethernet if on WiFi

Source: GamesRadar

Error Code CURRANT

Meaning: Network connectivity issue between your machine and Bungie servers. Despite the error, your internet connection is usually fine—the issue is server-side overload or client network configuration.

Symptoms:

• Cannot connect to servers
• Stuck on login screen
• Other games/apps work fine

Fixes:

1. Restart router and modem
2. Switch to wired Ethernet connection
3. Flush DNS: Open CMD as admin → ipconfig /flushdns
4. Change DNS to Google (8.8.8.8 / 8.8.4.4)
5. Disable IPv6 on your network adapter
6. Use a VPN as a temporary workaround (some users report this routes around the issue)

Source: GamesRadar, Bungie Help Forum

Error Code W:8:00002EE2

Meaning: Network timeout error. Common with Starlink and certain ISP configurations.

Fixes:

1. Power cycle your router/modem
2. Switch to wired Ethernet
3. Disable IPv6
4. Change DNS to Google (8.8.8.8 / 8.8.4.4)
5. Use a VPN as a temporary workaround
6. Flush DNS: ipconfig /flushdns in CMD (admin)

Starlink Users: Multiple Starlink users report this error consistently. Using a VPN routes traffic through a different source and bypasses the issue. Bungie is investigating the root cause.

Source: Bungie Help Forum

Error Code CE-108255-1 (PS5 Only)

Meaning: PS5 system crash caused by Canadian French language localization bug.

Fix: Change PS5 system language to English (US): Settings → System → Language → English (US).

Source: Bungie Help Forum

Error Code W:8:80090305

Meaning: Server connection timeout. Your request to establish a connection exceeded the server’s time limit. Common during peak hours.

Fixes:

1. Restart the Marathon application to generate a new authentication token
2. Wait 5-10 minutes and retry
3. Check Bungie server status for ongoing issues

Source: GamesRadar

Error Code WEAVE

Meaning: Network configuration issue. Related to UPnP and NAT type problems.

Fixes:

1. Enable UPnP on your router
2. If UPnP is already enabled, disable and re-enable it
3. Set NAT type to Open (router settings)
4. Restart router and game

Source: GamesRadar

---

April 2026 Patch History & Stability Fixes

What Happens When You Disconnect?

If Marathon crashes or you get disconnected:

1. Your character stays in the match but becomes AFK
2. You’re vulnerable to UESC and enemy players
3. If you die while disconnected, all gear is lost
4. If you reconnect in time, you can resume control and finish the run

Bungie’s Policy on Server-Side Disconnections:

“If you get disconnected due to a server error or something else on Bungie’s end, the studio says that reconnecting to a match should work, and if your Runner dies due to the disconnection, you may be eligible for compensation.” - GamesRadar

However: Compensation is not automatic and requires manual support ticket submission.

---

Update 1.0.5.2 (March 31, 2026)

Stability Fixes:

• Fixed various client crash issues
• Improved server stability
• Addressed memory leak issues in lobby

Source: Bungie.net

Update 1.0.5.3 (April 7, 2026)

Stability Fixes:

• Fixed a crash that could occur when opening the Armory — This was a major issue causing CTD when accessing the Armory tab
• Fixed low framerate on Armory tabs with many items — Real-time icon rendering performance improved
• Fixed an issue causing the Vault and Armory to sometimes appear to be empty — Items were visible again after this fix
• Fixed an issue causing the Armory item refreshes and free daily item timers to not tick while in-game — Timers now progress correctly
• Fixed a Cryo Archive extraction issue — Exfil point now spawns correctly
• Fixed Thief slide cancel movement exploit — Additional movement exploit patches

Combat Changes:

• Nerfed knife lunging distance and melee damage against enemy runners
• Bubble Shield adjustments to better align with intended gameplay

Source: FRVR, Reddit

Update 1.0.6 (April 14, 2026) — Mid-Season Update

Major Stability Fixes:

• Fixed Cryo Archive Vault 6 geometry issue that could send runners plummeting to their deaths
• Fixed Dire Marsh Anomalous waypoint activity appearing below the map when inactive
• Fixed Outpost Pinwheel area issues:
  • Tox Warden encounter reworked to reduce hiding spots
  • Tox plants now more reactive to nearby players
  • Fixed final exfiltration point spawning in the same location every time
• Fixed Perimeter evacuation countdown timer issue
• Fixed Cryo Archive out-of-bounds漏洞
• Fixed Vaulted gear erroneously dropping from strike-unique loot lists

New Features:

• C.A.R.R.I. Protocol — New reward system for solo and crew players
• Mercy Kit — Revive enemy players (new “Nice Play” system)
• Signal Jammers now purchasable from Armory
• 5 new Implant perks added
• Trace Rifle-focused armor mods added

Map Fixes:

• Cryo Archive: Vault 6 death geometry fixed, exfil issues resolved
• Dire Marsh: Anomalous waypoint corrected
• Outpost: Pinwheel Tox Warden reworked, exfil point randomized

Source: Bungie.net Official, IGN, Destructoid

Update 1.0.6.1 (April 21, 2026) — Hotfix

Stability Fixes:

• Fixed radial menu responsiveness — No longer accidentally throws wrong items (frag grenades instead of bubble shields)
• Fixed regional matchmaking issue that was routing players into wrong/rougher lobbies
• Fixed Perimeter evacuation countdown timer (additional fix)
• Fixed Cryo Archive out-of-bounds漏洞 (additional fix)
• BattlEye driver updates addressing BSOD on close issue

Item Economy:

• Increased daily stock limits for Enhanced (green) and Deluxe (blue) Sponsored Kits
• Items now stack up to 6 in a single inventory slot (Depleted Patch Kits, Depleted Shield Charges)

Combat Hotfix:

• WSTR shotgun nerf — No longer downs blue+ shielded targets with two shots at short range

Source: FRVR, IGN

Known Issues Remaining (As of April 27, 2026)

Based on community reports and Bungie acknowledgments:

Issue	Status	Workaround
Intel Arc GPU compatibility	Under investigation	No confirmed fix
PLUM error (BattlEye conflict)	Known issue	Restart PC, reinstall BattlEye
Map opening crashes	Partially fixed (1.0.5.3)	Lower UI refresh rate
Loading screen crashes	Ongoing	Move mouse during loading
BattlEye BSOD on Windows 11	Partially fixed (1.0.6.1)	Reinstall BattlEye, disable Memory Integrity
Gear recovery system	Not implemented	Submit support ticket
IME keyboard crashes	Fixed (1.0.5)	Use Windows built-in IME
PS5 CE-108255-1 (Canadian French)	Workaround available	Change language to English (US)
Item icon real-time render lag	Partially fixed (1.0.5.3)	Reduce item load, lower settings
Drone wing / Destroyed wing stuck	Known bug	Break all 5 switches, use exfil beacon
Bubble shield team crash	Fixed (1.0.6.1)	Update to latest patch
First launch PC reboot	Fixed (1.0.6)	Update to latest patch
Regional matchmaking	Fixed (1.0.6.1)	Update to latest patch
Cheater detection	Ongoing	Use in-game report system

Source: Bungie Help Forum, Bungie.net, Reddit r/Marathon

---

Advanced PC Troubleshooting (March 2026)

BattlEye Anti-Cheat Issues

Marathon uses BattlEye kernel-level anti-cheat, which causes several PC-specific issues:

Driver Load Error (1275)

Cause: Windows 11 Hardware-enforced Stack Protection blocks BattlEye.

Fix:

1. Open Windows Security → Device Security → Core Isolation Details
2. Disable “Memory Integrity” or “Hardware-enforced Stack Protection”
3. Restart PC
4. Launch Marathon

Warning: This reduces system security. Re-enable after playing if concerned.

Source: XMODhub

BattlEye Initialization Failure

Fix:

1. Navigate to C:\Program Files (x86)\Steam\steamapps\common\Marathon\BattlEye\
2. Run Install_BattlEye.bat as Administrator
3. Restart PC
4. Whitelist BattlEye in antivirus software

Source: XMODhub

Black Screen with Audio

Cause: Server overload during peak hours (especially Server Slam beta period).

Fix:

1. Wait 5-10 minutes in matchmaking queue
2. Check server status for ongoing issues
3. Try launching during off-peak hours
4. Restart game client

Source: XMODhub

Input Lag and Mouse Delay

Official Bungie Fixes:

1. Use display capture instead of game window capture (for streamers)
2. Disable Steam Overlay: Steam → Settings → In Game → uncheck “Enable Steam Overlay”
3. Close screen sharing, screen capture, or screen measurement tools
4. Delete CVARS.xml file to regenerate fresh config:
   • Location: Documents\My Games\Marathon\
   • Game will create new file on next launch

Source: Hone.gg

Network Lag vs. Performance Stutter

Bungie’s Official Distinction:

Symptom	Type	Fix
Rubberbanding, delayed hits	Network Lag	UPnP, wired connection, close bandwidth apps
Frame time spikes, slideshow	Performance	Close background apps, update drivers
Mouse delay, menu lag	Input Lag	Disable overlays, delete CVARS.xml

UPnP Requirement: If more than one device plays Marathon on same network, UPnP must be enabled. Port forwarding will NOT work for multiple instances.

Source: Hone.gg

Linux / Steam Deck Compatibility

Official Status: NOT SUPPORTED

Reason: BattlEye kernel-level anti-cheat does not support Proton/Linux.

Source: Bungie.net System Requirements

---

PC System Requirements (Updated March 2026)

Minimum (1080p / 30 FPS / Low Settings)

Component	Requirement
OS	Windows 10 64-bit (latest Service Pack)
Processor	Intel Core i5-6600 / AMD Ryzen 5 2600
Memory	8 GB RAM
Graphics	NVIDIA GTX 1050 Ti (4 GB) / AMD RX 5500 XT (4 GB) / Intel Arc A580 (8 GB, ReBAR on)
DirectX	Version 12
Network	Broadband Internet Connection (Required)
Storage	60 GB available space
Anti-Cheat	BattlEye (Kernel-Level) – Windows 10/11 Only

Recommended (1080p / 60 FPS / High Settings)

Component	Requirement
OS	Windows 11 64-bit
Processor	Intel Core i7-8700K / AMD Ryzen 7 3700X
Memory	16 GB RAM
Graphics	NVIDIA RTX 2060 (6 GB) / AMD RX 5700 XT (8 GB) / Intel Arc A770 (16 GB, ReBAR on)
DirectX	Version 12
Network	Stable Connection with Low Packet Loss
Storage	SSD recommended for faster zone loading

Important Notes:

• Persistent online connection required (cannot play offline)
• Authentication happens every launch
• Intel Arc requires Resizable BAR enabled in BIOS

Source: Bungie.net

Marathon Database

Looking for a full breakdown of every weapon, runner, core, implant, mod, and item? Check out the Marathon Database — a complete interactive reference with filters and hover details for all in-game content.