[Experimental] Manual Fan Control

[seerge]

Hello fellow community,

Recently I have discovered a way to directly set fan speed in percentage points for each fan individually.
It uses same method as MyASUS does when runs your "fan testing".

In existing and standard way to set a "custom" fan curve - fan behavior would be still handled by BIOS and follow it's internal algorithm. This BIOS algorithm is different for different models, sometimes includes a very high hysteresis (delays before acting), can override some custom fan behavior, etc.

In "alternative" approach, it's possible to actually literally manually set fan speed every second based on temperature readings.

This build implements "manual" fan control as soon as you check Apply Custom Fan Curve, when you uncheck it - fan behavior will be returned back to BIOS.

Current implementation details

• More precise fan speeds, following custom fan curve as close as possible
• Fan speeds are being updated every second
• CPU and GPU temps are calculated as an average from last 6 seconds (can be set via config)
• CPU fan follows CPU temp, GPU fan follows GPU temp, Mid fan follows CPU temp
• If GPU temp is not available by some reason (for example GPU is disabled or sleeping) - GPU fan will follow CPU temp instead
• If CPU temp is also not available by some reason - fan behavior will be returned back to BIOS defaults
• Minimum fan speed is 20% unless it's set to OFF completely (similar to how BIOS handles this)
• Maximum fan speed is 100%
• Fan speed will follow line between dots, not only dots themselves
• Fans will react on temp change almost immediately

Potential downsides and risks

• If you quit application incorrectly during manual fan control, fans may keep running on last used speed and will not react on temperature changes
• No idiot-protection. If you set fan speeds to be low, they will be low and your device will heat up quickly

Please test on your own risk (!) and only as a last resort in case you can't achieve desired fan behavior otherwise

Download Experimental Release

Updated 11.09.2025 (0.229)

Note

NOTE

The latest Asus System Control Interface v3.1.41+ restricts access to the driver required for "manual" fan control to SYSTEM processes only. So if it doesn't work for you, you can:

Method 1

1. Uninstall the latest Asus System Control Interface
2. Install the previous version 3.1.40 (or earlier)
3. If Windows Update still overrides it, go to Device Manager -> System Devices -> Asus System Control Interface, then select Driver -> Roll Back Driver to 3.1.40

Method 2

1. Download and extract PSTools
2. Place PsExec.exe into the same folder as GHelper.exe
3. Run in PowerShell as Administrator:

   ./psexec -i -s "$PWD\GHelper.exe"

Possible params for %APPDATA%\GHelper\config.json (with their default values)

"fan_min": 20, - minimum fan speed (in %) when it's not OFF
"fan_hysteresis": 6, - number of seconds to calculate average CPU / GPU temp (set 1 for instant reaction)
"fan_shift" : 50, - weighted average coefficient between CPU (or GPU) temp and MAX(CPU,GPU) temps in a range from 0 to 100

• If you want GPU (CPU) fan to follow only GPU (CPU) temp, leave it as is
• If you want GPU (CPU) fan to follow MAX(CPU,GPU) temps, set it to 100
• If you want GPU (CPU) fan to follow average between GPU(CPU) and MAX(CPU,GPU) set it to 50, etc :)

If you see a big (more than 500RPM) difference between fan curve and actual readings - try to click Calibrate, it will run a quick measurement process and adjust Y-axis to match actual maximum RPMs

You will see what is actually being set as your fan speeds on Fans+Power screen under fan curves chart. Don't forget to click Apply.

[FliesQQ]

At this setting, the fan speed on the left side of the machine(CPU fan) is at full speed.

At this setting, the fan speed on the right side of the machine(GPU fan) is at full speed.

But, At this setting, fan speed raise to max speed need almost 1 min, not particularly fast.
However, It's worked.

[seerge]

@FliesQQ how fast fans will speed up still depends on hardware of course :) actual command is being sent immediately (i.e. every second)

[FliesQQ]

