[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

ExperimentalGHelper.zip

Note

As some people have reported, latest Asus System Control Interface v 3.0.1.41 blocks access to current experimental "manual" control. So if it doesn't work for you - you can (temporarily) install previous version 3.0.1.40 (or below)

Updated 24.02.2025 (0.204)

Possible params for 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

[Genialler]

Hello and Thanks.
I'm now using this tools on Zephyrus G14 2021(GA401QM),but the fans(both CPU and GPU) doesn't match the curve I set,both RPMs are 10% higher or so.I try to calibrate several times but it seems no use.
Should I just change the fan_max_0 and fan_max_1 manually in config.json to match the fans' RPM-percent ?Or there is some other solution?

[seerge]

@Genialler hello, measures max fan speeds (8400?) seem too high, that's why it may not match. Do fans really go that high when you click Calibrate ?

[Genialler]

@Genialler您好，测量的最大风扇速度（8400？）似乎太高了，这就是为什么它可能不匹配。单击“校准”时风扇真的会变得那么高吗？

Yes it is. MyAsus also get this result.
But when I try to calibrate in un-experimental GHelper(0.202.0), the results are 7100RPM(CPU) and 7400RPM(GPU),should I try this result instead?

[szetyi]

Hi both, thanks for the work @seerge.

Same issue for me on Zenbook UP6502ZA.
Works great other than reporting different RPM as opposed to fan curve:

I tried calibrating, detected as 8400 RPM:

[Genialler]

I notice that the max RPMs of CPU（8400） and GPU（5800）, have you try to run the fans analysis in MyAsus？

Hi both, thanks for the work @seerge.

Same issue for me on Zenbook UP6502ZA. Works great other than reporting different RPM as opposed to fan curve: I tried calibrating, detected as 8400 RPM:

[TheOne320]

Will the features of this experimental version ever be ported to the non-experimental version?

[seerge]

I don't plan that for now

[Yandeko]

I would like to know how to configure the fan update because I don't have config.json but I have GHelper.dll.config, should I literally enter in the line "fan_hysteresis": 5 or how to make the code clearer like this

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<System.Windows.Forms.ApplicationConfigurationSection>
<add key="DpiAwareness" value="PerMonitorV2" />
</System.Windows.Forms.ApplicationConfigurationSection>
<appSettings>
<add key="EnableWindowsFormsHighDpiAutoResizing" value="true" />
</appSettings>
</configuration>

[seerge]

Config is located under %appdata%\GHelper\config.json

[Yandeko]

thanks

[Yandeko]

I would also like to know if I can install fan control on the second Linux system, in fact, this is the only thing that keeps me from switching to Linux

[NODARYN]

I'm using Asus ROG Strix Scar 17 X3D. I recently received the Asus System Control Interface V3 3.1.41.0 update. After this update, the functionality of the experimental version stopped working. Overall the cooling performance has deteriorated significantly since the update. Therefore, I strictly do not recommend updating the firmware at this time. Stay on version 3.1.40.0.

[seerge]

@cgamingpro Try to re-install Control Interface from scratch :) it could be something is wrong with your specific installation

[cgamingpro]

still no solution man , and as for Asus system control interface i still got 3.1.40.0 , when i try the normal version it works perfectly , but the expermental version ain't even showing CPU temps at this point , untill tonight it was working just fine been using it for months

[seerge]

@cgamingpro please read on how to properly reinstall it :)

The only thing from Asus System Control Interface that is needed is a driver that gives access to fan-testing feature from myasus. And that one is unchanged from what i see.

[cgamingpro]

FIxed it , the issue was this update , windows update had already downloaded this update ,but still the installed version was 3.1.40 even after a restart , so manually installing it form windows update and then followinf this https://github.com/seerge/g-helper/wiki/Troubleshooting#reinstalling-asus-system-control-interface fixed it , so the version 3.1.41.0 is not the issue

[NODARYN]

@cgamingpro Try to re-install Control Interface from scratch :) it could be something is wrong with your specific installation

I have tried many times to reinstall System Control Interface from scratch (via uninstallation), but it didn't work in my case. For the moment I am back to the .40 version.
In the screenshot, you can see that G-Helper does not display cooler speeds on version .41

[Retr0680]

the experimental build is no longer adjusting my fan speed. here is my log file
log.txt

[Retr0680]

@seerge my Asus driver also automatically updated. It seems the new driver partially breaks things. I wish I knew how to stop asus drivers from auto-updating....

It's a windows thing you can disable auto updates for your components using windows update but I will probably break the update system of every component so I wouldn't recommend it.

[seerge]

