Not sure what temp files are there that could "take over" control from FanControl, and only for those 2 specific fans. I did, yes, removed anything related to the Gigabyte "SIV" software.
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 Weird that for some fans you can override the BIOS profile, for some you cant. 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. I have a Gigabyte Z390 AORUS ULTRA MoBo, when I used Gigabyte's software I was able to control these as well. The fan curves were all applied correctly, and now they are not (and all have the ?).Īny 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. Can you look into this 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.
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). Thus I suspect the problem comes from the new AMD driver, and not from FanControl itself. 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. 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).
0 kommentar(er)