So this is already very good now.
But FN Lock not work.
And use this should I stop all ASUS services? Now my running Asus service is 0.

[FliesQQ]

If GPU and CPU both in use, seems like CPU fan curve not function correct.

[abdulkadirozyurt]

@abdulkadirozyurt in relation to this experimental build it's only ones listed in the head post here :) As for the rest you can check Power user settings

I didn't mean the one about this experimental build, I actually asked if there is any documentation about what all the entries in config.json mean and what they do. Thank you anyway.

I would also like to point out something like this.

With this 0.194 beta version, I was able to control the fan on my 2021 asus tuf gaming f17 model code device, which I normally could not control the fan. However, today I upgraded to 0.195 pre-release version and the fan control was canceled. First I closed ghelper completely, then I deleted the GHelper folder in %AppData%, then I deleted the exe file of GHelper. Then I downloaded the 0.194 stable version and when I tried again, the fan control did not work again. Then I did the same thing again, deleted everything that needed to be deleted, downloaded this beta version and it worked.

But here's the thing, I started using the beta version and then the stable version came, I upgraded to the stable version and it was working. I deleted everything and installed the 0.194 stable version and it stopped working, I don't understand why this happened?

[seerge]

@abdulkadirozyurt Power user settings - is a full list of config settings that you may change (that don't exist in UI)

If you are using Experimental build - you need to keep using it , mainstream branch does not have this manual fan control.

[abdulkadirozyurt]

@abdulkadirozyurt Power user settings - is a full list of config settings that you may change (that don't exist in UI)

If you are using Experimental build - you need to keep using it , mainstream branch does not have this manual fan control.

Okay, I get it now, so I shouldn't update until I see this experimental feature in the new stable release description, right? Will this feature come to the stable release in the future?

[seerge]

Yes, you should download updates from this thread only :) I don't plan to merge manual fan control into mainstream branch yet.

[abdulkadirozyurt]

Yes, you should download updates from this thread only :) I don't plan to merge manual fan control into mainstream branch yet.

I got it.

[seerge]

@FliesQQ values that is being set look correct and along the fan curve.

You have mentioned that fans take time to spin up, most probably it’s slightly lagging because of that. Cause, as I understand, temps jump quickly in your testing :)

[FliesQQ]

Yes, the temperature changes too quickly and the fan responds too slowly. If the temperature fluctuates, it is possible that the temperature has risen, but the fan speed setting is still at the low temperature speed.

[seerge]

@FliesQQ fan "setting" is what you see in a red label (so it's practically instant). But how fast actual fans would react on this - is something outside of my control unfortunately

[FliesQQ]

Yes, it's really a pity.

[seerge]

@FliesQQ you can tackle that with a fan curve :) rise it to higher RPMs a bit faster

P.S. I have also updated build in the header-message, now it will refresh speeds once every 500ms (so twice more frequent)

[inthecatsdreams]

Before this update it was impossible for me to set a custom fan curve because of the bios rejecting it, now I can finally set the one I want! Thank you so much!

EDIT: My Laptop is TUF A15 with an RTX 3050

[seerge]

Great news

[fscottcopeland]

Unfortunately this build doesn't appear to be respecting my fan curves still :(

Log extract:

