AMD Radeon Software Host Application Has Stopped Responding Fix

When This Error Shows Up

You're in the middle of a game — maybe Call of Duty Modern Warfare II, Fortnite, or Cyberpunk 2077 — and suddenly the screen freezes for a few seconds. Then it goes black for a moment, and a popup appears: "AMD Radeon Software Host Application Has Stopped Responding".

The game might crash to desktop, or it might recover and let you keep playing. But it keeps happening every 10-20 minutes. You've updated drivers, rolled them back, and even reinstalled Windows — but the error won't go away.

What's Actually Causing This

This error is not a driver corruption problem. It's a timeout issue. Windows has a built-in watchdog called TDR (Timeout Detection and Recovery) that monitors your graphics card. If the GPU takes longer than 2 seconds to respond to a command — usually because of a driver hang or a heavy frame spike — Windows kills the driver and restarts it.

The root cause is almost always one of three things:

1. Unstable GPU overclock — even factory overclocks can be too aggressive for your specific card.
2. Windows display driver timeout is too tight — the default 2-second limit is too short for modern games with shader compilation stutters.
3. Multiple overlays or MPO (Multiplane Overlay) conflicts — Discord, Xbox Game Bar, or even the Radeon overlay can trip up the driver.

The Fix That Actually Works

Skip reinstalling the driver. Skip DDU. The real fix is extending the TDR timeout and disabling Multiplane Overlay. Here's how to do it step by step.

Step 1: Disable Multiplane Overlay (MPO)

MPO lets Windows combine multiple layers (like the game and an overlay) on the same screen. On AMD GPUs, this causes driver hangs. Turning it off fixes a lot of these crashes.

1. Press Windows Key + R, type regedit, and hit Enter.
2. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm.
3. Right-click on the Dwm folder (or the empty space), choose New > DWORD (32-bit) Value.
4. Name it OverlayTestMode.
5. Double-click it and set the value to 00000005 (hexadecimal). The base should already say Hexadecimal. If not, change it.
6. Click OK and close Registry Editor.
7. Restart your computer.

After restart: MPO is disabled. You might notice a tiny performance hit in windowed mode, but games in fullscreen run the same. The crash should stop happening.

Step 2: Extend the TDR Timeout

If MPO didn't fix it, the TDR timeout is too short. Extending it gives the driver more time to recover from a stutter before Windows kills it.

1. Open Registry Editor again (Win + R, regedit).
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers.
3. Right-click on the GraphicsDrivers folder, choose New > DWORD (32-bit) Value.
4. Name it TdrDelay.
5. Double-click it and set the value to 8 (decimal). That's 8 seconds — enough for almost any stutter.
6. Click OK.
7. Create another DWORD named TdrDdiDelay and set it to 8 (decimal) as well.
8. Close Registry Editor and restart.

Step 3: Disable Overlays in Radeon Software

The Radeon overlay itself can cause this crash. Turn it off temporarily to test.

1. Open AMD Radeon Software (right-click on desktop, or find it in Start).
2. Click the gear icon (Settings) in the top right.
3. Go to the General tab.
4. Turn off In-Game Overlay.
5. Also turn off Fan Speed and Power Monitoring if they're on — these can trigger timeouts.
6. Close Radeon Software.

Test now: Launch the game that was crashing. If it works, the overlay was the culprit. You can re-enable it later one feature at a time to find the exact one that breaks.

Step 4: Disable Xbox Game Bar

Windows Game Bar's overlay conflicts with AMD drivers. Turn it off.

1. Press Win + I to open Settings.
2. Go to Gaming > Game Bar.
3. Toggle Game Bar off.
4. Go to Captures and turn off background recording if it's on.
5. Close Settings.

Still Crashing? Check These

• GPU overclock: If you overclocked your card (even a factory "OC" model), reduce the core clock by 50 MHz using MSI Afterburner or AMD Adrenalin's tuning tab. Test the game for 30 minutes.
• RAM instability: Run sfc /scannow in Command Prompt as admin, then test RAM with Windows Memory Diagnostic (search for it in Start). Corrupt RAM causes driver timeouts.
• Run DDU in Safe Mode: Download Display Driver Uninstaller. Boot into Safe Mode (hold Shift while clicking Restart), run DDU, select "AMD" and "Clean and restart". Then install the latest driver fresh from AMD's site. This removes any leftover junk from past installations.
• Event Viewer: Press Win + X and choose Event Viewer. Go to Windows Logs > System. Look for Display driver amdkmdap stopped responding entries. That confirms TDR is the issue.

If all else fails, try an older driver — version 23.11.1 or 22.5.1 are known stable releases for many RX 6000 and RX 7000 series cards. Newer isn't always better with AMD drivers.