A bluescreen that lands every time you move a wireless mouse after a Windows 11 update points squarely at a HID or USB driver mismatch, not a failing mouse. SA users on Logitech, Razer and Corsair receivers can clear this with a driver rollback and a power-setting tweak.
Quick Answer
Roll back the USB and HID drivers in Device Manager, disable USB selective suspend, and update the mouse firmware through the vendor app. A wireless mouse cannot itself cause a stop code; the Windows 11 update shipped a USB stack change that conflicts with the receiver. A R600 replacement is only warranted if the receiver fails on a clean install of a second PC.
Read the stop code before touching hardware
Note the exact BSOD code; DRIVER_POWER_STATE_FAILURE and IRQL errors almost always mean a USB power-management clash, not a hardware fault. Open Event Viewer, find the bugcheck, and match it to the receiver's driver. This tells you whether to roll back the USB driver or the mouse software.
The Windows 11 USB power fix
Disable USB selective suspend in the active power plan, then untick 'allow the computer to turn off this device' on every USB Root Hub. Reinstall the receiver firmware so it matches the new Windows USB stack. Test for an hour on a known-stable game to confirm the crashes have stopped.
When the mouse is genuinely the problem
Swap to a wired mouse temporarily; if the BSOD disappears, the receiver or its 2.4GHz link is the suspect, and a clean firmware flash usually revives it. A reliable wireless mouse for SA buyers runs from R600 to R1,800, and a model with onboard memory survives OS reinstalls without losing its profile.
FAQ
Why does my PC bluescreen when I move the mouse?
The Windows 11 update changed the USB power stack, and the receiver's older driver triggers a stop code on a power-state transition. Rolling back the USB driver and disabling selective suspend removes the trigger. The mouse hardware is rarely at fault.
Is it safe to disable USB selective suspend?
Yes, it only stops Windows from powering down idle USB devices, which has no downside on a desktop. It prevents the power-state crash that the update introduced and is a standard fix for HID bluescreens.
Will a wired mouse avoid this entirely?
A wired mouse sidesteps the 2.4GHz receiver path and often avoids the crash, which makes it a quick R400 diagnostic. If the wired mouse is stable, you have confirmed the receiver, not Windows, needs the firmware update.
Pro Tip
Create a System Restore point before the rollback so you can step back cleanly if a different USB device starts misbehaving after the change.