2024-03-23 20:43:21: Mode = 0 : OK
2024-03-23 20:43:21: GET GPU CLOCKS: 0, 0
2024-03-23 20:43:21: GET CLOCK LIMIT: 0
2024-03-23 20:43:21: ReadGPUPowerBase: -65536
2024-03-23 20:43:21: Manual fan control OFF
2024-03-23 20:43:22: Mode = 0 : OK
2024-03-23 20:43:22: GET GPU CLOCKS: 0, 0
2024-03-23 20:43:22: GET CLOCK LIMIT: 0
2024-03-23 20:43:22: ReadGPUPowerBase: -65536
2024-03-23 20:43:22: FanCPU = 32-3C-46-4B-50-55-5A-5F-0C-16-1F-28-31-39-43-4A : OK
2024-03-23 20:43:22: FanGPU = 28-32-37-3C-41-46-4B-50-0C-16-1F-28-31-39-41-4A : OK
2024-03-23 20:43:22: Manual fan control ON
2024-03-23 20:43:22: PowerLimit A3 = 40 : OK
2024-03-23 20:43:22: PowerLimit A0 = 60 : OK
2024-03-23 20:43:22: PowerLimit C1 = 80 : OK
2024-03-23 20:43:23: PowerLimit C0 (GPU BOOST) = 25 : OK
2024-03-23 20:43:23: PowerLimit C2 (GPU TEMP) = 87 : OK
2024-03-23 20:43:23: PowerLimit A3 = 40 : OK
2024-03-23 20:43:23: PowerLimit A0 = 60 : OK
2024-03-23 20:43:23: PowerLimit C1 = 80 : OK
2024-03-23 20:43:23: PowerLimit C0 (GPU BOOST) = 25 : OK
2024-03-23 20:43:23: PowerLimit C2 (GPU TEMP) = 87 : OK

As you can see, the FanCPU and FanGPU percentages don't match what is actually running (confirmed by hwinfo fan reading)

[seerge]

@fscottcopeland can you switch scale to RPM? Asus has quite specific interpretation of % points :)

[fscottcopeland]

Here you go. I've included my HWiNFO graphs too, in case it helps. GPU seems to hit ~71c and then jumps to 5000RPM, despite the 70c point being 4200RPM and 75c being 4600RPM. CPU doesn't seem right either.

[fscottcopeland]

The frustrating thing is that if I disable the custom fan curve, the fans then run slower - e.g. the GPU fan won't then jump to 5000rpm as soon as it hits 70c.

[fscottcopeland]

@Summersoff what's your laptop? Duo 16 2023 too?

[seerge]

@Summersoff then it's just a BIOS idiot-protection, which is actually ... good :) I have similar behavior on my ROG Ally. It would keep fans off until something like 55-60C and then no matter what app sets to it - will ramp them up.

[seerge]

@fscottcopeland if you disable custom fan curve, it's back to whatever default fan behavior is for each of your modes :)

[fscottcopeland]

Yeah. Such a shame. The stock balanced fan curve isn't aggressive enough - whilst the manual fan curve gets overridden and then becomes OTT. I really need a balance in between.

[yesnt10]

Thank you so much! it works great!

[seerge]

@yesnt10 amazing

[manciuszz]

Testing it atm. Seems to work fine so far. Though an optional hysteresis feature would be nice, cause I hear the fans whooshing up and down often

[seerge]