@fscottcopeland I have 41 and it works just fine. But i have installed it from asus website (i.e. G-Helper's Updates section)

[fscottcopeland]

@seerge I have 41 too, but it doesn't work for me! This is the download URL for my laptop.
https://dlcdnets.asus.com/pub/ASUS/GamingNB/Image/Software/SoftwareandUtility/16504/ASUSSystemControlInterfacev3_ASUS_Z_V3.1.41.0_16504.exe?model=GX650PY

[fscottcopeland]

I wish we could just stop the ASUS drivers auto-updating. That'd solve these issues.

[cgamingpro]

Found any solution to block the updates for a specific device?cause aam tired of rolling back drivers daily

[C4r3s-1]

I think it would be a good idea to link the CPU and GPU fan curve graphs (not permanent, tickable setting). I use the "fan_shift": 100 setting, so the hotter component always determines the cooling. Since there are connected parts in the cooling system, one component somewhat cools the other as well. However, I always have to set the fan curve twice.

[seerge]

@C4r3s-1 you can achieve that already (as you have correctly mentioned by setting fan_shift to 100). But I don't see any sense in doing it by default. As mainly people come to Experimental build and manual fan control when they are not happy with fans working "on their own" and usually demand them to strictly follow fan curves.

[C4r3s-1]

Most of the time, the CPU temperature is higher than the GPU's, so the fans will operate based on the CPU temperature but according to individually set values. I want both fans to run in sync. With fan_shift: 100, the fan speed is adjusted based on the hotter component. However, for example, if the CPU is at 80°C and set to 5200 RPM, the GPU at 65°C will follow the fan speed value set for 80°C on the GPU graph. This means I have to manually sync both if I want to modify the settings
Ultimately, it's not a big deal since I don't adjust the fan speeds daily. But when I do, this would speed up the process.

[tektonsound]

Hi guys!

First of all thank you to Seerge for putting together this incredible tool - it is an absolute gamechanger for cooling my laptop properly with a constant and smooth fan noise (comapred to the standard Asus 'burst' / 'wash' fan behaviours).

I am using the Ghelper experimental version on an Asus TUF F15 FX507ZC4 and encounter the following - I have both CPU & GPU fans running at a constant low 1200 RPM, which is great to keep a cool idle (achieving below 40C for both CPU & GPU in light use/reading/browsing etc) - however both fans continue to spin when Windows11 goes into sleep mode.

I can bypass this - by selecting a different mode which does not have the custom fan curve enabled (Silent), then the fans stop on sleep - or by using the standard Ghelper where this is not an issue.

Wondering if this is something anyone here has seen / knows about?

Thanks in advance!

Alex

[seerge]

@tektonsound hello,

Are you sure that your device actually goes to sleep in that case ? Check modern standby sleepstudy if there is any apps preventing windows from going into sleep.

It could be also that firmware on your device is programmed in that way, that it doesn't turn fans off when going into sleep

[MrHanz00]

Custom fan curves suddenly will not work with the 3.1.41.0 version of Asus System Control Interface V3, as of now my current solution was reverting to previous version.

[Retr0680]

@seerge my bad i couldn't see it earlier but i'm facing the same issue on version 41

[seerge]

@Retr0680 try to run app as admin and if it doesn't work post an issue with a log. I can try to look into, but can't promise anything since i don't face it even with 41

[Retr0680]

I'll update the controller and try to run it on admin

[cgamingpro]

tried to run it on admin still not working

[MrHanz00]

@MrHanz00 did you install 41 via windows update or via asus website / g-helper ? I could be that windows update has a broken version.

@seerge sorry for the late reply, I used G-helper to install to 41

[Yandeko]

Hello, is this thing supported on Linux?

[seerge]

@Yandeko hello, no - it's not supported on Linux

[starlinetor]

I used to have this version install allowing me to have max fan speed around 7000 rpm. But the following happened in order :

1. g-helper prompted me to update and i did
2. fans speed went to 0
3. i restarted the PC and i couldn't turn it on for a few minutes i imagine from over heating
4. i reinstalled this version
   Now i don't get the cpu temperature and the red text under the fan curve is missing when i check "Apply custom fan curve".
   Also the max fan speed has been reduced to 5600 rpm when before it was running at 7000 rpm.
   Did i burn my cpu or is it a software problem ?

[seerge]

@starlinetor did you also happen to update Asus System Control Interface to 3.1.41 ? Many people report that with it manual fan control doesn't work (app just falls back to defaults, i.e.. fans controlled by BIOS). So you may want to roll back to 3.1.40

There are no other changes in this regard in the app :) if manual fan control is not working due to asus drivers - then 5600 is just your typical RPM set by BIOS (i.e. default behavior)

[starlinetor]

Yes you where right, thanks you very much.
Also I thank you a lot in general, you have been very helpful every time.

[Ipherc]

