RGB Peripherals and inpoutx64.sys Crashing Windows 11: How to Fix
Our content follows trusted Editorial Standards - accurate & unbiased.
Summary:
Windows 11 is crashing games and triggering BSoDs since the August 11, 2026, KB5121003 update. The conflict is due to the inpoutx64.sys driver bundled with RGB software. To temporarily fix the issue, disable or remove the driver rather than uninstalling. No permanent fix is released yet.
Following Windows 11’s August 2026 update, some gamers reported that popular titles like ARC Raiders and The Finals were crashing unexpectedly. In more severe cases, the crashes even caused systems to restart and display a Black Screen of Death (BSoD). Embark, the studio behind the games, was quick to point to Microsoft, confirming that the latest Windows update had introduced a compatibility issue with a driver, ultimately triggering the crashes.
What’s Causing the Windows 11 BSoD and Game Crashes?
The issue appears to be a conflict between RGB software, the inpoutx64.sys driver, and the anti-cheat systems used by some online games. The problem surfaced after Microsoft released the KB5121003 update, but Microsoft says the update itself is not the cause. Instead, the issue affects systems with RGB-related drivers or code components with file names similar to inpoutx64. The official statement from Microsoft explains:
“This issue is not caused by Windows updates and is related to peripherals or internal device components which have RGB lighting features. Such devices may install drivers or code components with file names similar to inpoutx64.”
The inpoutx64.sys driver is used by RGB utilities to communicate with hardware at a low level. Because it operates in kernel mode, it has deeper access to Windows than a regular app. This can create a conflict when you launch a game with kernel-level anti-cheat software. The anti-cheat system may block the driver, and if the RGB software then tries to access it, the resulting conflict can cause an EXCEPTION_ACCESS_VIOLATION error, game crash, or, in severe cases, a BSoD.
You also don’t necessarily need a dedicated RGB device to be affected. Many motherboards come with built-in RGB lighting and may install similar drivers automatically. Microsoft is still investigating the relationship between these RGB components and the affected games.
Which Games and Systems Are Affected?
So far, three games have been confirmed to experience the issue. All are online multiplayer titles that use anti-cheat software with a close eye on kernel-level activity: Arc Raiders, Marvel Tokon (Fighting Souls), and The Finals.
However, this may not be the complete list. The problem is still relatively new, so other games could also be affected as more users encounter the issue. In terms of system scope, the problem currently appears limited to Windows 11 24H2 and 25H2 running OS Build 26100.9168 or later, and affects client editions only. Windows Server systems do not appear to be impacted.
Symptoms to Watch For
If your PC is affected by this issue, you may notice one or more of the following symptoms:
- The game hangs shortly after you launch it
- It closes without any warning
- Windows throws an EXCEPTION_ACCESS_VIOLATION error
- In the worst case, the whole system goes down in a BSoD
How to Fix the inpoutx64 Driver Crash?
If Windows 11 started crashing games or showing a BSoD after installing KB5121003, the most effective workaround is to disable the inpoutx64.sys driver. This driver is commonly installed by RGB lighting, fan-control, hardware-monitoring, or similar utilities.
1. Disable the Driver via Command Prompt
Disabling the driver prevents Windows from loading it while leaving the driver files on your PC. This is a good first step if you want to avoid permanently removing the driver.
- Press Win + S and open Command Prompt as administrator.
- Execute the following command:
sc.exe config inpoutx64 start= disabled
- Restart your PC.
- Launch the affected game and check if the crash has stopped.
In case the game runs normally after disabling the driver, you can keep it disabled until the RGB or hardware-software vendor releases a compatible update.
Note: After you disable the inpoutx64, some RGB lighting or hardware control features may stop working. You can re-enable the driver later, if needed.
2. Check for an Updated RGB Driver from Your Hardware Vendor
If you don’t want to disable or remove the driver permanently, check the website or support page of your motherboard, RGB controller, or peripheral manufacturer for an updated RGB utility or driver. This is especially important if your RGB software controls your keyboard, mouse, fans, motherboard lighting, or other components.
Since inpoutx64.sys is a third-party driver rather than a core Windows component, a vendor update that no longer relies on the incompatible driver may restore your RGB features while allowing the affected games to run normally. Until a compatible version is available, you can keep the driver disabled and continue using Windows with KB5121003 installed.
Should You Uninstall KB5121003 Instead?
It may seem easiest to uninstall KB5121003 altogether, especially since the crashes disappear once the update is removed. However, doing so also undoes the security fixes that addressed around 400 vulnerabilities, leaving your system exposed to the same threats the update was designed to patch.
Sacrificing important security protections just to avoid game crashes is hardly an ideal solution. A safer approach is to disable the affected driver or wait for an updated RGB utility that resolves the compatibility issue, allowing you to avoid the crashes without losing the update’s security improvements.
Will Microsoft Fix This Permanently?
At this stage, the issue is still under investigation rather than fully resolved. Microsoft is looking into how certain RGB components interact with the affected games, but it has not yet announced a permanent fix or provided a specific timeline for one.
If you are experiencing these crashes, consider submitting a report through the Feedback Hub by pressing Win + F. User reports can help Microsoft identify the extent of the problem and prioritize potential fixes.
How to Recover Data After a BSoD Crash?
A single BSoD caused by the inpoutx64.sys driver shouldn’t normally put your personal files at risk. But repeated crashes, failed restarts, or an inability to boot into Windows can make your data inaccessible.
If your PC still starts normally, back up your important files before attempting further troubleshooting. If Windows won’t boot, you can use Stellar Data Recovery Professional to create a bootable recovery media and copy your files from the affected drive.
Once your important data is safe, you can disable or remove the affected driver and troubleshoot the Windows installation. Do not repeatedly force restart the PC if it remains stuck in a boot loop as it can make an existing file-system problem much worse.
Summing Up
The current BSoD issue on Windows linked to the inpoutx64.sys seems to be a compatibility issue which involves the August 2026 update, some RGB or hardware-control software, and affected games. There isn’t a permanent fix yet as Microsoft is still investigating the issue. We recommend that instead of uninstalling the entire Windows update disable inpoutx64.sys first. Then check for an updated RGB or hardware-control driver from your device manufacturer and keep an eye out for Microsoft’s eventual fix. If repeated crashes have made Windows unbootable, recover your important files before making further system changes.