@manciuszz they do :) because one main complains that people accuse G-Helper of - is that fans are "slow" to react and "don't follow curve precisely" (even though when fans are controlled by BIOS it's absolutely not related to the app)

I can add a hysteresis in a form of calculating an average of CPU / GPU temps for last 3 or 5 seconds, instead of acting immediately

[manciuszz]

That would be a nice to have. Preferably, hysteresis could be adjustable by the user, that would allow the user to set their preference whether they want faster reaction times or more stable fan speeds. I personally don't hear the fans because I'm wearing a headset, but I don't think the fans should be whooshing up and down that often either xD

[seerge]

@manciuszz I have updated build in the main post, and added default hystheresis in a form of using average temperature for last 6 seconds. It can be also adjusted via config.

[manciuszz]

Very nice. I'll check it out.

--- EDIT ---
It works really well. I also think the fan shift and hysteresis settings should be available in the UI, so we can do adjustments on the fly, instead of close app/edit config/reopen sequence.

[seerge]

@manciuszz my idea to keep things simple on this stage

[FliesQQ]

I've give up using this function... Now I'm using default setting.

…

________________________________ 发件人: Serge ***@***.***> 发送时间: 2024年3月24日 18:13 收件人: seerge/g-helper ***@***.***> 抄送: FliesQQ ***@***.***>; Mention ***@***.***> 主题: Re: [seerge/g-helper] [Experimental] Manual Fan Control (Discussion #2272) @Summersoff<https://github.com/Summersoff> "same problem" in what sense ? — Reply to this email directly, view it on GitHub<#2272 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AH6FUHMO4CMMCEVIINFIDV3YZ2RNFAVCNFSM6AAAAABFET5V5GVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DQOJRG43TI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[seerge]

@FliesQQ no worries, default fan curves are best choice for majority :)

Btw I did few more tweaks, and updated release in a header-message here. So you may also check that and see if fans react faster now (or not)

[ElluIFX]

Nice feature, thanks!
It works great on my Zephyrus M15 and acts rapidly.
But sometimes it can't turn off the CPU fan:

Could it be that my method of forcing CPU fan off is not supported？

[ElluIFX]

And it can fully turn off it after I switch to Turbo and back to Silence.

[seerge]

@ElluIFX since it shows 0% in red label, this is what app actually sets as fan speed. As I mentioned in other comment here, it is possible that BIOS would override that as an idiot-protection if CPU is too hot for it's thinking.

[ElluIFX]

@seerge That's really stupid.
What's more, maybe another check box is required for switching the legacy custom mode and this new one.
Anyway, it's a cool feature for me to avoid the broken fan from making noise, thank you.

[Akalikaton]

My Laptop is ROG G14 2020, it's very intersting, after Calibre i cant set the Fan unter 2900 RPM. The Situation is just same like 0.154.0.
I hope the Fan can keep 1000 RPM with 15 TDP, a good Plan for Document read and simple surfing.

[Akalikaton]

PS: 0.154.0 can set minimal 1800RPM and real 1800~2400 RPM

[seerge]

Currently I have set min fan speed to be 25% and max 100% correspondingly (for most laptops 25% would be 1800-2000RPM) Theoretically i can allow even 1% in manual mode, but i'm not sure if it's healthy for the fans ...

[Akalikaton]

Recently i use my G14 almost only PDF and Powerpoint reading, so light, lang battery life and quiet are much important. Maybe i should buy Macbook Air M3...But now G14 works also very well.

[seerge]

I think for office use you can get away with fans being completely off at all. Its also good for battery life

[Akalikaton]

Yeah, and i have heard about, 4800HS performance better than newest 7840H under 10W, a Surprise.

[hadixcanimm]

I bought my laptop in 2019, and Armory Crate didn't allow me to make manual fan adjustments. Since then, I've been researching for a solution every few months. Then I found you and have been using your software, constantly checking for updates, but I still couldn't find a solution for fan adjustments... until today. It's working perfectly now, and your software allows me to make manual fan adjustments. My device is ASUS TUF 506LI. I think the only thing left for me is one setting; being able to undervolt directly on my device without the ThrottleStop application.

[seerge]

I'm glad it works

[Constrat]

Working exactly as expected on G713RW.
Tried the calibration first and I got scared how fast they started ramping up, also with this version I was able to get a much higher calibration max value: (6600 and 6800)
Before I was only able to reach 5400 and 6000, because it was too slow to ramp up.

GHelper keeps on delivering!

[hadixcanimm]

When I completely shut down the fans, I occasionally encounter a blue screen error. On the blue screen, I see an error code like 'fail tdr'. Prior to the blue screen, there are black screens resembling the graphics card attempting to restart itself, followed by the blue screen error.

I don't think it's due to overheating because I monitor the temperatures and they usually hover around 50-60 degrees.

[seerge]

Are you sure it's related ? may be it's just some gpu issues? try to run fans on minimal speeds otherwise :)

[hadixcanimm]

I've set the fans to 1800rpm and never encounter a blue screen, but sometimes, when I turn off the fans, it gives a blue screen error at an uncertain time. To make sure, I formatted the computer and installed Windows 11. I've installed all drivers and will test it.

[seerge]

