Microsoft has narrowed its investigation into Windows 11 game crashes reported after KB5121003 and later updates. The company now says the issue is associated with some peripherals or internal components with RGB lighting features, which can install drivers or software components with names similar to inpoutx64.
The incident remains under investigation on Windows 11 versions 24H2 and 25H2, but Microsoft has now published a temporary workaround for affected systems. ARC Raiders, MARVEL Tōkon: Fighting Souls and The Finals remain the games named in Microsoft’s reports.
Microsoft links the crashes to RGB-related components
Microsoft’s updated Windows Release Health entry says systems with the relevant RGB-related drivers can encounter the problem when certain games are launched. Reported symptoms include games becoming unresponsive, closing without notice, showing an EXCEPTION_ACCESS_VIOLATION error or causing the PC to restart without warning.
The status is still Investigating. Microsoft says it is continuing to study the relationship between the RGB components and the games that trigger the issue, so the new information should not be read as a final explanation for every crash reported after KB5121003. The company is still asking affected users to submit reports through Feedback Hub.
KB5121003 remains the originating Windows update
KB5121003 was released on August 11 for Windows 11 versions 24H2 and 25H2, with OS builds 26100.9168 and 26200.9168 respectively. Microsoft’s Release Health entry continues to list build 26100.9168 and KB5121003 as the originating update for the incident.
Microsoft has also updated the KB5121003 support article itself. Its change log says the known issue covering games becoming unresponsive was added on August 20, replacing the earlier situation where Release Health contained more current information than the KB support page.
Windows 11 version 26H1 is still not listed among the affected client platforms. Microsoft’s current incident entry names only Windows 11 24H2 and 25H2, with no Windows Server platform listed as affected.
Microsoft now provides an inpoutx64 workaround
For systems affected by this specific issue, Microsoft says it can be prevented by temporarily disabling the inpoutx64 driver through the Windows Registry. Its instructions point to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64, where the Start value is changed to 4 before restarting the PC.
Microsoft warns users to back up the Registry before making the change. Disabling the driver can also interfere with RGB features or the software used to control them, and restoring the previous Registry value may be necessary to regain that functionality.
This is a targeted workaround, not a reason to remove KB5121003 or disable unrelated drivers on systems that are not experiencing the problem. Microsoft has not announced a permanent Windows fix or a timetable for one.
The investigation is still open
Embark had already linked crashes affecting ARC Raiders to inpoutx64.sys and shared temporary guidance with affected players. Microsoft’s newer investigation now independently identifies the same class of RGB-related components and inpoutx64-style drivers as part of the wider incident.
Players who are affected should follow Microsoft’s current Release Health guidance and the support channel for the game involved. Microsoft says it will publish another update when it has more information about the interaction between the RGB components and the games triggering the crashes.
Source note: Microsoft’s Windows Release Health dashboard and KB5121003 support page provide the official incident and update status. PC Gamer was used for Embark’s ARC Raiders driver and workaround reporting.