A Windows update can quietly rewrite the contract between your operating system and your hardware. Most of the time nobody notices. Once in a while, a routine cumulative update ships and a subset of users start crashing. That is the situation around KB5121003, the August 11, 2026 cumulative update for Windows 11. The crash signature is consistent across reports: a game freezes, gets dumped to the desktop, or restarts the PC with an EXCEPTION_ACCESS_VIOLATION (a Windows error code that means a program tried to read or write memory it was not allowed to touch) in the event log. The common thread is RGB hardware.
Microsoft has acknowledged the problem and published a workaround. The workaround is a registry edit (a manual change to the Windows registry, the central database Windows uses to track hardware drivers and system settings) that disables a specific driver family. It is not a real patch. The real patch is still in development, and the timeline is not public.
What actually broke
RGB peripherals do not always behave like normal peripherals. Many of them ship with kernel-level drivers (software that runs deep inside Windows, with the same privileges as Windows itself) that talk directly to hardware ports (the low-level communication channels between the CPU and connected devices). One of the most common driver families is named something like inpoutx64, and it gets installed by RGB RAM, RGB fans, RGB keyboards, and the configuration tools that ship with those parts. The drivers let the software flip colors, set per-key effects, and coordinate lighting profiles across multiple devices.
KB5121003 changed how Windows arbitrates hardware port access. The change was small and intended. Unfortunately, it interacted badly with the way inpoutx64-style drivers request memory access. Games that called into those drivers started tripping Windows’ protection. Once the kernel sees an access violation in the middle of a frame, it has two choices: kill the process or restart the machine. The first symptom users reported was games freezing. The deeper symptom was the EXCEPTION_ACCESS_VIOLATION crash, which is the kernel’s way of saying “I caught a memory error and I am not going to let it through.”
The titles that surfaced first were ARC Raiders, MARVEL T?kon: Fighting Souls, and THE FINALS. None of those games are unique in any technical sense. They got reported first because their player base is large and their forums are loud. Any game that touches the same code path can hit the same crash.
- The driver family is inpoutx64-style. Anything that installs a kernel driver with a similar name can hit this.
- The conflict is in memory access. KB5121003 changed how the kernel grants that access, and the RGB drivers had not been updated.
- The crash is the kernel doing its job. Windows is preventing a memory error from propagating. The fix has to come from the driver side, not the kernel side.
- Game choice is irrelevant. Any title can trigger it. The early reports were loud, not exclusive.
The registry edit Microsoft is recommending
Microsoft’s Release Health note for this issue describes a temporary workaround. Open Registry Editor (the built-in Windows tool for editing the registry database) as an administrator, navigate to a specific key, change one value, restart. That is the whole recipe. The key path is HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64. The value is called Start. The new value data is 4, which tells Windows not to load the driver at boot.
Back up the registry before you change anything. Editing the wrong value is not the kind of mistake you recover from quickly without an export. Right-click the inpoutx64 key, choose Export, save the file to a folder you will remember. That gives you an undo button if the change does not behave the way Microsoft says it will.
- Launch regedit as Administrator. The standard user can read the registry but cannot edit system keys.
- Export the inpoutx64 key first. Save the .reg file somewhere safe. That is your rollback.
- Change the Start value to 4. Anything other than 0, 1, 2, 3, or 4 means “disabled” to Windows. Microsoft specifically recommends 4.
- Restart. The change only takes effect at the next boot.
Once Windows reboots, the inpoutx64 driver is out of the picture. Any game that was crashing because of the driver interaction should stop crashing. That is the upside.
What the registry edit actually costs
The downside is the part Microsoft spends less time on. Disabling inpoutx64 does not just turn off the crashes. It also turns off the RGB lighting on every device that uses that driver. If your RAM sticks were glowing because of this driver, they will not glow anymore. If your keyboard’s per-key effects were going through this driver, the lights may stop responding, and the configuration tool may refuse to detect the hardware. The same applies to RGB fans, RGB controllers, and any other component that relies on this specific driver path.
The practical result is a binary choice. You can have RGB lighting, or you can have stable games. You cannot have both until Microsoft ships a real patch that addresses the underlying kernel change without breaking the driver contract.
There is also the smaller risk of editing the registry incorrectly. The recipe is straightforward, but Windows does not protect you from typos. A wrong key, a wrong value name, or a wrong value data can leave the system in a state that requires recovery options to undo. The export step exists exactly because of this. Skipping it is a gamble with very low odds and a very bad payout.
- RGB lighting is collateral damage. Every device on this driver loses its glow.
- Configuration software may break. Vendor tools that talk to the driver will refuse to detect hardware.
- Recovery requires a clean export. Without a backup, restoring the original value means guessing what Windows had set.
- The fix is binary. RGB on, or games stable. There is no middle ground.
When to apply and when to wait
If your games crash, apply the workaround today. The recipe takes two minutes, the export gives you an undo, and the only cost is the loss of RGB effects until a permanent patch lands. Most people will consider that a fair trade. Ranked matches and live-service save files are worth more than rainbow RAM.
If your games do not crash, or if you play older single-player titles that do not hit the affected code path, wait. Microsoft is tracking this as a known issue, and the Release Health note will update when a permanent patch is ready. The registry edit is not preventative. It only helps systems that are already crashing. Applying it on a system that does not crash means turning off RGB for no benefit.
There is one more case worth flagging. If you bought a pre-built RGB system and you do not know which driver your hardware uses, open Device Manager (the Windows tool that lists every piece of hardware on your system and its associated driver) and look for inpoutx64 in the list of system devices. If it is there, the workaround applies to you. If it is not, the crash you are seeing is something else, and the workaround will not help.
- Apply if games crash. Two minutes of work, an export as insurance, and stable play sessions in return.
- Wait if games do not crash. The workaround is not a preventative measure.
- Check Device Manager if unsure. Look for inpoutx64 in the system device list before you edit anything.
- Watch the Release Health note. Microsoft will update it when a permanent patch is ready.
Trade-offs
Microsoft’s workaround is a temporary patch for a vendor-owned driver problem. The kernel change in KB5121003 is not going to be reverted. The fix has to come from inpoutx64 itself, which lives with each RGB hardware vendor. That makes the timeline fuzzy. Some vendors will update quickly. Others will take months. Some will not update at all, and their hardware will need a registry edit forever.
There is also a longer-term lesson here. The RGB lighting market is built on a stack of vendor-specific drivers, each one talking to the kernel in slightly different ways. When Microsoft changes the kernel, somebody’s RGB driver breaks. That is not a one-time event. It will happen again. The choice to live with RGB hardware means accepting that your lights may go dark for a Patch Tuesday (the monthly Tuesday when Microsoft ships security updates to Windows) every couple of years.
- Vendor-owned driver. Microsoft cannot push inpoutx64. Each vendor has to update its own copy.
- The kernel change is permanent. KB5121003 will not be reverted. The fix has to come from the driver side.
- The RGB market is fragile. This kind of conflict will happen again with future Windows updates.
- Registry edits are temporary workarounds, not a fix. Plan on revisiting this if you upgrade Windows or swap hardware.
Bottom line
Back up the registry, set Start to 4 under the inpoutx64 key, restart, and your games should stop crashing. Save the export to a folder you will not accidentally empty. If you have not been crashing, do not touch the registry. Either way, watch the Release Health note for an update from Microsoft, and check with your RGB hardware vendor when their driver fix is ready. That is the most you can do until the real patch ships.