@hadixcanimm well, apparently something is overheating then :) it may be not CPU or GPU directly, but something on the motherboard itself or so (w/o own temperature sensor). And running fans apparently keep it in a good condition probably :)

[l-naumann]

Thank you! Works a lot better to control the fans on Zephyrus G14 2024 (GA403UI).
However, the fan now runs slightly faster on the slowest setting than with the old build. I use my laptop 95% for office and programming and I can't keep it fanless in balanced mode. Occasionally the fans have to rev up briefly, so I would prefer to run them permanently on very low RPM. At 20% they already produce a very high-pitched noise. Could you add a power-user setting to set the min fan percentage?
I also think that you need an adjustable hysteresis. When the processor is boosted for a short time, there are brief temperature peaks that cause the fans to spin up immediately.

[seerge]

@l-naumann ok. Problem is that different models seem to have different minimum fan speed (and corresponding fan % setting that triggers that) .

At first my idea to mimic asus own fan curves, where 0% = OFF, and 1% = is usually something like 1800RPM (or around 25% of max speed), so people will not have to re-edit their fan curves when they switch.

Reality is more complicated than it is.

Also there is some deviations from actual set value (in %) and real fan speed often. On my G14 2022 20% setting = 25% speed, but from what I have seen here sometimes deviation reaches up to 15% in total ... :|

[l-naumann]

@seerge I see. Maybe the automatic calibration could identify when fans start spinning by increasing fans in 1% steps, starting at 0%. When fans start spinning, add 1-2% as a safety margin and set it as new min percentage.

[seerge]

@l-naumann I have updated build in main post, now it should re-apply fan speeds after wake up no matter what

[l-naumann]

@seerge Thank you, seems to work! Could you please provide a build with min fan percentage = 0% again? Apart from that, this version is perfect for me.

[seerge]

@l-naumann i have updated build in main post again. Now you can set min-fan speed as a parameter in config
"fan_min": 20, - minimum fan speed (in %) when it's not OFF

[AtillaDAMAR]

Hey @seerge, I hope you are okay. I have a problem that occurred after Control Interface update. I realized that my Asus TUF A15 is overheating. But I wasn't able to put finger on what might happens. Due to thermal stutter I wasn't able to play any game. So about two weeks ago I tried to turn off turbo boost and I was shocked with results. The difference were 25-30 degree even tho CPU begin use 10-15 more watts. I know that it shouldn't be like that. So what can I do about this? Right now I use Turbo Boost closed but sometimes I need extra power.

[seerge]

@AtillaDAMAR hello, how is this related to the experimental build with the manual fan control ? Turning boost on or off is just a way to restrict CPU power. It's up to you.

[AtillaDAMAR]

I use the experimental build, so that's why I asked here. For just extra 15-20 Watt power usage, there shouldn't be 25-30 degree Celcius difference. There is something wrong here. I saw that after new version of Control Interface, people faced with overheating problems. I mean as soon as I turn on boost, the temp hits 90 degree from 60-65 and it increases until it reach temp limit.

[kittaro]

ig its not related by experimental build.
In my laptop (vivobook) CPU too by poorly Intel: w/o turbo boost uses ~15w, with ~25watts. This causes temperatures to rise from 70-80° during hard load to ~90° and sometimes throttled down to 800mhz on 1-2secs to save temps. Its really annoying.

[seerge]

@AtillaDAMAR the only difference between experimental build and mainstream, is ability to manually set fan speeds.

The rest is just physics, and extra power used by any component - generates (pretty much) same amount of heat. How fast it will get dissipated depends on actual device thermal interface (i.e, quality of liquid metal or thermal paste, etc), ventilation (fan speeds, access to airvents) and ambient temp :)

[GoodEnoughGear]

