Jump to content
Corsair Logo Corsair Logo
Corsair Community
CORSAIR COMMUNITY Survey, we want to hear your feedback!

Corsair Utility Engine - disables my M65 and K65 when started

DeniCevap

By DeniCevap
in Legacy Corsair Software

Recommended Posts

DeniCevap

DeniCevap

Posted
Posted

Earlier today I got the K65 and M65 (awesome quality by the way!) and when I plugged it in it all worked perfectly from the start. However, I downloaded CUE and installed it to update the firmware for the mouse and the keyboard and this is where I am stuck now.

 

When CUE is started, my mouse starts lagging for like 2 seconds and then the lights turn off and I can't use any buttons on the mouse nor move the cursor (re-plugging it does not work.). The keyboard starts the rainbow colour switchero, but the keys stop working (and re-plugging does not work). To be able to use my mouse and keyboard, I had to disable CUE from auto-start and then restart my PC. As long as CUE is not started, my mouse and keyboard works perfectly.

 

I have searched for a fix but it seems nobody has had the same issue as I do. I have removed all earlier drivers from previous mouse and keyboard (Razer...). If I use a different USB mouse while CUE is opened, the non-corsair mouse works perfectly.

 

I really love this new set-up I have going, but CUE is just messing with me right now...

 

 

This is the CUE log:

