Jump to content
Corsair Community

ICue Issues : Keeps adding the same fans over and over / Not responding to profile change etc.


Recommended Posts

First things first, my setup:
- Asus ROG Maximus XIII Hero (as expected: patched to latest Bios)
- Commander Pro (attached to board) 
- H150 Elite Capellix (USB header attached to Commander Pro)
- Lighting Node (from the QL120 3-Pack) (USB header attached to Commander Pro)
- OS: Windows 11 with latest available stable iCue and all device packages patched

First Issue: Sometimes iCue starts to multiply the fans (only those attached to Commander Pro)
The original 1-6 are there and being read, few seconds later another 1-6 get added to dashboard, and this repeats then until I reboot. I tried restarting iCue Service & iCue GUI App - no change. I have to say this happens absolutely randomly, not that often , but now 3 times in 2 days. When trying to remove one of the duplicates manually, iCue crashed.

Second Issue: Sometimes iCue stops responding to profile change

Again, only affects the fans on the Commander Pro. I change from my high performance profile to my balanced profile - the AIO instantly reacts starting to throttle down the fans - while the fans attached to Commander Pro do nothing or one or two of them randomly then increase their speeds (not always, just sometimes) - again, this is happening totally randomly - but contrary to the first issue, this issue can be resolved by restarting the iCue service.

Third Issue: Weird Sensor Reading for the Mainboard
The iCue Software is showing totally 17 different sensor readings for the ROG Maximus XIII Hero. so I assume youre using some sort of direct access to the bord internals, as no other independent temperature reading application I have tested is showing that many readings, otherwise I would have reported that issue directly to ASUS. Sensor #6 only knows 2 different values: either 127 or 0 (Celsius), while being 99% of the readouts on 127.
PS: Couldn't we get some more meaningful default descriptors rather than "Temperature #1" etc. ? Even HWInfo is capable of telling me the location of the readout. And a little question: Why don't we get a readout specifically for the PCH? It's one of the more problematic zones of a ROG Maximus XIII Hero - and all other sensor readers are capable of reading out the value - and I doubt they even have an as direct line to the firmware/bios as you seem to have (due to the number of different readings you display).

Fourth Issue: ICue Randomly Starts to heavily use GPU

I've recently seen ICue using 25% of a throttling-prevented RTX 3090. The application was responsive, could be minimized and maximized normally, nothing suspicious happening (like one of the other issues occurring concurrently). The only way to resolve was to restart the application.

 

 

Link to comment
Share on other sites

Question: Are you running any other monitoring software? In particular, are you running anything that will read the Commander Core's temperatures (and you have a Commander Core, not a Commander Pro - see https://youtu.be/nQRdMICK-qQ for a guide to all of the devices and what they are called).

 

Link to comment
Share on other sites

Posted (edited)

the commander core is from the capellix, i bought a seperate commander pro due to the 2 usb headers it has - so i can attach everything and not having to loose my front usb connectors from the case and i need the extra pwm headers too, as i run the capellix as a push/pull all those headers are already used 😉 but i understand why you thought I would only have the commander xt core 

nope, I'm fully aware of the signaling issues due to multiple concurrent monitoring applications accessing the same sensors - i have only iCue running automatically. And when i do checks with something else, i stop iCue and the corresponding service. After i couldn't get the interop between iCue and Aura working, i also completely deinstalled all the asus crapware - with the cleaner tools and like i always do, afterwards cleaned all leftovers from the registry etc. 

image.thumb.png.b5f06e55351238d9adf4304cadd39b3b.png

Edited by RKaySwiss
Link to comment
Share on other sites

  • Corsair Employees

What happens when you plug the devices directly into the USB 2.0 headers on the motherboard instead of the USB passthrough?

Link to comment
Share on other sites

1 hour ago, RKaySwiss said:

I would only have the commander xt core 

Actually, the Commander Core XT is yet another different device. (And yes, it does matter.) People get these three devices mixed up all the time.

Which fans are being duplicated? Is it the PWM fans? Or do you have fans attached to the LED headers and those are being duplicated? Is it only in the Dashboard or is it on the corresponding tab for the Commander Pro?

Issues 1 & 2 really sound/smell like a software conflict.

Link to comment
Share on other sites

I have to test this in the next week, as my system is nonstop in use the next days.
But I have to say: The issue with the fan duplication is happening randomly, its been 3 times in 2 days - but now since this morning nothing - so i doubt its an issue related to the usb. Just from (my) logics point  of view: The data coming in actually from the cappelix (which is attached to the commander) never showed an issue and were talking here about a quite stable (timing & bandwith) dataflow. Not saying it couldn't be, if computers taught us one thing: expect everything -laugh- but i think its not very likely. Also, i would assume, if the usb is the issue, it would probably also duplicate the voltage sensors from the Commander Pro, but those have never been duplicated. Anyway Ill test as soon as I can and give you feedback - just need to get an external USB hub, as my internal USB connectors are all used and to attach the Cappelix directly to the MB i need to detach my front USB.

