K70 Lux Flicker on color change

Hey guys,

I got an issue with my K70 Lux. When applying any "dynamic" lightning effect (i.e. Rainbow) some of the keys will occasionally flicker when switching colors. Not all the time, not always the same. No pattern to it that I see.

So far I've tried:

- RMAing the keyboard. Replacement shows the same behavior.

- Updating the USB Controller driver (Intel USB 3.0 eXtensible-Hostcontroler" according to mainboard specs and device manager. Running driver version 10.0.14393.0. Latest driver according to Windows)

- Updated my BIOS and my Chipset driver to latest available.

- Switched through all my USB ports. Tried all possible cominations, neither USB 3.0 nor 2.0 help

- Reinstalled CUE (multiple times). Installed CUE V. 1.*

This is my most recent .log file

2017-02-17T19:33:29 I cue.init: CUE version: 2.10.71
2017-02-17T19:33:29 I cue.init: Updates server: https://www3.corsair.com/software/HID/
2017-02-17T19:33:29 I cue.init: Build type: Public Release
2017-02-17T19:33:29 I cue.init: Applicaiton ID: 9752
2017-02-17T19:33:30 I cue.init.font: Using Regular text font family: "Open Sans"
2017-02-17T19:33:30 I cue.init.font: Using Title text font family: "Gotham Bold"
2017-02-17T19:33:30 I cue.action.macro.win: Init time: 0.400209 (init: 0 reset: 0 )
2017-02-17T19:33:30 I cue.manifest: Tried 35 files.
2017-02-17T19:33:30 I cue.manifest: Loaded: 42 manifests.
2017-02-17T19:33:30 I cue.session: Locked changed to false
2017-02-17T19:33:30 I cue.session.win: Will notify 'connected changed to' with delay
2017-02-17T19:33:30 I cue.session: Local changed to true
2017-02-17T19:33:30 W cue.profiles.manager.serialization: "C:/Users/User/AppData/Roaming/Corsair/CUE/profiles/{14f36b83-5ccb-4d41-ae56-5200dedd0b71}.cueprofiledata" Could not detect cereal root node - likely due to empty or invalid input
2017-02-17T19:33:30 W cue.profiles.manager.serialization: "C:/Users/User/AppData/Roaming/Corsair/CUE/profiles/{949701c4-10dc-4cd8-b90b-1510f2a261c7}.cueprofiledata" Could not detect cereal root node - likely due to empty or invalid input
2017-02-17T19:33:31 I cue.session: Connected changed to true
2017-02-17T19:33:31 I cue.dev: Requesting working state enter because session connected.
2017-02-17T19:33:31 I cue.dev.enum.hid: Entering working state.
2017-02-17T19:33:31 I cue.sdk: Entering working state, session connected.
2017-02-17T19:33:31 I cue.sdk: Starting router.
2017-02-17T19:33:31 I cue.dev: Created new device object: K70 LUX RGB; ready: 0
2017-02-17T19:33:31 I cue.dev: Manifest for device vid=1852 pid=7022 not found.
2017-02-17T19:33:31 I cue.dev: Manifest for device vid=1532 pid=43 not found.
2017-02-17T19:33:31 I cue.dev: Attached to device object K70 LUX RGB: b=0 a=0
2017-02-17T19:33:31 I cue.dev: Attached to device object K70 LUX RGB: b=0 a=0
2017-02-17T19:33:31 I cue.dev: Failed to open device: vid=1b1c pid=1b33 path=\\?\hid#vid_1b1c&pid_1b33&mi_00#7&34f92246&1&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2017-02-17T19:33:31 I cue.dev: Manifest for device vid=1532 pid=43 not found.
2017-02-17T19:33:31 I cue.dev: Manifest for device vid=1532 pid=43 not found.
2017-02-17T19:33:31 I cue.dev: Failed to open device: vid=1b1c pid=1b33 path=\\?\hid#vid_1b1c&pid_1b33&mi_01&col01#7&9f19dbd&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2017-02-17T19:33:31 I cue.dev: Manifest for device vid=1532 pid=43 not found.
2017-02-17T19:33:31 I cue.dev: Manifest for device vid=1532 pid=43 not found.
2017-02-17T19:33:31 I cue.dev: Manifest for device vid=1532 pid=43 not found.
2017-02-17T19:33:31 I cue.dev: Attached to device object K70 LUX RGB: b=0 a=1
2017-02-17T19:33:31 I cue.dev: Initializing K70 LUX RGB...
2017-02-17T19:33:31 I cue.dev: Manifest for device vid=1532 pid=43 not found.
2017-02-17T19:33:31 I cue.dev: Initialized (st=1) K70 LUX RGB.
2017-02-17T19:33:31 I cue.lightings.player: Started lighting worker in 0x2978
2017-02-17T19:33:33 I cue.dev: Device insertion processing complete for K70 LUX RGB.
2017-02-17T19:33:33 W QFSFileEngine::open: No file name specified
2017-02-17T19:33:33 C cue.download.fw: Aborting idle process not supported.
2017-02-17T19:33:33 W QFile::remove: Empty or null file name
2017-02-17T19:33:34 I cue.dev: Buffer write failed, 1. request timed out for K70 LUX RGB
2017-02-17T19:33:35 I cue.dev: Buffer write failed, 1. request timed out for K70 LUX RGB
2017-02-17T19:42:31 I cue.dev: Buffer apply for Green failed. request timed out for K70 LUX RGB

I am using an Asus Z97-P.

What I noticed: Apparently there is a package drop in the log?

Also, the Keyboard just shows up "USB Input Device" in the device manager. All other devices there are listed by name.

No other devices connected over USB show any problem. Including a Razer mouse which also cycles colors.

Can someone help me?

The last three lines in the log would the time out error. Though i can't really suggest anything else to try as you have basically done all of the possible fixes.

If you can find a way to reproduce this, Then maybe something could be looked into.

The last three lines in the log would the time out error. Though i can't really suggest anything else to try as you have basically done all of the possible fixes.

 

If you can find a way to reproduce this, Then maybe something could be looked into.

No way to reproduce it. Seems to happen pretty much randomly. I've yet to test it on another pc.

[ame=https://youtu.be/4VGde2m8vAA]Here is a video of the flicker.[/ame]

yep, welcome to the club.

corsair doesn't care about it, they know this issue long time ago. even one time they posted answering that there's gonna be released a firmware update with the fix. still nothing up to today

bump

I've same issue there is still no fix :(

Same here, flickering happened first for a few weeks then red LED under one key died. Now it displays only green or blue.

Returning the keyboard, but it does make me wonder, this doesn't seem too rare of a phenomenon, would it not be better for Corsair to work on a fix for this than to ignore the issue, in terms of product replacement costs?

This is possibly due to software / firmware failing to manage voltage to the LED's sufficiently and thus overloading red LED which is most sensitive to any fluctuations.

yep, welcome to the club.

corsair doesn't care about it, they know this issue long time ago. even one time they posted answering that there's gonna be released a firmware update with the fix. still nothing up to today

they have never stated that there would be a fix for this through a firmware patch because the issue is on the user's computer.

Same here, flickering happened first for a few weeks then red LED under one key died. Now it displays only green or blue.

Returning the keyboard, but it does make me wonder, this doesn't seem too rare of a phenomenon, would it not be better for Corsair to work on a fix for this than to ignore the issue, in terms of product replacement costs?

 

This is possibly due to software / firmware failing to manage voltage to the LED's sufficiently and thus overloading red LED which is most sensitive to any fluctuations.

It's due to the USB controller failing to send the signal for a color change, aka dropping a packet. And once the packet has been dropped you can go back in time and patch it in so the flickering occurs.

they have never stated that there would be a fix for this through a firmware patch because the issue is on the user's computer.

 

 

 

It's due to the USB controller failing to send the signal for a color change, aka dropping a packet. And once the packet has been dropped you can go back in time and patch it in so the flickering occurs.

Maybe they should make complex tutorial how to fix it by user then instead of copy-pasting "update drivers/firmware if that doesn't help send it back... etc".

Anyway I don't think it's user's computer problem because me and many other users have never had any sort of usb controller problems it occurs only with corsair board.

Maybe they should make complex tutorial how to fix it by user then instead of copy-pasting "update drivers/firmware if that doesn't help send it back... etc".

 

Anyway I don't think it's user's computer problem because me and many other users have never had any sort of usb controller problems it occurs only with corsair board.

What can they tell you that would fix it.

You don't seem to understand how time sensitive packets work. Just because your files transfers over USB doesn't mean the controller got every packet. They're not going to inform you oh sir we dropped packet number 183 would you like us to re-transfer it so your file isn't corrupted? If they miss a packet it can be resent right away and it won't matter. But with something like lighting if a packet is dropped what do you expect the controller or software to do. Turn back time and resend the packet. By the time the keyboard notices the bad packet of info its already half a second too late.

And yes people have this issue but there are also people who bought a USB 3.0 add on card and fixed this issue. How do you explain that? The keyboard magically fixed itself because oh add on card?

What can they tell you that would fix it.

 

You don't seem to understand how time sensitive packets work. Just because your files transfers over USB doesn't mean the controller got every packet. They're not going to inform you oh sir we dropped packet number 183 would you like us to re-transfer it so your file isn't corrupted? If they miss a packet it can be resent right away and it won't matter. But with something like lighting if a packet is dropped what do you expect the controller or software to do. Turn back time and resend the packet. By the time the keyboard notices the bad packet of info its already half a second too late.

 

And yes people have this issue but there are also people who bought a USB 3.0 add on card and fixed this issue. How do you explain that? The keyboard magically fixed itself because oh add on card?

The keyboards I know with this magical issue because usb bad packets are on those keyboard from Corsair (k70, some strafe)... I can't find this issue at other brands keyboards with the same lighting functions (rgb, transitions)

I really like the keyboard i'm using (k70 lux rgb), but it's a shame, with that price, I have to stay with static colors because it "can't handle" some basic transitions without those annoying flicks... because of my bad usb controllers of course, lol.

Only corsair have this issue! Magically...

ps: someday with time i'm gonna search for that comment from a corsair member saying about the firmware with the fix to be released after CUE 2 finished

The keyboards I know with this magical issue because usb bad packets are on those keyboard from Corsair (k70, some strafe)... I can't find this issue at other brands keyboards with the same lighting functions (rgb, transitions)

 

I really like the keyboard i'm using (k70 lux rgb), but it's a shame, with that price, I have to stay with static colors because it "can't handle" some basic transitions without those annoying flicks... because of my bad usb controllers of course, lol.

 

Only corsair have this issue! Magically...

 

ps: someday with time i'm gonna search for that comment from a corsair member saying about the firmware with the fix to be released after CUE 2 finished

True you might not have this problem with other brands, I don't doubt that, but if you look on Logitech's forum or Razers they have the same complaints too. So it's not just Corsair, but if you want to magically ignore the fact other companies have the same issue then goes ahead. If someone else's board doesn't flicker for you get it, what else can you do? I haven't seen any good solutions to this issue from them either other than what Corsair provides.

If you don't want to try getting an add-on card or try messing with your system then all I can say is stay away from Razer, Logitech is a mich better buy.

@Inheritance

Is there any other way to fix it without buying usb add-on card?

Maybe you have some experience with fixing it with software?

I'm using MSI Gaming 3 Z97 board and as I said all drivers are updated (atleast Windows says so). In your "Quick Fux Guide" you said about Intel usb cotroller but I can't find one to this chipset on their site.

@Inheritance

 

Is there any other way to fix it without buying usb add-on card?

Maybe you have some experience with fixing it with software?

 

I'm using MSI Gaming 3 Z97 board and as I said all drivers are updated (atleast Windows says so). In your "Quick Fux Guide" you said about Intel usb cotroller but I can't find one to this chipset on their site.

If it was a software fix it would have to come from Intel, AMD, one of the board partners or USB controller manufacturers. But I doubt even those guys can fix a hardware problem with pure software.

Just because windows says it's up to date doesn't mean it's the drivers from the manufacturers. Windows will just install their generic driver's so everyday users don't have to fuss about. And trust me their approach to drivers is if USB driver in slot = data being transferred then success. Even if their dropping packets left and right a normal user would never notice a difference because they don't even know what the transfer speed should be, and all they care about is my files better be on my compute.

https://downloadcenter.intel.com/product/82012/Intel-Z97-Chipset

^ that should be the driver for the chipset. And it appears you have 2 USB 2.0 ports try using those. They are labeled as "gaming ports" on the product page, so I'm guessing they added some special sauce. You can also try contacting MSI and asking them if there are any settings you should be turning of or on in their BIOS.