You can use software like USBDeview to see what is triggering the sound when it happens as well to isolate the issue: If your USB port is using a hub for example (not physical hub but USB device hub on motherboard), youll get the disconnect sound because the hub didn't enumerate correctly to our polling request. To be more elaborate, CUE always will poll the USB ports to detect your RGB peripherals. Next select the "Power Management" tab, and uncheck "allow the computer to turn off this device to save power".ĭo this for all of them and see if you still have issues. In that sub menu, Next double click the first "USB Root Hub" entry. Select "Universal Serial Bus Controllers". Seems to work, but I was curious what the hell kept creating the USB disconnect sound to fire. T02:46:00 I cue.dev: Attached to device object K70 LUX RGB: b=1 a=1 T02:46:00 I cue.dev: Initializing K70 LUX RGB. T02:46:00 I cue.dev: Attached to device object K70 LUX RGB: b=0 a=1 T17:12:57 I cue.dev: Initializing K95 RGB PLATINUM. I listed a few snippets from the log below. I'll go ahead and mention here that the logs do contain multiple "Failed to open device." and "Cannot find path for manifest key." errors. I went ahead and submitted a ticket regarding the issue and included the logs. I tried polling rates of both 500 and 250 Hz, but I still receive the disconnect sound. Just a good rundown)Īlso, please remember to create a ticket with our technical support team so they can coordinate that information with the devs.
Logs are located here: C:\Users\\AppData\Local\Corsair\CUE\logsĭXDiag help: (ignore that this a Wizards of the Coast link.
Because of this, please make sure to provide a copy of your system information, and perhaps the logs generated by CUE when you open it.
Sudden communication issues related to the drivers could cause this issue of a sudden disconnect.īut, please remember that issues such as this can also be hard to track. When CUE is on, it is using several Corsair specific drivers in order to coordinate Macros and Lighting changes. When CUE is not running, the mouse is likely using the standard Windows HID driver. Please note, the driver actually changes slightly when CUE is activated. So, if CUE's activation suddenly causes a disconnect, then it could be a setting which changes once CUE is on. One of the things that Corsair Utility Engine does when it activates is apply all of the settings it controls. Try turning your polling rate down to 500Mhz/2ms.
0 kommentar(er)
