Cyberpunk 2077 AMD FSR crash is still a known issue in AMD Adrenalin 26.10.2, released on 30 October 2026. The problem concerns some Radeon RX 9000 systems using FSR Upscaling, Radeon Anti-Lag and in-game frame generation while video plays on a second display. AMD’s workaround is to disable in-game frame generation.
This is a specific Radeon graphics combination, not a warning that every FSR setting breaks Cyberpunk 2077. If you have a second monitor playing video while you game, AMD’s recommended change is quick to test. You can leave the rest of your graphics preset as it is.
What triggers the Cyberpunk 2077 AMD FSR crash?
AMD’s 26.10.2 release notes continue to list this Cyberpunk 2077 AMD FSR crash under Known Issues, not Fixed Issues. The documented combination is FSR Upscaling, AMD Radeon Anti-Lag, in-game frame generation and video playback on a secondary monitor on some RX 9000 graphics systems. You should not infer that FSR on its own is broken or that every RX 9000 owner will see a crash.
How to apply AMD’s Cyberpunk 2077 AMD FSR crash workaround
Open Cyberpunk 2077’s graphics settings and disable the game’s Frame Generation option. Keep your upscaling, Anti-Lag and resolution settings unchanged for the first test, then repeat the same scene with your second-monitor video running. AMD’s recommendation is to turn off in-game frame generation, not to uninstall the driver.
If the game runs without the crash, you’ve found a useful way to keep playing. If it still times out, note what happened and whether the GPU driver recovered. Changing several settings at once won’t tell you which one helped.
Why video playback on a second monitor matters
AMD’s report specifically mentions video playback on a second display. If you normally watch something on another monitor, try pausing the video and repeat the test. That comparison can help explain your setup to support, but AMD’s published workaround is still the in-game frame-generation toggle.
Adrenalin 26.10.2 does fix a different RX 9000 frame-generation problem involving switching applications or toggling overlays during games. That is separate from the Cyberpunk 2077 AMD FSR crash involving a second display, which remains in the Known Issues list. The overlay and app-switch fix does not establish that the Cyberpunk-specific case has been resolved.
Should FSR upscaling stay enabled?
Upscaling and frame generation do different jobs. Turning off frame generation may lower the displayed frame rate, but you can still test FSR Upscaling if the game offers it separately. The Cyberpunk 2077 AMD FSR crash advisory doesn’t tell players to switch off every AMD feature.
If you’re missing an FSR option entirely, see our Cyberpunk 2077 FSR settings guide. A missing menu option is not the same problem as a driver timeout while video plays on another screen.
Which Radeon cards can be affected?
AMD names some RX 9000 series products in the Cyberpunk 2077 AMD FSR crash warning. That is not a claim that all RX 9000 configurations fail, and it does not extend the same confirmed issue to RX 6000 or RX 7000 cards. Confirm your precise GPU in AMD Software. General Radeon problem-solving is covered in articles such as AMD Adrenalin 26.10.2, but the symptoms and official fixes for other games should not be copied into this one without supporting evidence.
Is there a permanent fix yet?
AMD does not list the Cyberpunk 2077 AMD FSR crash as fixed in Adrenalin 26.10.2. It remains an acknowledged known issue as of 30 October 2026, and AMD still advises disabling in-game frame generation. You can install the updated driver for its other fixes, but this release does not supply a confirmed resolution for the specific Cyberpunk combination.
AMD’s 26.10.2 release notes are the source for this known issue and workaround. Other Cyberpunk guides on The Click cover game updates, photo mode and display settings, but those changes don’t replace the Radeon frame-generation fix.
For the Cyberpunk 2077 AMD FSR crash, turn off in-game frame generation and retest while keeping a note of other graphics settings. You can compare the result with secondary-display video paused, but AMD’s published workaround is the frame-generation setting. If the crash continues, record the GPU, driver, game build and circumstances for a support report.
