Current Crash Status
As of August 21, 2026, the development team says it is working with AMD on client crashes affecting some AMD GPU players. That investigation is separate from a specific server crash involving North Vietnamese tunnels that was fixed in Patch 1.2.
This distinction matters: Patch 1.2 did not claim to fix every client or server crash. The official AMD steps below are temporary troubleshooting options, not a guaranteed permanent solution.
Identify the Problem Branch
Before changing settings, record the platform, GPU, driver version, game build, crash timing, and whether the symptom affects only the local client or the entire server.
| Symptom branch | Relevant current information |
|---|---|
| AMD GPU client crash | Still under investigation; official temporary steps are available |
| Server crash during overlapping tunnel events | Specific path fixed in Patch 1.2 |
| Non-AMD client crash | No equivalent official GPU-specific fix in the local source set |
| Connection drop without a client crash | Treat separately from a rendering or application crash |
Do not apply every suggested change at once. A single-variable sequence makes it possible to identify which change affected the symptom and to reverse ineffective changes.
The Patch 1.2 Tunnel Fix
Official updates describe a server failure that could occur when multiple events happened while players were traversing North Vietnamese tunnels. Patch 1.2 was released on all platforms and includes a fix for that specific path.
The fix does not establish that all tunnel issues, all server crashes, or all client crashes were resolved. If a similar failure occurs after Patch 1.2, record the current build and the exact sequence instead of assuming it is the same cause.
Official AMD Temporary Steps
Test the official options one at a time and reverse an option before trying its alternative.
Test the DirectX 12 launch parameters
Set the Steam launch options to:
-dx12 -USEALLAVAILABLECORES -malloc=system
Run the same scenario and record whether the crash frequency changes. If it does not help, remove the complete parameter string before testing DirectX 11.
Test the DirectX 11 launch parameters
Use the alternative official string:
-dx11 -USEALLAVAILABLECORES -malloc=system
Do not combine -dx11 and -dx12. Remove the string if it has no benefit or makes performance worse.
Test High graphics quality
The official temporary guidance includes setting graphics quality to High. This is a troubleshooting variable for the AMD crash investigation, not a general performance recommendation. Save the original settings and restore them if the change has no effect.
Disable the AMD Adrenalin in-game overlay
Turn off the in-game overlay, repeat the same crash scenario, and re-enable it if there is no improvement. This step applies to AMD Software: Adrenalin Edition environments.
Reversible Third-Party Steps
If the official AMD sequence does not apply or does not help, one direct troubleshooting video recommends verifying Steam files, performing a clean GPU-driver installation, and returning GPU overclock or undervolt settings to defaults.
These are third-party suggestions, not game-specific guarantees. Record the existing driver and tuning state before changing it. A clean driver installation is more disruptive than verifying files, so preserve rollback information and avoid changing several variables in the same test.
Advice to use a wired connection can help diagnose network instability, but it should not be presented as a primary fix for an application crash.
Record and Restore Results
Use a small test log:
| Change | Test scenario | Repetitions | Result | Rollback |
|---|---|---|---|---|
| DX12 parameters | Same map and crash timing | 3 | Better, unchanged, or worse | Remove full string |
| DX11 parameters | Same map and crash timing | 3 | Better, unchanged, or worse | Remove full string |
| High quality | Same scenario | 3 | Better, unchanged, or worse | Restore saved preset |
| AMD overlay off | Same scenario | 3 | Better, unchanged, or worse | Re-enable overlay |
Avoid promising a fix from one successful launch. A repeated result under the same conditions is stronger evidence.
Updates That Are Not Current Fixes
The official Community Update says FSR 4.1 is targeted for Update 1.5. That is a future graphics plan, not a present crash fix, and its timing remains subject to change.
Frequently Asked Questions
Did Patch 1.2 fix every crash?
No. It specifically confirms a fix for a server crash path involving simultaneous tunnel events. The AMD client issue remained under investigation on August 21, 2026.
Should AMD players use DX11 or DX12?
The official guidance provides them as alternatives. Test one complete parameter set at a time and remove it before trying the other.
Is setting graphics quality to High a performance recommendation?
No. It is an official temporary troubleshooting step for the AMD crash investigation.
Is FSR 4.1 the current crash fix?
No. It is described as a target for Update 1.5, not a current remedy.