NG New Games Guide

Halo: Campaign Evolved

Halo: Campaign Evolved crash fix: work through it in this order

By the New Games Guide team ·

Crashes are not one problem, and treating them as one is why people spend an evening reinstalling and end up exactly where they started. When it crashes tells you what is wrong. Find your row in the table below, then jump to the fix.

When it crashesAlmost alwaysGo to
Before any menu appearsOverlay injection or GPU driverFix 1 · Fix 2
A few minutes into any session, randomlyShader cache or memoryFix 3 · Fix 6
At the same mission, every timeCorrupt installed fileFix 4
Only when loading a saveCorrupt save or profileFix 7
Only in co-opNetwork or version mismatchFix 8
After a driver or Windows updateStale cache against new driverFix 3
Console only, repeatedlyPersistent cacheFix 9
Crash timing mapped to cause: before the menu means overlays or drivers; random mid-session means shader cache or VRAM; the same mission every time means a corrupt file; only on one save means the save; only in co-op means version mismatch or packet loss.
Match the fix to the timing. Crashes before the menu and crashes mid-session have almost nothing in common.

Fix 1 — Kill every overlay#

This is first because it is free, takes two minutes, and is responsible for a large share of launch-day PC crashes on Unreal Engine titles. Overlays inject a DLL into the game's rendering pipeline. When the game's render path and the overlay's hook disagree, the process dies before you ever see a menu.

Turn all of these off, then test:

RivaTuner in particular is worth singling out: it hooks aggressively, it is bundled with Afterburner so people forget it is running, and it survives closing Afterburner's window.

Fix 2 — Clean-install your GPU driver#

"I updated my driver" is not the same as a clean install. Driver upgrades layer over the previous installation and carry forward the corrupted shader caches and stale profile entries that cause crashes in the first place.

NVIDIA:

  1. Download the current driver first, so you are not without one mid-process.
  2. Run the installer, choose Custom, and tick Perform a clean installation.
  3. For a stubborn case, boot into Safe Mode and run Display Driver Uninstaller (DDU) before installing.

AMD:

  1. Download the current Adrenalin package.
  2. Use the AMD Cleanup Utility, or DDU in Safe Mode.
  3. Install fresh.

Fix 3 — Delete the shader cache#

Unreal games compile shaders for your specific GPU and driver, then cache them. When the driver changes or the game patches, that cache can become invalid — and an invalid cache produces random crashes minutes into a session, plus stutter and visual corruption.

Delete these, then launch and expect one stuttery session while it rebuilds:

%LOCALAPPDATA%\NVIDIA\DXCache
%LOCALAPPDATA%\NVIDIA\GLCache
%LOCALAPPDATA%\AMD\DxCache
%LOCALAPPDATA%\D3DSCache

Also clear the game's own cache under its Saved folder in %LOCALAPPDATA%. Leave SaveGames alone — that is your campaign progress, and nothing in this fix requires touching it.

On Steam, disabling Shader Pre-Caching in Settings → Downloads and then re-enabling it forces a rebuild of Steam's copy as well.

Fix 4 — Verify or repair, don't reinstall#

A single corrupt file produces the most diagnosable crash there is: the same point, every time, reproducibly. Verification finds and replaces exactly that file in minutes.

Reinstalling does the same thing plus a full re-download. Only do it if verification reports errors it cannot fix.

Fix 5 — Turn off the settings that commonly break first#

If the game runs but crashes under load, these are the settings that most often cause it on Unreal titles. Test at lowest settings first to confirm it is a settings problem at all, then raise them back one at a time.

SettingTryWhy
Ray tracing / hardware LumenOffHighest VRAM and driver-path risk
Frame generationOffInteracts badly with overlays and unstable framerates
UpscalingSwitch DLSS ↔ FSR ↔ offIsolates a specific upscaler's driver path
Texture qualityOne step downThe usual cause of VRAM exhaustion crashes
Fullscreen modeBorderless windowedAvoids exclusive-fullscreen mode-switch crashes
Framerate capCap 10 below your refresh rateUncapped menus can spike a GPU to thermal limits
Resolution scale100%Above 100% multiplies VRAM use quickly

Fix 6 — Give it more memory headroom#

Modern Unreal games crash when they run out of VRAM or when Windows refuses a page-file expansion. Both look identical to the player: a hard crash to desktop, no error.

Fix 7 — When one save is the problem#

If everything is stable until you load one specific save, the save is what is broken.

  1. Start a new campaign and play for a few minutes. If that is stable, the installation is fine.
  2. Load a different, earlier save. If that works, you have isolated the bad one.
  3. Copy your entire save folder somewhere safe before doing anything else.
  4. Move the bad save out of the folder — do not delete it. If a future patch fixes the underlying bug, you can put it back.
  5. Continue from the last good checkpoint.

Losing an hour of progress is annoying. Losing every save because you deleted the folder to "clean it out" is worse, and it happens constantly.

Fix 8 — Co-op only crashes#

Crashes that only occur in co-op are network or version problems wearing a crash costume.

Fix 9 — Console crashes#

Console troubleshooting is short because there are fewer variables.

  1. Full power cycle, not a restart. Hold the power button for ten seconds until the console fully shuts down, unplug it for thirty seconds, plug it back in and start it. This clears the persistent cache; a menu restart does not.
  2. Check free storage. Consoles behave badly below roughly 10% free space, and the symptoms include crashes on save.
  3. Clear the game's saved data cache, not your saves, from the platform's storage menu.
  4. Delete and re-download the game — on console this is the equivalent of verification. Save data is stored separately and survives, but confirm it is in cloud storage first.
  5. Try an external drive, or move it off one. A failing external drive produces crashes that look exactly like game bugs.

Still crashing? Collect this before you report it#

A useful crash report gets a real answer. Include:

FAQ#

Why does it crash at the same spot every time?#

That is the signature of a corrupt installed file or a specific asset your hardware cannot load. Verify the installation first (Fix 4) — a reproducible crash at a fixed point is the easiest kind to fix, and verification usually does it in under five minutes.

Is it my hardware or the game?#

Run something else demanding for an hour — another heavy game, or a stress test. If your system is stable elsewhere and only this game crashes, it is the game or its configuration. If other things crash too, look at memory profiles, temperatures and power supply before touching game settings.

Should I underclock or undervolt my GPU?#

Undervolting is a legitimate diagnostic. If a modest undervolt or a slight core offset stops the crashes, you have a power-delivery or stability problem under load rather than a game bug — and that is worth knowing regardless of this game.

Does lowering settings actually stop crashes?#

Yes, when the cause is VRAM exhaustion or an unstable GPU under load — which covers a large share of mid-session crashes. It does nothing for crashes before the menu appears, which are almost always overlays or drivers. Match the fix to the timing.

Spotted something out of date? Patch notes move fast — tell us at newgamesguide.com/contact and we will re-test the steps.

Related guides