[2016-06-06T15:29:25]: UserSessionInfo: locked changed to 0.
[2016-06-06T15:29:25]: UserSessionInfo: connected changed to 1.
[2016-06-06T15:29:25]: UserSessionInfo: local changed to 1.
[2016-06-06T15:29:31]: UserSessionInfo: locked changed to 0.
[2016-06-06T15:29:31]: UserSessionInfo: connected changed to 1.
[2016-06-06T15:29:31]: UserSessionInfo: local changed to 1.
[2016-06-06T15:29:32]: UserSessionInfo: locked changed to 0.
[2016-06-06T15:29:32]: UserSessionInfo: connected changed to 1.
[2016-06-06T15:29:32]: UserSessionInfo: local changed to 1.
[2016-06-06T15:29:32]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_01&col01#9&338820b7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-06T15:29:32]: Created new device object: M65 PRO RGB; ready: 0
[2016-06-06T15:29:32]: Attached to device object M65 PRO RGB: b=1 a=1
[2016-06-06T15:29:32]: Attached to device object M65 PRO RGB: b=1 a=1
[2016-06-06T15:29:32]: Failed to open device: vid=1b1c pid=1b37 path=\\?\hid#vid_1b1c&pid_1b37&mi_01&col01#9&2f8b3ede&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-06T15:29:32]: Created new device object: K65 LUX RGB; ready: 0
[2016-06-06T15:29:32]: Attached to device object K65 LUX RGB: b=1 a=1
[2016-06-06T15:29:32]: Attached to device object K65 LUX RGB: b=1 a=1
[2016-06-06T15:29:32]: Failed to open device: vid=1b1c pid=1b37 path=\\?\hid#vid_1b1c&pid_1b37&mi_00#9&1c5b22a0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-06T15:29:32]: Attached to device object K65 LUX RGB: b=1 a=0
[2016-06-06T15:29:32]: Initializing K65 LUX RGB...
[2016-06-06T15:29:32]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_00#9&1bc49472&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-06T15:29:32]: Attached to device object M65 PRO RGB: b=1 a=0
[2016-06-06T15:29:32]: Initializing M65 PRO RGB...
[2016-06-06T15:29:32]: M65 PRO RGB : trying to force P00 instead of P04
[2016-06-06T15:29:32]: M65 PRO RGB : success, continue initialization on P00
[2016-06-06T15:29:32]: Get device info failed. request timed out for K65 LUX RGB
[2016-06-06T15:29:32]: Get device info failed.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:32]: Get device info failed. request timed out for K65 LUX RGB
[2016-06-06T15:29:32]: Get device info failed.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:32]: Initializing K65 LUX RGB: spent all tries on getDeviceInfo().
[2016-06-06T15:29:32]: Initialized (st=1) K65 LUX RGB.
[2016-06-06T15:29:34]: Initialized (st=1) M65 PRO RGB.
[2016-06-06T15:29:35]: Set dpi properties failed. Current storage 0. request timed out for M65 PRO RGB
[2016-06-06T15:29:35]: Buffer write failed, 1. request timed out for K65 LUX RGB
[2016-06-06T15:29:35]: Set dpi properties failed. Current storage 0.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:35]: Cannot set enabled DPIs mask for M65 PRO RGB, because getting of enabled DPIs mask failed.
[2016-06-06T15:29:35]: Buffer write failed, 1.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:35]: Set current dpi index failed. Current storage 0. request timed out for M65 PRO RGB
[2016-06-06T15:29:35]: Buffer write failed, 2. request timed out for K65 LUX RGB
[2016-06-06T15:29:36]: Set current dpi index failed. Current storage 0.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:36]: Buffer write failed, 2.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:36]: Buffer write failed, 2. request timed out for K65 LUX RGB
[2016-06-06T15:29:36]: Buffer write failed, 2.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:36]: Set key specific brightness failed request timed out for M65 PRO RGB
[2016-06-06T15:29:37]: Set key specific brightness failedDevice : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:37]: Buffer write failed, 1. request timed out for K65 LUX RGB
[2016-06-06T15:29:37]: Set dpi properties failed. Current storage 0. request timed out for M65 PRO RGB
[2016-06-06T15:29:37]: Fail counter for K65 LUX RGB reached zero, setting status 2.
[2016-06-06T15:29:37]: Buffer write failed, 1.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:37]: Buffer write failed, 2. request timed out for K65 LUX RGB
[2016-06-06T15:29:37]: Cannot set enabled DPIs mask for M65 PRO RGB, because getting of enabled DPIs mask failed.
[2016-06-06T15:29:37]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-06T15:29:37]: Set dpi properties failed. Current storage 0.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:38]: Set dpi properties failed. Current storage 0. request timed out for M65 PRO RGB
[2016-06-06T15:29:38]: Buffer write failed, 2.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:38]: Buffer write failed, 2. request timed out for K65 LUX RGB
[2016-06-06T15:29:38]: Set dpi properties failed. Current storage 0.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:38]: Cannot set enabled DPIs mask for M65 PRO RGB, because getting of enabled DPIs mask failed.
[2016-06-06T15:29:38]: Set current dpi index failed. Current storage 0. request timed out for M65 PRO RGB
[2016-06-06T15:29:38]: Buffer write failed, 2.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:38]: Buffer write failed, 2. request timed out for K65 LUX RGB
[2016-06-06T15:29:39]: Set current dpi index failed. Current storage 0.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:39]: Set lift height failed. Current storage 0. request timed out for M65 PRO RGB
[2016-06-06T15:29:39]: Buffer write failed, 2.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:39]: Set lift height failed. Current storage 0.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:39]: Profile/mode uuid and cookie get prepare failed. request timed out for M65 PRO RGB
[2016-06-06T15:29:40]: Profile/mode uuid and cookie get prepare failed.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:40]: Device insertion processing complete for M65 PRO RGB.
[2016-06-06T15:29:40]: Profile/mode uuid and cookie get prepare failed. request timed out for K65 LUX RGB
[2016-06-06T15:29:40]: Profile/mode uuid and cookie get prepare failed.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-06T15:29:40]: Device insertion processing complete for K65 LUX RGB.

Link to comment
Share on other sites
DeniCevap

DeniCevap

Posted
  • Author
Posted
Please fill-out our system specs;

http://forum.corsair.com/v3/profile.php?do=extra

 

Do you have the latest BIOS, Chipset drivers, Windows updates installed?

Have you tried a different USB port?

 

Filled out my system specs.

 

I have updated BIOS to the newest version, newest chipset for my mobo (z77x-ud3h) and all Windows updates for Windows 10 installed.

I have tried all USB ports, but the same thing happens on them all - as soon as CUE starts, my mouse lights turns off and stops working completely, my keyboard does the rainbow colours twice and then stops working competely (execpt the lights). I also noticed that when CUE starts, it wants to update the firmware for the mouse and keyboard but it can not finish because it can't find the mouse nor keyboard because CUE somehow disables them...

 

Only a reboot fixes the mouse and keyboard, but as soon as CUE starts the same thing happens over and over again.

Link to comment
Share on other sites
DeniCevap

