Question Issues with Corsair Peripherals ?

[EyesOfJack]

Hi there! Have been having a few issues recently with the following Corsair peripherals:

With the K70 MK.2 Keyboard the volume wheel seems to be less sensitive than it used to be. Seems to occasionally put volume up when I'm scrolling down, and vice versa. Unsure if this is a wear and tear issue! Have had the keyboard since 2020.

With the Glaive RGB Pro Mouse, I occasionally have double click issues, and the scroll wheel does a similar thing to the keyboard where it randomly scrolls the opposite direction sometimes. I have reset the mouse a bunch of times and reinstalled iCUE!

Finally, with the SP120 Fans, the lighting on them seems to glitch out occasionally. They sit on the rainbow wave lighting link so that all peripherals share the same lighting. However, the fans occasionally flash off, or flash back to the start of the sequence (seemingly at random). Sometimes this issue occurs more often, sometimes not at all...

I have sent off a support ticket to Corsair, but believe the responses will just be to reinstall iCUE again. Was just wondering if anyone had any similar issues and had fixes!

Many thanks

 

[Aeacus]

With the Glaive mouse, I occasionally have double click issues, and the scroll wheel does a similar thing to the keyboard where it randomly scrolls the opposite direction sometimes.

Corsair mice have model specific issues.

E.g;
Corsair Sabre RGB mice will produce, after ~1 year of usage, double- and triple-click issue on left click button, despite you only clicking it once.
It has happened with 3x Sabre RGB mice i've owned. Both me and missus used to use that mice. First one to develop this issue was mine (since mine was older). I RMA'd it. Got brand new as a replacement (under warranty). My 2nd one (from RMA) also developed the very same issue after ~1 year of usage. And missus'es Sabre RGB developed that very same issue as well, after ~1.2 year usage.

So, we ditched the Corsair Sabre RGB mice all together and now, we both are using Corsair Nightsword RGB mice.

Corsair Nightsword RGB mice, of course, has different model specific issue.
Namely, ~1 year of (heavy) usage, the middle button press won't register anymore. Scroll up/down works fine, but clicking the scroll button down, won't register. It has happened to 2x Nightsword RGB mice already. 1st one was again mine (since i use middle button a lot). RMAd it under warranty and got replacement. Since RMA takes time, i bought 2nd Nightsword RGB mice to use until RMA completes (can't use PC without mice). Now, the 2nd one has also developed the same fault. Middle button works sporadically. Since RMA was successful, i have 3rd, brand new, Nightsword RGB next to me, but i haven't had time to switch it out yet (since my 2nd one, more-or-less, still works). Missus'es Nightsword RGB hasn't developed this fault. Then again, my missus doesn't use middle button that often.

So, either RMA your Glaive RGB mice (if it still is under warranty) and get replacement Glaive RGB, whereby the same fault developing in the same span of time as with 1st mice (to confirm it to be model specific issue), or go with new model. Nightsword RGB would be something to consider.

With the K70 MK.2 Keyboard the volume wheel seems to be less sensitive than it used to be.

I'd say it's wear-and-tear issue. Loosing sensitivity and registering it vice-versa.

I have Corsair Strafe RGB with Cherry MX Silent switches and mine has been in use since Q1 '17 (8 years old). And to set aside my own fault of spilling liquid on it and making the G button not work anymore (i've rebinded G to < key in iCUE), all other keys work fine.
Over the years, only few single key lightning issues have appeared. E.g red LED won't work under right Shift; discolor under A, F, C, M, left Alt, right CTRL (very easy to see when you put LEDs to white color).

