Third-Party Driver Causes Windows 11 Crashes — Patch Now
A bug in the third-party driver inpoutx64.sys, commonly bundled with RGB peripheral software, caused system crashes and game launch failures on Windows 11 versions 24H2 and 25H2. The root issue highlights how third-party hardware drivers introduced via consumer peripherals can destabilize enterprise and personal systems without adequate vetting. Microsoft's remediation — disabling the offending driver — underscores the risk of unvetted software components entering systems through the supply chain of peripheral manufacturers. This matters because driver-level code runs with kernel privileges, meaning a faulty or malicious driver can compromise entire system stability and security. Organizations must treat third-party drivers with the same scrutiny applied to any privileged software component.
Tactical Insight
Immediate actions
- Apply Microsoft's latest Windows 11 cumulative update to disable the vulnerable inpoutx64.sys driver on affected systems.
- Audit all endpoints for the presence of inpoutx64.sys and flag systems running RGB peripheral management software for review.
Configuration & supply chain controls
- Enforce driver allowlisting policies (e.g., Windows Defender Application Control) to block unsigned or unapproved kernel drivers from loading.
- Establish a vetting process for third-party peripheral software before it is permitted on corporate endpoints.
- Maintain an up-to-date inventory of all installed drivers across the fleet using endpoint management tools (e.g., SCCM, Intune).
Long-term improvements
- Implement automated patch compliance reporting to ensure cumulative updates are applied within defined SLA windows.
- Engage peripheral hardware vendors in your supply chain risk management program and require disclosure of bundled driver components.
- Use crash telemetry and endpoint detection tools to proactively identify driver-related instability before it impacts users at scale.