DeniCevap

Posted
  • Author
Posted

By downgrading to CUE v1.14.43 I managed to stop CUE from disabling my mouse and keyboard. However now it can not find the devices and I get different errors in the logs. I do NOT get the "Device not detected" error from CUE UNTIL I unplug the devices... so it seems like CUE knows they are there, but can not attach to them or something.

 

[2016-06-09T15:00:55]: UserSessionInfo: locked changed to 0.
[2016-06-09T15:00:55]: UserSessionInfo: connected changed to 1.
[2016-06-09T15:00:55]: UserSessionInfo: local changed to 1.
[2016-06-09T15:00:57]: UserSessionInfo: locked changed to 0.
[2016-06-09T15:00:57]: UserSessionInfo: connected changed to 1.
[2016-06-09T15:00:57]: UserSessionInfo: local changed to 1.
[2016-06-09T15:00:57]: UserSessionInfo: locked changed to 0.
[2016-06-09T15:00:57]: UserSessionInfo: connected changed to 1.
[2016-06-09T15:00:57]: UserSessionInfo: local changed to 1.
[2016-06-09T15:00:57]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_00#9&29e688a3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-09T15:00:57]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_01&col01#9&60f4ae1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-09T15:00:57]: Created new device object: M65 PRO RGB; ready: 0
[2016-06-09T15:00:57]: Attached to device object M65 PRO RGB: b=1 a=1
[2016-06-09T15:00:57]: Attached to device object M65 PRO RGB: b=1 a=0
[2016-06-09T15:00:57]: Initializing M65 PRO RGB...
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Initializing M65 PRO RGB: spent all tries on getDeviceInfo().
[2016-06-09T15:00:58]: Initializing M65 PRO RGB: failed to read proto version.
[2016-06-09T15:00:58]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Initialized (st=0) M65 PRO RGB.
[2016-06-09T15:00:58]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:00:58]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:00:58]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:00:58]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:00:58]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:00:58]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:00:58]: Device object failed to initialize, so it won't be registered with application susbystems. M65 PRO RGB.
[2016-06-09T15:00:58]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:00:58]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:00:58]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:01:02]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:01:02]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:01:02]: Firmware Download: Failed to parse firmware version.
[2016-06-09T15:01:02]: Firmware Download: Failed to read firmware version.
[2016-06-09T15:01:02]: Firmware Download: Some of required values are not set, aborting.
[2016-06-09T15:01:19]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:01:19]: Set OpMode failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:01:19]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:01:19]: Set OpMode failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:01:19]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:01:19]: Set OpMode failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.

 

My mouse and keyboard is found by Windows and the drivers for the keyboard and mouse is installed by Windows Update. If I remove the drivers and replug the devices, Windows update still finds and installs the drivers for the devices. However it seems like CUE can not attach itself to the mouse and keyboard... I have disabled firewall, anti-virus etc, but still no luck... I really want to make this work because what is the point of RGB tools if they do not work?

 

EDIT: After some tires, I finally get my mouse detected in CUE but in malfunction mode... My keyboard is still not detected at all by CUE.

 

http://i.imgur.com/x7IvhOP.png

 

[2016-06-09T15:26:49]: UserSessionInfo: locked changed to 0.
[2016-06-09T15:26:49]: UserSessionInfo: connected changed to 1.
[2016-06-09T15:26:49]: UserSessionInfo: local changed to 1.
[2016-06-09T15:26:49]: UserSessionInfo: locked changed to 0.
[2016-06-09T15:26:49]: UserSessionInfo: connected changed to 1.
[2016-06-09T15:26:49]: UserSessionInfo: local changed to 1.
[2016-06-09T15:26:50]: UserSessionInfo: locked changed to 0.
[2016-06-09T15:26:50]: UserSessionInfo: connected changed to 1.
[2016-06-09T15:26:50]: UserSessionInfo: local changed to 1.
[2016-06-09T15:26:50]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_00#9&29e688a3&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-09T15:26:50]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_01&col01#9&60f4ae1&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-09T15:26:50]: Created new device object: M65 PRO RGB; ready: 0
[2016-06-09T15:26:50]: Attached to device object M65 PRO RGB: b=1 a=1
[2016-06-09T15:26:50]: Attached to device object M65 PRO RGB: b=1 a=0
[2016-06-09T15:26:50]: Initializing M65 PRO RGB...
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Initializing M65 PRO RGB: spent all tries on getDeviceInfo().
[2016-06-09T15:26:50]: Initializing M65 PRO RGB: failed to read proto version.
[2016-06-09T15:26:50]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Initialized (st=0) M65 PRO RGB.
[2016-06-09T15:26:50]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:26:50]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:26:50]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:26:50]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:26:50]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:26:50]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-09T15:26:50]: Device object failed to initialize, so it won't be registered with application susbystems. M65 PRO RGB.
[2016-06-09T15:26:50]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:50]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:50]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:52]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:52]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:52]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:52]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:52]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:52]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.
[2016-06-09T15:26:54]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-09T15:26:54]: Get device info prepare failed.Device : M65 PRO RGB,Execution result = 1, result = 0, platform error code = 1.

