Rem0o
X870 Worked, then stopped after a reboot
If you are experiencing a crash Link the relevant/associated Windows EventViewer logs, and also FanControl's own log.txt.
Describe the bug I saw that version 221 fixes x870, so I decided to go into my BIOS and turn off the smart fan control. I set PWM as the fan type. I then tried to correctly pair the sensor with my three missing fans and to my surprise they all worked! It even automatically calibrated the fans and set all of the percentages and RPMs. After I rebooted my machine this no longer works and I cannot get it to work even if I completely uninstall the software and remove the fan control folder from the programs files x86 folder. It now fails to find anything. I am so fed up with this, why can't this work? Nothing in my BIOS changed. All I did was turn the machine off. I saved the configuration. I even made a backup of the configuration. This configuration that I saved no longer works. It could no longer pair a sensor properly or properly calibrate a fan. GPU fans were always fine and never stopped working (update: now that doesn't work at all either). everything has question marks.
Is there a log.txt file next to FanControl.exe with recent date entries? [Link it here]
Relevant hardware specs and setup MSI X870E Carbon Wifi AMD 9800X3D
@Alcolawl any clue?
Haven't experienced this issue on my end (nor have any testers) when developing the MSI solution. In fact I've just been running your latest release version since it came out and I'm not able to replicate this issue.
AMD Ryzen 7 9700X MSI X870 Tomahawk
I'd suggest attempting to create an entire new configuration. If it still doesn't show the ability to monitor or control any of the Fan headers then I'd start to question what's wrong with LHM and run that program individually (without FanControl running) and see if monitoring and controls work there.
BIOS version is a factor too. MSI released some updates specifically related to HW monitoring a few months back. I'm still on a BIOS version from December before all that nonsense happened because it's rock solid. So, for the end user, that might be worth looking into as well.
It's possible that signal RGB might have been interfering with this even though there were no fans set up in it to be monitored. That being the case, I need to use these programs alongside each other anyway. If it's confirmed that they conflict with each other then that's my fault I guess
I was going to suggest a conflicting program. This certainly could be the case. I've definitely encountered this several times with LHM, Fan Control, or HWInfo, etc.
Simple way to tell would be to ensure Signal RGB and it's associated processes and services aren't running and see if FanControl functionality returns. There's no reason a reboot should break its ability to detect hardware or control fan headers.
If you're using Signal RGB for RGB control, you can try OpenRGB or Mystic Light (I know, yuck. But I use it on my end and it's been completely unobtrusive).