Microsoft has discovered why this month’s Windows 11 update (KB5121003) can trigger errors and reboots when running three PC games: It turns out RGB accessories and components are involved.
But the problem isn’t the hardware, or the colorful lighting. Surprisingly, Microsoft says that file name similarities in the software for the peripherals are to blame.
In an update posted on Thursday, the company explained: “Ongoing investigation indicates that this issue 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. In systems where these drivers are found, the issue is then triggered by launching certain games.”
Redmond didn’t elaborate. There’s also not much official information about Inpoutx64.sys, but it operates as a core system file and driver that can be located in the C:WindowsSystem32drivers folder. Still, Embark Studios, a developer behind one of the affected games, told users earlier this week: “This is a crash related to the file inpoutx64.sys, which changed with the Windows update.”
The problem has been affecting three games, MARVEL Tōkon: Fighting Souls along with ARC Raiders and THE FINALS, two titles from Embark Studios. The bug can cause an affected game to become unresponsive, abruptly close, display the error message “EXCEPTION_ACCESS_VIOLATION,” or even cause a PC to reboot.
Microsoft hasn’t issued a fix yet. For now, the company says: “We are presently working to understand the relationship between these RGB components and the games which trigger this issue. We will provide an update when more information is available.”
The developer of Arc Raiders, Embark Studios, has also been telling users in the game’s Discord chat server: “We’re working towards a long-term fix but in the meantime there is a work-around solution that will safely remove the file in question and allow you to play the game without issue.” The work-around solution involves basically deleting Inpoutx64.sys, and wiping it from the OS’s registry.