Link to comment
Share on other sites
DeniCevap

DeniCevap

Posted
  • Author
Posted
Try an even older version and see if that helps.

http://forum.corsair.com/v3/showthread.php?t=138472

 

It could be outdated firmware that is causing the issue.

 

The devices are not found at all if I am under CUE V.1.15.36. Same messages for each version.

 

[2016-06-10T14:33:07]: UserSessionInfo: locked changed to 0.
[2016-06-10T14:33:07]: UserSessionInfo: connected changed to 1.
[2016-06-10T14:33:07]: UserSessionInfo: local changed to 1.
[2016-06-10T14:33:10]: UserSessionInfo: locked changed to 0.
[2016-06-10T14:33:10]: UserSessionInfo: connected changed to 1.
[2016-06-10T14:33:10]: UserSessionInfo: local changed to 1.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b2e not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b2e not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b2e not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b2e not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b2e not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b37 not found.
[2016-06-10T14:33:11]: Device profile (meta) for device vid=1b1c pid=1b2e not found.

 

Getting really annoying right now. I paid a lot of money for this, and the software does not even work? And a lot of people have issues with the software.

Link to comment
Share on other sites
DeniCevap

DeniCevap

Posted
  • Author
Posted
Want to try CUE2? PM me. This sounds like a possible issue though with your USB controller playing with the virtual driver.

 

Sorry for late answer, I work 12hours shifts 3 days in a row.

 

I have somehow fixed it to a certain percentage. I removed all unused devices in Device Manager, reinstalled my USB 3.0 drivers, restarted my pc with only the keyboard plugged in. CUE found the keyboard and it works perfectly, plug in the mouse and it also works but I had to change the polling rate from 1 ms to 2ms and then it works perfectly. Sometimes when I change ANY setting at all in CUE it stops working again.

 

Too be honest, I would love to try CUE2, but I am afraid that it will stop working again...

 

Keyboard and mouse stops working, after PC gets out of sleep mode, IF a custom button is pressed such as the sniper button (DPI clutch) - replugging does not work...

Link to comment
Share on other sites
DeniCevap

DeniCevap

Posted
  • Author
Posted

It has started to mess with me again.

 

In CUE, everytime I open up the mouse settings it will stop my devices again!

Tinkering with the keyboard settings works perfectly. What is this?...

 

