Haydn

I've had the same issues with my 3950x and voltages staying at 1.45V+ with only iCue running. Temperature wasn't a problem but there's no way the cpu should be receiving load voltages when iCue is using maybe 3% of it and that voltage is for all cores. I found that playing around with the PBO settings on my Aorus Master has allowed me to idle at 1.20V even down to 0.950V on some cores all while iCue runs my whole system lighting in the background. I have AMD CBS PBO setting set to auto for both options and in the other PBO options setting I have turned it to manual with a 10x scalar and +200mhz boost. While this 'fixes' the issue of high idle voltage, it limits the max all core boost. Single core boost is still reaching 4.6Ghz to 4.7Ghz. All core when I was idling at high voltage was able to reach and hold 4.2ghz all core boost. With the PBO settings on I can only acheive 4.025Ghz for all cores. Hope this helps until this issue is properly fixed.

DevBiker is right, I had an almost identical issue and spent ages trying to figure it out. I thought fan 2 in my chain of 5 was okay since only 3,4 and 5 were flickering but turns out fan 2 was the issue. Replaced it with a new fan and problem solved, no more flickering at all. If you have a spare fan handy that would be great, but otherwise try and re-arrange the order they are plugged into your rgb hub. From your video it looks like the fan at the top-rear of the case is not glitching like the rest? if this fan is in port 1 then I would suspect that is the faulty fan (even though it isnt flickering)

I also get this issue, only started a few days ago I believe when I last updated iCue. Unfortunately I don't have an Asus Xonar card so it might be something else causing the issue. I don't even know where to start looking to solve the issue but for now I can just ignore it

Pretty sure 0.10.4 is the latest version. Mine is currently on that and when I tell it to update it finds nothing new

It's a bit dissapointing. My only option to actually fix the issue for the time being is to close iCue and run the hardware lighting while I need maximum boosts. I did a bit more testing to see if using an affinity for iCue could fix things but somehow it still caused all cores to lower their boost, the second iCue was closed it instantly boosted 2 cores to 4.7ghz. As well Asus Aura lightingservice.exe also causes this issue, however corsairservice.exe doesn't affect the boost. I was able to hit 4.7ghz with corsairservice still using 2% cpu. Lets just hope that either Corsair or AMD can do something about this because I would like to use my Corsair products as intended without destroying my pc performance.

I was having a very similar issue with my LL fans where they were doing their own rainbow lighting effects ignoring the set lighting as well as flickering on and off. My set up used 2 rgb hubs to control 5 fans and 3 fans which then goes to a commander pro. I've tried everything I can possibly think of with no change except the issue getting worse. I was fiddling around with the services running on my pc and trying to cut down unnecessary services and to my surprise shutting off all rgb fusion related services fixed the issue. Everything was fine for about a week until i decided to uninstall Gigabyte app center and RGB fusion. Now the problem is back and no matter what I do to undo my actions it won't fix. Corsair also said to RMA but surely that isn't the only option, something seems to be conflicting with iCue, although i get issues when booting before bios even appears.

Seems like the issue is gone *fingers crossed*. Gigabyte RGB Fusion was somehow altering iCue and trying to control the 3 glitching fans. For some reason it ignored the other 5 fans. Completely closing that program as well as its associated checkkill.exe, suddenly my fans seem to be fine. Will update if the issue comes back

Since building my new system running a Ryzen 3950x I've been fiddling with the bios settings desperately trying to understand why my system was scoring so much less in benchmarks than others systems. My main issue was pretty clear that the cpu would boost all cores to around 4.2ghz when doing single threaded benchmarks, rather than going for 4.7 on at least one core and scaling across the rest of the cores. After some trial and error I figured maybe it was the 4% cpu usage when idle on the desktop that was causing some sort of issue, something was chewing up resources. After forcing iCue and all Corsair Services to stop suddenly usage dropped to 1% or even 0% in task manager. I re-ran the benchmarks and to my surprise my scores seriously improved. I know the obvious would have been to have nothing running in the first place when benchmarking but I assumed that performance couldn't be gimped so much but I was wrong. In Cinebench R20 with iCue running my multi core score was around 8700 and single core 470. With iCue and Corsair services disable my scores went to multi core 9400 and single core 520. The reason for this as far as I can tell is the program and service somehow make the cpu think it is under a reasonable load and therefore should boost more cores to a lower frequency ignoring whatever other task is being run. When the services were disabled the cpu was able to boost individual cores much higher, easily achieving at least one core at over 4.7ghz and scaling across the others. Is there anything that can be done with iCue to try to sort out this boost issue, I can only assume that it would be present in all Ryzen 3000 chips as its a conflict with iCue and Precision Boost 2. I have tried using core affinity to mitigate the issue but scores become gimped as soon as iCue and the services are running. Also game fps drops due to this issue. My other concern is that the cpu hardly downclocks to save power when idle because it sees iCue constantly running, most cores remain above 4ghz when iCue is running and the services are running but all cores hover around 3.5ghz when those aren't running. Cpu power draw is around 50W at idle with iCue running and services, but 35W with all turned off.

Nothing is in the lighting library, but I agree it definitely looks like its rapidly switching between hardware lighting and the profile lighting. Any idea how to stop it if that is the issue?

Yesterday I built my new pc from scratch, this time using a commander pro for controlling fans, lighting and using it as a usb hub. Today iCue shows me there in update 3.23.66 available so I installed that. Then it says there is a firmware update for my commander pro, firmware 0.9.212 so I updated that. After then restarting my pc 4 of my 8 LL series fans started flicking various different types of rainbows whilst the rest of the fans did the default lighting. Once iCue launched the flickering continued despite a profile being applied. No matter what profile lighting I use various rainbow colours flicker on these 4 fans. For example I can set all to white but 4 fans will flash rapidly between white and rainbows. To try and solve the problem I have changed which hub is connected to which led port on the commander pro, swapped in a spare lighting hub to see if my hub was broken, force updated the firmware on the commander pro, reinstalled iCue 3 times, tried to reset the commander pro by connecting SATA power while pressing the pinhole button (which did absolutely nothing), changed which SATA power cable is used, changed the led hub cable to a new one, rearranged the order of the lights on the hub, pretty sure more but I can't remember. Anyone with any advice will be appreciated, I'm at a complete loss for what to do. Thanks

Hi, It's really frustrating but I had a similar issue with the Node Pro refusing to update firmware for more than a year and various updates to iCue. I never found a solution to the issue other than simply waiting, eventually an iCue update managed to allow me to update firmware on these devices. Just be very careful with that feature as I kept trying to update when it wouldn't work and it ended up somehow mixing up my lighting assignments for the Nodes in all profiles and I had no backups of my profiles. Hope this helps a little!

Finally! After three days of scratching my head I think I've solved my issue. I reinstalled Corsair Link v4.9.6.19, then tried to install CUE v3.1.133. When the install got stuck on 60% starting services I restarted the pc which left the program fully installed just without the service started. I then went to C:\ProgramData\Corsair and deleted the folder CUE. I then launched CUE and went to the CUE install folder and launched Corsair Service. Not sure if this did much but it seemed to fix the issue as the service would now run. Also all my devices now showed up. Then I went to Services.msc and found Corsair Service and started it. Unlike before where it would instantly stop, this time it stayed running and all my devices have been recognised and work!