TechFixSignal
Windows 11

Windows 11 Games Crash With an RGB Driver

How to identify and work around game freezes, silent closes, access-violation errors, or restarts linked to inpoutx64 after Windows 11 KB5121003.

Last checked
Aug 26, 2026
Applies to
Windows, Desktop
Fix status
Verified
Fastest useful check

Quick answer

Microsoft is investigating game hangs, silent closes, EXCEPTION_ACCESS_VIOLATION errors, and unexpected restarts on some Windows 11 24H2 and 25H2 PCs after KB5121003. The documented pattern involves an inpoutx64-like driver installed by some RGB devices or utilities. Confirm the update, symptom, and driver first; then back up the relevant registry key and use Microsoft's temporary registry workaround if they match.

On this page

What we're seeing

  • Microsoft lists Windows 11 versions 24H2 and 25H2 as affected and traces reports to KB5121003 or later updates.
  • The documented symptoms include a game becoming unresponsive, closing without notice, showing EXCEPTION_ACCESS_VIOLATION, or restarting the PC.
  • Microsoft says peripherals or internal components with RGB lighting may install drivers or components with names similar to inpoutx64.
  • A crash without the affected update or driver is not enough to attribute the problem to this known issue.

Start here

Try these first

Fix 1

Confirm that your PC matches the known issue

Verified

The registry workaround is relevant only when the update, symptom, and inpoutx64 driver pattern match Microsoft's report.

  1. Open Settings, select Windows Update, then Update history, and check for KB5121003 or a later update.
  2. Note whether the game hangs, closes silently, shows EXCEPTION_ACCESS_VIOLATION, or restarts the PC.
  3. Open Registry Editor and check whether HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64 exists, but do not change it yet.

Applies to Windows, Desktop

Fix 2

Check for an update to the RGB utility

Possible Workaround

The affected driver can be installed by software that controls an RGB peripheral or internal component. A vendor update may remove the need for a registry change, but Microsoft does not identify every affected utility.

  1. Identify the trusted utility used to control RGB lighting on the PC.
  2. Check the hardware vendor's official support page or the utility's built-in updater for a current version.
  3. Restart Windows after an update and test the same game again.

Applies to Windows, Desktop

Fix 3

Temporarily disable inpoutx64 in the registry

Verified

Microsoft documents setting the inpoutx64 service Start value to 4 as a temporary prevention measure. This can disable RGB features or their control software.

  1. In Registry Editor, select HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64 and use File, Export to back up that key.
  2. Open the Start value, record its existing value, change Value data to 4, and close Registry Editor.
  3. Restart the PC and test the affected game.
  4. If RGB control stops working and you need it back, import the backup or restore the previous Start value, then restart.

Applies to Windows, Desktop

Fix 4

Report crashes that do not match

Verified

Microsoft asks affected users to submit Feedback Hub reports while it investigates, and a different symptom may have a separate cause.

  1. Press Windows key and F to open Feedback Hub.
  2. Include the game name, Windows version and build, update history, exact error, and whether inpoutx64 exists.
  3. Do not apply the registry workaround when the driver key is absent; continue with the game's official crash guidance instead.

Applies to Windows, Desktop

Confirm that this is the same Windows 11 problem

Microsoft is investigating a specific compatibility pattern after the August 11, 2026 Windows updates. On affected Windows 11 24H2 and 25H2 PCs, launching certain games can make the game unresponsive, close it without a message, show `EXCEPTION_ACCESS_VIOLATION`, or restart the computer.

The originating update is KB5121003, although Microsoft says later updates can also be involved. Reports named ARC Raiders, MARVEL Tōkon: Fighting Souls, and THE FINALS. That list describes confirmed reports, not every game that can be affected.

The other important clue is an `inpoutx64`-like driver. Microsoft says some peripherals or internal components with RGB lighting install these drivers or related code. A game crash by itself does not prove that this known issue is the cause.

Before changing anything, check all three points:

  • KB5121003 or a later update appears in Settings > Windows Update > Update history.
  • The symptom resembles the hang, silent close, access-violation error, or restart Microsoft describes.
  • The `HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\inpoutx64` registry key exists.

If the key does not exist, do not create it. Use the game's official crash troubleshooting and check graphics, anti-cheat, overlay, and game-file guidance instead.

Try the least disruptive option first

Identify the software that controls RGB lighting for your keyboard, mouse, motherboard, memory, or another component. Check the hardware maker's official support page or the utility's own updater for a current version, then restart Windows and test again.

Microsoft has not published a complete list of affected devices or utilities. Do not remove an unrelated driver based only on a similar filename, and avoid third-party driver-download sites.

Use Microsoft's temporary registry workaround

Microsoft's current workaround disables the `inpoutx64` driver by setting its registry service Start value to `4`. This is reversible, but it can stop RGB features or the software used to control them.

Back up the key before editing it:

1. Open Start, type `regedit`, and open Registry Editor. 2. Go to `HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\inpoutx64`. 3. Select the `inpoutx64` key, then choose File > Export and save the backup somewhere you can find it. 4. On the right, open `Start` and record its existing value. 5. Set Value data to `4`, close Registry Editor, and restart the PC.

Launch the same game and repeat the action that previously caused the crash. If it now runs normally, leave the driver disabled while Microsoft and the relevant vendor work on a permanent resolution.

If RGB controls stop working and that tradeoff is not acceptable, restore the exported key or put the Start value back to the number you recorded, then restart. The game problem may return when the driver is enabled again.

Avoid deleting the driver unless its vendor directs you

Some independent reports describe stopping the service, deleting it, and removing the driver file. Microsoft's published workaround is narrower: disable the service through the registry. Prefer that reversible official method.

Do not uninstall KB5121003 as the first response. It is a security update, and removing it also removes its protections. Microsoft currently recommends the temporary driver workaround while the investigation continues.

Verify and report the result

After restarting, test the same game for long enough to reproduce the former symptom. Also open the RGB control utility and check the lighting features you use.

Submit a Feedback Hub report whether the workaround succeeds or fails. Press Windows key and F, then include the game, Windows version and build, installed update, exact error, and whether the `inpoutx64` key was present. This helps distinguish Microsoft's known issue from unrelated game crashes.

The issue was still marked Investigating when checked on August 26, 2026. Revisit Microsoft's Windows release-health page before making further changes because the workaround or status may change.

Device notes

Windows
Microsoft currently lists Windows 11 versions 24H2 and 25H2 as affected; Windows Server is not listed.
Desktop
The driver may come from an RGB peripheral or an internal RGB component, so laptops and desktops can both require a device-specific check.

Official information

Microsoft opened this known issue on August 19, 2026 and last updated it on August 21. It remains under investigation, with a temporary registry workaround rather than a final fix.

Sources

Keep troubleshooting

Related problems