Corsair Expects Losses to Reach $11 Million for 2Q 2022

[A Computer Guy]

Watch out for a known bug there - HWinfo reading the settings freezes the corsair service, and it locks into last known settings until the service is reset. Shutdowns don't fix it.
Easy to spot, because icue wont show voltage readings any more.

The easy fix is to disable the corsair/asetek setting in HWinfo, but that stops you reading those readings

From what I recall iCue and HWinfo (or any other vendor attempting to get the data) end up fighting each other over the telemetry data and the Corsair service locks up because of it. If you closed HWinfo you could restart the corsair service from iCue, then close iCue and reopen HWinfo. I never had a problem with HWinfo getting the data (temps and fans speeds) as long as I never had them running at the same time. (version 3.xx of iCue) I was operating like this for years right up until I killed my PC with PBO. Another thing with Corsair is their service had some stupid timer somewhere in their software that kept everyone's AMD CPU boosting all the time. There was a windows command to get the OS to report it but I don't recall what that command was.

 

[Mussels]

From what I recall iCue and HWinfo (or any other vendor attempting to get the data) end up fighting each other over the telemetry data and the Corsair service locks up because of it. If you closed HWinfo you could restart the corsair service from iCue, then close iCue and reopen HWinfo. I never had a problem with HWinfo getting the data (temps and fans speeds) as long as I never had them running at the same time. (version 3.xx of iCue) I was operating like this for years right up until I killed my PC with PBO. Another thing with Corsair is their service had some stupid timer somewhere in their software that kept everyone's AMD CPU boosting all the time. There was a windows command to get the OS to report it but I don't recall what that command was.

This bug has been around a very VERY long time, icue refuse to fix it at their end - it's still an issue today, i had to fix it on my brothers PC as he ran HWinfo and locked his CPU pump to 0% (PWM controlled) and was hard crashing his system within seconds of loading windows. OH WHAT FUN.
(I made him wire it to the mobo header)

That boost bug affected intel as well if you didnt have an all core OC, and was because they used 5 year old CPUID code for their sensor readings - they finally updated that with icue 4, but you could delete a single sensor file and fix the issue.

 

[Palladium]

I can't recall anything they make that wasn't overpriced at least over here.

 

[A Computer Guy]

That boost bug affected intel as well if you didnt have an all core OC, and was because they used 5 year old CPUID code for their sensor readings - they finally updated that with icue 4, but you could delete a single sensor file and fix the issue.

I hate to go off topic but is version 4 worth it yet? I had reached a point of stability with 3.xx and especially with my headset and refused to upgrade at a certain point because they seemed to keep in a cycle of breaking / fixing stuff. The software issues are why when my command pro or RGB dies I'm not going back to Corsair.

 

[Mussels]

I hate to go off topic but is version 4 worth it yet? I had reached a point of stability with 3.xx and especially with my headset and refused to upgrade at a certain point because they seemed to keep in a cycle of breaking / fixing stuff. The software issues are why when my command pro or RGB dies I'm not going back to Corsair.

It's better than 3, but still heavy on RAM usage.
CPU usage is fixed and quite low, and you can still set hardware lighting for devices and quit it.

There was a big scandal on them abandoning a lot of hardware, but they backtracked and added most of the devices back in.

Dont install NVBroadcast for supported mics (see my recent thread for why)
If you dont plan to update it, you can disable a lot of their extra services or delete the relevant exes and debloat it somewhat - disable the audio services if you dont use their headsets, disable their hardware monitoring, etc.

I get the feeling that due to dropping sales, someone finally threw money at their software team - they may do a synapse and have a comeback here (synapse 3 is genuinely light on resources, unlike just about every other RGB software out there)