Pick the symptom before a fix
| Symptom | First safe action | Do not assume |
|---|---|---|
| Startup or launcher error | Save the exact message and storefront, then use that storefront’s official file-verification path. Patch 1.2 lists a fix for one boot crash caused by rapidly clicking the left mouse button. | Do not treat that named fix as proof that every startup error is resolved. |
| D3D or device lost message | Record the full message, GPU, driver version and whether it happens at startup or in a match. Verify files before stacking graphics changes. | A D3D message alone does not prove the AMD launch workaround applies. |
| In-match crash on an AMD GPU | Check the current official status, then test one item from the dated AMD GPU branch below. | Hotfix 1 improved stability; it did not promise every machine was resolved. |
| Server crash or disconnect | Check whether the server disappeared and whether other players were removed. Patch 1.2 fixes one NVA Tunnel server-crash case. | A server-side failure is not the same as a local client crash, and one named fix does not cover every disconnect. |
Current official status
Patch 1.2 has been live on all platforms since 21 August. Its changelog says more than 500 fixes and improvements shipped, including a client crash during boot after rapid left-mouse clicks and a server crash involving NVA Tunnels. The changelog does not promise that every crash is resolved.
Hotfix 1 remains the latest cited update that specifically names further AMD GPU stability improvements. Patch 1.2 does not add an AMD-specific claim, so the older AMD launch options below remain a dated fallback rather than the default first step.
Startup or launcher: preserve the error first
Take a screenshot or copy the complete message. Record the storefront, operating system, GPU and whether the game reached its own window. On Steam, the official low-risk first check is Verify integrity of game files. On another storefront, use that storefront’s own current verification instructions rather than copying the Steam menu path.
After verification, retry once without adding new launch flags. If the exact launcher or entitlement error remains, report that message; renderer changes are not a substitute for a launcher diagnosis.
D3D or device lost: keep the branch narrow
Record the full D3D/device-lost wording, GPU model, installed driver version and the crash point. Verify files, then repeat the same situation once. If the GPU is not AMD, stop before the AMD-only options below and report the evidence to the current support path.
AMD GPU branch
The following options come from the dated launch guidance for affected AMD systems. They remain a fallback, not a required post-Hotfix configuration.
Try one renderer option
In Steam, open the game’s properties and record any existing launch options before editing them. Start with one official variant—never both at once.
DirectX 12 variant
-dx12 -USEALLAVAILABLECORES -malloc=system
Launch the game and test the same situation that previously crashed. If it becomes less stable, remove the entire line before trying anything else.
DirectX 11 alternative
-dx11 -USEALLAVAILABLECORES -malloc=system
Use this only after removing the DirectX 12 line. Test again under the same conditions.
Try the accompanying AMD settings separately
The Important Launch Info post also suggests the High graphics preset and disabling the AMD Adrenalin overlay. Apply and test one change at a time so you can tell which change helped or hurt.
Undo every temporary change
- Remove the complete temporary Steam launch command.
- Restore the graphics preset used before the test.
- Re-enable the AMD Adrenalin overlay only if you want it back.
- Restart the game and confirm that the original configuration has returned.
If the crash continues
Report the platform/storefront, GPU, driver version, exact error, current game build, launch option tested and whether the crash occurred before the game window, in a menu, on a server or during a repeatable action. Recheck the Patch 1.2 changelog and official launch thread first because temporary launch guidance can be replaced by a later patch.