I do have replacement KB as well, Corsair K100 RGB with Corsair OPX switches but i haven't bothered to replace it either. My Strafe RGB KB still works, for the most part.
Missus has Corsair Strafe RGB MK.2 with Corsair MX Silent switches (bought her KB in Q3 '19, 6 years old now) and she hasn't reported any issues with her KB as of now.


Of course, Corsair headsets (namely Void Pro RGB USB and Void RGB Elite USB) have their own issues as well. Namely the cable, or the rubber insulating part of it, will deteriorate over time. My headset's cable (Void Pro) is patched up on several places and missuse's headset (Void Elite) also has one cable patch on it.
Again, i have replacement headset as well (Void Elite), but again, haven't bothered to change it, yet.

Other Corsair peripherals we have (ST100 RGB for both of us and MM800 RGB Polaris i have), haven't developed a fault over the years.

My main issue of not replacing my Corsair peripherals is due to the iCUE update bug. I'm currently running v4.24.193 but when i want to update it to v5.x, the automatic updater fails to do it, telling me that i have v3.14 installed that it can not remove. And update fails. 😒
I can fix it by completely uninstalling iCUE and then installing v5.x, but this makes me loose all the custom macros and settings i have for my peripherals. Setting it all up is PITA, that i'd do once i've moved on to Win11 (or preferably Win12).

Finally, with the fans, the lighting on them seems to glitch out occasionally.

Most likely iCUE issue.

For my peripherals, lighting also sometimes glitches out. Since i have rainbow wave for my KB for the most of the times, and when iCUE itself crashes, the wave motion stops. So, i have to launch iCUE again.

But then again, Corsair SP120 RGB fans are old. 🤔 Released even before my Corsair ML120/140 Pro LED fans came out, that i'm running in my builds (full specs with pics in my sig). My oldest ML Pro LED fans are from Q1 '17. 0 issues with any of them, even years later.
Gave a quick look and original SP-series was released in 2015, while SP RGB-series was released in 2016.

All-in-all, nothing lasts for forever.

 

[EyesOfJack]

So, either RMA your Glaive RGB mice (if it still is under warranty) and get replacement Glaive RGB, whereby the same fault developing in the same span of time as with 1st mice (to confirm it to be model specific issue), or go with new model. Nightsword RGB would be something to consider.

Thank you for the response on this topic! Looks like I have had both the keyboard and mouse since 2020! (Quickly checked my Amazon account) So the mouse may be in need of being replaced. The keyboard has 0 issues other than the scroll volume wheel (which i seem to have sorted by just spinning it pretty aggressively and it seems to have stopped the issue haha)

Most likely iCUE issue.

Quite definitely, as it usually fixes it temporarily by just quitting and reopening iCUE!


I have a bunch of other Corsair branded stuff that works all good, just the one or two snags here and there

Thank you again!

 

[Roland Of Gilead]

Corsair mice have model specific issues.

E.g;
Corsair Sabre RGB mice will produce, after ~1 year of usage, double- and triple-click issue on left click button, despite you only clicking it once.
It has happened with 3x Sabre RGB mice i've owned. Both me and missus used to use that mice. First one to develop this issue was mine (since mine was older). I RMA'd it. Got brand new as a replacement (under warranty). My 2nd one (from RMA) also developed the very same issue after ~1 year of usage. And missus'es Sabre RGB developed that very same issue as well, after ~1.2 year usage.

So, we ditched the Corsair Sabre RGB mice all together and now, we both are using Corsair Nightsword RGB mice.

Corsair Nightsword RGB mice, of course, has different model specific issue.
Namely, ~1 year of (heavy) usage, the middle button press won't register anymore. Scroll up/down works fine, but clicking the scroll button down, won't register. It has happened to 2x Nightsword RGB mice already. 1st one was again mine (since i use middle button a lot). RMAd it under warranty and got replacement. Since RMA takes time, i bought 2nd Nightsword RGB mice to use until RMA completes (can't use PC without mice). Now, the 2nd one has also developed the same fault. Middle button works sporadically. Since RMA was successful, i have 3rd, brand new, Nightsword RGB next to me, but i haven't had time to switch it out yet (since my 2nd one, more-or-less, still works). Missus'es Nightsword RGB hasn't developed this fault. Then again, my missus doesn't use middle button that often.

So, either RMA your Glaive RGB mice (if it still is under warranty) and get replacement Glaive RGB, whereby the same fault developing in the same span of time as with 1st mice (to confirm it to be model specific issue), or go with new model. Nightsword RGB would be something to consider.


I'd say it's wear-and-tear issue. Loosing sensitivity and registering it vice-versa.

I have Corsair Strafe RGB with Cherry MX Silent switches and mine has been in use since Q1 '17 (8 years old). And to set aside my own fault of spilling liquid on it and making the G button not work anymore (i've rebinded G to < key in iCUE), all other keys work fine.
Over the years, only few single key lightning issues have appeared. E.g red LED won't work under right Shift; discolor under A, F, C, M, left Alt, right CTRL (very easy to see when you put LEDs to white color).

I do have replacement KB as well, Corsair K100 RGB with Corsair OPX switches but i haven't bothered to replace it either. My Strafe RGB KB still works, for the most part.
Missus has Corsair Strafe RGB MK.2 with Corsair MX Silent switches (bought her KB in Q3 '19, 6 years old now) and she hasn't reported any issues with her KB as of now.


Of course, Corsair headsets (namely Void Pro RGB USB and Void RGB Elite USB) have their own issues as well. Namely the cable, or the rubber insulating part of it, will deteriorate over time. My headset's cable (Void Pro) is patched up on several places and missuse's headset (Void Elite) also has one cable patch on it.
Again, i have replacement headset as well (Void Elite), but again, haven't bothered to change it, yet.

Other Corsair peripherals we have (ST100 RGB for both of us and MM800 RGB Polaris i have), haven't developed a fault over the years.

My main issue of not replacing my Corsair peripherals is due to the iCUE update bug. I'm currently running v4.24.193 but when i want to update it to v5.x, the automatic updater fails to do it, telling me that i have v3.14 installed that it can not remove. And update fails. 😒
I can fix it by completely uninstalling iCUE and then installing v5.x, but this makes me loose all the custom macros and settings i have for my peripherals. Setting it all up is PITA, that i'd do once i've moved on to Win11 (or preferably Win12).


Most likely iCUE issue.

For my peripherals, lighting also sometimes glitches out. Since i have rainbow wave for my KB for the most of the times, and when iCUE itself crashes, the wave motion stops. So, i have to launch iCUE again.

But then again, Corsair SP120 RGB fans are old. 🤔 Released even before my Corsair ML120/140 Pro LED fans came out, that i'm running in my builds (full specs with pics in my sig). My oldest ML Pro LED fans are from Q1 '17. 0 issues with any of them, even years later.
Gave a quick look and original SP-series was released in 2015, while SP RGB-series was released in 2016.

All-in-all, nothing lasts for forever.

Excellent post.

 

[Roland Of Gilead]

Thank you for the response on this topic! Looks like I have had both the keyboard and mouse since 2020! (Quickly checked my Amazon account) So the mouse may be in need of being replaced. The keyboard has 0 issues other than the scroll volume wheel (which i seem to have sorted by just spinning it pretty aggressively and it seems to have stopped the issue haha)

Quite definitely, as it usually fixes it temporarily by just quitting and reopening iCUE!


I have a bunch of other Corsair branded stuff that works all good, just the one or two snags here and there

Thank you again!

I've mostly owned only Corsair products. I've not had any issues with my mk2 LP. It works perfectly with no issues and similarly I got it on 2020, but my experience is not indicative of yours.. I'd agree @Aeacus wear and tear is the likely culprit. But, just in case, I'd use the iCue uninstaller in the program folder and uninstall and reinstall fresh (not a repair). iCue can get very buggy over time, and I find that doing this can solve a lot of issues.

For the SP120's. What profile did you choose for them in iCue? If you choose SP RGB from the drop down menu, it can cause issues with the fans. I came across a thread on Corsair forums, and one of the techs mentioned you have to actually choose the 8-Led option to ensure the fans work as intended. Seemingly it's related to the older SP120's. The newer versions aren't specified in the menu, so 8-led is best.

Do you have any other hardware using a different software package like Asus Armoury Crate or anything? They can really mess with functionality too. So only use one or the other. iCue has the option to install plugins for different manufacturers, so be sure to install the ones relevant to you.

 

[EyesOfJack]

Do you have any other hardware using a different software package like Asus Armoury Crate or anything? They can really mess with functionality too. So only use one or the other. iCue has the option to install plugins for different manufacturers, so be sure to install the ones relevant to you.

Good shout actually, I have an MSI 3080, and NZXT Phantom AIO which both have their own lighting software which could be doing something. I'll look into it!

Seemingly it's related to the older SP120's. The newer versions aren't specified in the menu, so 8-led is best.

Have got it set up to 8-LED! Was a bit confusing initially setting it up when the SP fans didn't appear on there. I use the Corsair 5000X, so bought a couple more of the SP Elite fans to fill it up.

Appreciate the response!

 

[Roland Of Gilead]

Good shout actually, I have an MSI 3080, and NZXT Phantom AIO which both have their own lighting software which could be doing something. I'll look into it!

Have got it set up to 8-LED! Was a bit confusing initially setting it up when the SP fans didn't appear on there. I use the Corsair 5000X, so bought a couple more of the SP Elite fans to fill it up.

Appreciate the response!

You're welcome. If the MSI plugin doesn't work on the GPU, try the nVidia plugin too.

Good luck in finding the issue 👍

 

[Aeacus]

and NZXT Phantom AIO which both have their own lighting software which could be doing something. I'll look into it!

We too have NZXT CAM as well (controlling AER140 RGB fans, HUE+ and LED strips), in my and missus'es builds. But for us, NZXT CAM hasn't conflicted with iCUE. Of course, that doesn't mean it won't conflict in another PC.

We also have MSI GPUs, but i haven't installed MSI app to control the GPU LEDs (and my MSI monitor LEDs), since i'm content with default LED profile. Also, i don't want to have several different software installed just to control different eyecandy. It can lead into conflicts.

As far as of NZXT CAM goes, that program is CPU resource hog. Even when the CAM isn't doing much, only system telemetry, it takes up 25% of my CPU compute power. And that is A LOT. 😒
Lately, once OS boots and CAM loads, while loading my LED profile, i've exited (closed) the CAM for good. Since HUE+ keeps the LED profile running even when CAM isn't running. And i don't need CAM to take 25% of my CPU compute power for nothing. (For comparison, iCUE uses 3-4% of my CPU compute power when it is running.)
Did report it to NZXT as well (opened a ticket) and they forwarded the issue to dev team. Now, 4-5 CAM updates later, the issue still remains. So, i'm thinking to open up new ticket about it as well.

 

[Roland Of Gilead]

We too have NZXT CAM as well (controlling AER140 RGB fans, HUE+ and LED strips), in my and missus'es builds. But for us, NZXT CAM hasn't conflicted with iCUE. Of course, that doesn't mean it won't conflict in another PC.

We also have MSI GPUs, but i haven't installed MSI app to control the GPU LEDs (and my MSI monitor LEDs), since i'm content with default LED profile. Also, i don't want to have several different software installed just to control different eyecandy. It can lead into conflicts.

As far as of NZXT CAM goes, that program is CPU resource hog. Even when the CAM isn't doing much, only system telemetry, it takes up 25% of my CPU compute power. And that is A LOT. 😒
Lately, once OS boots and CAM loads, while loading my LED profile, i've exited (closed) the CAM for good. Since HUE+ keeps the LED profile running even when CAM isn't running. And i don't need CAM to take 25% of my CPU compute power for nothing. (For comparison, iCUE uses 3-4% of my CPU compute power when it is running.)
Did report it to NZXT as well (opened a ticket) and they forwarded the issue to dev team. Now, 4-5 CAM updates later, the issue still remains. So, i'm thinking to open up new ticket about it as well.

Do your devices have on board memory? That was a way I got around some of the conflicts. Meant I didn't have to start up the software which would conflict, they just stayed on their onboard setting.

Right now, fingers crossed, I have my ASUS mobo running through iCue. Don't ask me how, it just happened one day, and I've not changed it since. I've spent hours tryig to figure it out, and the BOOM. Lol