Closed brunoherrera closed 1 year ago
One way to fix it. Whitelist entire FanControl folder in Windows Defender. Instant fix to high CPU usage
One way to fix it. Whitelist entire FanControl folder in Windows Defender. Instant fix to high CPU usage
that's not a fix, liquidctl.exe is constantly being open and closed, making unnecessary writes to storage and taxing the cpu, rising temperatures.
hmmm, maybe its Fan Control that is trying to poll the exe the same way it does with dll files, when it should just do that only with the dll's, but liquidctl should actualy let us know if that's the case so we can open an issue in fan control. EDIT: It is polling the exe the same way it does the dll's, but it's just the way it is, liquidctl works that way and is not efficient. I found a workaround launching it (liquidctl.exe) with task scheduler and argument initialize all, it lets me use HWiNFO for liquid temperature and pump speed reliably.
@jmarucha maybe you can change liquidctl.exe out of plugins fodler so it isn't called by FanControl every second? I tried changing LiquidctlCLIWrapper.cs:11 to public static string liquidctlexe = "liquidctl\liquidctl.exe"; But I'm a mess in windows with WSL and python3, it has some errors when executing build-liquidctl.sh, so becasue I don't even know if changing that line in wrapper.cs will work and re-path I'll just quit, but please move that .exe out of plugins folder
Since this issue was bugging me for some time now, I made a custom fork of liquidctl and this plugin, which stops liquidctl from starting every second by using a custom made interactive mode in liquidctl. Haven't tested it at all on anything else than my computer, so use at your own risk if you want to. I'm just leaving this here if anyone more knowledgable is interested in using this approach and maybe commit a better change to liquidctl and this plugin and needs a base start which works. Link
@SuspiciousActivity could you create pull requests on the original repos ?
Since this issue was bugging me for some time now, I made a custom fork of liquidctl and this plugin, which stops liquidctl from starting every second by using a custom made interactive mode in liquidctl. Haven't tested it at all on anything else than my computer, so use at your own risk if you want to. I'm just leaving this here if anyone more knowledgable is interested in using this approach and maybe commit a better change to liquidctl and this plugin and needs a base start which works. Link
works in my pc with Kraken X73, thanks!!!
Since this issue was bugging me for some time now, I made a custom fork of liquidctl and this plugin, which stops liquidctl from starting every second by using a custom made interactive mode in liquidctl. Haven't tested it at all on anything else than my computer, so use at your own risk if you want to. I'm just leaving this here if anyone more knowledgable is interested in using this approach and maybe commit a better change to liquidctl and this plugin and needs a base start which works. Link
Hi,
I tried to use your fork, but I get "LiquidctlPlugin could not initialize or has no sensors." message when starting Fan Control (v149). Liquidctl is working OK, beacause if run liquidctl status I get:
ASUS Aura LED Controller (experimental) ├── ARGB channels: 3 └── RGB channels: 1 Asetek 690LC (assuming EVGA CLC) ├── Liquid temperature 34.7 °C ├── Fan speed 0 rpm ├── Pump speed 2910 rpm └── Firmware version 2.10.0.0
I think that it fails because it's trying to interpre "Firmware version" as sensor data... because I get this in the Fan Control log:
@kromosomX that should go in the issues section of the fork, I will cite the following comment from @jmarucha in regards to the executable needed for liquidctl:
In the case of that specific plugin, sadly yes, it would seem to be highly inefficient since it most likely call the exe at every update cycle ( 1 Hz ) to push and pull the information.
That's specific to that plugin implementation.
and since @SuspiciousActivity solution works for me I'll close this issue
@SuspiciousActivity have you tried talking to LiquidCTL team? The idea is amazing and I think they may be willing to get it upstream.
I am having issues with it recognizing a nzxt smart device 2, it works with my x72 but not the smart device 2
Follow up of High CPU Usage (Antimalware Service Executable)
The root of the issue is that liquidctl.exe is constantly being opened and closed, I think 2 times per second, maybe more, checking resource monitor its constantly writing to %LocalAppData%/Temp, folders named something like: _MEI154122, constantly modifying, deleting and creating thema gain and again, I added appdata folder to windows defender exclusions and it fixed the Antimalware Service Executable (MsMpEng.exe) high cpu issue, but opening and closing liquidctl.exe still makes the CPU work too much and temps rise anyways.
I'll disable the plugin and use HWiNFO instead untill this gets sorted out.