HELLDIVERS 2 runs through nProtect GameGuard. A startup loop often happens before the renderer has done anything, so graphics settings are not the first place to look.
Fixing GameGuard Crashes and Startup Loops
Verified field fixThe shortest safe order for this issue:
- Verify the game files and remove overlay or capture hooks from startup.
- Restart the PC after the anti-cheat update, then test a cold launch.
- Rename the local user settings file only if the client fails after the splash screen.
Read the point of failure
A failure before the Arrowhead logo points to anti-cheat or file integrity. A crash after the logo can involve local settings, a display hook, or the network connection. Note the last visible frame before changing anything.
$config = Join-Path $env:APPDATA "Arrowhead/Helldivers2"
if (Test-Path $config) {
Get-ChildItem $config -Recurse -File |
Sort-Object LastWriteTime -Descending |
Select-Object -First 8 FullName, Length
} Do not bypass the protected path
Disabling security software permanently is not a fix. Remove conflicting overlays, verify the game, and restart. If a tool requires injection to run, it does not belong in a crash test.
Field notes before you change the build
A crash report for HELLDIVERS 2 is only useful if it can be repeated. Record the last visible frame, the exact game build, the GPU driver, and whether the failure happens before or after the anti-cheat splash. “It crashed” is a category, not a reproduction.
If the client fails again after a clean launch, test a second save or a fresh profile before changing the Autodesk Stingray configuration. That separates a local game-state problem from a client, driver, or protected-launch problem.
- Do not delete the entire config, save, or game folder before making a backup.
- Do not reinstall Windows for a single-title startup failure.
- Do not stack launcher flags and driver rollbacks in the same test run.
Check it before you keep it
Cold boot and launch without any capture software
0 / 5 completeKeep the rollback boring
A known-good local profile and one current log are more valuable than another speculative repair pack. If the fix works, save the exact steps with the patch number.
The line to keep
A protected game needs a protected baseline. Keep the client clean and the evidence specific.
Did this fix work on Patch 01.003.300 — GameGuard and networking update?
One click. No account. Your vote is stored in this browser and de-duplicated per file.
Verified against 01.003.300 — GameGuard and networking update. Votes are local-only telemetry.
HELLDIVERS 2: bench questions
2 answersWhy does HELLDIVERS 2 close after the anti-cheat splash?
Can I play offline to test the crash?
Crash & Startup
This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.
HELLDIVERS 2: Best Build, Graphics Preset Matrix & Beginner Checklist
A spoiler-light progression and build plan for HELLDIVERS 2, plus Low, Competitive, and Ultra graphics matrices and the mechanics checklist for the first ten hours.
HELLDIVERS 2: CTD, DXGI_ERROR_DEVICE_HUNG & Black-Screen Launch Fixes
Stabilise HELLDIVERS 2 on PC: diagnose crash-to-desktop loops, DXGI device-hung resets, black-screen starts, and anti-cheat or DLL launch blocks on Autodesk Stingray.
HELLDIVERS 2: Shader Stutter, Frame Pacing & Autodesk Stingray Config Tuning
A measured stutter-hunting routine for HELLDIVERS 2: shader compilation warm-up, frame-pacing limits, upscaler presets, and the exact Autodesk Stingray settings file to edit.