Helldivers 2 Crashing: A Step-by-Step Diagnostic

Step 1 — Identify the pattern

Before changing anything, note when it crashes. That single observation eliminates most of the possibilities.

• Crash on launch or during the first mission: usually driver, shader compilation, or overlay software.
• Crash at extraction or on mission end: usually a connection or session handoff problem rather than a rendering one.
• Crash after 20–40 minutes: usually heat, power, or a memory leak triggered by long sessions.
• Crash only in specific missions or with specific stratagems: usually a corrupted local file.

Step 2 — Remove the usual suspects

Verify the game files. On Steam this is a two-minute check that repairs corrupted data, and it fixes a real share of “only crashes in one mission” cases. Update the GPU driver, cleanly. A clean install is more reliable than an update over an old driver, especially if you have changed GPU generations. Disable overlays. Discord, Steam, and recording software all hook into the renderer, and each one is a crash candidate. Turn them all off, confirm stability, then re-enable one at a time.

Step 3 — Reduce uncertainty

Cap the frame rate. An uncapped frame rate on a heavy menu screen is a classic crash cause, and capping costs nothing. Lower one setting at a time. Change one thing, play a mission, observe. Changing five settings at once tells you nothing. Clear the shader cache. Recompiling shaders is slow but it removes a whole category of stutter-crash behaviour.

Step 4 — Check the machine, not the game

Long-session crashes are frequently thermal or power-related. Clean the cooler, check that the power supply is not being asked for more than it delivers, and try a session with the case open. If the crash time moves, the problem is hardware.

On console

A PS5 that crashes repeatedly benefits from a database rebuild, and from checking whether the game is installed on an external drive — an unreliable external drive produces exactly the “crashes at random” pattern.

If it is still crashing

Record the crash time and mission, and search the error code rather than the symptom. If the whole squad drops at once, the fault is the session handoff rather than your machine — the crossplay page covers mixed-platform squads. Symptom searches return speculation; error codes return reports from players with the same fault. The official support channel is the correct place for a persistent, reproducible fault, and the crossplay page is worth checking if the crash only happens in a mixed-platform squad.