Helldivers 2 Low FPS and Stuttering: PC Checks

Name the symptom before changing settings

This guide covers Steam on Windows when the game stays open but feels slow or uneven. We reviewed current official support and one detailed community case on September 16, 2026; we did not benchmark the game.

Do not compare the ship with a busy high-difficulty mission as if they were the same load. “All Low is still slow” is useful evidence, but does not by itself prove the CPU, GPU, patch or network is responsible.

Capture one repeatable baseline

Finish pending game updates, then record the visible game version, Windows version, CPU, GPU, RAM, driver version, display resolution and refresh rate. Write down the render scale or upscaler, frame generation state, FPS limit, display mode and graphics preset. Do not copy another player’s settings without noting the hardware difference.

Choose a repeatable comparison: the same ship viewpoint or the same early section of a mission. Record an FPS range and what the hitch looks like for 60–90 seconds. If you can view frame time with a tool you already trust, record it; do not install an unknown “optimizer” for this guide.

Save screenshots of current settings so every experiment has a way back. Change only one item per run. A result from a different planet, squad size or combat intensity is not a clean before/after comparison.

Run safe, reversible comparisons

The Arrowhead technical guide explicitly supports these four starting checks:

1. Compare the PC with the current minimum requirements.
2. Check the GPU or laptop manufacturer’s supported driver. Record both the old and replacement version; do not stack driver, game and firmware changes into one test.
3. If files may be incomplete after an update, verify them once through Steam Library → HELLDIVERS 2 → Properties → Installed Files → Verify integrity of game files, then repeat the baseline once.
4. Toggle Async Compute once, repeat the same scene, and restore it if frame time or stability does not improve. Arrowhead says it may help some systems depending on hardware, not all systems.

The following are our reversible diagnostic comparisons, not steps attributed to Arrowhead:

1. Confirm the monitor cable is connected to the intended graphics output and Windows reports the expected GPU.
2. Compare one lower graphics preset with your saved original while keeping resolution, limiter and scene unchanged. Then restore it. If the result barely moves, record that rather than randomly raising every setting.
3. If you already use a frame limit, compare one clearly documented limit method at a time. Restore the original method when it does not help.

Do not reset BIOS settings, overclock or undervolt hardware, disable security/anti-cheat, or add old launch parameters as part of this page. Those changes add risk and make the result harder to attribute.

Interpret the comparison without overclaiming

A large change from one graphics adjustment suggests a useful direction for that scene and hardware; it is not a universal “best setting.” A small or inconsistent change needs another same-scene run before you keep it. Total CPU usage alone cannot show whether one busy thread is limiting frame delivery, and low GPU usage alone does not prove a faulty graphics card.

The reviewed community thread involved a Ryzen 7 5700X, RX 7800 XT and 1080p Low. Replies disagreed about resolution, CPU limitation and settings. The original poster reported a small improvement after moving the limiter, but that individual percentage is not our benchmark and is not a promised result.

Arrowhead’s September 15 known-issues page says most performance problems are ongoing and not individually listed. An absent entry therefore does not prove your system is at fault. If performance changed immediately after a patch and controlled tests do not help, preserve the evidence and check newer official notes rather than repeating unsafe tweaks.

Stop testing and prepare a support report

Stop when results are unchanged, stability worsens, the PC overheats or the process begins crashing. Restore the saved settings. Send Arrowhead support the hardware and software versions, visible game version, exact scene, before/after table, one-variable changes and timestamps. Review screenshots and logs for personal information.

This page is a diagnostic comparison, not a benchmark. Its useful outcome may be “no tested setting produced a repeatable improvement,” which prevents more random changes and gives support a clearer case.