Which problem you actually have
Three different failure modes get described as "the AMD crash", and they need different answers:
| Symptom | Likely cause | Where to start |
|---|---|---|
| Hard crash to desktop, often with a driver timeout | The acknowledged AMD issue, worst with path tracing on | Steps 1–2 below |
| FPS drops after changing a graphics preset mid-session | Stale shader cache / state not rebuilt | Steps 3–4 |
| Constant stutter with FSR + frame generation enabled | Overlapping upscaling and frame-gen | Step 5 |
If you get a false "out of video memory" message, treat that as the first category. That error is a known downstream report of an unstable GPU scheduling path rather than a genuine VRAM shortage, so buying a bigger card will not help.
What Remedy and AMD have said
Remedy's public position, posted on 25 September 2026, is that some players on AMD graphics cards are experiencing crashes and FPS drops, that AMD is developing a driver update intended to resolve it, and that it should arrive shortly. The statement did not carry a date.
That matters for how you read this page: the fix is upstream of the game. Patch 1.4 did include crash fixes across all platforms, plus performance work aimed at PC minimum and recommended specs, and it addressed HDR tearing and artefacts. But nothing in the patch notes claims to have resolved the AMD driver path specifically.
The workarounds, in order
1. Disable path tracing. Fastest possible test. The reports clustering on RX 7000 and RX 9000 series cards all have it enabled. If crashes stop, you have confirmed you are on this issue and can decide later whether the visuals are worth the instability.
2. Turn off Hardware-accelerated GPU scheduling (HAGS). The most-cited community workaround. Windows Settings, then System, Display, Graphics, then "Change default graphics settings". Reboot after toggling — it does not apply live. This is a Windows-wide change, so if you depend on HAGS for another title, note the state before you flip it.
3. Fully restart after changing in-game graphics settings. Users reporting this pattern describe severe stutter specifically after changing a preset while the game is running, with FSR super resolution and frame generation enabled. Exiting to desktop between changes avoids the state mismatch.
4. Clear the shader cache. Do this from AMD Software with a factory reset of the shader cache rather than deleting random folders. Expect a slow first session while shaders rebuild — that is normal and not a regression.
5. Stop stacking FSR with frame generation. Pick one. This combination is where the worst stutter reports sit, and DLSS users are describing a different, milder set of symptoms, which is the tell that the upscaler path is involved.
6. Install the latest Adrenalin driver and re-test. Once AMD ships the fix Remedy pointed at, re-enable path tracing one setting at a time so you know which one brings the crash back.
If none of that works
Then you are probably not on the AMD-driver issue, and the likelier candidates are:
- A degraded Intel 13th/14th-gen CPU causing decompression failures during shader compilation, which presents as a crash at a specific loading point rather than random mid-combat crashes
- An unrelated conflict from overlay software
Both are worth a separate pass. Say which one you are seeing in the community thread and we will write it up properly rather than guessing.
What we still do not know
- Whether the 1.4.1 hotfix changed anything for AMD users specifically — the notes cover the Park Resonant mould interaction and a Rush-while-Elevating bug only
- The AMD driver release date, because none was ever given
- Whether Xbox Series X/S, which uses AMD silicon, shares any of this. The only console-side report we found was an Xbox Series X audio dropout fixed in 1.4, which is a different bug
People also ask
- Is this a Control Resonant problem or an AMD problem?
- Both, effectively. Remedy publicly acknowledged that players on AMD graphics cards were seeing crashes and FPS drops and said AMD was preparing a driver update to address it. The 1.4 patch shipped general crash fixes for all platforms, but the AMD-specific behaviour was assigned to the driver, not the game.
- Do I need to reinstall Windows?
- No. Nothing in the official thread or the community reports points at an OS reinstall. Start with the GPU scheduling toggle and the shader cache, and only move to a clean driver reinstall if those do not help.
- Will disabling path tracing fix it?
- For many reports, yes — the worst behaviour clusters around path tracing being enabled on RX 7000 and RX 9000 series cards. Turning it off trades visual fidelity for stability and is the fastest test of whether you are hitting this issue at all.
Sources & version history
External claims on this page trace to the items below. Anything we could not confirm is written as a question, not a fact.