Key chatter?... Or loose fingers?

[Rechinan]

I purchased a K70 RGB with MX red switches late in the summer last year, and needless to say i love it, but i have come across a double hit effect on several keys (`,Numpad 8, o and on occasion p). I read that this could be chatter but also could be my typing style, as its my first mechanical keyboard.

 

I read the unofficial faq and ran EK's Switch Hitter but received no chatter detection until i changed the threshold to above 24ms.

 

I do wish this isn't my typing style as I find membrane keyboards hard to type on now.

 

My main question is this, can I RMA this or is this just my peasant fingers succumbing to the effect of no feedback on actuation after years of membrane keyboards?

 

P.S I have attached screenshots of Switch Hitter and my log file in case this helps.

 

Thanks in advance c:

RechinanEKSH.txt

[Toasted]

Yes, the keyboard can be replaced via RMA. But i'm not too sure whether it may be related to key chatter.

 

Have you tried a different USB port and computer?

Have you tried reflashing the firmware?

Do you have the latest BIOS and chipset drivers installed?

Move the BIOS switch to a different polling rate and BIOS mode. Is the repeat issue still present?

[Rechinan]

Yes, the keyboard can be replaced via RMA. But i'm not too sure whether it may be related to key chatter.

 

Have you tried a different USB port and computer?

Have you tried reflashing the firmware?

Do you have the latest BIOS and chipset drivers installed?

Move the BIOS switch to a different polling rate and BIOS mode. Is the repeat issue still present?

 

Hey I appreciate the reply, so the polling rate made no difference i originally thought this and tried different positions over a few days to no avail. My bios/chipset drivers are all up to date also. Different usb ports are the same unfortunately.

 

I'll try a reflash and get back to you. Thanks again o7

 

Edit to follow...EDIT No change after a reflash of the firmware

[Toasted]

Could possibly be a faulty keyboard.

 

You can request an RMA to replace the keyboard. Make sure you upload a picture of your invoice as proof of purchase.

[Rechinan]

I'll get on it, thanks for the help.

[Toasted]

Actually, on second thoughts, i think it may be just your finger placement as the red switches require very little pressure to activate.

 

Corsair provides a two year warranty with their keyboards. I think it will be best to get used to the keyboard first as this is your first mechanical keyboard.

[Greybeard]

If it's really a faulty KB, then I don't have problems sending a replacement via RMA. You just have to create a ticket and we'll take care of it.

 

BUT before doing so, I would suggest that you contact our support guys and ask them to do a hard reset on your KB and see if that will make a difference.

 

OR perhaps Toasted is right, it's just a matter of getting used to it as Cherry MX Red switches are really sensitive.

[Rechinan]

Taking on board what both have you have put across. I'm deciding to hold off on the RMA request but I will contact support about a hard reset.

 

I feel that muscle memory should have taken over by now as I bought the keyboard back in August of last year. Nevertheless what harm can a few more weeks of use do except possibly fix my problem.

 

Thanks to both of you for the replies, I'll update you on my progress as and when I can.

[Rechinan]

It seems the guys over at support just decided to go with an RMA after the hard reset failed, thanks so much for the help guys. Felt awkward asking about this c:

[Toasted]

Not a problem, If you do ever encounter a issue. You can update this thread or contact Corsair directly via your ticket.

[marcoycoco]

Hello, I've just ssended a RMMA ticket because mmy K70 RGB started failing onnly one month after buying. I've tryed to reinstall the software, change the switch to other possitions and channging the 3.0 usb connectionn. As you can see I can't finnd a solutionn for this. MMy keaboard is absolutely CLEAN and have not been exposed to any dirt or liquids... It has been a lot of money innvestmment for a keyboard that doesn¡t work as my old 20$ one that I ussed during 10 years!!!! That's really dissapointing...

[Corsair Henry]

Hello, I've just ssended a RMMA ticket because mmy K70 RGB started failing onnly one month after buying. I've tryed to reinstall the software, change the switch to other possitions and channging the 3.0 usb connectionn. As you can see I can't finnd a solutionn for this. MMy keaboard is absolutely CLEAN and have not been exposed to any dirt or liquids... It has been a lot of money innvestmment for a keyboard that doesn¡t work as my old 20$ one that I ussed during 10 years!!!! That's really dissapointing...

 

stating that it's Failing is kind of broad. I know you mentioned that you have submitted a RMA already, but if you provide us with some symptoms we can try to help here as well.

[marcoycoco]

:(: Thannkss, Henry ... I'mm sorry, thiss fail drives me crazy... I's hard to think that this is a hardware problem, because letters started failing one after other almost each day! As you can see fail means repeating letter, doubling themm.. first was the N, after the MM, S T W... I have been using mechanical keyboards (cherry) for mmany yearss, and I know how to type :(

 

I can't provide no mmore clues about WHY is failing, I only know that the keyboard. Frommm the first day I used a single 3.0 usb connection and provided softwware from your web and started failing, as I said, in less than a month.

 

As you see mmy writing is NOT acceptable on working sessions and I use an "antichatter" softtware nammed kcfix0.0.1 And I have to adjust it at 100ms. Every time I use the keyboard the alarmm sound for a double-pressed key activates and I realize that there are too mmuch of themm.

 

(Now using the kcfix) Problems dissapear and no more keys are doubled, but the problem is I have a LOT of lag in my games and some programs are failing in some actions. I want to know if there is some else I can do under your knowdeledge...

 

THANKS

[Hostage83]

Hello,

 

I just encountered the same problem with my keyboard. Vengeance K70 Black, Cherry MX Brown (US Layout)

My letter "K" would double, triple register when typing a few minutes ago.

Opened to notepad to see what was wrong and did this :

 

kkkkkkkkkk

kkkkkkkkkk

 

I wrote "k" 10 times in a row.

Now it seems to work but it looked like this when i did it a few minutes ago :

 

kkkkkkkkkkkk

kkkkkkkkkkk

kkkkkkkkkk

kkkkkkkkkkkk

kkkkkkkkkk

 

For some reason it seems fixed now.

I had the same problem with the letter "E" and "D" a few days ago and it disappeared for some reason.

 

Now I wonder, is the worst yet to come?

It seems that the keys I use the most are showing these symptoms. My keyboard is only 2 months old.

 

Edit : Nope, character "K" is still doing it. Is my keyboard faulty?

Edit 2 : Character "K" is working again as normal. This is really weird.

Edit 3 : It's back again. I used Switch Hitter with Chatter threshold @ 10 and these are the results :

31:39.0292 K (0x4B, BIOS 0x25) DOWN

31:39.0323 K (0x4B, BIOS 0x25) UP -> 59ms

31:39.0464 K (0x4B, BIOS 0x25) DOWN

31:39.0526 K (0x4B, BIOS 0x25) UP -> 64ms

31:39.0682 K (0x4B, BIOS 0x25) DOWN

31:39.0744 K (0x4B, BIOS 0x25) UP -> 60ms

31:39.0900 K (0x4B, BIOS 0x25) DOWN

31:39.0963 K (0x4B, BIOS 0x25) UP -> 68ms

31:40.0103 K (0x4B, BIOS 0x25) DOWN

31:40.0134 K (0x4B, BIOS 0x25) UP -> 20ms

31:40.0134 K (0x4B, BIOS 0x25) DOWN

31:40.0134 K (0x4B, BIOS 0x25) CHATTER DETECTED -> 7ms

31:40.0181 K (0x4B, BIOS 0x25) UP -> 44ms

31:40.0322 K (0x4B, BIOS 0x25) DOWN

31:40.0400 K (0x4B, BIOS 0x25) UP -> 68ms

31:40.0556 K (0x4B, BIOS 0x25) DOWN

31:40.0618 K (0x4B, BIOS 0x25) UP -> 68ms

31:40.0774 K (0x4B, BIOS 0x25) DOWN

31:40.0852 K (0x4B, BIOS 0x25) UP -> 68ms

31:41.0008 K (0x4B, BIOS 0x25) DOWN

31:41.0086 K (0x4B, BIOS 0x25) UP -> 80ms

31:41.0258 K (0x4B, BIOS 0x25) DOWN

31:41.0304 K (0x4B, BIOS 0x25) UP -> 52ms

31:41.0460 K (0x4B, BIOS 0x25) DOWN

31:41.0538 K (0x4B, BIOS 0x25) UP -> 72ms

31:41.0710 K (0x4B, BIOS 0x25) DOWN

31:41.0788 K (0x4B, BIOS 0x25) UP -> 76ms

31:41.0928 K (0x4B, BIOS 0x25) DOWN

31:41.0991 K (0x4B, BIOS 0x25) UP -> 68ms

31:42.0162 K (0x4B, BIOS 0x25) DOWN

31:42.0209 K (0x4B, BIOS 0x25) UP -> 51ms

31:42.0381 K (0x4B, BIOS 0x25) DOWN

31:42.0428 K (0x4B, BIOS 0x25) UP -> 39ms

31:42.0568 K (0x4B, BIOS 0x25) DOWN

31:42.0662 K (0x4B, BIOS 0x25) UP -> 96ms

31:42.0802 K (0x4B, BIOS 0x25) DOWN

31:42.0864 K (0x4B, BIOS 0x25) UP -> 60ms

31:43.0036 K (0x4B, BIOS 0x25) DOWN

31:43.0083 K (0x4B, BIOS 0x25) UP -> 48ms

31:43.0254 K (0x4B, BIOS 0x25) DOWN

31:43.0317 K (0x4B, BIOS 0x25) UP -> 60ms

31:43.0473 K (0x4B, BIOS 0x25) DOWN

31:43.0551 K (0x4B, BIOS 0x25) UP -> 76ms

31:43.0707 K (0x4B, BIOS 0x25) DOWN

31:43.0769 K (0x4B, BIOS 0x25) UP -> 68ms

31:43.0941 K (0x4B, BIOS 0x25) DOWN

31:43.0988 K (0x4B, BIOS 0x25) UP -> 43ms

31:44.0144 K (0x4B, BIOS 0x25) DOWN

31:44.0222 K (0x4B, BIOS 0x25) UP -> 80ms

31:44.0393 K (0x4B, BIOS 0x25) DOWN

31:44.0456 K (0x4B, BIOS 0x25) UP -> 68ms

31:44.0612 K (0x4B, BIOS 0x25) DOWN

31:44.0674 K (0x4B, BIOS 0x25) UP -> 60ms

31:44.0830 K (0x4B, BIOS 0x25) DOWN

31:44.0877 K (0x4B, BIOS 0x25) UP -> 48ms

31:45.0064 K (0x4B, BIOS 0x25) DOWN

31:45.0126 K (0x4B, BIOS 0x25) UP -> 60ms

31:45.0267 K (0x4B, BIOS 0x25) DOWN

31:45.0329 K (0x4B, BIOS 0x25) UP -> 72ms

31:45.0501 K (0x4B, BIOS 0x25) DOWN

31:45.0579 K (0x4B, BIOS 0x25) UP -> 71ms

31:45.0719 K (0x4B, BIOS 0x25) DOWN

31:45.0782 K (0x4B, BIOS 0x25) UP -> 59ms

31:45.0938 K (0x4B, BIOS 0x25) DOWN

31:46.0000 K (0x4B, BIOS 0x25) UP -> 55ms

31:46.0156 K (0x4B, BIOS 0x25) DOWN

31:46.0156 K (0x4B, BIOS 0x25) UP -> 8ms

31:46.0172 K (0x4B, BIOS 0x25) DOWN

31:46.0172 K (0x4B, BIOS 0x25) CHATTER DETECTED -> 9ms

31:46.0218 K (0x4B, BIOS 0x25) UP -> 47ms

31:46.0359 K (0x4B, BIOS 0x25) DOWN

31:46.0437 K (0x4B, BIOS 0x25) UP -> 76ms

31:46.0624 K (0x4B, BIOS 0x25) DOWN

31:46.0686 K (0x4B, BIOS 0x25) UP -> 51ms

31:46.0858 K (0x4B, BIOS 0x25) DOWN

31:46.0936 K (0x4B, BIOS 0x25) UP -> 68ms

31:47.0061 K (0x4B, BIOS 0x25) DOWN

31:47.0139 K (0x4B, BIOS 0x25) UP -> 72ms

31:47.0310 K (0x4B, BIOS 0x25) DOWN

31:47.0357 K (0x4B, BIOS 0x25) UP -> 52ms

31:47.0529 K (0x4B, BIOS 0x25) DOWN

31:47.0607 K (0x4B, BIOS 0x25) UP -> 80ms

31:47.0778 K (0x4B, BIOS 0x25) DOWN

31:47.0825 K (0x4B, BIOS 0x25) UP -> 53ms

31:47.0981 K (0x4B, BIOS 0x25) DOWN

31:48.0044 K (0x4B, BIOS 0x25) UP -> 68ms

31:48.0200 K (0x4B, BIOS 0x25) DOWN

31:48.0262 K (0x4B, BIOS 0x25) UP -> 60ms

31:48.0418 K (0x4B, BIOS 0x25) DOWN

31:48.0434 K (0x4B, BIOS 0x25) UP -> 12ms

31:48.0434 K (0x4B, BIOS 0x25) DOWN

31:48.0449 K (0x4B, BIOS 0x25) CHATTER DETECTED -> 8ms

31:48.0496 K (0x4B, BIOS 0x25) UP -> 56ms

31:48.0668 K (0x4B, BIOS 0x25) DOWN

31:48.0714 K (0x4B, BIOS 0x25) UP -> 44ms

31:48.0870 K (0x4B, BIOS 0x25) DOWN

31:48.0886 K (0x4B, BIOS 0x25) UP -> 8ms

31:48.0886 K (0x4B, BIOS 0x25) DOWN

31:48.0886 K (0x4B, BIOS 0x25) CHATTER DETECTED -> 8ms

31:48.0933 K (0x4B, BIOS 0x25) UP -> 44ms

31:49.0104 K (0x4B, BIOS 0x25) DOWN

31:49.0167 K (0x4B, BIOS 0x25) UP -> 56ms

31:49.0338 K (0x4B, BIOS 0x25) DOWN

31:49.0401 K (0x4B, BIOS 0x25) UP -> 60ms

31:49.0541 K (0x4B, BIOS 0x25) DOWN

31:49.0604 K (0x4B, BIOS 0x25) UP -> 60ms

31:49.0791 K (0x4B, BIOS 0x25) DOWN

31:49.0822 K (0x4B, BIOS 0x25) UP -> 37ms

31:49.0994 K (0x4B, BIOS 0x25) DOWN

31:50.0056 K (0x4B, BIOS 0x25) UP -> 60ms

31:50.0196 K (0x4B, BIOS 0x25) DOWN

31:50.0212 K (0x4B, BIOS 0x25) UP -> 12ms

31:50.0228 K (0x4B, BIOS 0x25) DOWN

31:50.0274 K (0x4B, BIOS 0x25) UP -> 44ms

31:50.0446 K (0x4B, BIOS 0x25) DOWN

31:50.0446 K (0x4B, BIOS 0x25) UP -> 12ms

31:50.0477 K (0x4B, BIOS 0x25) DOWN

31:50.0524 K (0x4B, BIOS 0x25) UP -> 36ms

31:50.0664 K (0x4B, BIOS 0x25) DOWN

31:50.0664 K (0x4B, BIOS 0x25) UP -> 8ms

31:50.0680 K (0x4B, BIOS 0x25) DOWN

31:50.0680 K (0x4B, BIOS 0x25) CHATTER DETECTED -> 8ms

31:50.0711 K (0x4B, BIOS 0x25) UP -> 36ms

31:50.0898 K (0x4B, BIOS 0x25) DOWN

31:50.0945 K (0x4B, BIOS 0x25) UP -> 52ms

31:51.0132 K (0x4B, BIOS 0x25) DOWN

31:51.0179 K (0x4B, BIOS 0x25) UP -> 56ms

31:51.0335 K (0x4B, BIOS 0x25) DOWN

31:51.0398 K (0x4B, BIOS 0x25) UP -> 68ms

31:51.0554 K (0x4B, BIOS 0x25) DOWN

31:51.0632 K (0x4B, BIOS 0x25) UP -> 72ms

31:51.0772 K (0x4B, BIOS 0x25) DOWN

31:51.0850 K (0x4B, BIOS 0x25) UP -> 68ms

31:51.0990 K (0x4B, BIOS 0x25) DOWN

31:52.0053 K (0x4B, BIOS 0x25) UP -> 68ms

31:52.0209 K (0x4B, BIOS 0x25) DOWN

31:52.0271 K (0x4B, BIOS 0x25) UP -> 68ms

31:52.0412 K (0x4B, BIOS 0x25) DOWN

31:52.0490 K (0x4B, BIOS 0x25) UP -> 72ms

31:52.0677 K (0x4B, BIOS 0x25) DOWN

31:52.0724 K (0x4B, BIOS 0x25) UP -> 56ms

[Toasted]

Can you try the keyboard on another computer? If it appears/disappears randomly, it could be either the keyboard or the computer.

 

Have you also tried changing the polling rate?

[Hostage83]

Can you try the keyboard on another computer? If it appears/disappears randomly, it could be either the keyboard or the computer.

 

Have you also tried changing the polling rate?

 

Thank you for replying.

I doubt it's my pc but I am not counting anything out. My previous keyboard which was 8 years old never did this. My pc is fully updated.

The character "K" is working as normal again. This is driving me nuts.

It seems to disapear if "spam" the key for a while. They key made a squeaky noise when it was chattering. That squeaky noise is gone for now.

 

So far it's working again. Let's hope it stays this way. I really don't want to rma this unless it's really necessary. I love this thing and I don't have a backup keyboard.

Should I put a higher or lower polling rate if the problem occurs again?

 

Thx

 

Edit : Misunderstood polling rate. I thought you ment chatter threshold. I'll change the switch if it happens again.