Fan control not starting

[RicoW1985]

Hi, Today i noticed fancontrol is not working at all.
I uninstalled and installed latest version from the website, tried both installers and the zipfile.
it asks permissions but after that nothing happens.
Im running windows 11 with latest updates.
I hope anyone can help, because i really love the program.
thanks in advance
(added screenshot with specs)

[boogieboard]

I also have the same issue. I attempted to update via the GUI and nothing comes up anymore.

[adonaldson]

Edit: While my comment worked for me, it may not work for you.

In case anyone stumbles onto this in the future, clearing out / backing up my old userConfig file allowed the app to start. Then it's a case of re-creating your old settings.

[RicoW1985]

adonaldson, unfortunatly this didn't help

[adonaldson]

Good to know, I'll update my comment to make it sound less confident :)

[Rem0o]

Any crash event in eventviewer? Any logs in logs.txt?

[N1ckstars]

yeah i have the same issue too, tried reinstalling it with .net 4.8 and 8, tried using revo uninstaller to remove all the files associated with it, with and without restarts, and still nothing

[WCDThor]

Consider figuring out how to revert to V208 or V207. This latest version (V209) has caused me a lot of issues, different from yours though, and when I have time after I'm done with school I'm thinking of reverting if there hasn't been a patch by December 10th.

[AdiMarianMutu]

I'm having the same issue, I have an AMD GPU (RX 7900XTX) and I've done a bisect install starting from the last version 209 and found out that the last working version on my system is 194.

I see this in the 195 version changelogs New built-in AMD GPU (ADLX) support.

I think that the built-in AMD GPU support is clearly failing.

Any crash event in eventviewer? Any logs in logs.txt?

The logs.txt file is not even being created.

P.S: Anything above 195 fails to start even when the AdlxWrapperSettings property is disabled from the fans_curves.json file.

P.P.S: I'd happily try to solve this on my own if you'd make the project open source.

---

For anyone having the same issue as me (which started by noticing that FanControl GPU sensor was not working anymore), the (hopefully temporary) solution is:

As HWInfo is able to correctly read the sensor of my AMD GPU you can follow these steps for FanControl v194.

1. Install HWInfo
2. Download this plugin: https://github.com/Rem0o/FanControl.HWInfo
3. Create the HWInfo folder inside the Plugins folder of FanControl
4. Add there the FanControl.HWInfo.dll file
5. Go the HWInfo's "Configure Sensors" option menu, then to the "HWInfo Gadget" tab. Have the "Enable reporting to gadget" checkbox checked and select "Report value in Gadget" for all sensors you want to import.
6. Now you can use the reports from HWInfo into FanControl.

[Rem0o]

@AdiMarianMutu

I'd happily try to solve this on my own if you'd make the project open source.

Good news, the AMD driver/api portion of it is: https://github.com/Rem0o/ADLXWrapper . There is a test app in there you can play with.

Otherwise, if there are crash events in your Eventviewer, would be useful. Also the driver version you are using for your AMD card.

[RicoW1985]

im sorry im not that handy with computers to install the adlxwrapper.

Application: FanControl.exe
CoreCLR Version: 8.0.1124.51707
.NET Version: 8.0.11
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF80B4F2BD3

Naam van toepassing met fout: FanControl.exe, versie: 207.0.0.0, tijdstempel: 0x66e80000
Naam van module met fout: atiadlxx.dll, versie: 32.0.12019.1028, tijdstempel: 0x670985c5
Uitzonderingscode: 0xc0000005
Foutmarge: 0x0000000000062bd3
Id van proces met fout: 0x0x43E0
Starttijd van toepassing met fout: 0x0x1DB44D6D249CDA6
Pad naar toepassing met fout: C:\Program Files (x86)\FanControl\FanControl.exe
Pad naar module met fout: C:\Windows\SYSTEM32\atiadlxx.dll
Rapport-id: 2779fba1-4710-4ed3-aa0d-d07f230fb145
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout:

this is what i get in eventviewer.
running 24.8.1 of amd software.

hope this helps.

thanks in advance

[Rem0o]

running 24.8.1 of amd software

Is there a reason you are not running the latest version? 24.8.1 is busted and causes various crashes.

[RicoW1985]

Yes, it crashed alot of games on dx12, will update and see if it works now.

[RicoW1985]

well, fancontrol works again! thanks!
now I need to figure something else out though.

the main reason I downgraded to 24.8.1.
I guess i will be gaming on dx11 until it gets fixed

[AdiMarianMutu]

@AdiMarianMutu

I'd happily try to solve this on my own if you'd make the project open source.

Good news, the AMD driver/api portion of it is: https://github.com/Rem0o/ADLXWrapper . There is a test app in there you can play with.

Otherwise, if there are crash events in your Eventviewer, would be useful. Also the driver version you are using for your AMD card.

I'll take a look once I have some more free time on my hands.

I'm using the 24.8.1 driver as the last one 24.10.1 is pure crap, crashes over crashes (reddit is full of people reporting this).

Here the result of the Eventviewer for the v209:

Faulting application name: FanControl.exe, version: 209.0.0.0, time stamp: 0x67110000
Faulting module name: atiadlxx.dll, version: 32.0.12019.1028, time stamp: 0x670985c5
Exception code: 0xc0000005
Fault offset: 0x0000000000062bd3
Faulting process id: 0x0x44E4
Faulting application start time: 0x0x1DB44787D2369D1
Faulting application path: Z:\Stand Alone Apps\FanControl\FanControl.exe
Faulting module path: C:\Windows\SYSTEM32\atiadlxx.dll
Report Id: 4dade99d-e101-4ed9-a8a7-8b14fe83a4db
Faulting package full name: 
Faulting package-relative application ID: 

It seems that the atiadlxx dll is the one failing, to be honest I'm not surprised, AMD is the best in providing faulty drivers :)

[RicoW1985]

@AdiMarianMutu

I'm using the 24.8.1 driver as the last one 24.10.1 is pure crap, crashes over crashes (reddit is full of people reporting this).

this here is your problem. I had the same issue... now running dx11 for the time being