X670e Hero & corsair Icue with Asus plug in.

[sfdmark]

I am not sure if this is the right "place" to post this, I apologize if not .
I am having some trouble to make the Icue Asus plug in to report the right readings and control lighting since I 've build this new PC.
Everything is updated and freshly installed, no problems in any other specific area but only in the motherboard readings through the plug in in ICUE. Icue is working fine, it reads perfectly fine my 3080ti and everything but not my M/B rog crosshair x670e Hero. Armoury crate on the other hand, it does read all sensors from motherboard correctly and can control the leds perfectly ok with it.
Also I don't know if it is related somehow, but when armoury crate services loading during windows start up my pc becomes unresponsive and choppy for 3-4 secs.
Does anybody else experiencing same issues ? I couldn't find any relevant posts regarding this, although I tend to believe it is asus plug in/ armoury crate issue.
There is also a screen capture of icue readings for my motherboard that it is actually frozen:

[sfdmark]

So there is none around with corsair icue and asus x670e hero motherboard to confirm either that asus plug in works or it doesn't?

[Anthony_Kinson]

sfdmark wrote:
So there is none around with corsair icue and asus x670e hero motherboard to confirm either that Asus plug-in works or it doesn't?

I have the X670E Hero + icue. mine doesn't show anything at all though. icue won't even detect the memory to control the lighting. Unfortunately, this motherboard is a hot mess at the moment with multiple issues.

[sfdmark]

Yes it is like mine , this happened after the latest update of fanexpert in Armoury crate. Thank you for replying. At least I know that I am not alone into this 🙂

[Airman86]

sfdmark wrote:
Yes it is like mine , this happened after the latest update of fanexpert in Armoury crate. Thank you for replying. At least I know that I am not alone into this 🙂

you’re not alone, same for me. Have you done all the updates in armoury crate?
It suggests me updates for the board and the gpu to list them as devices.

I’m not trusting this piece of software so I have not done it yet. Â*

[Airman86]

UPDATE:

Solved the problem for me. You need to deactivate the thunderbolt controller within the windows device manager. reeboot the system and the ram rgb is detected and you can control it via icue. read this in a german forum:
https://www.computerbase.de/forum/threads/probleme-mit-rgb-ram-beleuchtung-amd-x670e.2105524/#post-2...


dont know if its a problem with ique or the asus board, but it's quite disappointing keeping the price of the hardware in mind ...

[sfdmark]

Airman86 wrote:
UPDATE:

Solved the problem for me. You need to deactivate the thunderbolt controller within the windows device manager. reeboot the system and the ram rgb is detected and you can control it via icue. read this in a german forum:
https://www.computerbase.de/forum/threads/probleme-mit-rgb-ram-beleuchtung-amd-x670e.2105524/#post-2...


dont know if its a problem with ique or the asus board, but it's quite disappointing keeping the price of the hardware in mind ...

So to get this straight, we need to deactivate thunderbolt/usb4 from the bios and reboot in order for the asus plug in to work with ICUE. I will give it a go, though if I understand correctly the problem is not the memory rgb lights, which always was bugged in my previous built. My problem is that something is Armoury crate is blocking the Asus plugin of ICUE to read and control motherboard lights and fans. In the screenshot you can see for example that the plugin is unable to read any sensor from the motherboard or control the lights. On the other hand, armoury alone, is working fine but it doesn't have any control to any NON-asus hardware. So basically is no go for me and I guess for anyone with full setup (fans, cases etc...). ICUE did that before with the ASUS plugin which worked fine for 2 years in my previous built. I still have an open ticket with Corsair and the guys waiting for Asus armoury crate developers for a fix. Icue is working fine. The asus plugin bugs out.
Anyway, I will test this one and come back here for conformation, thank you for the info.

[sfdmark]

Just tested your suggestion which unfortunately didn't solve anything. As I said is previous post, is not the memory rgb control issue. The asus plug in doesn't recognise anything regarding the motherboard. It is working fine for my graphics card though which is 1+ old.
Asus have to update the plug in or fix armoury crate. Something is wrong on their end, not corsair's.

[Anthony_Kinson]

motherboard sensors are showing up in iCue for me now, but iCue still isn't detecting the DDR5 Dominator memory. Seen a thread over on the corsair forums that there was a mixture of hardware faults and thunderbolt driver issues. However, my memory S/N isn't in their list, and iCue still won't detect my memory after thunderbolt is disabled. Not the end of the world but rather annoying, as stated, the prices of this stuff isn't cheap.

[sfdmark]

Anthony Kinson wrote:
motherboard sensors are showing up in iCue for me now, but iCue still isn't detecting the DDR5 Dominator memory. Seen a thread over on the corsair forums that there was a mixture of hardware faults and thunderbolt driver issues. However, my memory S/N isn't in their list, and iCue still won't detect my memory after thunderbolt is disabled. Not the end of the world but rather annoying, as stated, the prices of this stuff isn't cheap.

I am still left with the same issue. Tried disabling Thunderbolt 4 in device manager of windows and then disabled thunderbolt through the bios. Nothing is working. The only thing that I am able to control and see through icue is the RGB lighting (Not the A-rgb just the old 12v rgb header)