• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

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

Joined
Jul 30, 2019
Messages
2,589 (1.45/day)
System Name Not a thread ripper but pretty good.
Processor Ryzen 9 5950x
Motherboard ASRock X570 Taichi (revision 1.06, BIOS/UEFI version P5.50)
Cooling EK-Quantum Velocity, EK-Quantum Reflection PC-O11, EK-CoolStream PE 360, XSPC TX360
Memory Micron DDR4-3200 ECC Unbuffered Memory (4 sticks, 128GB, 18ASF4G72AZ-3G2F1)
Video Card(s) XFX Radeon RX 5700 & EK-Quantum Vector Radeon RX 5700 +XT & Backplate
Storage Samsung 2TB 980 PRO 2TB Gen4x4 NVMe, 2 x Samsung 2TB 970 EVO Plus Gen3x4 NVMe, AMD Radeon RAMDisk
Display(s) 2 x 4K LG 27UL600-W (and HUANUO Dual Monitor Mount)
Case Lian Li PC-O11 Dynamic Black (original model)
Power Supply Corsair RM750x
Mouse Logitech M575
Keyboard Corsair Strafe RGB MK.2
Software Windows 10 Professional (64bit)
Benchmark Scores Typical for non-overclocked CPU.
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

Freshwater Moderator
Staff member
Joined
Oct 6, 2004
Messages
58,413 (8.12/day)
Location
Oystralia
System Name Rainbow Sparkles (Power efficient, <350W gaming load)
Processor Ryzen R7 5800x3D (Undervolted, 4.45GHz all core)
Motherboard Asus x570-F (BIOS Modded)
Cooling Alphacool Apex UV - Alphacool Eisblock XPX Aurora + EK Quantum ARGB 3090 w/ active backplate
Memory 2x32GB DDR4 3600 Corsair Vengeance RGB @3866 C18-22-22-22-42 TRFC704 (1.4V Hynix MJR - SoC 1.15V)
Video Card(s) Galax RTX 3090 SG 24GB: Underclocked to 1700Mhz 0.750v (375W down to 250W))
Storage 2TB WD SN850 NVME + 1TB Sasmsung 970 Pro NVME + 1TB Intel 6000P NVME USB 3.2
Display(s) Phillips 32 32M1N5800A (4k144), LG 32" (4K60) | Gigabyte G32QC (2k165) | Phillips 328m6fjrmb (2K144)
Case Fractal Design R6
Audio Device(s) Logitech G560 | Corsair Void pro RGB |Blue Yeti mic
Power Supply Fractal Ion+ 2 860W (Platinum) (This thing is God-tier. Silent and TINY)
Mouse Logitech G Pro wireless + Steelseries Prisma XL
Keyboard Razer Huntsman TE ( Sexy white keycaps)
VR HMD Oculus Rift S + Quest 2
Software Windows 11 pro x64 (Yes, it's genuinely a good OS) OpenRGB - ditch the branded bloatware!
Benchmark Scores Nyooom.
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.
 
Joined
Jul 31, 2014
Messages
266 (0.07/day)
Location
Singapore
System Name Garbage / Trash
Processor Ryzen 5600X / 5600
Motherboard MSI B450M Mortar Ti / GB B550M Aorus Pro-P
Cooling Deepcool GTE / ID Cooling SE224XT
Memory Micron 32GB DDR4-3200 E-die @ 3600C16 / Ballistix Elite 16GB 3600C16
Video Card(s) MSI 2060 Super Armor OC / Zotac 3070 Twin Edge
Storage HP EX920 1TB Micron 1100 2TB, Crucial M550 1TB, Hynix P31 1TB
Display(s) Acer XB271HU @ 150Hz x2
Audio Device(s) JBL LSR305 + Topping D50S / iLoud MM + SMSL DO100
Power Supply Seasonic Focus Plus 850W / G-series 650W
Mouse Logitech G304 x2
I can't recall anything they make that wasn't overpriced at least over here.
 
Joined
Jul 30, 2019
Messages
2,589 (1.45/day)
System Name Not a thread ripper but pretty good.
Processor Ryzen 9 5950x
Motherboard ASRock X570 Taichi (revision 1.06, BIOS/UEFI version P5.50)
Cooling EK-Quantum Velocity, EK-Quantum Reflection PC-O11, EK-CoolStream PE 360, XSPC TX360
Memory Micron DDR4-3200 ECC Unbuffered Memory (4 sticks, 128GB, 18ASF4G72AZ-3G2F1)
Video Card(s) XFX Radeon RX 5700 & EK-Quantum Vector Radeon RX 5700 +XT & Backplate
Storage Samsung 2TB 980 PRO 2TB Gen4x4 NVMe, 2 x Samsung 2TB 970 EVO Plus Gen3x4 NVMe, AMD Radeon RAMDisk
Display(s) 2 x 4K LG 27UL600-W (and HUANUO Dual Monitor Mount)
Case Lian Li PC-O11 Dynamic Black (original model)
Power Supply Corsair RM750x
Mouse Logitech M575
Keyboard Corsair Strafe RGB MK.2
Software Windows 10 Professional (64bit)
Benchmark Scores Typical for non-overclocked CPU.
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

Freshwater Moderator
Staff member
Joined
Oct 6, 2004
Messages
58,413 (8.12/day)
Location
Oystralia
System Name Rainbow Sparkles (Power efficient, <350W gaming load)
Processor Ryzen R7 5800x3D (Undervolted, 4.45GHz all core)
Motherboard Asus x570-F (BIOS Modded)
Cooling Alphacool Apex UV - Alphacool Eisblock XPX Aurora + EK Quantum ARGB 3090 w/ active backplate
Memory 2x32GB DDR4 3600 Corsair Vengeance RGB @3866 C18-22-22-22-42 TRFC704 (1.4V Hynix MJR - SoC 1.15V)
Video Card(s) Galax RTX 3090 SG 24GB: Underclocked to 1700Mhz 0.750v (375W down to 250W))
Storage 2TB WD SN850 NVME + 1TB Sasmsung 970 Pro NVME + 1TB Intel 6000P NVME USB 3.2
Display(s) Phillips 32 32M1N5800A (4k144), LG 32" (4K60) | Gigabyte G32QC (2k165) | Phillips 328m6fjrmb (2K144)
Case Fractal Design R6
Audio Device(s) Logitech G560 | Corsair Void pro RGB |Blue Yeti mic
Power Supply Fractal Ion+ 2 860W (Platinum) (This thing is God-tier. Silent and TINY)
Mouse Logitech G Pro wireless + Steelseries Prisma XL
Keyboard Razer Huntsman TE ( Sexy white keycaps)
VR HMD Oculus Rift S + Quest 2
Software Windows 11 pro x64 (Yes, it's genuinely a good OS) OpenRGB - ditch the branded bloatware!
Benchmark Scores Nyooom.
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)
 
Top