Jump to content
Corsair Community

K70 Device Malfunction


knives00005

Recommended Posts

Hello!

 

I have a K70 RGB, and it's been working ok but a few weeks after an update to Windows 10 (an update, not the update to get 10), my keyboard randomly disconnects and re-connects.

 

I have a profile of moving rainbows, and it's stopping and it's saying on the CUE "Device Malfunction". They keyboard itself still works though.

 

I have tried re-flashing the keyboard, reinstalling CUE, getting a different profile (profiles that promotes static lighting doesn't seem to trigger the issue very much).

 

The logs says the following:

 

[2016-03-10T05:40:41]: Initialized (st=1) K70 RGB.

[2016-03-10T05:40:41]: Device insertion processing complete for K70 RGB.

[2016-03-10T05:41:14]: Device vid=1b1c pid=1b13 is marked 'slow startup'.

[2016-03-10T05:41:15]: Failed to open device: vid=1b1c pid=1b13 path=\\?\hid#vid_1b1c&pid_1b13#7&3365770d&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-03-10T05:41:17]: Device vid=1b1c pid=1b13 is marked 'slow startup'.

[2016-03-10T05:41:17]: Device vid=1b1c pid=1b13 is marked 'slow startup'.

[2016-03-10T05:41:17]: Device vid=1b1c pid=1b13 is marked 'slow startup'.

[2016-03-10T05:41:17]: Device vid=1b1c pid=1b13 is marked 'slow startup'.

[2016-03-10T05:41:17]: Device vid=1b1c pid=1b13 is marked 'slow startup'.

[2016-03-10T05:41:18]: Created new device object: K70 RGB; ready: 0

[2016-03-10T05:41:18]: Attached to device object K70 RGB: b=1 a=1

[2016-03-10T05:41:18]: Attached to device object K70 RGB: b=1 a=0

[2016-03-10T05:41:18]: Initializing K70 RGB...

[2016-03-10T05:41:18]: Failed to open device: vid=1b1c pid=1b13 path=\\?\hid#vid_1b1c&pid_1b13&mi_00#8&1d4a5187&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-03-10T05:41:18]: Failed to open device: vid=1b1c pid=1b13 path=\\?\hid#vid_1b1c&pid_1b13&mi_01&col01#8&586c542&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-03-10T05:41:18]: Initialized (st=1) K70 RGB.

[2016-03-10T05:41:18]: Device insertion processing complete for K70 RGB.

[2016-03-10T05:41:35]: SdkController. Requesting working state leave because of transition to Suspended or Shutdown state.

[2016-03-10T05:41:35]: Requesting working state leave because of transition to Suspended or Shutdown state.

[2016-03-10T05:41:35]: Leaving working state.

Link to comment
Share on other sites

Few things come to mind:

Try different USB ports. USB3.0 x 1 cable or USB2.0 x 2 cables.

Uninstall HID keyboard devices in Device manager and then replug the keyboard.

 

For more information, one of our awesome users have documented a meticulously thorough guide here.

Link to comment
Share on other sites

Not on my end. How many times per week/day does it happen?

 

It happens like every few seconds. It works - basic function like typing, adjusting volume, Windows key, but then no running/moving/reactive LEDs for me.

 

And it disconnects every so often.

Link to comment
Share on other sites

It happens like every few seconds. It works - basic function like typing, adjusting volume, Windows key, but then no running/moving/reactive LEDs for me.

 

And it disconnects every so often.

 

I would contact Corsair Support and see if you need to RMA. I know windows updates seem to mess things up for the Scimitar (it uninstalls drivers) but I'm not aware of any issues they bring up with the RGB keyboards. I would not be surprised though if the windows update messed up a driver installation.

 

Just to be safe, make sure when you are using USB 3.0 that you only use 1 USB connector (the one with the keyboard on it) and when using USB 2.0, use both connectors - plugging in the connector with the keyboard on it last.

Link to comment
Share on other sites

I would contact Corsair Support and see if you need to RMA. I know windows updates seem to mess things up for the Scimitar (it uninstalls drivers) but I'm not aware of any issues they bring up with the RGB keyboards. I would not be surprised though if the windows update messed up a driver installation.

 

Just to be safe, make sure when you are using USB 3.0 that you only use 1 USB connector (the one with the keyboard on it) and when using USB 2.0, use both connectors - plugging in the connector with the keyboard on it last.

 

Yep, I have a ticket open, sadly Corsair doesn't do RMA on the PH.

They did offer me a refund, however idk if they still would do it provided I live in the Philippines.

 

I would prefer to get another keyboard than RMA, I like this keyboard.

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...