Just checked on my side, I am on the same interface version, but I don’t experience the issue you are seeing. Everything seems to be working as it should. From: bottiger1 ***@***.***> Sent: Sunday, 13 July 2025 01:48 To: seerge/g-helper ***@***.***> Cc: GoodEnoughGear ***@***.***>; Manual ***@***.***> Subject: Re: [seerge/g-helper] [Experimental] Manual Fan Control (Discussion #2272) I'm using the option of running GHelper as SYSTEM as described earlier in this thread, using PSExec.exe. There are security implications to this, but it works with any version (so far) of the Control Interface. I have been using this but today I just noticed it stopped working after I updated windows and rebooted. Asus System Control interface is at 3.1.45 and dated 6/17/2025

[bottiger1]

Are you using the latest version of ghelper experimental? The red text at the bottom disappeared for me like in this screenshot.

Maybe it is actually working but I do not know because the only way to tell if it was working correctly before was if the red text shows up.

This is what mine looks like right now.

[fire332]

Would it be possible to automatically set the fan profile to one of the BIOS-controlled modes when the screen is not on (S0 sleep, hibernate, etc)? I have my laptop set to stay on when the lid is closed if it's plugged in and I find that the fan doesn't turn on, even if the entire laptop gets too hot to touch.

[seerge]

@fire332 not really, system suppresses all processes when it goes to sleep. But when device is in S0 sleep - firmware takes over fans anyway (it has separate mode for that). That's how it happens on all my devices.

[AndreaCap7]

Is there a way in the config file to force both GPU and CPU fans to follow only CPU temp in the same way as when GPU is disabled?
When i run CPU intensive programs my fans end up being like 4500rpm on cpu side and 2000rpm on gpu side cause gpu isn't hot at all, but possibly run both fans high would reduce cpu temp better.
Thanks in advance for help :)

[AndreaCap7]

@seerge Ok everything works fine with "fan_shift": 100, but if I try every other value (let's say 50 or 75 or even 99) the fans behave just like if the setting is 0 and follow only CPU (GPU) temp. Every time I modify the json I close ghelper, and I tried reboot pc but nothing changed. Only 100 seems to work. I use latest 0.216 experimental version

[seerge]

It's a weighted average. It affects on how "temperature" is calculated for each fan.

            float tempMax = Math.Max((float)tempCPU, (float)tempGPU);
            float shift = fanShift / 100;

            SetTemp(AsusFan.CPU, (1 - shift) * (float)tempCPU + shift * tempMax);
            SetTemp(AsusFan.GPU, (1 - shift) * (float)tempGPU + shift * tempMax);

So any value will work.

[AndreaCap7]

@seerge Interesting, and thanks for the code. So it's a mistery why on my pc (TUF F16 fx607jv motherboard) it works only with shift=100.
I've tried shift = 150, same behave as 100. With shift=200 it double the fan speed. Any value under 100 (even 99) behave like 0.
Seems like using only integer part of the fraction even though it's a float.

Image shows that even with 99, GPU fan speed follows only gpu temp. Custom 5 profile is a copy of Turbo with Custom fan speed activated, so gpu and cpu curve is the same and fans should be at the same speed (very little less cause of 99).

[seerge]

@AndreaCap7 can you check if this build makes any difference ?

GHelper.zip

[AndreaCap7]

@AndreaCap7 can you check if this build makes any difference ?

GHelper.zip

Yes! With this build it works flawlessly- I tried with 50, 75, 99 and fans follow temps as intended :)

This app is getting better every day for me and extremely useful. Thank you for making it and being always so helpful.

[frozennutzz]

heyy @seerge idk if there exists any problem but..eversince i updated to the latest experimental build 0.219 my fans started to tweak for unwanted reasons like even if the cpu reaches upto 70 C the fans wont turn on or sometimes the fans starts to spin at 3500rpm even the temps are 35 C.
I tried to hard reset troubleshooting and even double checked if its V 40 on the device manager , still its annoying me. is there any solutions or any way to get back to the older 0.216 build i were previously using😭😭

i forgot to mention i tried to calibrate but the fans that were once blasting till 8000rpm now onlly goes till 2500rpm and the gpu fans wont even spin...what might be the reason...hoping to hear ur taught and fix on this🥰😁

[frozennutzz]

as i mentoned above its the recommended Version 40 and i had done hard reset troubleshooting and even reinstalled GHelper but its still acting weird

[seerge]

@frozennutzz can you upload app log ? it will show what it's doing :) on your screenshot manual fan control is not enabled at all.

[frozennutzz]

log.txt
is this the right one?

[seerge]

@frozennutzz yes, i see that access to ASCI driver is denied (which was introduced in v41+, by raising access level requirements)

7/19/2025 12:07:44 PM: Can't connect to SAIO: C:\WINDOWS\system32\DriverStore\FileRepository\asussci2.inf_amd64_cceffaf9805aa134\ASUSSystemAnalysis Error connecting to \\.\\AsusSAIO Error Code: 5 <--- denied

Most likely windows has silently updated driver again. Try to completely uninstall and reinstall 40 agian.

It's not due to app version change :)

[frozennutzz]

thankyou @seerge that really worked....the fact that this asus keep updating and giving me those micorsoft edge kind of vibes dude....it literally took me like 20 mins not joking, every time i reinstalled and restarted my laptop on the boot every asus services revives itself and starts to update itself to the latest version back within seconds was the most painful to see😭😭 in the end i had to unplug the wifi and had to reinsatll it and had to disble the asus services asap booted.....
was one hell of an experience with asus softwares

[abdulkadirozyurt]

This experimental version does not work with any version other than Asus system control interface v3.1.40.0. Windows update constantly updates to v3.1.45.0, causing ghelper to stop working. I have to use this experimental version because my device does not support manual fan control by default.

Device: Asus TUF Gaming F17 2021 (FX706HM-HX037)

[GoodEnoughGear]

That is correct - there are two ways to deal with it as shown in this thread: either prevent the automatic update or run GHelper as SYSTEM.

[NineBallo]

Start G-Helper.zip
Here is an example startup task for starting ghelper as system on login. You can unzip and import it through the windows task schedule and I think it should just work as long as the required files are in the right place.

Default Requirements:
PSExec to be at "C:\Program Files\PSTools\PsExec.exe"
Ghelper to be at "C:\Program Files\GHelper\GHelper.exe"

Just seeing a lot of people confused abt this. Goal is to provide an easy solution without blocking driver updates. Just note, if it crashes it won't automatically restart due to how I invoke psexec. Might be possible to fix that, but I haven't bothered as it's not a simple change.

[Behroz666]

calibrate seems to not work for me is there anyway to input the manual max fan speed for the chart ?

[seerge]

@Behroz666 what do you mean under "not working" ?

[Behroz666]

If the fan is already at high speed because of high temps the app thinks that's the max speed but if the fans speed are low it don't go up to the max like before. I have the Asus driver version right and the other parts of the app works fine but calibrate not at all.

[seerge]

@Behroz666 there is a good chance, manual fan control is not active in your case. When it's ON - you will see red labels under Fasn + Power screen indicating what fan speed is currently set. You can try to reinstall ASCI driver again to tackle that.

[Behroz666]

thanks reinstalling the ASCI driver fixed it

[nit0211]

How do I run Ghelper as SYSTEM? I'm completely new to this. I'm running v40 for ASUS System Control Interface v3 and I'm wondering if this would work with helping the fan's follow my curve better on my non-experimental version of GHelper, because my fan curve does not work properly at all. I've seen people in this thread say that it works for them

[nit0211]

I just read it, I couldn't find a config.json file anywhere, I think I dont know where i'm looking

[seerge]

%APPDATA%\GHelper\config.json

[nit0211]

Alright thanks, I added those 3 params into the file, it looks like it works a bit better

[nit0211]

I did some testing and stuff with fan curves, I realized that the fan_hysteresis didn't do any effect for some reason. I tried to remove the code line and replace and save it but nothing helped

[seerge]

Default value is 6, if you just add or remove it - of course nothing changes. You need to set much higher (like 30) if you want to see a difference.

