pc guide | Updated August 15, 2026

Halo Campaign Evolved Crashing & Keyes Known Issues

Quick answer

Halo Support still lists a Keyes crash for NVIDIA RTX 50-series cards on drivers 610.47, 610.62, and 610.74; its documented workaround is driver 610.88.

Checked August 15, 2026. Match your platform, hardware, driver, and crash point to an official entry before changing anything. The July 29 patch improved other stability cases, but the current Known Issues page still lists the Keyes case.

Halo Campaign Evolved campaign scene used to identify crash and known-issue guidance
Official Halo: Campaign Evolved media. Used for editorial identification.

Officially confirmed crashes and blockers

Halo Support currently lists the Keyes crash only for NVIDIA RTX 50-series graphics cards using drivers 610.47, 610.62, or 610.74. The official workaround links to NVIDIA driver 610.88. Do not apply that diagnosis to a different GPU, mission, or driver version.

The same official page says some Intel 13th- and 14th-generation processors may crash before the splash screen because of a pre-existing microcode issue. It also documents an AMD high-refresh-rate crash condition when VSync is enabled and the in-game frame cap is set below one quarter of the display refresh rate.

A separate global issue can block progress in Two Betrayals if the Banshee is destroyed after the first generator. Halo Support lists the condition but does not publish a universal repair for an already affected save.

Safe troubleshooting matched to the symptom

Use only the branch that exactly matches what you see. Stop after each change and retest the same launch or mission point.

  1. If Steam was launched through HaloCampaignEvolved.exe, close it and start the game from the Steam library.
  2. For the documented RTX 50-series Keyes case, confirm the GPU and driver version first; use the official 610.88 link only when the listed versions match.
  3. For a pre-splash crash on an Intel 13th- or 14th-generation system, check the system or motherboard manufacturer for its latest BIOS rather than using a third-party updater.
  4. For the documented AMD high-refresh condition, raise the in-game cap to at least one quarter of the display refresh rate or disable VSync.
  5. Install the current game update, verify PC files through the official platform flow, and submit a Halo Support ticket when the symptom does not match a published entry.

What the July 29 patch changed

Halo Support says the July 29 build improved stability when watching or skipping The Maw introduction with FSR on AMD driver 26.6.2 or 26.6.4, added warnings for AMD or NVIDIA driver versions with known issues, and made general Pillar of Autumn stability improvements.

That patch note does not say every crash was fixed. It also states that installing the update resets mid-mission saved progress while preserving unlocked missions and rally points.

Unverified advice: do not do this

Do not download drivers, BIOS files, DLLs, registry files, or crash-fix utilities from an unofficial mirror. Do not disable security software, delete save data, or roll back a driver only because a forum post reports success.

Community threads and videos prove that players are still searching for help, but they do not establish a root cause or a safe fix. Treat any step not repeated by Halo Support, the hardware vendor, or the platform owner as unverified.

Prepare a useful support report

When the official branches do not match, preserve the evidence instead of stacking speculative fixes.

  1. Record the platform, game build, CPU, GPU, and exact driver version.
  2. Name the mission, rally point, or launch stage where the crash occurs.
  3. Note whether the same point reproduces after a clean restart and file verification.
  4. Use the official Halo Support issue form and attach only the files it requests.

Frequently asked questions

Is the Halo Campaign Evolved Keyes crash fixed?

Not for every affected setup. As checked August 15, 2026, Halo Support still lists the RTX 50-series Keyes crash on drivers 610.47, 610.62, and 610.74, with 610.88 as the documented workaround.

Why does Halo Campaign Evolved crash before the splash screen?

Halo Support identifies one specific cause on some Intel 13th- and 14th-generation processors and directs affected players to the latest BIOS from their system or motherboard manufacturer. Other startup crashes need separate diagnosis.

Should I update my GPU driver?

Only match the advice to the official issue. The current Keyes entry names RTX 50-series cards, three affected driver versions, and driver 610.88; it is not a universal fix for every crash.

Did the July 29 patch fix The Maw crashes?

The official patch notes say stability was improved for the FSR introduction-cinematic case on AMD drivers 26.6.2 and 26.6.4. That wording should not be expanded into a claim that every The Maw crash is fixed.

Where should I report an unlisted crash?

Use the Halo Support Game Issue Report Form and include the platform, game build, hardware, driver, crash point, and reproducibility details.