Schmittius

Small update: I've now been in contact with support, where I shared my logs and stuff. The support-technician said that there were a problem with that version of iCUE and the use of custom fan curves, and said I should set it to default. So I retried it, but it did not solve it for me but I did send over more logs, and not many days after while still troubleshooting did a new software update for iCUE: 'Core, v. 5.8.130' come out, and this one seems to have solved the issue for me. Even-though the technician said that version had a new known issue, and recommended me not to install it but iCUE auto updated before I saw the message, and now the problem has so far not reappeared and 🤞 it won't return.

Welp even a factory reset of the Commander Pro didn't fix it 😢 So I have now also tried this (⬆️ quote), and the HWinfo was able to read the info from the Commander Pro. I didn't have it run for that long, but considering it's able to read from it, I do believe that it's not a hardware fault here but a problem with iCUE software. But now I have exhausted all tests I can do myself, time to go to the Corsair support staff and hope they can check my logs to see if they find what is causing this fault.

Second to last ditch-effort before the last mentioned test. I've just factory reset my Commander Pro, following this guide: https://help.corsair.com/hc/en-us/articles/360057712532-How-to-Perform-a-factory-reset-on-the-Commander-Pro iCUE is currently updating the firmware on it but seems stuck at 0% though, for now. And once it's done, I'll run a short period in order to see if it fixed it or now. Oh boy please fix it... and don't be stuck on forever 0% to get it to version 0.9.212

Worst part is only since my last post, the issue appeared 3 more times on more or less 30-40 min intervalls. I guess my next test ought to be the disabling of iCUE on startup, for so to test with HWinfo to see if I can connect to the Commander Pro without issues, that you suggested. As it's beginning to sound a lot like a hardware problems.

That didn't take long, after the clean reinstall of iCUE it took roughly 30 min before the problem acted up again. Seems like I'm in need of the Corsair Support staff on this one to see through my Debug-logs. But before I open a ticket, c-attack, you seem like you have the knowledge of various programs that might interfare with iCUE. Do you know if the side program to MSI Afterburner called RivaTuner Statistics Server could interfare with iCUE?

Once again thank you c-attack, there is a lot here to try and do. Worst case senario I'm having hardware issue, and my component is now over the warranty life time 😞. But this seems like a good place to start, when I have tried the reinstallation I have completely blanked on doing a full clean reinstallation. So I'll start here, if the problem presist I'll try the other suggestion where I temporary uninstall iCUE and install HWinfo to see if the problem is with iCUE or the Hardware. But this seems also like a fine weekend project, *Fingers crossed* that this isn't the typical tech issue where the moment you ask for help on the tech the problem completely disappears until you have closed the issue with support/forum, as it hasn't happened again since I installed for so uninstalling HWinfo. So I'll be back with an update in a week or two depending on whether it's cooperative or not.

Thanks for the advice c-attack, it could seem like the base of the issue may lay there. I do however not use AIDA and/or HWinfo as I tend to use the programs like HWMonitor, TechPowerUp GPU-Z, Task Manager and/or MSI Afterburner if I need to monitor my system. And the problem with the fans do still happen even after I have restarted my computer and not started any other monitoring program but iCUE. But it seems like it could be some software entanglement as I did test by installing HWinfo, just to check it out, before quickly uninstalling it again as it immediately provocated the same issue I'm having with iCUE. Is there a proper log system for iCUE, or any other logging system, that I could use to pinpoint what/where the problem could be? To see if it is just a software entanglement crash that is the problem, or just a problem with iCUE and my Commander Pro in general, and how to permanently solve it.

I've started having this problem with my system where all of a sudden my fans wired up to my Commander Pro go from calm and quiet to max rpm out of nowhere. I've found that the problem lies in iCUE where my Commander Pro seems to "forget" the RPM control of my fans, and simply starts showing the voltage. I have a total of 6 fans: 3x HD140mm fans hocked up to my Commander Pro. (In the Gif these are the Fan #4-6 in the Commander Pro "Cooling" page), and the main problem. 3x HD120mm that has the RGB hocked to a RGB hub for so to be hocked up to the Commander Pro, while the fan control is hocked up to my H150i CPU cooler. Unnecessary? Maybe. Have it worked so far? Yes! (In the Gif these are the Fan #1-3 in the Commander Pro "Cooling" page, and can even be hidden.) In order for me to get the RPM down again on my fans and get iCUE to recognise the fans correctly again, I've come to the conclusion that the fastes way is to use "End Task" on Corsair.Service (32 bit) in the "Task Manager" over and over again. This was something I have only needed to do every blue moon or so when it started, but now I'm at times having to do it 2-3 times a day and it's getting old. And I've come to the realisation that I need to figure out what the problem actually is and have it fixed. I have tried to google the problem to see if other people have the same problem as me, but I can't say I've found a definitive explanation there that is the "Holy Grail" solution that have fixed my problem. Things I have tried to solve it is reinstall iCUE, but I used the export/import profile as I didn't feel like dealing with setting everything up again, and that's about it. I'm making this in hopes that it could shed some light, possible for Corsair to find/fix a possible bug in the software, and to get a definitive answer to WHY it is happening.