CONTROL Resonant PC Crashes, Low FPS and Audio Problems

For crashes, sudden FPS drops, crackling or delayed audio, controller reconnection problems and blocked quests.

Saved articles →
No account needed. Saved only in this browser.

The short answer

Remedy documents Radeon RX 7000/9000 performance problems and a restart workaround after changing ray-tracing quality. Check the current issue notice and AMD driver notes for your GPU. Audio problems start with the Windows output device and a controlled comparison of settings.

Open My Games →Keep this game’s fixes handy. No account. This browser only.

Key facts

Steam saves (default Steam installation)
C:\Program Files (x86)\Steam\userdata\<Steam ID>\3669870
Epic saves (account subfolder inside)
%LocalAppData%\Remedy\CONTROLResonant
Minimum GPU / RAM / storage
GTX 1070, RX 5600 XT or Arc A580; 16 GB RAM; 120 GB SSD; Windows 10/11.
Recommended GPU / RAM
RTX 3060 Ti, RX 6700 XT or Arc B580; 16 GB RAM.
Launch roadmap announcement
New Game++ was planned for October and photo mode for November. Check current announcements for availability.

Report an issue or a fix

Find your symptom

Start with your symptom. Skip steps that do not apply to your setup.

What you seeWhat to checkGo to
RX 7000/9000 performance problems or crashesCheck the documented AMD issue and driver status.Step 1
FPS drops after changing graphics settingsTry the ray-tracing restart workaround.Step 2
Crashes on any GPUCheck drivers and game files.Step 3
Audio crackles, cuts out or falls out of syncCompare Windows output and audio settings.Step 4
A reconnected controller does not respondCheck the Steam Input reconnection issue.Step 5
A barrier or unreachable enemy blocks progressUse the documented quest workaround.Step 6

Fixes, in order

Continue this issue

Private notes stay in this browser. Nothing is sent automatically. Back up important notes on My Page. PC settings are never changed by this site.

Step 1|Check the AMD driver notice for RX 7000/9000

Remedy’s issue notice describes an optional AMD driver remedy. That notice alone does not establish whether a newer driver is available today.

Time: About 10 minutes · Risk: low

  1. Open Task Manager → Performance → GPU and record the GPU model.
  2. For RX 7000/9000 hardware, check AMD’s official driver page and release notes for this game and your exact GPU.
  3. If the remedy is not available or does not apply, compare lower graphics settings, especially ray tracing.

An optional driver may not arrive through automatic updates. Avoid unofficial driver packages.

Results that did not fix the problem help the next reader too.

Step 2|Restart after changing ray-tracing quality

Remedy describes a substantial FPS drop after a ray-tracing quality change; its workaround is a restart with the setting saved.

Time: About 2 minutes · Risk: low

  1. Exit the game after changing ray-tracing quality.
  2. Relaunch and compare the same scene’s performance.

Results that did not fix the problem help the next reader too.

Step 3|Check GPU drivers and game files

For crashes across GPU models, inspect the installation before making broad system changes.

Time: About 15 minutes · Risk: low

  1. Use NVIDIA App or AMD Software: Adrenalin Edition to obtain the current driver appropriate for your hardware, then restart the PC.
  2. Steam: right-click the game in Library → Properties → Installed Files → Verify integrity of game files.
  3. Epic Games Launcher: open the game’s … menu in Library → Manage → Verify.
  4. Confirm the game is installed on an SSD, as required.

Results that did not fix the problem help the next reader too.

Step 4|Compare Windows audio settings

Follow Remedy’s audio checks one change at a time. Similar trouble in other applications points toward the device or Windows audio path.

Time: About 15 minutes · Risk: low

  1. Exit the game and compare audio in another application, such as a video player.
  2. If comfortable and appropriate for your accessibility needs, compare the in-game baseline: Dynamic Range at its default, Mono Audio and Hyperacusis Filter off, and Bass/Treble at 0. Keep volume comfortable and restore any setting you need.
  3. The game has no output-device selector: choose the intended device in Windows Settings → System → Sound.
  4. Temporarily turn off Audio enhancements and Spatial sound for that output; record their previous state.
  5. Compare a format supported by the device, for example 24-bit, 48000 Hz if offered. Record and restore the original if it does not help.
  6. Close virtual audio mixers, equalizers and recording/streaming applications, then retest before reopening them.

Results that did not fix the problem help the next reader too.

Step 5|Restart with the controller connected

Remedy lists reconnection problems after a controller disconnects while using Steam Input.

Time: About 2 minutes · Risk: low

  1. Reconnect the controller, then restart the game.
  2. Avoid swapping controllers during a session. The original PCGamingWiki review also noted that a swap may require a restart.

Results that did not fix the problem help the next reader too.

Step 6|Use the matching quest workaround

These quest names and workarounds come from Remedy’s known-issue list. Reloading a checkpoint can discard progress since that checkpoint.

Time: About 3 minutes · Risk: low

  1. Evacuation Protocols: if the Hiss barrier remains after the floor-12 battle, reload the last checkpoint.
  2. The End: if an enemy spawns out of reach, reload the last checkpoint.
  3. If an outfit is removed after using a Fast Travel Door, select the outfit again.

Results that did not fix the problem help the next reader too.

Avoid

  • Do not substitute unofficial drivers or speculative configuration edits for a documented AMD remedy.
  • Do not edit or delete saves. Close the game and launcher before copying the complete save folder; use your actual Steam installation location and account folder.
  • Never give support your Steam/Epic password or authentication codes.

Important cautions

  • The known-issue page describes fixes planned for a subsequent update. A plan is not proof that a fix has shipped or that every symptom is resolved.
  • For unresolved issues, use the chat on the official remedy.helpshift.com help site.

FAQ

Why are early enemies so tough?

The original launch review records hotfix 1.3.3 reducing many enemies’ health and stagger thresholds and increasing Dylan’s maximum damage. Gameplay options also include assist settings for enemy aggression and damage taken. Check current patch notes before assuming the launch build is current.

Why are some HDR areas oversaturated?

Remedy lists oversaturation in some HDR scenes as a known issue with a planned fix. Check the latest issue/update notice rather than assuming it has already been resolved.

Is photo mode available?

The launch announcement planned photo mode for November and New Game++ for October. Those dates are the historical roadmap, not a newly verified statement of current availability.

Sources

English adaptation preserving the original six steps. Remedy known-issue, audio and save documentation and the Steam store were rechecked. Launch patch/roadmap and PCGamingWiki details retain the original September 28 review context, not a fresh in-game test.

Remedy: known issues and updatesRemedy: audio troubleshootingRemedy: PC save locationsSteam official news: launch hotfix and roadmapSteam: CONTROL Resonant requirementsPCGamingWiki: Control ResonantCONTROL Resonant (Japanese)Japanese version of this page