How to Fix Marathon Crashing and Not Launching on PC (2026)

How to Fix Marathon Crashing and Not Launching on PC (2026)

Marathon just dropped and you’re stuck staring at a crash report instead of looting zones. Typical launch day stuff. If you need to fix Marathon crashing on PC, you’re not alone — the Server Slam already showed us that Bungie’s extraction shooter has some rough edges on certain hardware configs. The good news is that most of these crashes have straightforward fixes.

TL;DR — Quick Ways to Fix Marathon Crashing on PC

• Update your GPU drivers to the latest Game Ready / Adrenalin release. This alone fixes crashes for most players.
• Verify game files through Steam. Corrupted downloads from the 80GB install are extremely common.
• Disable overlays (Discord, GeForce Experience, Steam Overlay). They conflict with Marathon’s renderer.
• Run as Administrator and make sure Windows is fully updated.

If those didn’t fix Marathon crashing on your PC, keep reading. We’ve got 12 fixes below that cover every known crash scenario.

—

1. Update Your GPU Drivers

This is fix number one for a reason. Both NVIDIA and AMD push out day-one driver updates for major releases like Marathon, and running outdated drivers is the single most common reason for crashes at launch.

What to do:

• NVIDIA: Open GeForce Experience or go to nvidia.com/drivers and grab the latest Game Ready Driver.
• AMD: Open Radeon Software or download from amd.com/support.
• Intel Arc: Update through Intel Driver & Support Assistant.

Why it works: New game-specific driver profiles fix shader compilation errors and rendering bugs that cause crashes to desktop. Marathon uses a custom engine, so driver-level optimizations matter a lot here.

2. Verify Game Files on Steam

An 80GB download is a lot of data to transfer without a single hiccup. If even one file got corrupted during the install, Marathon will crash on launch or freeze during loading screens.

What to do:

1. Open Steam, right-click Marathon in your library.
2. Go to Properties > Installed Files > Verify integrity of game files.
3. Wait for the scan to finish. It’ll re-download anything that’s broken.

Why it works: Corrupted or incomplete files get replaced with clean copies from Steam’s servers. This takes 5-10 minutes but fixes a huge chunk of launch failures.

3. Run Marathon as Administrator

Windows sometimes blocks games from accessing the files and system resources they need, especially on fresh installs. Running as admin gives Marathon full permissions.

What to do:

1. Navigate to Marathon’s install folder (right-click in Steam > Manage > Browse local files).
2. Right-click the main .exe file and select Properties.
3. Go to the Compatibility tab and check Run this program as an administrator.
4. Click Apply.

Why it works: Some anti-cheat systems and shader cache writes require elevated permissions. Without them, Marathon can silently crash during initialization.

4. Disable Overlays

Overlays from Discord, GeForce Experience, Steam, and MSI Afterburner inject code into the game’s rendering pipeline. Marathon’s custom engine doesn’t always play nice with that.

What to do:

• Discord: Settings > Game Overlay > toggle off.
• GeForce Experience: Settings > General > In-Game Overlay > toggle off.
• Steam: Right-click Marathon > Properties > uncheck “Enable the Steam Overlay while in-game.”
• MSI Afterburner / RivaTuner: Close them entirely before launching.

Why it works: Overlay hooks can cause Direct3D conflicts, especially during the first few weeks before developers patch in broader compatibility. If Marathon was crashing during loading screens or right after the splash screen, overlays are a prime suspect.

5. Delete the Shader Cache

Marathon compiles shaders on your first launch, and sometimes that cache gets corrupted. Deleting it forces a fresh compile.

What to do:

1. Press Win + R, type %localappdata%, and hit Enter.
2. Look for a Bungie or Marathon folder.
3. Delete any folder named ShaderCache, Cache, or PipelineCache.
4. Relaunch the game. Expect longer load times on the first boot — that’s normal.

Why it works: Corrupted shader caches cause crashes during map loading or when specific visual effects trigger. A fresh compile rebuilds everything cleanly for your GPU.

6. Set the Correct DirectX Version

Marathon supports both DirectX 11 and DirectX 12. Some GPUs — particularly older NVIDIA cards like the GTX 1050 Ti — are more stable on DX11, while newer cards run better on DX12.

What to do:

1. Open Steam, right-click Marathon > Properties.
2. In Launch Options, type: -dx11 to force DirectX 11 or -dx12 to force DirectX 12.
3. If you’re on the minimum spec (GTX 1050 Ti / i5-6600), start with DX11.

Why it works: DX12 gives better performance on modern hardware but can be unstable on older GPUs. DX11 is more forgiving and eliminates an entire class of rendering crashes.

7. Update Windows

Yeah, it’s boring advice. But Windows updates include DirectX runtime updates, security patches, and driver framework changes that directly affect game stability.

