K100 OPX - Line of keys stopped working

[Markoo7]

I have a brand new K100 keyboard and all of a sudden some keys stopped working (F5, 5, T, G, V, Num4).
I tried everything: used different computer, used with or without iCUE, tried ESC / FN + F4 recovery, Force Updated the keyboard firmware from iCUE, nothing worked.

Yesterday, after 3 days of having the keyboard totally unplugged, I tried it again on my PC and the keys worked perfectly a couple of seconds, then while I kept the faulty keys pressed, they started to lag more and more (the typing frequency dropped more and more) until they stopped working all together and it returned to my initial problem.

I took the keycaps out to check maybe there is some kind of dirt or whatever, but silly me, I didn't know that the interior of the key is actually completely sealed up and there's no space for anything to go in. 🙂 Tried also to use the default keyboard profile which has no predefined macro assigned anywhere (I was thinking that maybe my Caps Lock Disable function that I had in place on my custom profile "contaminated" somehow the other keys, but it's nothing like that, same issue on the default profile as well). Keyboard had no water issues whatsoever and was never unscrewed or tempered with.

I see that I am not the only one having this problem.
I've opened a ticket to support 4 days ago, didn't got any reply, not sure what to try out next.

Any thoughts please?
Appreciate any suggestion! Thank you!

Edited February 24 by Markoo7

[c-attack]

The two tools you have to work with are the soft reset and forced firmware update. The forced firmware requires it be connected by usb and then “check for update -> None -> Force update”. 
 

The soft update ESC key reset is detailed below. Be aware this will wipe any stored profiles on the KB.

https://help.corsair.com/hc/en-us/articles/360025465031-How-to-Reset-your-keyboard

 

If something is wrong on the circuit board, there not much you can do and I would contact Corsair Support for a replacement or the same path through the purchase vendor. 

Edited February 26 by c-attack

[Markoo7]

Already tried that. 😞 After firmware force update the keys are temporarily working. For a couple of seconds and somehow laggy. And then it's back to square 1.
Appreciate your suggestions though!

It's been a week now since I've requested support via ticket. Do you know if this is the average wait time or could I reach out to them differently?
Thank you!

[c-attack]

Support times appear to have lengthened since the holidays.  There is a massive crush each year during the Nov-Jan 1st period and I am not sure they have recovered.  

If the the forced firmware update works temporarily but then reverts, that seems like a clear hardware issue to me.  Incidentally, which firmware version do you have?  There are fair number of reported issues for one variant.

Edited February 27 by c-attack

[Markoo7]

Why do you think that this is a HW issue indication? How did you judged this? If it would be a HW problem, why would changing the SW make any difference for it?
Why would a broken circuit care about a driver? I mean you could be right, but I don't get the approach / logic.

Firmware is latest available for it: v0.32.262
Meaning no new updates are detected while checking. And obviously, force update is performed with the same version.

Can I get a different firmware from somewhere? At least I would like to try everything, just to be at peace with myself. 😞
Thank you!

[Corsair Notepad]

If the resets and forced firmware update did not resolve your issues you will need to reach out to our support team directly by opening a ticket at https://help.corsair.com and they will be happy to further assist.

[c-attack]

On 2/28/2023 at 2:24 AM, Markoo7 said:

 

Why do you think that this is a HW issue indication?

 

Because firmware addresses the MCU and hardware and those are not related to CUE. You can quit the software and see if the problem continues in the hardware operational state. I didn’t say anything about broken circuits or physical damage. 
 

You have the original version of the product which has very few issues. Most other K100 issues are going to be on a firmware version for the other model (1.xx) and do not relate to yours. You don’t need a new version and 0.32 is  current and has been in use for a very long time. This is not a common issue for that variant and it’s not going to be related to the firmware itself in any way.  If flashing the firmware to the MCU only solves it temporarily, something is wrong there.