[2016-06-14T18:12:13]: UserSessionInfo: locked changed to 0.
[2016-06-14T18:12:13]: UserSessionInfo: connected changed to 1.
[2016-06-14T18:12:13]: UserSessionInfo: local changed to 1.
[2016-06-14T18:12:15]: UserSessionInfo: locked changed to 0.
[2016-06-14T18:12:15]: UserSessionInfo: connected changed to 1.
[2016-06-14T18:12:15]: UserSessionInfo: local changed to 1.
[2016-06-14T18:12:16]: UserSessionInfo: locked changed to 0.
[2016-06-14T18:12:16]: UserSessionInfo: connected changed to 1.
[2016-06-14T18:12:16]: UserSessionInfo: local changed to 1.
[2016-06-14T18:12:16]: Failed to open device: vid=1b1c pid=1b37 path=\\?\hid#vid_1b1c&pid_1b37&mi_01&col01#9&25c9c540&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-14T18:12:16]: Created new device object: K65 LUX RGB; ready: 0
[2016-06-14T18:12:16]: Attached to device object K65 LUX RGB: b=1 a=1
[2016-06-14T18:12:16]: Attached to device object K65 LUX RGB: b=1 a=1
[2016-06-14T18:12:16]: Attached to device object K65 LUX RGB: b=1 a=0
[2016-06-14T18:12:16]: Initializing K65 LUX RGB...
[2016-06-14T18:12:16]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_01&col01#9&3b881124&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-14T18:12:16]: Created new device object: M65 PRO RGB; ready: 0
[2016-06-14T18:12:16]: Attached to device object M65 PRO RGB: b=1 a=1
[2016-06-14T18:12:16]: Attached to device object M65 PRO RGB: b=1 a=1
[2016-06-14T18:12:16]: Failed to open device: vid=1b1c pid=1b2e path=\\?\hid#vid_1b1c&pid_1b2e&mi_00#9&17b0d362&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-14T18:12:16]: Failed to open device: vid=1b1c pid=1b37 path=\\?\hid#vid_1b1c&pid_1b37&mi_00#9&38f9e17e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-06-14T18:12:16]: Attached to device object M65 PRO RGB: b=1 a=0
[2016-06-14T18:12:16]: Initializing M65 PRO RGB...
[2016-06-14T18:12:16]: Device profile (meta) for device vid=54c pid=5c4 not found.
[2016-06-14T18:12:16]: M65 PRO RGB : trying to force P00 instead of P04
[2016-06-14T18:12:16]: M65 PRO RGB : success, continue initialization on P00
[2016-06-14T18:12:16]: Initialized (st=1) K65 LUX RGB.
[2016-06-14T18:12:16]: Device insertion processing complete for K65 LUX RGB.
[2016-06-14T18:12:19]: Initialized (st=1) M65 PRO RGB.
[2016-06-14T18:12:20]: Device insertion processing complete for M65 PRO RGB.
[2016-06-14T18:12:23]: Firmware Download: Aborting idle process not supported.
[2016-06-14T18:12:24]: Buffer write failed, 1. request timed out for K65 LUX RGB
[2016-06-14T18:12:25]: Buffer write failed, 1.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:12:25]: Buffer write failed, 2. request timed out for K65 LUX RGB
[2016-06-14T18:12:25]: Buffer write failed, 2.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:12:25]: Mouse LED colors change failed. request timed out for M65 PRO RGB
[2016-06-14T18:12:26]: Mouse LED colors change failed.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:12:26]: Buffer write failed, 1. request timed out for K65 LUX RGB
[2016-06-14T18:12:56]: Set dpi properties failed. Current storage 0. request timed out for M65 PRO RGB
[2016-06-14T18:12:56]: Buffer apply for Red failed. request timed out for K65 LUX RGB
[2016-06-14T18:12:57]: Set dpi properties failed. Current storage 0.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:12:57]: Buffer apply for Red failed.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:12:57]: Buffer write failed, 2. request timed out for K65 LUX RGB
[2016-06-14T18:12:57]: Set dpi properties failed. Current storage 0. request timed out for M65 PRO RGB
[2016-06-14T18:12:57]: Buffer write failed, 2.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:12:57]: Buffer write failed, 1. request timed out for K65 LUX RGB
[2016-06-14T18:12:57]: Set dpi properties failed. Current storage 0.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:12:58]: Buffer write failed, 1.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:12:58]: Buffer write failed, 2. request timed out for K65 LUX RGB
[2016-06-14T18:12:58]: Fail counter for K65 LUX RGB reached zero, setting status 2.
[2016-06-14T18:12:58]: Buffer write failed, 2.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:12:58]: Buffer write failed, 2. request timed out for K65 LUX RGB
[2016-06-14T18:12:59]: Buffer write failed, 2.Device : K65 LUX RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:12:59]: Set key specific brightness failed request timed out for M65 PRO RGB
[2016-06-14T18:12:59]: Set key specific brightness failedDevice : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.
[2016-06-14T18:13:00]: Mouse LED colors change failed. request timed out for M65 PRO RGB
[2016-06-14T18:13:01]: Fail counter for M65 PRO RGB reached zero, setting status 2.
[2016-06-14T18:13:01]: Mouse LED colors change failed.Device : M65 PRO RGB,Execution result = 0, result = 0, platform error code = 995.

