My custom loop is nine Corsair ML fans (non-RGB) and they ran fine off the motherboard headers on my Asus Z370. Previously I had a profile for general use, and one that I toggled on before I started a game (headphones = I don't care if the fans are loud) and that is basically what I want to go back to. This means that I would either have to have two apps to control cooling, or drop ~$80 on a new Corsair fan hub. Now they have iCUE and while I have it for my AIO, the Commander mini fan controller hub that I have had & used for around 5 years, is not compatible with the new software. I will give them a try, but I still don't like having to restart to get to the controls.įor several years I have been using the Corsair link software, and other than some problems with their crappy 'Link' software a couple years back, I was fine with it. Yes my fans are PWM and I did look at the UEFI fan controls last night after you mentioned it, and there is a way to set curves. PSU: EVGA SuperNOVA 750 G+, 80 Plus Gold 750W RAM: G.SKILL Ripjaws V Series 64GB (2 x 32GB) 288-Pin DDR4 SDRAM DDR4 3600 Mobo: MSI MAG Z490 TOMAHAWK LGA 1200 Intel Z490ĪIO: CORSAIR iCUE H150i RGB PRO XT, 360mm (we keep the house around 23) I would be just fine with the case fans not spinning (with the AIO fans at low RPM) until temps hit the high 30's, and then ramping up.

I found out that using a custom order of sensor in HWinfo and moving the sensor I read from at the very top of the list will prevent this from happening.īeta Was this translation helpful? Give feedback.Most of the time my idle temps for CPU & GPU are around 28-30. This will happen if the added or removed sensor is over (on top) of the one FanControl is reading from in HWinfo list. if a sensor is added, removed or hidden in HWinfo while running), FanControl will returrn an incorrect or NaN reading and the fans associated with that sensor will ramp up or stop. Note2: This plugin rely on the order of the sensors listed in HWinfo, meaning if the order of sensor changes in HWinfo (ex. This has nothing to do with FanControl as it is a limitation of HWinfo free version.

Furthermore, unless you use the paying version of HWinfo (PRO) the feature will deactivate itself every 12hrs. You will need to activate it in HWinfo (settings, General/ user interface tab). Note: This plugin rely on a feature of HWinfo called 'Shared memory support'. While fancontrol is closed, unzip the files from the zip in the plugin folder of Fancontrol, if needed, unblock the dll (see here), start fancontrol, activate the plugin in the sensor menu (top right 3 dots), refresh sensors (you might need to restart FanControl).

Fan control using hwinfo