Microsoft now says its investigation links these Windows 11 gaming crashes to certain RGB-capable peripherals or internal components and the low-level drivers or software they install. The company has not declared a completed root cause: it is still investigating the relationship among KB5121003, affected games, and components with names similar to inpoutx64.
Current Microsoft status: Investigating
What Microsoft has officially confirmed
Microsoft opened the incident on August 19 and says the reports began after updates released August 11—KB5121003 and later. In its August 21 update, Microsoft said its ongoing investigation indicates an association with certain RGB-capable peripherals or internal components and drivers or software with names similar to inpoutx64. Microsoft is still working to understand the relationship; “associated” does not mean every RGB device is affected or that the final root cause is proved.
Microsoft lists three examples: ARC Raiders, MARVEL Tōkon: Fighting Souls, and The Finals. That does not mean every installation of those games will fail, and it does not establish that every other crash report after August 11 belongs to this incident.
Which Windows versions and builds are involved?
| Platform | August update | OS build | Microsoft incident status |
|---|---|---|---|
| Windows 11 25H2 | KB5121003 | 26200.9168 | Investigating |
| Windows 11 24H2 | KB5121003 | 26100.9168 | Investigating |
| Windows 11 26H1 | KB5121000 | 28000.2704 | Not listed in this incident |
| Windows Server | — | — | None affected, per release health |
Check your PC at Settings → System → About, or press Windows key + R, type winver, and press Enter. A nearby build does not automatically prove the update caused your crash; it only establishes that the machine is in the investigated version family.
What Microsoft has not confirmed
No final root cause
Microsoft says its investigation indicates an RGB-component association but is still working to understand the relationship. That is narrower than a completed root-cause finding.
No universal RGB failure
The relevant layer is associated driver or control software—not decorative lighting itself. Microsoft has not named every affected utility, vendor, or device model.
Temporary workaround—not a permanent fix
Microsoft now documents temporarily disabling the driver through the registry, with backup/restore preparation and an explicit warning that RGB features or control software may stop working. It has not announced a permanent Windows fix.
No confirmation of every side report
Graphics corruption, Windows Hello, frame-rate drops, and crashes in other titles have been reported elsewhere, but they are not all inside this official incident scope.
What Microsoft learned about RGB-control components
Microsoft now says affected systems are associated with certain peripherals or internal components that support RGB lighting. Their drivers or software may include code components with names similar to inpoutx64. That wording matters: Microsoft did not say every system has one universal exact binary, and it did not say the lights themselves are defective.
Embark Studios—the developer behind ARC Raiders and The Finals—separately acknowledges ARC Raiders PC crashes related to KB5121003 and links a temporary workaround while it works on a fix. The evidence supports a limited compatibility interaction among Windows changes, particular games, and some low-level hardware-control components—not a blanket indictment of RGB hardware.
What affected gamers should do now
Prove the timing
Record when the crash first appeared, the KB installation date, Windows version/build, game version, launcher, GPU driver version, and whether another utility updated at the same time.
Capture the symptom
Photograph the error, preserve the game crash report, and note whether it hangs, closes, shows EXCEPTION_ACCESS_VIOLATION, reboots the PC, or produces a different failure.
Update the game stack
Install current game, launcher, anti-cheat, GPU-driver, chipset, and hardware-utility updates from their official vendors. Restart once; do not pile on repeated reinstalls without evidence.
Verify game files
Use the launcher’s verify/repair function. This is faster and less destructive than reinstalling a large title and can rule out damaged local files.
Check the game vendor
For ARC Raiders, consult Embark’s Live Update 1.42.0 known-issues section. For other games, use the developer’s current support channel rather than applying an ARC-specific driver change.
Submit useful feedback
Open Feedback Hub, reproduce the issue if safe, attach diagnostic data, include KB5121003/build/game/error details, and share the Feedback Hub link with the game vendor if requested.
Change one variable at a time
If a vendor recommends disabling an overlay, hardware utility, or driver, make only that controlled change, test, document the result, and preserve a rollback path.
Wait for a verified fix when possible
A stable PC that runs other software normally is usually safer waiting for Microsoft and the game studio than removing a cumulative security update.
Does your crash fit this incident?
The date alone is not enough. A game can fail after August 11 because of a game patch, anti-cheat update, GPU driver, unstable memory profile, overheating, overlay, corrupted file, or background utility. Use the shape of the failure to decide what to test next.
Only one named game fails
If ARC Raiders, MARVEL Tōkon: Fighting Souls, or The Finals fails while other demanding games remain stable, this Microsoft incident and the game vendor’s current guidance move higher on the list. Capture the exact game build and error before changing anything.
Every game fails
A broader failure deserves broader checks: GPU-driver installation, temperatures, power, RAM stability, storage health, overlays, and recent hardware-utility updates. Do not force every crash into the KB5121003 explanation.
The PC hard-restarts
Microsoft lists unexpected restart as a possible symptom, but a restart can also indicate power, thermal, driver, or hardware instability. Record whether Windows created a bugcheck, kernel-power event, or dump file.
You see access violation
EXCEPTION_ACCESS_VIOLATION is inside Microsoft’s symptom list, but it is not unique to this incident. The faulting module, timestamp, game, and build are what make the report useful.
Fast fix first—then understand why
For a single affected game, start with reversible steps: restart Windows once, install the game’s current patch, verify its files, update the launcher and anti-cheat, close nonessential overlays, and check the developer’s known-issues page. If one of those fixes the crash, restore optional tools one at a time so you learn which component mattered.
If the issue follows a hardware-control application, look in that application’s settings and support documentation before touching its driver. Record the component’s exact name, digital signature, version, and owning software; do not assume that Microsoft’s phrase “names similar to inpoutx64” identifies one universal file on every affected PC. Use Microsoft’s current live workaround for the Windows incident and the affected game’s own support path, with a documented restoration plan.
If a vendor workaround succeeds, report that result. Microsoft’s Feedback Hub submission should include the before-and-after state: Windows 11 version, OS build, KB5121003 installation date, game name and build, crash text, faulting module if known, attached diagnostics, and the exact reversible change that stopped the failure. Send the Feedback Hub link to the game studio when its support team asks; that helps Microsoft and the developer correlate duplicate reports.
Do not erase the evidence
Repeated clean installs, registry cleaners, driver-updater bundles, “PC optimization” tools, and wholesale deletion of crash folders can make the machine less trustworthy while destroying the chronology investigators need. Preserve the original error and logs before experimenting. If the game contains an automatic crash reporter, let it finish once and keep its reference number.
For an unexpected restart, note the exact wall-clock time and check whether Windows wrote a memory dump. For a silent game close, record the Reliability Monitor fault bucket and module. For a hang, wait briefly to see whether Windows offers a close/report dialog. For graphical corruption without a crash, capture a screenshot or short phone video and note whether the corruption appears in the capture; that can help distinguish rendering output from the display path.
How to collect evidence without becoming a crash detective forever
Reliability Monitor
Search Windows for “View reliability history.” Open the failure, record the application name, faulting module, exception code, and timestamp.
Event Viewer
Check Windows Logs → Application and System around the exact failure time. Export only relevant entries; do not post an entire private system log publicly.
Game crash folder
Many games save logs or dumps in their installation or local-app-data folder. Use the developer’s support instructions so you send the right files.
Feedback Hub
Choose a gaming/performance category, reproduce only when safe, describe expected versus actual behavior, and include the build, KB, hardware, and game version.
Should you uninstall KB5121003?
Not by default. KB5121003 is a cumulative Windows security update. Removing it can re-expose vulnerabilities and also removes quality fixes bundled into the same package. A healthy gaming PC should keep the update installed.
Rollback becomes a reasonable discussion only when the failure is severe, repeatable, began with the update, prevents necessary use, and safer vendor-supported mitigations failed. Before removal, make a verified backup, document the current build, understand how long Windows permits uninstalling the update, and have a plan to reinstall promptly when Microsoft or the game vendor publishes a fix.
The Microsoft pages now agree on the incident
The KB5121003 support article now includes the gaming issue, RGB-component association, named games and symptoms. That closes the documentation mismatch noted in the original version of this article. The release-health incident remains the best live status source because it carries the current Investigating state, timestamp, scope and workaround.
Incident timeline
August 11
Microsoft releases KB5121003 for Windows 11 24H2 and 25H2.
After installation
Players and game studios report hangs, closes, access violations, and unexpected restarts on some systems.
August 18
Embark’s Live Update 1.42.0 lists ARC Raiders PC crashes related to KB5121003 and points players to a workaround while it works on a fix.
August 19
Microsoft opens the release-health incident and marks it Investigating.
August 21
Microsoft updates the incident with the RGB-component association, official temporary registry workaround, and warning that RGB functions or control software may be disrupted. The status remains Investigating.
August 22 cutoff
No completed root cause or permanent Windows fix is announced in the reviewed primary sources.
Frequently asked questions
Does KB5121003 break every game?
No. Microsoft says a limited number of games are involved and names three examples.
Which games has Microsoft named?
ARC Raiders, MARVEL Tōkon: Fighting Souls, and The Finals.
Did Microsoft prove that RGB lighting causes the crashes?
No. Microsoft reports an association with certain RGB-capable components and related low-level software while it continues investigating the relationship. It has not said every RGB device is affected.
Is Windows 11 23H2 affected?
Microsoft’s incident lists only Windows 11 24H2 and 25H2. Do not generalize it to other versions without new evidence.
Should I delete inpoutx64.sys?
No—not as generic advice. Identify the owning utility and use Microsoft’s current live workaround with registry backup and a restoration plan. Microsoft warns that disabling the component may disrupt RGB features or control software.
Should I reinstall my game?
Verify files first. Reinstallation rarely proves the root cause and can waste hours while discarding useful evidence.
Should I remove the Windows update?
Only as a bounded last resort for a severe, reproducible problem after backup and support review. Healthy PCs should keep the security update.
How will I know when the incident changes?
Watch Microsoft’s Windows release-health entry and the affected game’s official support page. Check the status and last-updated time, not just an old headline.
Sources
- Microsoft Windows 11 25H2 release health: gaming investigation and workaround
- Microsoft support: KB5121003 known issue and RGB-component association
- Microsoft: Send feedback with Feedback Hub
- Embark: ARC Raiders Live Update 1.42.0 known issues
- Windows Latest: Microsoft and Embark investigation details
- PC Gamer: affected games and Embark workaround context
Check Microsoft’s live incident status
Updated reporting cutoff: August 22, 2026 at 2:15 p.m. EDT / 18:15 UTC. Microsoft’s incident remained Investigating at this check. This article will be updated if Microsoft changes the status, workaround, or publishes a permanent fix. Game and company names belong to their owners. The IT Guys is not affiliated with Microsoft, Embark, or the cited publications.