Controller Freezing Mid-Game
A controller that freezes mid-game — inputs stop registering while the controller stays powered and connected — has four common causes: DualSense audio-routing hang on PC, a stalled Windows HID driver, a specific-game controller-loop bug, or thermal throttling during long sessions. The button test isolates whether the controller is transmitting; if it is, the game is the culprit.
Diagnose before you fix
Confirm the symptom and measure its severity first. The test result tells you whether to clean, recalibrate, or replace — different severities call for different fixes.
Button Test
The button test runs in the browser independently of any game. If your controller freezes in a specific game but the button test still registers inputs during the same session, the controller and its OS-level connection are healthy — the freeze is inside that game or its middleware, not the controller. If the button test also freezes at the same moment, the OS-level connection has stalled and the fix is at the driver or wireless layer.
Run the button testConnection Stability
For wireless controllers, run the stability test in a second browser tab during a long play session. Packet drops or extended silences visible in the test around the moment of the freeze pin the cause to the wireless link. Steady packets during the freeze mean the wireless is fine and the game or driver is stalling.
Run the connection stability- A Chrome or Edge browser (for parallel button-test verification)
- A USB data cable (to eliminate wireless as a variable)
- Task Manager access on Windows
Step by step
Work through these in order. After the last step, run the diagnostic again to confirm the fix held.
- 01
Isolate: is the controller frozen, or the game?
This is the whole diagnosis. When the freeze happens, alt-tab (or Windows key) to a browser and open the button test. If your buttons register in the test, the controller and OS-level connection are working — the game itself has stopped reading input. If the button test also shows no response, the OS-level input pipeline has stalled and the fix is at the driver or wireless layer, not the game.
- 02
For DualSense on PC: fix audio routing
A documented bug: on Windows, DualSense audio can lock up the entire controller input pipeline. Games crash or freeze while Steam becomes unresponsive after 30-60 minutes. The fix is to set Windows default output back to your real speakers (not 'Wireless Controller'), disable the DualSense's speaker/microphone audio devices in Sound Settings, and consider DS4Windows to present the DualSense as an Xbox pad — which bypasses the audio subsystem entirely.
- 03
Reset the Windows HID pipeline
If the button test freezes alongside the game, Windows' HID stack has stalled. Open Device Manager → Human Interface Devices → find your controller → right-click → Disable device → wait 5 seconds → Enable device. This re-initializes the HID connection without unpairing or restarting. If this works but the freeze returns later, disable USB Selective Suspend in Power Options — Windows may be putting the USB device to sleep mid-session.
- 04
Switch to wired to eliminate wireless variables
Wireless freezes have more variables (signal, interference, battery, driver) than wired. Connect via USB data cable and play the same game for the same duration. If wired doesn't freeze but Bluetooth did, the wireless path is the culprit — bad Bluetooth driver, low battery cutting transmission, or interference. If wired also freezes, wireless is off the suspect list and the fix is game-side or driver-side.
- 05
Check game-specific known issues
Some games ship with controller-loop bugs that hang input after specific triggers — audio-device changes, alt-tab, cutscene transitions, network hiccups. Search '{game name} controller freeze' on the game's Steam Community forum and reddit — known issues usually have community-documented workarounds (specific settings, launch parameters, or wait-for-patch status). Don't waste time on system-level fixes if the game has a documented input bug the developer hasn't patched yet.
- 06
Rule out thermal throttling for wireless controllers
Some wireless controllers throttle transmit power when their internal temperature rises during long sessions — presenting as freezing after 45+ minutes of play, resolving after a break. This affects tightly-packaged controllers more than well-ventilated ones. If freezes correlate with session length, verify by playing the same game wired for the same duration — if wired doesn't freeze, thermal or battery-related wireless throttling is likely and a break-and-cool between sessions is the workaround.
- 07
Update firmware, reinstall Steam Input, restart clean
Last-resort software refresh: update your controller firmware through the vendor updater, uninstall/reinstall DS4Windows or Steam Input configuration (Settings → Controller → Reset), and cold-boot the PC (full power off, not restart). Corrupted middleware state can persist across ordinary reboots. If none of this resolves the freeze, the fault is either a genuine driver bug (worth submitting to the vendor) or hardware (controller returned during warranty).
Where to go next
Persistent symptoms usually mean hardware wear that cleaning and recalibration can't reach. These resources cover repair, replacement, and warranty paths.
Other tests for the same controller
A symptom rarely arrives alone. Worn sticks often coincide with deadzone creep and reduced circularity — run the related diagnostics while the controller is already in your hands.
Variants of this symptom
The same underlying issue presents differently across controllers. These device-specific guides cover the variations.
connection questions
The most common cause on PC is that the OS-level input pipeline stalls while the wireless or USB connection stays alive. This happens most often with the DualSense on Windows (documented audio-routing bug), during aggressive USB Selective Suspend behavior, or when a specific game has a controller-loop bug. The button test in a browser confirms whether the controller is still transmitting; if it is, the game is where the freeze lives, not the controller.
Often yes on PC. A known bug: DualSense audio delivery on Windows can hang the input pipeline after 30-60 minutes of play, particularly if Windows tries to route audio through the controller as a speaker. Set your default audio output back to your real speakers, disable the DualSense audio devices in Sound settings, or use DS4Windows to bypass the audio subsystem entirely — which resolves this specific freeze pattern.
Three possibilities. USB Selective Suspend puts idle ports to sleep after several minutes of low activity — disable it in Power Options. Thermal throttling in wireless controllers reduces transmit power after prolonged use — verify by playing wired for the same duration. Some games have documented memory leaks in their controller-input loop that manifest as freezes after 45+ minutes — check the game's community forum for known issues.
The button test tells you in 10 seconds. When the freeze happens, alt-tab to the browser and check the button test. If it registers your inputs, the controller and OS are fine — the game has stalled. If the button test also shows no input, the OS-level pipeline froze and it's a driver, wireless, or middleware issue. Different diagnosis paths, different fixes.
Yes, occasionally. Steam Input's overlay and controller polling can conflict with a game's own input handling — particularly if both are trying to manage the same controller. If freezes happen only in Steam games and stop when Steam is closed, adjust which controller types Steam Input handles (Settings → Controller) or set a per-game override to disable Steam Input for the affected title.
Usually resolves it in the moment, doesn't prevent recurrence. Restart clears cached HID state and closes hung processes, but if the underlying cause is a driver bug, a game issue, or a Windows setting, it comes back. Fix the root cause (audio routing, Selective Suspend, game update) rather than treating restart as the solution.
Sometimes. Outdated controller firmware can carry known bugs the manufacturer has patched. Update your controller firmware via the vendor updater (PS5 accessories settings, Xbox Accessories app, 8BitDo Ultimate Software, GuliKit, Flydigi apps). If the release notes mention input-loop or connection improvements, install and retest. This won't cure a game-side bug, but it rules out one of the free fixes.
Still seeing the issue?
Re-run the diagnostic to confirm whether the fix held or whether escalation is needed.
Run the test again