Monday, July 25th 2022

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

Corsair, one of the world's leading PC component brands, is being hit hard by macroeconomics and consumers' choice - and sometimes need - to keep more dollars in their pockets. According to its own internal accounting, the company has announced that it expects between $10 and $11 million dollars in losses for 2Q 2022 (April-June) throughout its business. Remember that this isn't a case of a company being too specific in its product line and taking the heat from it; Corsair has one of the most diverse lineups in PC components, ranging from memory, water and air cooling, SSDs, peripherals, and even monitors.

Not unlike other businesses, which have seen inventory levels soar on account of much lower than expected sales, Corsair too has seen its warehouses starting to fill up - not unlike the company's financials, there's less and less oxygen within its warehouses as inventory piles up. Corsair did say it expects business to pick up considerably in the third quarter, as it has seen an uptick in enthusiast-level PC gaming sales (likely spurred by the dropping prices of GPUs as miners dump their graphics cards in expectation of Ethereum's Merge event, set for September). The increase in sales leads the company to believe it will achieve a 35% YoY (year-over-year) growth throughout the second half of 2022, which will hopefully be enough to push the company back above the red line.
Source: via TechSpot
Add your own comment

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

#51
Mussels
Freshwater Moderator
A Computer GuyFrom 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.
Posted on Reply
#52
Palladium
I can't recall anything they make that wasn't overpriced at least over here.
Posted on Reply
#53
A Computer Guy
MusselsThat 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.
Posted on Reply
#54
Mussels
Freshwater Moderator
A Computer GuyI 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)
Posted on Reply
Add your own comment
Nov 15th, 2026 23:17 CST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts