Service stops after waking from Sleep

[memlir]

When issuing Sleep and waking the device up, the service is not there anymore.

Thanks for killing any middle-man software to get a service out of this, really needed this, and it's working well under non-admin users baring in mind that all it requested was a Controller Folder Access whitelist.

[Rem0o]

service_log.txt ?
Event viewer logs?

[memlir]

I'm having a hard time pinning down what the issue is, can't reproduce it anymore.

But the Service itself is not loading, and there's nothing on the log file.

[Rem0o]

can't reproduce it anymore.

But the Service itself is not loading

So which one is it? I'm confused.

[dankocrnkovic]

I have the sam issue. On every wake up, service craches.
Application: FanControl.Service.exe
CoreCLR Version: 10.0.826.23019
.NET Version: 10.0.8
Description: The process was terminated due to an unhandled exception.
Stack:
at FanControl.NvThermalSensors.NvThermalSensorsPlugin.Initialize()
at FanControl.Domain.BackendProviders.Plugin.PluginBackendProvider.Open()
at FanControl.Domain.ComputerAccessLayer.Initialize()
at FanControl.Models.IResultExtensions.Then[[System.__Canon, System.Private.CoreLib, Version=10.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]](FanControl.Models.IResult, System.Func1<FanControl.Models.IResult1<System.__Canon>>)
at FanControl.Domain.ComputerAccessLayer+<>c__DisplayClass18_0+<b__0>d.MoveNext()
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.Start[[FanControl.Domain.ComputerAccessLayer+<>c__DisplayClass18_0+<b__0>d, FanControl.Library, Version=268.0.0.0, Culture=neutral, PublicKeyToken=null]](<b__0>d ByRef)
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder1[[System.__Canon, System.Private.CoreLib, Version=10.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].Start[[FanControl.Domain.ComputerAccessLayer+<>c__DisplayClass18_0+<<TryRefresh>b__0>d, FanControl.Library, Version=268.0.0.0, Culture=neutral, PublicKeyToken=null]](<<TryRefresh>b__0>d ByRef) at FanControl.Domain.ComputerAccessLayer+<>c__DisplayClass18_0.<TryRefresh>b__0() at System.Threading.Tasks.Task1[[System.__Canon, System.Private.CoreLib, Version=10.0.0.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]].InnerInvoke()
at System.Threading.ExecutionContext.RunFromThreadPoolDispatchLoop(System.Threading.Thread, System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.Tasks.Task.ExecuteWithThreadLocal(System.Threading.Tasks.Task ByRef, System.Threading.Thread)
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading.PortableThreadPool+WorkerThread.WorkerThreadStart()
at System.Threading.Thread.StartCallback()

[svensvond]

Same here: Fan Control - not the Service - is crashing when waking up from sleep / hibernate.
It is not ADLX related.

---

Environment

• OS: Windows 11 25H2
• GPU: AMD Radeon RX 7900 XT
• Mainboard: ASUS ROG STRIX Z790-A GAMING WIFI D4
• CPU: Intel (Z790 platform)
• Fan Control version: (bitte ergänzen)
• Sensor backend: LibreHardwareMonitor (embedded in Fan Control)
• GPU backend tested: AMD ADLX (also disabled during troubleshooting)

---

When the service is running, I also run Fan Control because of the temperature tray icons.
The service drops one single log line after wakeup:

LHM detected new sensors and asked for a refresh: /lpc/nct6798d/temperature/5

Notes

• Issue is reproducible after every Hibernate cycle
• Normal system operation (no sleep/hibernate) is stable
• Likely related to sensor reinitialization rather than GPU stack

[Rem0o]

@dankocrnkovic
@svensvond

you two are completely different issues. Please open seperate tickets.

@dankocrnkovic That's seems like a plugin issue, with a native exception (at FanControl.NvThermalSensors.NvThermalSensorsPlugin.Initialize()). I can't handle that from FanControl itself. Needs to be addressed in the plugin.

@svensvond
Do you experience a crash or are you just reporting that there is a log every wake from sleep? Because that log is "normal". It just reports a late responding sensor.

[svensvond]

#4053

[dankocrnkovic]

@Rem0o

@dankocrnkovic That's seems like a plugin issue, with a native exception (at FanControl.NvThermalSensors.NvThermalSensorsPlugin.Initialize()). I can't handle that from FanControl itself. Needs to be addressed in the plugin.

Yes, I can confirm it was NvThermalSensors plugin. Without it, there is no crach.
But, logic should guard against problems in plugins. Some try catch around FanControl.Domain.BackendProviders.Plugin.PluginBackendProvider.Open() ?

[Rem0o]

There are try catches, but managed Try catch won't do anything for native exceptions.

[memlir]

My apologies for not finding time to get back on this.

I found myself having to rebuild Windows for irrelevant reasons, but i am still facing the issue on a fresh setup, although i think the Service itself is not loading up at all. On the previous system, it was loading 30+ seconds after the admin user logged in, but not for the rest of the non-admin users, therefore it makes sense why it wasn't surviving a user switch, but i am still confused as to how the service loads up. As for waking from sleep, that was something that i could never make a theory on.

Event Viewer has no entries unless i manually try to load the service up, which it fails.

If i load the app manually, in the previous system it was requesting if i want to kill the service process to start the normal process. Obviously it is not doing that now since no service is running.

I am very aware that I as the user am the problem here, and the sole point why i started the thread was to see if this can be formulated more friendly in terms of configuration.

EDIT:

Alright, i think i reported this when you shared the zip of the service prior releasing it.

This is what i got when running the service file manually in terminal:

`PS C:\Program Files (x86)\FanControl> .\FanControl.Service.exe
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\Program Files\dotnet'.
Failed to run as a self-contained app.

• The application was run as a self-contained app because 'C:\Program Files (x86)\FanControl\FanControl.Service.runtimeconfig.json' was not found.
• If this should be a framework-dependent app, add the 'C:\Program Files (x86)\FanControl\FanControl.Service.runtimeconfig.json' file and specify the appropriate framework.`

FanControl.Service.runtimeconfig.json file is not located at:

C:\Program Files (x86)\FanControl\FanControl.Service.runtimeconfig.json

It's on:

C:\Program Files (x86)\FanControl\Configurations\FanControl.Service.runtimeconfig.json

After copying the file over, the Service is able to run manually without an error.

EDIT2:

Service runs now during boot fine, and from the two tests I've run, it's active prior the login screen. This is fantastic and very much desired.

However, when login in, it's probably killing the process and re-running it, which is taking up to 30 seconds. Clearly audible as fans go to max output, followed by reading the actual config.