What to do:

1. Open Settings > Windows Update.
2. Click Check for updates and install everything, including optional updates.
3. Restart your PC after updates finish.

Why it works: Outdated DirectX runtimes and .NET frameworks can cause Marathon to crash before it even reaches the main menu. This is especially true if you’ve been deferring updates.

8. Close Background Apps and Free Up RAM

Marathon recommends 16GB of RAM for a reason. If you’ve got Chrome tabs, Spotify, and a dozen background apps eating your memory, the game will crash when it tries to load large zones.

What to do:

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Sort by Memory usage and close anything you don’t need.
3. Pay special attention to browsers (Chrome alone can eat 4-6GB), Wallpaper Engine, and hardware monitoring tools.

Why it works: When Marathon runs out of available RAM, Windows starts using the page file on your drive. This causes massive stutters and often leads to a full crash, especially during zone transitions. If you want to squeeze even more performance out of your rig, check out our guide on how to reduce input lag for more system-level tweaks.

9. Disable Fullscreen Optimizations

Windows 10 and 11 apply “fullscreen optimizations” by default, which essentially force games into a borderless windowed mode. This causes input lag and, in some cases, outright crashes.

What to do:

1. Right-click Marathon’s .exe file > Properties.
2. Go to the Compatibility tab.
3. Check Disable fullscreen optimizations.
4. Click Apply.

Why it works: Fullscreen optimizations add an extra compositing layer that some game engines don’t handle well. Disabling it lets Marathon take full exclusive control of your display, which is more stable.

10. Reinstall Visual C++ Redistributables

Marathon relies on Visual C++ runtime libraries. If yours are outdated or corrupted, the game will crash immediately on launch — sometimes without even showing an error message.

What to do:

1. Download the latest Visual C++ Redistributable from Microsoft (both x64 and x86 versions).
2. Install both. If prompted to repair, choose Repair.
3. Restart your PC.

Why it works: Missing or corrupted VC++ runtimes are one of the most common causes of games failing to launch entirely. You’ll see either a cryptic DLL error or just… nothing happens when you click Play.

11. Check Your SSD Space and Install Location

Marathon requires an SSD and takes up 80GB. If your SSD is nearly full, Windows can’t create the temporary files and swap space the game needs, leading to random crashes.

What to do:

• Make sure you have at least 100GB free on the drive where Marathon is installed (the game needs breathing room beyond its base install size).
• If you installed Marathon on a hard drive (HDD), move it to an SSD. Right-click in Steam > Properties > Installed Files > Move Install Folder.

Why it works: Bungie requires an SSD for a reason. The extraction shooter loads massive zones dynamically, and HDDs simply can’t keep up. This causes texture streaming failures and hard crashes. The DLSS vs FSR vs XeSS comparison we published is also worth reading — using upscaling reduces VRAM load and can prevent out-of-memory crashes on GPUs with 4-6GB.

12. Disable Overclocks

If you’re running a GPU or CPU overclock, dial it back to stock settings before troubleshooting Marathon crashes. Overclocks that are stable in other games might not be stable here.

What to do:

• GPU: Open MSI Afterburner (or your preferred OC tool) and reset core clock and memory clock to default.
• CPU: Enter BIOS and disable XMP/EXPO or any manual CPU overclock temporarily.
• Test Marathon at stock. If it stops crashing, your overclock is the problem. You can try re-applying it at lower values.

Why it works: Every game stresses your hardware differently. Marathon’s custom engine and anti-cheat may push your CPU or GPU in ways that expose instability in your overclock. This is especially common with aggressive memory overclocks.

—

Still Need to Fix Marathon Crashing on PC?

If you’ve tried all 12 fixes above and Marathon is still crashing on your PC, here are your last resorts:

• Check Bungie’s known issues page. They actively track launch bugs and push hotfixes. A server-side fix might already be in the works.
• Submit a crash report. When Marathon crashes, it usually generates a log file in %localappdata%\Bungie\Marathon\Logs. Attach this to your support ticket.
• Try a clean GPU driver install. Use DDU (Display Driver Uninstaller) in Safe Mode to completely remove your GPU drivers, then install fresh.
• Monitor your temps. Use HWMonitor or HWiNFO to check if your CPU or GPU is thermal throttling. If your GPU hits 90C+ or your CPU hits 100C, that’s a hardware problem, not a game problem.

The same troubleshooting approach that helped players fix Valorant crashing applies here — work through fixes one at a time and test after each change so you know exactly what solved it.

These 12 methods cover every known way to fix Marathon crashing on PC as of launch week. Marathon is a demanding game, but it should run fine once you eliminate the software conflicts. Bungie will keep patching stability issues over the coming weeks, so keep your game updated and check back here for any new fixes we discover.