Hwinfo Msi Afterburner

[Stayce Cawthorn]

Finallyfound out why my fan speeds have been weird as well as my older AIO running off my CoPro - as soon as HWinfo64 is opened **Even if you select the option to ignore corsair sensors** the commander pro crashes.

The problem is the Corsair Commander Pro and your Corsair AIO cooler are listed separately in HWInfo now. I don't remember this being the case before, but my build has been down for quite some time getting it rebuilt (several months - I know, I'm lazy). After getting everything set back up and updated, I ran into exactly the same issue. Thinking it was a problem with the Commander Pro, I tried force updating the firmware, which would fix it until HWInfo was opened again. Really drove me nuts at first. I knew I had Corsair disabled in HWInfo, but when I went to look again and double check, the cooler (H150i Pro, think it's called Corsair CLC) was still disabled but the Commander Pro was not. I don't remember the Commander Pro showing up in HWInfo before, but it sure is now. Right click on the Commander Pro in HWInfo (can't remember the specific name, but it was right above the Corsair CLC and had sensors for fan speeds, voltages, etc) and disable monitoring. Reboot the computer, and now you should be able to open both iCUE and HWInfo without the Commander Pro going all wonky.

Alternatively, you could just leave the AIO and Commander Pro enabled in HWInfo, close HWInfo, get everything set up in iCUE, which saves it to the hardware (make sure to edit the hardware profiles for lighting if you want that too), then close iCUE and just use HWInfo for monitoring, which would also allow you to import the sensors from HWInfo into MSI Afterburner/Rivatuner so you can monitor the sensors in game if you like.

How about setting up the fan speed curve based on Commander Pro temperature sensors and then shutting down the iCue services. Then will that allow the fan speed to be automatically handled by Commander Pro hardware while HWiNFO show the fan speeds?

The Commander will continue to run its fans from its native temp sensors with or without the software running. So if you prefer to use AIDA, HWiNFO, whatever, you just need to not run iCUE in background. The Commander is very easy to set up for this. Most other Corsair devices also have hardware settings you can save to use when the software is not running. Some users are able to successfully use both programs by disabling the monitoring of all Corsair devices in HWiNFO. However, I don't see a lot of reason to run two simultaneously. If you need the more detailed monitoring info, use the other program and don't run iCUE at the same time.

That's nto a solution, that's a poor workaround. I can't use a custom fan curve on my H80i V2, as it seems to be reliant on software. Also, I have RGB set to do things based on temps, that can't seem to be applied in HW. Also, the patterns running my LED strip can' be applied in HW.

I am not responsible for re-writing the software or changing the way the world works. The thread is about how to keep the software programs from crashing, giving back garbage values, or losing control. As stated, the best advice is not to run them at same time if you don't need to. If you do, exclude Corsair hardware from the monitoring so they aren't polling the same device over and over. No one said anything about Afterburner. We are all using that.

And ... let's be clear. This isn't Corsair's issue. It's HWInfo's. They - for some reason - insist on accessing the Corsair hardware knowing that the devices only support single access. Now, they reverse engineered that interface because it's not documented (for a reason). So ... in other words ... they really shouldn't be doing it. And it certainly shouldn't be the default behavior and require you to opt-out. It's rude, at best.

Disabling "Corsair Link/Asetek" support and using the portable version of HWInfo (without loading the driver) does work. I use HWInfo all the time without issue. But you must jump through the hoops due to HWInfo knowingly causing the issue. Because they do know about this and refuse to change it.

My point about afterburner was just that very often the response when people talk about this tool or that tool for monitoring temps/fans, etc, is that Corsair officially say you can't use any other monitoring software while running iCue, which is utter nonsense - if they mentioned that on packaging, and pre-sales I bet a lot of people would choose alternatives.

Thanks for the reply, I've uninstalled HWinfo64 completely and my iCUE is still crashing, Corsair support has told me to uninstall all CPU-Z/GPU-Z/HWinfo64/Core Temp etc but so far the crashes are still happening :confused::confused:

From then on things have worked for me, something about the way these two interact must corrupt something, somewhere and leave it corrupt... i've had it happen on two systems with various clean win10 installs, so something must have a chance of corrupting with these two softwares running and remaning despite updates to the software.

and i just installed Aida64 to do some stability testing for my 5.0 overclock on my 9700k and long behold i go to open msi afterburner and now aida64 opens ever time i open afterburner any help would be appreciated

Depending on what you need, you may need several programs for it under linux. As far as gui goes, i do not know an exact analogue. For the command line, if you need system component information, you can use hwinfo or inxi. If you need temperatures, sensors is your friend.

There is a gui program psensors. Also, if you need cpu-z, an almost exact analogue is cpu-x, but it is not in the repos (appimage is available).

3a8082e126