Btw. speaking off passthrough: Is it actually a passthrough? As we have an incoming 9-pin USB with an outgoing 2 x 9-pin USB (with the device itself also using the connection to the MB also), i would have assumed its more like a USB hub. 

Will let you know, for the moment im happy that since my post nothing more has happened and i can work without rebooting (and then waiting again 30 minutes until my large Visual Studio solution is ready -laugh-

Thanks for the attempt to help so far, appreciate it!

Link to comment
Share on other sites

1 minute ago, RKaySwiss said:

Btw. speaking off passthrough: Is it actually a passthrough? As we have an incoming 9-pin USB with an outgoing 2 x 9-pin USB (with the device itself also using the connection to the MB also), i would have assumed its more like a USB hub. 

It's an small, unpowered hub that sits on one of the USB ports on the header the the CoPro is connected to. The other physical port is used for the CoPro MCU. It's the unpowered part that seems to cause issues - which is why you so frequently see recommendations here for a powered internal USB hub.

Link to comment
Share on other sites

only the PWM fan widgets, only on the commander pro - voltage not affected and the capellix' commander core which is attached to the pro is still working properly when the issue arises, thats the weird thing. the Leds never showed any issues at all - the cappelix neither.

I feel ya regarding the conflict, that was the first thing I suspected myself too - its quite like typical behaviour. But i can guarantee, no monitors running - unless Windows has a hidden internal thermal monitoring interfering with it 😉

The duplicated fans did also show up in the device selection - when I tried to remove the first duplicate, iCue crashed - that counts for both: Attempt to remove the widget from the dashboard aswel as the entry in the device selection.

Link to comment
Share on other sites

3 minutes ago, DevBiker said:

It's an small, unpowered hub that sits on one of the USB ports on the header the the CoPro is connected to. The other physical port is used for the CoPro MCU. It's the unpowered part that seems to cause issues - which is why you so frequently see recommendations here for a powered internal USB hub.

An extra internal hub would be a good thing anyway, then i could test the direct attach for failure seek without losing my front usbs which i need for work. And speaking of power, could actually really be the issue, I have a lot of devices that draw their power to operate directly via USB port. Good point, thx DevBiker.

Link to comment
Share on other sites

Especially as i run totally 14 fans, 9 of those with LEDS

Link to comment
Share on other sites

21 hours ago, RKaySwiss said:

Especially as i run totally 14 fans, 9 of those with LEDS

The fans won't draw from the USB +5V power line. It doesn't have anywhere near enough juice to actually power them (spec for USB 2.0 is 500mA, for USB 3.0 is 900mA). They'll be powered from the SATA header (up to 4.5A).

Link to comment
Share on other sites

I also have a ROG Maximus XIII Hero mobo, temp sensor #6 is definitely messed up or buggy, mine also shows either 0 or currently melting into the center of the earth

max13.jpg

Link to comment
Share on other sites

On 6/5/2022 at 8:35 AM, Oxnull said:

also have a ROG Maximus XIII Hero mobo,

All Asus motherboards from the last 6-7 generations will report some extraneous or erroneous data in CUE.  CUE has trouble with the Asus embedded controller and other programs like HWiNFO and AIDA also make note of this.  There will be duplicates and some junk data.  Nothing on your board is 15C.  Nothing on your board is 127C or 216C (common max values for specific sensors).  You can delete the obvious wrong values from the block and they will not return.  

Link to comment
Share on other sites

Posted (edited)
On 6/5/2022 at 3:20 PM, c-attack said:

All Asus motherboards from the last 6-7 generations will report some extraneous or erroneous data in CUE.  CUE has trouble with the Asus embedded controller and other programs like HWiNFO and AIDA also make note of this.  There will be duplicates and some junk data.  Nothing on your board is 15C.  Nothing on your board is 127C or 216C (common max values for specific sensors).  You can delete the obvious wrong values from the block and they will not return.  

Actually on HWInfo i have no issues with Asus at all! All sensor properly named, reporting the same values as AI Suite is reporting. The 127C or 0C (seems like a on/off sensor -lol- was clear to be absolutely nonsense. 127C would start to smell smokey on the board i Assume. I think we got nothing that even gets close to that temp, at least not under normal conditions, and not for longer than a few seconds before frying. Closest to that temp is my 3090 memory junction hotspot, which sometimes scratches the 100C - but thats ok for this specific thingy. 

@Oxnull Afaik: When i changed the bios settings back to defaults, while troubleshooting, the ASUS display "normalized" in iCue. Actually showing only 8 or 9 Sensors , not 16 or 17 - so the doubling is an issue on the asus data too. If i remember right, it changed to normal, plausible state when I had the Intel Multicore Limits back in place (Asus Multicore Enhancements Disabled - Enforce All Limits). Yeah i see the same behaviour, with the doubled CPU fan being displayed.

@c-attack
Unless your doubling is repeating every 5 seconds ending up with thousands of fans #1 to #6 - interesstingly only affecting the Commander Pro, the Capellix i wasnt able to influence, not even forcefully - i opened every monitoring tool i had at once - the Capellix was there reporting in as usual not caring - the commander pro starts to fiddle around like a scared chicken whenever something reads the same sensor, whenever it looses the connection to something or there is a small hickup in ICue - then it starts to repeat the fans, over and over, and when you try to delete just one of them, iCue Freezes - and then crashes. Would trade the commander pro against another commander core (not xt) instantly ^^ Thed commander pro also doesnt really care for my profiles - switching to silent, the core goees from 2400 rpm on my push fans to 700, the pro from 1600 to maybe 1500 - if even 😛Basically: The CORE is smart, while the PRO is not smart - understanding only absolute values, every smart setting (no matter if silent, balanced, intensive) results in 1500-1600 rpm on the fans

 

Edited by RKaySwiss
Link to comment
Share on other sites

@DevBiker Im aware of that that they dont draw via USB, but with the additional USB headers I can now also dynamically control my 4 small noctuas indepedently - instead of being synched with fans of other RPM - now i can give them the fan controller they deserve -laugh- if i can get any more sata cable through that gordian cable knot out hell. 

Just thinking about having to rebuild that **** when the 4090 comes out drives me already crazy. 

Link to comment
Share on other sites

new issue, and - who would have expected something different, just the commander pro affected  -  mixing up false values, stuck metrics, 0 values and missing histograms , all in one issue occurence . And to avoid the same questions:

- No monitoring tools running (beside ICue)
- Just the commander - the fans are running, the leds (through rgb hub attached to commander pro) working properly - i can also change the lighting properly.
- State is just after a reboot
- Yes i reinstalled iCue multiple times
- Yes I replugged the device and checked every connection - the commander is now directly attached to the bord, no USB header device behind (also tested with the commander pro on a powered USB hub)

Question: Is the Commander Core (from the Capellix) (not XT) available as standalone product? never got any issues with that one, even when trying to make it fail during testing, and i prefer its port layout, as i dont use rgb stripes etc. and dont need the sensors and no usb passthrough (anymore). I tried to force such issues on the capellix, by starting every monitor tool i know, i couldn't make it show any issues, even when the commander pro was not attached (so the only corsair commander that could be affected was the core, but it never let me down - while the pro is causing just issues - i can't even count anymore how i often i was forced to do a reboot due to it)

 

image.png.d4a68620e16be612ae7b32b66d5192f0.png

Link to comment
Share on other sites

1 hour ago, RKaySwiss said:

Actually on HWInfo i have no issues with Asus at all!

My post was in response to the Oxnull query above and your original question. I did not say HWinfo does the same thing. Only that it notes the presence of the Asus EC. The duplicates and end of range values are standard for CUE across several generations of board and program and is not related to the fan doubling in any way.

 

Do not use the presets for the Commander Pro. It’s using a water cooling configured curve with CPU temp data. Those two have very different ranges. You should create your own curve regardless of controller. None of them are “smart”. They each have specific fan rpm vs temperature control points, but since they are hidden from view it’s not overly helpful. Better off making your own curve. 
 

I don’t know what is happening with your “fan duplication”. Can you clarify if this occurs only on the dashboard or if the fans in the Commander Pro -> cooling tab also multiply?

 

Turn on debug logging in the CUE settings. After the next fan doubling, export the logs. 

Link to comment
Share on other sites

Even better, I have now debugger / profiler / trace listener continously attached to iCue with debug symbols. The next time it happens, ill be able to even inspect the line of code and whats on iCues memory when it happens.

Yes it doubled even the the entries on the device settings - and when trying to get rid of them , icue crashes. 

The fact that it repeats the doubling then over and over speaks for a loop in code which doesnt end (very often the reason for this, is an unexpected condition/exception in code not handled but also not having - what we call a retry-logic-circuit-breaker. Like infinitely retrying an action, without either a break on a certain number of fails or time-based to avoid the execution getting stuck in there. 

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...