FanControl.Releases
FanControl.Releases copied to clipboard
Rem0o
being overridden by external ??? i have no other control software
why is this software not trying to force primary control i have no other software to control my fans so why is it now with the latest update v121 that the software is allowing this
especially with my cpu header i have it set to 70% but its sitting at 43% now this was never an issue in v120
I have had 2 thermal shutdown due to fancontrol being 'overriden by an external software' leaving my CPU fan at 0% under load.
i think fancontrol is allowing the bios level control to take over isnt the point of this software to be the replacement to bios control now to figure out how to download older releases
@clutchmaster420 You can find v120 here: https://github.com/Rem0o/FanControl.Releases/blob/V120/FanControl.zip
@clutchmaster420 You can find
v120here: https://github.com/Rem0o/FanControl.Releases/blob/V120/FanControl.zip
thanks
The "being overridden by external" is just an indicator I added for an existing condition. It means the control is not following the curve due to an external source. No logic was changed as far as fan controlling is concerned. Any problem you identify with the "?", you had it before, I just didn't highlight it with an icon.
The "being overridden by external" is just an indicator I added for an existing condition. It means the control is not following the curve due to an external source. No logic was changed as far as fan controlling is concerned. Any problem you identify with the "?", you had it before, I just didn't highlight it with an icon.
if thats true then why on v119 i can watch it for 30 minutes and the % doesnt change and rpm doesnt change then i update to v121 it gives up control within 15 seconds
if what u think is happening with my system then i should expect the icon to be blinking since the software should be attempting to take back control but im just seeing a solid icon as if the software has hand off control
FanControl, with it's current implementation with LHM, won't "fight" for control over a header. It was always this way. The way the LHM control is done, it expects itself to be "alone" trying to control that specific header. It's kind of annoying in some scenarios, but you should also never have 2 sources trying to control a header, hence why I left it this way for now. I thought about a "force" mode for a control, which would force the value onto the header at every update cycle, but that would consume more resources.
hmmmm then i can only think something with the detection is causing an unintended affect resulting in loss of control cause im on v120 now and its working as it should
Keep in mind the condition may (should also) occur in V120, you just won't get the icon, as that was an addon with V121.
the only software i have that can control fans is msi afterburner and open fan control and my bios
How do I get fan control to control my fans? It wasn't always this way. I set a mix and watched/listened to Fan Control work, which it did for a long time. I think it may have changed in V120, but I can't be sure exactly when. Either way with this new update I'm seeing the question mark and it seems like BIOS is controlling the fans. I don't have any other software that would control them.
How do I get fan control to control my fans? It wasn't always this way. I set a mix and watched/listened to Fan Control work, which it did for a long time. I think it may have changed in V120, but I can't be sure exactly when. Either way with this new update I'm seeing the question mark and it seems like BIOS is controlling the fans. I don't have any other software that would control them.
maybe this will help image of my setup
Im getting this as well, however I do understand that you've simply implemented a UI feature to show an issue that was always there.
Could you maybe offer some suggestions on what we set our Bios too, in an effort to stop it interfering with our manual fan settings?
Thanks
EDIT: Went into the BIOS and set all my fans to PWM and disabled 'smartcontrol' Doesnt seem to of made a difference, ill keep trying to work it out.
I downgraded to version v119, and that removed the "?" marker, but not the behavior that leads to fanControl loosing control on the fan speed (thus locking the fan speed to whatever it was when that event happens).
What else has happened at the same time this new bug appeared is an update to Catalyst 22.7.1, which I believe also installed a new version of the chipset driver (for me a B450 chipset) at the same time. Thus I suspect the problem comes from the new AMD driver, and not from FanControl itself.
Is there a default bios setting for GPU's that provide thermal protection by operating the fans? I'm getting this error on my GPU fan control. Running a 3090ti and have disabled evga xi precision, armory crate so I don't know what other program could be interfering with it?
I downgraded to version v119, and that removed the "?" marker, but not the behavior that leads to fanControl loosing control on the fan speed (thus locking the fan speed to whatever it was when that event happens).
What else has happened at the same time this new bug appeared is an update to Catalyst 22.7.1, which I believe also installed a new version of the chipset driver (for me a B450 chipset) at the same time. Thus I suspect the problem comes from the new AMD driver, and not from FanControl itself.
I believe this might be the case. I recently updated to 121 and 22.7.1 as well (in the same restart actually) and I am now having this show up on all fans (where before it was just my RX 6750 XT that would not listen to FC). This might be unintentional. Can you look into this @Rem0o when you get a chance? I know, for a fact, it was working before because I opened it beforehand to check for an update (before the 22.7.1 Adrenaline update) and before I restarted. The fan curves were all applied correctly, and now they are not (and all have the ?).
after i slept on it im thinking it might be related to monitoring software polling fan RPM info im thinking this might be confusing fan control resulting in it to stop sending speed commands
in other words fan control is thinking somethings trying to take control so it stops sending commands
Any idea how to regain control over those fans? I have a default profile set in BIOS for all of my fans, but only 2 fans are actually getting overridden by the BIOS values and I cant see a difference there in the settings...
I have a Gigabyte Z390 AORUS ULTRA MoBo, when I used Gigabyte's software I was able to control these as well. (SIV was buggy as hell and the temp. sources were limited, that's why I changed to FanControl.) Currently the Fans in question seem to just use what I've set in the BIOS. Weird that for some fans you can override the BIOS profile, for some you cant.
ugg if only there was a debug option that could log what device id is causing the conflicts
Any idea how to regain control over those fans? I have a default profile set in BIOS for all of my fans, but only 2 fans are actually getting overridden by the BIOS values and I cant see a difference there in the settings...
have u uninstalled the gigabyte software and cleared ur temp files im thinking fan control has some temp file that doesnt get replaced with every boot cause i got my control back after clearing my temps and stopped running hwinfo and slightly adjusting the minimum values of my linears up and back to what i had it set to i still think what ever code is being used to detect the conflict is resulting in some kind of break so when fancontrol goes to command a header it doesnt go through as if fancontrol lost that address
Any idea how to regain control over those fans? I have a default profile set in BIOS for all of my fans, but only 2 fans are actually getting overridden by the BIOS values and I cant see a difference there in the settings...
have u uninstalled the gigabyte software and cleared ur temp files im thinking fan control has some temp file that doesnt get replaced with every boot cause i got my control back after clearing my temps and stopped running hwinfo and slightly adjusting the minimum values of my linears up and back to what i had it set to i still think what ever code is being used to detect the conflict is resulting in some kind of break so when fancontrol goes to command a header it doesnt go through as if fancontrol lost that address
I did, yes, removed anything related to the Gigabyte "SIV" software. Not sure what temp files are there that could "take over" control from FanControl, and only for those 2 specific fans. I've tried everything at this point, pair the speed sensor, detect fan speed, refresh sensors, but nothing worked.
EDIT: Tried one more thing; instead of leaving it on "auto" in the BIOS, I specified whether its PWM or Voltage, but no difference.
So today I tried to refresh the sensors, and the ? blinked on and off on all the fans about 15 times and then it went off and they are now controlled by FC. I am not sure what happened, I didnt change anything other than refreshing them again.
RX 6750 XT is still not controlled, and I know why (because Adrenaline is controlling them) but im not really sure how to tell Adrenaline to not control it (or if that is even possible).
@vikdean try setting a manual set speed in the bios instead of "auto".
Its set to manual, I'm using a custom curve for each fan.