RGB Lighting Crashing Windows: Microsoft’s Official Fix Explained

RGB lighting Crashing Windows are not a myth — Microsoft has officially confirmed that RGB peripheral software is triggering blue screens, game freezes, and unexpected restarts on Windows 11. If your PC has started acting up after a recent Windows update and you own a keyboard, mouse, or fan controller with RGB effects, there is a very good chance your lighting software is the culprit. Here is everything you need to know, including the exact steps to stabilise your system today.

Why RGB Software Is Crashing Windows 11

The root cause of the Windows 11 RGB crashes is a third-party kernel driver called inpoutx64.sys. This low-level driver is bundled with a wide range of RGB control applications — from Corsair iCUE to Razer Synapse to ASUS Armoury Crate — and it is used to give those apps direct hardware access for lighting control. Under normal conditions it works quietly in the background. However, a change introduced in the August 2026 Patch Tuesday update (build 26100.9168 and 26200.9168) exposed a kernel-level conflict that causes the driver to corrupt critical system structures, triggering CRITICAL_STRUCTURE_CORRUPTION blue screens and hard game crashes.

Microsoft acknowledged the issue publicly after a flood of user reports, confirming in a support advisory that drivers or components installed by RGB devices were interfering with core Windows components on affected systems. The problem is not with the RGB hardware itself — your Corsair keyboard and your ASUS motherboard LEDs are fine. It is the companion software sitting in the Windows kernel that is causing the instability.

Which Devices and Software Are Affected

Any application that ships with or installs the inpoutx64.sys driver can potentially trigger this issue. Known affected software includes:

• Corsair iCUE

• Razer Synapse

• ASUS Armoury Crate / Aura Sync

• MSI Dragon Center / MSI Center

• NZXT CAM

• Logitech G Hub

• SteelSeries GG

• HWiNFO (some versions)

• Various fan controller and RGB strip utilities

You do not have to own a flagship gaming peripheral to be affected. Many mid-range motherboards include onboard RGB headers and ship with software that installs the same problematic driver without any obvious prompt during setup. If you have ever clicked “install companion software” during a motherboard or peripheral driver installation, there is a reasonable chance inpoutx64.sys is sitting on your system right now.

How to Check If You Have the Problematic Driver

Before diving into fixes, confirm whether the driver is present on your PC. Open Command Prompt as Administrator and run the following command:

sc query inpoutx64

If you see a service listed with a status of RUNNING or STOPPED, the driver is installed. You can also navigate to C:\Windows\System32\drivers\ in File Explorer and search for inpoutx64.sys. Its presence confirms your system is exposed to the conflict.

Microsoft’s Official RGB Software Windows Fix

Microsoft has published a support article confirming the issue and providing two workaround steps while a permanent patch is developed. These are the official steps:

1. Stop the service: Open Command Prompt as Administrator and run sc stop inpoutx64 followed by sc delete inpoutx64. This stops and removes the service entry.

2. Delete the driver file: Navigate to C:\Windows\System32\drivers\ and delete inpoutx64.sys. You may need to take ownership of the file first if Windows reports it is in use.

3. Wipe the registry entry: Open Registry Editor (regedit), navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\inpoutx64, and delete the entire key. Back up your registry first using File → Export.

4. Restart Windows: A full reboot applies the changes and removes the driver from memory.

After completing these steps, most users report that blue screens stop and games run without freezing. Your RGB hardware will still function — keyboards and mice work fine — but the companion lighting software will lose the ability to change colour profiles until the vendor ships an updated, compatible driver. For most people, stable gaming is worth the temporary trade-off.

RGB Driver Blue Screen: The Longer-Term Solution

Removing inpoutx64.sys is a workaround, not a permanent fix. The lasting solution depends on two parties acting in parallel. Microsoft needs to ship a further Windows update that either restores compatibility for the driver or introduces tighter kernel signing controls that prevent the conflict recurring. Separately, peripheral manufacturers need to release updated versions of their RGB control software that do not rely on inpoutx64.sys for hardware access, or that ship a version of the driver that is compatible with the current kernel build.

Based on community reports across Reddit and dedicated hardware forums, several vendors including Corsair and ASUS were already working on updated software packages within days of Microsoft’s public acknowledgement. Check your RGB software’s update channel regularly — when a patched version arrives, you can reinstall it safely and your lighting profiles will come back to life. Until then, the manual removal steps above remain the most reliable path to a stable system.

Should You Roll Back the Windows Update?

