Helldivers 2 Crashing on PC: Checks After Updates

Choose the branch that matches your crash

This guide covers Windows PC through Steam. The original official support material and community reports were reviewed on September 14, 2026; the added file-validation, Error 114 and Steam review sources were read on September 15. We have not reproduced the crashes in a running client.

If Windows blue-screens or the whole PC restarts, stop repeated launch attempts and preserve the Windows error. That needs a separate system-support investigation.

Check the patch before copying an old workaround

The official announcements list fullscreen-terminal and superwide-window crash fixes in 7.0.1, and a Dynamic Resolution Scaling crash fix in 7.0.2 on August 25. They do not claim that every startup or mission crash is fixed.

The August 12 community reports predate those fixes. A September 5 report describes later crashes, but does not establish the same cause. Record the version shown by your client; a Windows executable version is not automatically the public patch number.

Repeated file verification: read the count before repeating it

A September 10 Steam review we read in full says a player with about 70 hours could no longer boot the game. It supplies no error code, hardware, build or cause, so use your own visible result to choose the next branch.

1. Use Complete one installation check below as this guide’s single verification pass. Record the exact result and number of files that fail, then test one launch to the same point. If you already did that check, use its recorded result instead of verifying again.
2. If only a few files fail again, Arrowhead says some authentication files are generated and sent to its backend on every launch, so that small recurring count can be normal. It does not prove a broken installation, and a completed verification does not prove the crash is resolved.
3. If 10 or more files continue to fail, use Arrowhead’s repeated-validation guidance for its further support recommendations and include the count in your report.
4. If the launcher shows exactly Error 114, use the dedicated official Error 114 guide. That branch is not for a generic GPU crash, and the September review did not report this code.

Do not turn this into an endless verify-and-reinstall loop. Do not delete the whole AppData folder or disable security tools just to force a different result.

Complete one installation check

1. Close the game. Finish pending HELLDIVERS 2 Steam downloads and any restart already requested by Windows.
2. In the Steam Library, right-click HELLDIVERS 2 → Properties → Installed Files → Verify integrity of game files. Wait for verification to finish.
3. Retry the same failure point once before changing settings.
4. If graphics problems accompany the crash, compare your hardware with the requirements and check the GPU or laptop manufacturer’s supported driver. Record the installed and replacement versions.

File verification and driver checks come from Arrowhead’s technical guide. They are diagnostics, not a guarantee that installation files caused the crash.

Optional: test the settings file with a way back

Arrowhead’s general guide suggests a broader AppData reset. The following is a narrower, reversible editorial adaptation: isolate the documented settings file only. It has not been tested by us as a HELLDIVERS 2 repair.

1. Photograph accessible graphics and control settings, then close the game and Steam.
2. Press Windows + R, enter %APPDATA%\Arrowhead\Helldivers2, and locate exactly user_settings.config. Enable filename extensions in File Explorer if needed. If the file is absent, skip this test.
3. Copy that file to a backup folder you can find again. Rename the original to user_settings.config.before-test; if that name exists, use a different backup name. Leave saves and all other folders untouched.
4. Start Steam and the game. If a fresh settings file appears, retry the same crash stage using the new defaults. Do not change several settings during this comparison.
5. To undo: close the game and Steam, rename any newly generated user_settings.config to a separate backup name, then rename your original back to user_settings.config. If the game cannot regenerate settings or behavior worsens, restore immediately.

This may reset local preferences during the test. It is not an instruction to clear your entire Arrowhead folder or delete progress.

If the ship works but a mission crashes

Keep the same settings and record whether hosting and joining fail differently. Preserve the mission name, elapsed time and any crash-report reference. A failure limited to one interaction is more useful to support than “crashes randomly.”

If you added launch arguments or optional recording overlays, save their original configuration and test removing one addition at a time. Restore anything that makes no difference; keep security and anti-cheat services enabled.

When to stop and send the evidence

After these checks, use Arrowhead support with your CPU/GPU/RAM, Windows and driver versions, visible game version, exact error, failure stage, timestamp/time zone and each test result. Review attachments for personal details before sending; never include passwords or session tokens.

The known-issues list is explicitly incomplete. An unlisted crash is not proof that your PC is responsible, and one successful launch is not proof of lasting recovery.