[acheronnroze]

Hello, I switched to experimental mode to be able to fully control the fans on my G14 Zephyrus 2022 model 6800HS 6700S device, but both the GPU and CPU are fluctuating by at least 200-300 rpm. (For example, in Cinebench R23, it should run at 4000 rpm at 80 degrees, but at 77 degrees, it runs at 4100 rpm.) You can see an example of this in the image as a idle state. I have the correct version of the Asus System Control Interface and have also calibrated the fans . Is this normal, or is there a solution if it is a problem?

[zackriso]

Does G-helper 0.226 uses different config files than previous versions? I loaded it with a config file from a previous version, and it would not adjust the fans at all.

[zackriso]

I am using 0.198.0, with the config files under the same folder. I put the new version of Ghelper into the same folder (removed the old one), and the fans, curves, etc dont work at all.

[seerge]

@zackriso 0.198 is very old :) then run latest experimental build and post an issue as i mentioned above

[zackriso]

Thank you. When I download the newest version of Ghelper (0.226), where are usually the config logs it uses, by default?

[seerge]

@zackriso newest version is 0.229 (linked to you). Logs/config are under %appdata%\GHelper as mentioned in the headpost. If you have manually placed config in a same folder as app - then it will use that instead

[zackriso]

Issue created with log, thanks: seerge/g-helper-experimental-release#1

[MrCheese-21]

Hello @seerge, trying to download version 3.1.40 of asussc2 driver but link in post seems to be broken (404 not found). Do you have an updated link?

[seerge]

@MrCheese-21 it seem like asus has removed it from their website :) May be try to run app with system permissions instead (method 2 explained in a head post)

[MrCheese-21]

I'm getting the following error when trying to run the command:

[seerge]

@MrCheese-21 you need to download it :)

[Retr0680]

@seerge so there's no way to prevent the update for asus controler anymore, and how do i run the method 2 on startup?

[Retr0680]

You can try to create a separate startup task launching psexec with ghelper as param (pretty much a command listed), just use a full path.

like this?

[seerge]

You can use a full path to GHelper.exe as well, like C:\GHelper\GHelper.exe (in your case)

I can try to extend an experimental build, so instead of relaunching itself as admin (if it's not running as admin yet), it will relaunch via psexec straight away (+ create a task based on psexec).

But I still want to find time, learn how to write a proper windows services, and actually move all manual fan controls to the service eventually. So this shenanigans won't be needed at all.

[Retr0680]

You can use a full path to GHelper.exe as well, like C:\GHelper\GHelper.exe (in your case)

I can try to extend an experimental build, so instead of relaunching itself as admin (if it's not running as admin yet), it will relaunch via psexec straight away (+ create a task based on psexec).

But I still want to find time, learn how to write a proper windows services, and actually move all manual fan controls to the service eventually. So this shenanigans won't be needed at all.

if you plan to try the relaunch via psexec method, let me know i'll try that build. rest best of luck for the windows services journey

[Retr0680]

You can use a full path to GHelper.exe as well, like C:\GHelper\GHelper.exe (in your case)

I can try to extend an experimental build, so instead of relaunching itself as admin (if it's not running as admin yet), it will relaunch via psexec straight away (+ create a task based on psexec).

But I still want to find time, learn how to write a proper windows services, and actually move all manual fan controls to the service eventually. So this shenanigans won't be needed at all.

Btw, what exactly did you mean by using the full path?

[seerge]

@Retr0680 i mean using using C:\GHelper\GHelper.exe and not a PWD thing

[abdulkadirozyurt]

Can you add this manual fan control feature to main branch? After every Asus System Control Interface driver update, we have to change the driver to previous version. Is it possible to add main branch?

[seerge]

@abdarslan adding it to the main branch won't change absolutely anything in relation to ASCI. Newer driver just restricts access to the apps running with a SYSTEM permission (like windows services)

[AboodiGamer]

Can this be ported to Linux?