Link to comment
Share on other sites
slykrysis

slykrysis

Posted
Posted

USE A USB 2.0 PORT!

 

I had these exact symptoms happen to me, with the addition of Corsair's Lapdog in the picture. I have a K70 RGB Rapidfire and an M65 Pro RGB hooked up through the Lapdog. I had the 5V power cable plugged in to power the additional USB 3.0 ports and had the USB 3.0 cable going from the Lapdog to my front panel and also my rear motherboard USB 3.0 ports.

 

As soon as I logged into my Windows profile and CUE loaded, my keyboard lighting and mouse froze and stopped working completely. I had to get around it by using a wireless keyboard/mouse combo.

 

Speaking to 2 Corsair techs, who both said the Lapdog NEEDED TO BE PLUGGED IN TO A USB 3.0 PORT, also suggested uninstalling CUE and reinstalling, which I did. It did the same thing upon reboot after logging in.

 

I also removed CUE altogether and was able to use the mouse/keyboard fine but obviously without any color lighting effects. Installing CUE again at this point caused the issue to happen again as expected.

 

The minute I plugged the Lapdog into a USB 2.0 port and rebooted with CUE installed, everything worked fine.

 

What I discovered while on the phone with Jason, was that my USB 3.0 ports were controlled by a VIA chipset but my 2.0 ports were controlled by an Intel chipset. It would seem that the VIA USB 3.0 extensible host controller has a problem with the Lapdog and/or powering it correctly.

Link to comment
Share on other sites
DeniCevap

DeniCevap

Posted
  • Author
Posted
USE A USB 2.0 PORT!

 

I had these exact symptoms happen to me, with the addition of Corsair's Lapdog in the picture. I have a K70 RGB Rapidfire and an M65 Pro RGB hooked up through the Lapdog. I had the 5V power cable plugged in to power the additional USB 3.0 ports and had the USB 3.0 cable going from the Lapdog to my front panel and also my rear motherboard USB 3.0 ports.

 

As soon as I logged into my Windows profile and CUE loaded, my keyboard lighting and mouse froze and stopped working completely. I had to get around it by using a wireless keyboard/mouse combo.

 

Speaking to 2 Corsair techs, who both said the Lapdog NEEDED TO BE PLUGGED IN TO A USB 3.0 PORT, also suggested uninstalling CUE and reinstalling, which I did. It did the same thing upon reboot after logging in.

 

I also removed CUE altogether and was able to use the mouse/keyboard fine but obviously without any color lighting effects. Installing CUE again at this point caused the issue to happen again as expected.

 

The minute I plugged the Lapdog into a USB 2.0 port and rebooted with CUE installed, everything worked fine.

 

What I discovered while on the phone with Jason, was that my USB 3.0 ports were controlled by a VIA chipset but my 2.0 ports were controlled by an Intel chipset. It would seem that the VIA USB 3.0 extensible host controller has a problem with the Lapdog and/or powering it correctly.

 

Oh wow, I need to try this! I also have VIA USB 3.0! Hopefully it fixes it! Reporting back when I test it!

 

EDIT: Wow.. I only have USB 3.0 ports on my motherboard... Guess I am out of luck.

Link to comment
Share on other sites
DeniCevap

DeniCevap

Posted
  • Author
Posted

Obligatory bump!

 

By going into BIOS and setting "xHCI Mode" to disabled (this turns off USB 3.0 ports and make them function like USB 2.0), it now works perfectly. No random CUE crashes, and my devices work without errors!

 

Why didn't I ever think of this? VIA Chipset is known for its bad quality, especially for USB 3.0 controller faults...

 

Solution:

If you are using VIA USB Controller, AND you are willing to give up USB 3.0 (I don't have any USB 3.0 devices), follow these steps.

1. Boot into BIOS.

2. Find xHCI Mode (or similar) and disable it.

3. Exit and save from BIOS, meanwhile remove all corsair devices.

4. Connect all corsair devices according to the manual for USB 2.0. (for K65 you need to input the USB 2.0 first and then the Keyboard usb.)

 

This could also potentially help other people having the same issue in the forums. Maybe if somebody can try this and confirm it is working, perhaps sticky this post or something?

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...