k70 rgb rapidfire K70 RGB MK2 LP hang up

Hello all,

i need some help with my brand new K70 RGB MK2 LP.

The keyboard is setup since a few hours and i getting sporadic hang ups.... in 1-2 hours window.

The last FW 3.24 is used. The key A-Z still working, but the RGB effects stop and for exampe the Win Key locker on top is out of service.

The iCUE tray icon shows a warning sign!

I did a restart of iCUE service via the software --> no change

I close the iCUE app in sys tray and restart --> no change

I need to unplug the K70 and reconnect --> works again.

2019-02-12T20:44:15 I cue.devices.nxp: Buffer write, 1. failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995
2019-02-12T20:44:15 I cue.devices.nxp: Buffer write, 2. failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:15 I cue.devices.nxp: Buffer write, 2. failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995
2019-02-12T20:44:15 I cue.devices.nxp: Buffer write, 1. failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:15 I cue.devices.nxp: Buffer write, 1. failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995
2019-02-12T20:44:15 I cue.devices.nxp: Buffer write, 2. failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:15 I cue.devices.nxp: Buffer write, 2. failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995

2019-02-12T20:44:26 I cue.devices: Begin attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_01#9&3b878140&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2019-02-12T20:44:26 I cue.devices: End attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_01#9&3b878140&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0
2019-02-12T20:44:26 I cue.devices: Created new device"K70 RGB MK.2 LP" (vid=1b1c, pid=1b55); ready:false
2019-02-12T20:44:26 I cue.devices: Begin attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col02#9&296bacf0&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2019-02-12T20:44:26 I cue.devices: End attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col02#9&296bacf0&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0
2019-02-12T20:44:26 I cue.devices: Begin attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col03#9&296bacf0&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2019-02-12T20:44:26 I cue.devices: End attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col03#9&296bacf0&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0
2019-02-12T20:44:26 I cue.devices: Begin attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col04#9&296bacf0&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2019-02-12T20:44:26 I cue.devices: End attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col04#9&296bacf0&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1
2019-02-12T20:44:26 I cue.devices: Initializing "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55)

2019-02-12T20:44:26 I cue.devices.nxp: Get device info prepare failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:26 I cue.devices.nxp: Get device info prepare failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995
2019-02-12T20:44:27 I cue.devices.nxp: Get device info prepare failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:27 I cue.devices.nxp: Get device info prepare failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995
2019-02-12T20:44:27 I cue.devices.nxp: Get device info prepare failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:27 I cue.devices.nxp: Get device info prepare failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995
2019-02-12T20:44:27 I cue.devices.nxp: Initializing K70 RGB MK.2 LP : spent all tries on getDeviceInfo().
2019-02-12T20:44:27 I cue.devices.nxp: Initializing  K70 RGB MK.2 LP : failed to read proto version.
2019-02-12T20:44:27 I cue.devices.nxp: Get device info prepare failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:27 I cue.devices.nxp: Get device info prepare failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995
2019-02-12T20:44:27 I cue.devices.nxp: Get device info prepare failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:27 I cue.devices.nxp: Get device info prepare failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995
2019-02-12T20:44:27 I cue.devices.nxp: Get device info prepare failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:27 I cue.devices.nxp: Get device info prepare failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995
2019-02-12T20:44:27 I cue.devices: Initialized false "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55)
2019-02-12T20:44:28 I cue.devices: Device object failed to initialize, so it won't be registered with application susbystems. K70 RGB MK.2 LP.
2019-02-12T20:44:28 I cue.session: Connected changed to true
2019-02-12T20:44:28 C cue.devices.manifest: Cannot find path for manifest key (vid=1b1c, pid=3)
2019-02-12T20:44:28 I cue.devices.nxp: Get device info prepare failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:28 I cue.devices.nxp: Get device info prepare failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995
2019-02-12T20:44:28 I cue.devices.nxp: Get device info prepare failed.  request timed out for K70 RGB MK.2 LP
2019-02-12T20:44:28 I cue.devices.nxp: Get device info prepare failed. Device: "K70 RGB MK.2 LP" , Execution result = 0 , result = false , platform error code = 995

