Unofficial fan site · Not affiliated with Team17, Expression Games, or the Hell Let Loose franchise.
Officially confirmed

How to Fix AMD Crashes in Hell Let Loose: Vietnam

Follow the official Hell Let Loose: Vietnam AMD crash workaround, test DX12 and DX11 safely, disable overlays, and keep a clear rollback path.

Last verifiedLanguageEnglishScopeLaunch build
Direct answer

Team17 has acknowledged crashes on some AMD GPU systems. Its official temporary Steam launch-option lines are -dx12 -USEALLAVAILABLECORES -malloc=system or -dx11 -USEALLAVAILABLECORES -malloc=system. Copy one complete line exactly, test one renderer at a time, and remove the full line to return to the game default.

Safe troubleshooting order

Start with reversible official steps. Do not combine multiple registry, BIOS and file edits from community posts before verifying the primary-source workaround.

  • Update AMD Software: Adrenalin Edition and reboot.
  • Disable the AMD in-game overlay and close other capture overlays.
  • In Steam Launch Options, enter the full line: -dx12 -USEALLAVAILABLECORES -malloc=system
  • Launch the game and test the same map or repeatable scenario.
  • If DX12 still crashes, replace the entire line with: -dx11 -USEALLAVAILABLECORES -malloc=system
  • Delete the complete launch-option line to return to the default renderer.

Keep the launch field clean

Never run -dx12 and -dx11 together, and do not shorten the published command while describing it as the official workaround. These launch options are temporary diagnostics, not a permanent guarantee. If you joined the Crossplay Playtest, restore Video settings to defaults before comparing results because official notes also acknowledge settings persistence problems.

Record the result

For each attempt, record GPU model, Adrenalin version, exact launch argument, graphics preset, map, time to crash and whether an overlay was active. This produces a useful support report and prevents repeating the same failed combination.

When to stop

If both official renderer modes fail after a clean driver update, remove all launch arguments and check the latest hotfix notes. Avoid stacking unverified fixes that make rollback or support diagnosis harder.

Frequently asked questions

Should I use the DirectX 11 or DirectX 12 line?

Try the complete -dx12 -USEALLAVAILABLECORES -malloc=system line first as documented, then replace the entire line with -dx11 -USEALLAVAILABLECORES -malloc=system if crashes continue. Never use both renderer flags together.

How do I undo the workaround?

Delete the complete launch-option line from Steam Properties → General → Launch Options.

Sources and verification

Sources are linked for independent checking. Dynamic figures are snapshots, not permanent values.

  1. Official launch workaround
  2. Official launch known issues
  3. Official post-launch developer update