Halo Campaign Evolved Crashing Fixes for PC
There is no single verified crash fix for Halo: Campaign Evolved, because the correct official branch depends on how the game is launched and which hardware and driver it runs on. Players should match every workaround to its saved date, driver version, and exact symptom instead of applying one step to every crash. Lead with the non-destructive checks and the official route before assuming a deeper fault, and treat live service status as To be confirmed because this reference is not a real-time dashboard.
Match the crash to the correct branch
The saved official Known Issues article splits PC crashes into several dated branches, and the right first move differs for each. Match the symptom below to its branch before changing drivers or settings, since the wrong branch wastes time and can introduce new risk. Every entry is tied to the 2026-08-06 snapshot of the article, so a branch that has since changed still appears as it was on that date. Use the sections that follow for the documented workaround.
| Symptom | Branch | First move | |---|---|---| | Freeze or sign-in failure after a direct .exe launch | Steam executable launch | Launch from the Steam library | | Crash on launch with an Intel 13th or 14th gen CPU | Intel microcode | Update BIOS from the system or motherboard maker | | Crash on Keyes with an RTX 50-series card | NVIDIA driver | Update the NVIDIA driver to 610.88 | | Crash on a high refresh rate display with VSync on | AMD VSync | Raise max FPS to at least one quarter of the refresh rate | | Crash when skipping The Maw intro cinematic with FSR | AMD FSR | Roll back the AMD driver, switch upscaler, or enable Frame Generation | | Visual freeze or cinematic glitches with XeSS Frame Generation | Intel XeSS | Use FSR or DLSS Frame Generation, or disable Frame Generation |
Steam executable launch
Launching the game directly from HaloCampaignEvolved.exe inside the Steam installation folder can start it without a live connection to Steam. The official article links that to sign-in failure, severe performance issues, or a freeze that needs Task Manager to close. The documented fix is simple and non-destructive: always launch Halo: Campaign Evolved from the Steam library inside the Steam app itself. Treat a freeze that begins right after a manual .exe launch as this branch first.
Intel 13th- and 14th-generation CPU crashes
Some Intel 13th and 14th generation processors crash on launch because of a pre-existing Intel microcode issue that can stop affected systems from starting certain applications. The official workaround is to install the latest BIOS update from the system or motherboard manufacturer, not from the game. That places the fix with the hardware vendor, so a game update alone will not resolve it. Players on these CPU generations who crash before reaching the menu should check for a BIOS update before trying anything else.
RTX 50-series crash on Keyes
In the visible 2026-08-06 article body, NVIDIA RTX 50 series graphics cards may crash on the mission Keyes when using driver versions 610.47, 610.62, and 610.74. The official fix is to update the NVIDIA driver to 610.88, which is the version Halo Support still recommended on that date. An earlier 2026-07-31 local capture also named The Maw and a 596.49 rollback, but those details were no longer visible on 2026-08-06, so current copy keeps the narrower fresh scope. Use the Keyes crash and the three listed driver versions as the matching signal for this branch.
AMD VSync and high-refresh crashes
AMD graphics cards may crash on high refresh rate displays when VSync is turned on and the maximum frame rate is set below one quarter of the refresh rate. The official workaround is to raise the maximum frame rate limit to at least one quarter of the refresh rate, or to disable VSync entirely. The article gives concrete thresholds that make the rule easy to apply without guessing.
| Display refresh rate | Minimum max FPS with VSync on | |---|---:| | 180 Hz | 45 FPS | | 240 Hz | 60 FPS | | 360 Hz | 90 FPS |
A crash that only happens on a high refresh rate monitor with VSync enabled fits this branch, so test the frame-rate cap before chasing a driver rollback. Disabling VSync removes the condition altogether, at the usual cost of possible screen tearing. Either choice is a settings-level fix, so it does not require a driver change.
The AMD FSR and The Maw conflict
AMD graphics cards using driver versions 26.6.2 or 26.6.4 may crash when skipping the introduction cinematic in the mission The Maw while FSR is turned on. The documented workarounds are to roll back to AMD driver 26.6.1, switch the upscaler to DLSS, XeSS, or TSR, or enable Frame Generation while using FSR. None of these is presented as a guaranteed fix, only as the official options for this branch.
Because the two official pages disagree, match the workaround to the driver version on the affected machine rather than assuming the patch settled it. A player on 26.6.2 or 26.6.4 who still sees the crash has a dated reason to roll back or switch upscaler. Re-check the live Known Issues and Release Notes pages before deciding the branch is closed.
XeSS Frame Generation freezes
Turning on XeSS Frame Generation while an in-game maximum frame rate limit is set can freeze the image, with only occasional frame updates. A separate branch notes that Frame Generation with XeSS upscaling can cause graphical issues and frame rate limits during cinematics. The official workaround for both is to use FSR or DLSS for Frame Generation instead of XeSS, to turn Frame Generation off while using XeSS, or to remove the in-game maximum frame rate limit. Players on Intel Arc hardware who see a frozen or glitching image should test these options before assuming a broader GPU fault.
When to submit a support ticket
Escalate once the documented workaround for the matching branch has been carried out and the crash still repeats on the same driver and build. File a report through the official Game Issue Report Form with the exact mission, driver version, and symptom attached, because that detail helps Halo Support reproduce the case. Live service status is To be confirmed here, so a current outage is best confirmed on the official Halo Support pages rather than inferred from a crash. Treat the dated snapshots above as a verified record, not a substitute for the current official guidance.
Official SourceHalo Support — Known Issues — accessed
Conflict SourceHalo Support — Release Notes — accessed
Official SourceHalo Support — July 29 Update — accessed