the_real_seebs

Ran upgrade, firmware install went smoothly, CUE update got stalled because somehow the UAC prompt didn't actually get displayed, just showed up as an icon in task bar, installed that, mouse seemed fine... For all of 30 seconds before I had to shut down for Windows updates. I'll see, but it looked like it was working so far.

Don't know whether it's relevant, but I set my scimitar to solid colors, and it has indeed not crashed since. But! After a day or so the light turns off, and I don't know why. Still works, just unlit.

Confirmed that the new CUE doesn't fix it; turn on rainbow lighting, few hours later, mouse is dysfunctional. Replug mouse, go to solid lighting, it's fine for a day or more.

Windows 7, no alienware software around. Crashes quickly if in rainbow mode, does not seem to crash ever if it's solid colors.

I switched to lighting on, but disabled the rainbow color change, and it's been about a day, no crashes. Have now set mouse back to 1ms polling rate, and will see whether it crashes anymore. It did seem that frequency of lockups was sort of linear with polling rate. I am reminded of a bug I encountered once in a Unix system long ago where changing console text color very often would eventually crash, because there was a memory leak.

It occurs to me: The rate of those messages appears very close to the rate at which messages would be sent for the "rainbow" color I'd selected for the mouse's lighting. I've set it to all solid colors and will see whether I still see it.

Hi! Having the issue, same thing in logs everyone else sees (nothing I can find but those pages and pages of "request timed out" messages). I note: The mouse buttons DO work when this is happening. They're just really, really, slow. It can take about a second of pressing before the press registers, and a release can also take quite a while to register. Set to 500Hz, and it did happen after a while, but I believe it took significantly longer. I'm now at 250Hz and will see what that does. I'm expecting it to take even longer at that point, but I bet it'd still happen if I left things up for a day or so. Note: Can't change settings when the mouse is doing this, because any attempt to change something like polling settings causes the mouse to eventually crash, disconnect, and reconnect as a generic HID device. (Although I think the settings may actually make it to the mouse, for when it next comes up.) When that happens, CUE crashes also, but if I restart cue, it comes up fine... but doesn't see the mouse. CUE 1.12.75, mouse is 1.06/0.02 firmware/bootloader. Problem has existed as long as I've had mouse, never had different software versions. Side note: You know what would be super convenient? A quick way to assign keys on the mouse to "the next key I hit", or just a "set thumb buttons to numeric keypad" button. Also, although this applies more to things like the keyboard, it might be handy to have a way to apply something like a gradient effect to a range of keys. So, doing the gradient over space, not time. (So, say, you make a rainbow gradient, then apply it to "all the keys", and then they just have static lighting that's a smooth gradient, instead of having to manually adjust colors of keys.)