2019-02-12T20:45:03 I cue.hid_device_detector: Device: "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col04#9&296bacf0&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" removed.
2019-02-12T20:45:03 W cue.devices: Device "K70 RGB MK.2 LP" worker thread has stopped

2019-02-12T20:45:12 I cue.devices: Begin attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_01#9&3b878140&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2019-02-12T20:45:12 I cue.hid_device_detector: Device: "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col03#9&296bacf0&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened.
2019-02-12T20:45:12 I cue.hid_device_detector: Device: "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col04#9&296bacf0&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened.
2019-02-12T20:45:12 I cue.devices: End attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_01#9&3b878140&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0
2019-02-12T20:45:12 I cue.devices: Created new device"K70 RGB MK.2 LP" (vid=1b1c, pid=1b55); ready:false
2019-02-12T20:45:12 I cue.devices: Begin attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col02#9&296bacf0&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2019-02-12T20:45:12 I cue.devices: End attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col02#9&296bacf0&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0
2019-02-12T20:45:12 I cue.devices: Begin attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col03#9&296bacf0&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2019-02-12T20:45:12 I cue.devices: End attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col03#9&296bacf0&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 0
2019-02-12T20:45:12 I cue.devices: Begin attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col04#9&296bacf0&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0
2019-02-12T20:45:12 I cue.devices: End attaching to "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55) "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col04#9&296bacf0&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1
2019-02-12T20:45:12 I cue.devices: Initializing "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55)
2019-02-12T20:45:12 C cue.hid_device_detector: Failed to open device: "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col05#9&296bacf0&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2019-02-12T20:45:12 C cue.hid_device_detector: Failed to open device: "\\\\?\\hid#vid_1b1c&pid_1b55&mi_00&col01#9&296bacf0&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}"
2019-02-12T20:45:12 I cue.hid_device_detector: Mark all tasks as finished.
2019-02-12T20:45:12 I cue.devices: Initialized true "K70 RGB MK.2 LP" (vid=1b1c, pid=1b55)
2019-02-12T20:45:12 C cue.devices: Unknown command in NxpPhysicalHidDevice: 56
2019-02-12T20:45:13 I cue.lightings.direct_player: Started lighting worker in 0x2cfc
2019-02-12T20:45:13 I cue.devices: Device insertion processing complete for K70 RGB MK.2 LP (vid=1b1c, pid=1b55)

Here is a logfile from iCUE can somebody assist me please?! :idea:

Hi Corsair Calico Jack,

the problem occur at last time some minutes after boot. I think no energy safer is active at this time, but i keep you hint in mind.

Currently i testing my last action. I reflash the K70 firmware with iCUE.

I know the last FW was installed but i repeat the process and load it again to the keyboard, let's see what happen.

If the problem reoccur i will change the USB energy safer profile at my Win10.

Did anybody else having the same problem in the past ??

sounds like the USB is going idle.

 

turn off USB selective suspend: https://www.windowscentral.com/how-prevent-windows-10-turning-usb-devices

 

If that does not work, try turning down your keyboard's polling rate in iCUE's Settings options.

What a nightmare...... the reflash of the Firmware did not solve the issue.

In the next step i try your hint to the "USB selective suspend" settings.

I edit the windows energy profile an restart the PC.

After 30-60 Min the problem was visible again..... :!:

Any further ideas ?

I think the problem is discoverd :mad: found an older topic with similar issues.

LINK

I am using an ATEN KVM switch to connect an server, my company notebook and gaming PC together with one set of mice, keyboard and screen.

It seems the K70 willl not work correctly with KVM environment :!:

All other EQ is working fine with this KVM, the Corsair M65Pro as well.

Only the K70 getting stuck :evil:

I have connected the K70 with keyboard plug into a USB2.0 port and passthrough plug into USB3.0 port of my PC.

It seems to be working correctly now.

A strange scenaro is if i using simply the keyboard plug of the K70.

In this state the RGB getting wrong effects. If i setup static color blue it result a red output :eek:

So in my option the K70 has such a high power usage and need two USB ports with sufficient 5V output.

If i connect the keyboard plug into the KVM and passthrough plug into USB3.0 port of my PC getting the same negative results.

In the past i had no issues with any keyboard at this environment.

I am really disappointed that the K70 will not work with my KVM switch!

Has anybody get managed to use a KVM switch with the K70 ???