Rolling back the August 2026 Patch Tuesday update is technically possible within 10 days of installation via Settings → Windows Update → Update History → Uninstall Updates. However, this approach is not recommended as a long-term strategy. The August 2026 update patched over 80 security vulnerabilities, including several rated Critical by Microsoft’s own severity scale. Running an unpatched Windows 11 build to preserve RGB lighting is not a sensible trade-off — especially on a gaming PC that connects to online services. The inpoutx64.sys removal method lets you keep your security patches and your stable system simultaneously.

Windows 11 RGB Crashes: Keeping Your System Stable Going Forward

This incident highlights a broader tension in the Windows ecosystem: third-party software that operates at the kernel level can destabilise the entire OS when a system update shifts the rules. RGB control utilities, overclocking tools, and fan-management apps all tend to use low-level drivers for performance reasons, and every major Windows update carries a small risk of breaking one of them. A few habits can significantly reduce your exposure:

• Delay non-critical updates by 7 days using the Windows Update pause option — by then, widespread issues like this one are usually flagged publicly.

• Keep RGB and hardware-control software updated independently — vendor patches often arrive within days of a major Windows build drop.

• Check the Windows Health Dashboard before applying a cumulative update — Microsoft documents known conflicts there before they appear in mainstream media.

• Create a System Restore point before every major update so you have a clean rollback option without losing personal files.

• Audit your installed drivers periodically using driverquery /fo list | more in Command Prompt — you may be surprised how many third-party kernel drivers are running on your machine.

For a broader look at squeezing performance and stability out of Windows, our guide on Windows performance tuning with hidden built-in tools covers the native utilities that most users overlook.

Do You Actually Need a Fresh Windows 11 Licence?

If this RGB lighting crash saga has you questioning whether your current Windows installation is properly activated — or if you are building a new gaming rig and want a clean, activated copy of Windows 11 before installing any peripheral software — Buy Now Key offers genuine Windows 11 Pro licences from €17.90, with lifetime activation on a single device and instant digital delivery. Starting with a properly licensed, clean install eliminates a whole category of activation-related instability before you even plug in your first RGB peripheral.

According to BleepingComputer’s coverage of Microsoft’s official statement, the company confirmed the gaming issues are caused specifically by drivers or components installed by RGB devices — not by Windows itself. That distinction matters: your Windows licence and core OS files are not corrupted. The fix is targeted and reversible.

FAQ

Will removing inpoutx64.sys break my RGB hardware permanently?

No. Your RGB hardware — keyboards, mice, fans, and motherboard headers — will continue to function normally for basic input and lighting after the driver is removed. What you lose temporarily is software-controlled lighting customisation: colour profiles, reactive effects, and sync across devices. Once your peripheral manufacturer ships an updated version of their RGB control software that is compatible with the current Windows kernel, you can reinstall it and your profiles will return.

How do I know if the RGB driver blue screen is causing my specific crashes?

The most reliable indicator is the stop code. If your blue screens display CRITICAL_STRUCTURE_CORRUPTION or if Windows Event Viewer logs show inpoutx64.sys as the faulting module, the RGB driver is almost certainly the cause. You can check Event Viewer under Windows Logs → System and look for Critical or Error events timestamped at the moment of each crash. If inpoutx64 appears in the log, the removal steps in this article will resolve the issue.

Is this problem limited to Windows 11, or does it affect Windows 10 too?

Microsoft’s official advisory specifically references Windows 11 builds 26100.9168 and 26200.9168, which correspond to the August 2026 Patch Tuesday cumulative updates. Windows 10 users are not currently cited as affected by this specific kernel conflict, though Windows 10 does share some driver infrastructure with Windows 11. If you are on Windows 10 and experiencing similar symptoms, the same inpoutx64.sys check and removal process applies as a diagnostic step.

Do I need to uninstall my RGB software entirely, or just delete the driver file?

You do not need to fully uninstall your RGB application. Deleting inpoutx64.sys and removing its registry entry is sufficient to resolve the crash. The RGB app itself can remain installed — it just will not be able to communicate with hardware at the kernel level until a compatible driver is available. Some users prefer a full uninstall for a cleaner result, but partial removal (driver file and registry key only) is the minimal fix and is fully reversible.

Will Windows automatically reinstall inpoutx64.sys after the next update?

Windows itself will not reinstall the driver — it belongs to third-party software, not to the OS. However, if you update or reinstall your RGB control application (Corsair iCUE, Razer Synapse, etc.) before the vendor has shipped a patched version, the installer will drop a new copy of inpoutx64.sys back onto your system. Always check that your RGB software update notes explicitly mention Windows 11 August 2026 compatibility before reinstalling.