After several attempts, I can confirm that the [Experimental] Manual Fan Control does not work with version 3.1.41, but it functions properly with 3.1.40. My main issue was that Windows 11 Pro kept automatically installing the new driver. After hours of research, I discovered that I could block the Asus System Control Interface auto-update driver by using (gpedit.msc). After making this change, I tried updating the driver again, but Windows blocked it. Now, I’m back on track.

Here is the steps for it. https://www.howtogeek.com/263851/how-to-prevent-windows-from-automatically-updating-specific-drivers/

Just FYI. Hopefully it will help others

ASUS TUF Gaming F15 FX506HM_TUF506HM
Windows 11 Pro 24H2

[seerge]

@Ipherc yeah, cause in 41 asus has restricted access to this driver only for processes running with SYSTEM permission (i.e. even running as admin is not enough). Check this issue for more info

[MrHanz00]

Asus is very sneaky to include greater system privileges in order to control the fans. Seems like they don't want Ghelper to freely work on their units, what a shame, they've become controlling.

[UncleBeanzie]

Thanks for sharing - the obvious risk with doing this is if ASUS makes core updates to other system or device-related drivers for the model we're on, and Windows auto-pushes those updates... If those updates are dependent on 3.1.41+, we could run into other issues.

I've also rolled back and made group policy change as a temporary solution - on the Zenbook S14, the ASUS-configured fan speed curves were seemingly put together by a 4 year old. It's an unusable device without GHelper! P.S. donated already :)

[fscottcopeland]

Thanks for sharing - the obvious risk with doing this is if ASUS makes core updates to other system or device-related drivers for the model we're on, and Windows auto-pushes those updates... If those updates are dependent on 3.1.41+, we could run into other issues.

I've also rolled back and made group policy change as a temporary solution - on the Zenbook S14, the ASUS-configured fan speed curves were seemingly put together by a 4 year old. It's an unusable device without GHelper! P.S. donated already :)

Is there any way to make such a change without the Group Policy Editor? I don't have the pro version of Windows.

[UncleBeanzie]

Thanks for sharing - the obvious risk with doing this is if ASUS makes core updates to other system or device-related drivers for the model we're on, and Windows auto-pushes those updates... If those updates are dependent on 3.1.41+, we could run into other issues.
I've also rolled back and made group policy change as a temporary solution - on the Zenbook S14, the ASUS-configured fan speed curves were seemingly put together by a 4 year old. It's an unusable device without GHelper! P.S. donated already :)

Is there any way to make such a change without the Group Policy Editor? I don't have the pro version of Windows.

Yes, you can download PolicyPlus. I too don't have Win Pro. I have Win 11 Home, and configuring the values with this worked fine for me. Just remember to "File > Save" after you make the changes in PolicyPlus to make sure they're pushed to the registry. PolicyPlus will alert you this is done after you save (if successful).

[Behroz666]

Why does the in-app update for the experimental version revert to the main release? I was on experimental build 202. The app prompted me to update to 204, but after the app relaunched, the detailed fan controls were gone. I had to manually update again to get them back.

[seerge]

@Behroz666 because I didn't point auto-updater in experimental version to this build by an accident :) I have re-uploaded v0.204 again with corrected auto-updater now. Meaning - if you would download it again, next time a new release comes, it should update to experimental branch,

[sharif221]

this experimental build correctly calibrate 7400 rpm on my fans on rog flow z13

normal build do this: #3744

[seerge]

@sharif221 both builds calibrate according to the way fan control is done in them.

In mainstream build - it's a firmware fan control (i.e. what you get in AC manual mode too) - there asus has limited it to 6600, and probably for a reason (to prevent wear off for example or to tackle noise)

In Experimental build it uses same trick as MyASUS does to test fan speeds, so in your specific model it can go a bit higher.

[sharif221]

You are 100% correct, I'm using g helper for like 7 moth until now and I just recently noticed that, because of an overheating in specific situation.

So even now with experimental build I'm not going up to 7000 in any situation, I guess literally I need to bench mark or something to make it go up to 6800 rpm.

I adjusted the fan curves in experimental build to go up to 6600 rpm so it's like normal curves, but also I have the turbo + or something like that , so I'll manually set that if I saw overheating or something similar.

Thanks for explaining why it's limited, it's by design limited to this values by Asus.

[hell0men]

Hi. Looks like 204 version curves control was changed for my G14. 202 works fine, in 204 where fans must be turned off, they spinning at 2000 rpm. So, in 204 the only way to make notebook silent is Eco mode. And temp is higher too. So, backed to 202.

[seerge]

@hell0men there are no changes in 0.204 for fan control. On your screenshot manual fan control is not working at all (otherwise you would see red label with fan speeds). Most likely cause you have update to Asus System Control Interface 3.0.1.41, that blocks it. Try to revert back to 3.0.1.40 as mentioned in a head post here.