Yeah it is still happening, but it has like 3 variations:
- Hearing a windows disconnect sound, but still responding and LEDs stay on, with the profile select led turning on (rare)
- Hearing disconnect sound, LEDs go off, reconnect sound sometimes, profile led turns on, not responding (no mouse movement)
- Disconnect, with the error message, windows couldn't recognize the device. (Happened only once when starting VirtualBox)
And I have also looked at the FPS drops in Valorant with a driver latency monitor, and in theory, the drivers are fast enough, so that it shouldn't drop the FPS. And apparently every poll causes an ISR (Interrupt service routine) in the framework driver. (Around 800k polls in 100 seconds for the 8k polling rate, if moving around mouse.)(This is how I also determined that the ISR count is responsible for handling mouse interrupts, since when moving the mouse the count rises faster.) So by this I can say, that the mouse is sending around 8000 packets per second to the controller, which is it's advertised speed. It also doesn't send too many, which was my suspicion, since that could cause problems, like the USB controller disconnecting it. I still suspect that the firmware is somehow broken and overloads the controller in the mouse itself for a little too long, which then causes missing packets, which then breaks the link. Here is the image of the latency monitor:
Here is the test for 100 seconds without touching the mouse and keyboard:
Apparently it adds a whole 5 seconds to process the requests over the 100 measured seconds, which is quite a lot. But since I think it is handled over a single CPU core, and I have 8 (16 threads) of them, the interrupts account for a whole 0,625% of the available computing power, if only the physical cores are counted.
So I still don't really have an idea what is causing the FPS drops and the disconnects, but I am hopeful that my observations can help figuring out the problem.