[GH-ISSUE #925] NBFC Inconsistent fan speed - Gigabyte P35x V5 #804

New issue

Closed

opened 2026-02-26 00:33:37 +03:00 by kerem · 1 comment

kerem commented

2026-02-26 00:33:37 +03:00

Owner

Originally created by @Lamb3 on GitHub (Jun 12, 2020).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/925

Hey all.

I have an overheating (97 degrees Celcius CPU temperatures and 88 degrees max temp for GPU) Gigabyte P35x V5 laptop which I have undervolted both CPU+GPU with good results; now giving me 82 degrees max CPU temp and 87 degrees for GPU averaging at around 83 Deg Celcius.
However, I want to take things up a notch further with a custom-made fan speed to temperature controls.

So far, I have managed to find the register in the EC that controls the fan speed which is 0x64 hexadecimal or 100 decimal. Fan speed value in that register from min to max are 00 and 08 respectively.

The problem and observations:
I've also made a new config file for this laptop and whenever I enable the fan service with my created config, the fan speed can only stay in a given, specified speed state for ~3.8 seconds before the EC somehow overwrites the fan speed to default parameters for around ~1300ms before again ramping back up to my specified thresholds.
The cycle goes on and on again and at times, the EC maxes out the fan speed even when there's no spikes in temperature (a bug perhaps?)

Note: I have tested multiple EC polling intervals within NBFC and have concluded that any interval gives more or less the same behaviour and greater intervals (eg. >3000ms) make the fan behave more like stock fan speeds and thresholds. But for now I have settled to keep it at 500ms for this discussion. Anything lower than 300ms will make the laptop act weird ie. battery empty notification and other things I find hard explaining.
Any way to circumvent this problem?

My goal here is to have the fan speeds adhere to the temperature thresholds I have set in the config. I appreciate everyone's input and help.

PS: I'm completely new to EC editing and all this deep hardware controls.

Originally created by @Lamb3 on GitHub (Jun 12, 2020). Original GitHub issue: https://github.com/hirschmann/nbfc/issues/925 Hey all. I have an overheating (97 degrees Celcius CPU temperatures and 88 degrees max temp for GPU) Gigabyte P35x V5 laptop which I have undervolted both CPU+GPU with good results; now giving me 82 degrees max CPU temp and 87 degrees for GPU averaging at around 83 Deg Celcius. However, I want to take things up a notch further with a custom-made fan speed to temperature controls. So far, I have managed to find the register in the EC that controls the fan speed which is 0x64 hexadecimal or 100 decimal. Fan speed value in that register from min to max are 00 and 08 respectively. **The problem and observations**: I've also made a new config file for this laptop and whenever I enable the fan service with my created config, the fan speed can only stay in a given, specified speed state for ~3.8 seconds before the EC somehow overwrites the fan speed to default parameters for around ~1300ms before again ramping back up to my specified thresholds. The cycle goes on and on again and at times, the EC maxes out the fan speed even when there's no spikes in temperature (a bug perhaps?) Note: I have tested multiple EC polling intervals within NBFC and have concluded that any interval gives more or less the same behaviour and greater intervals (eg. >3000ms) make the fan behave more like stock fan speeds and thresholds. But for now I have settled to keep it at 500ms for this discussion. Anything lower than 300ms will make the laptop act weird ie. battery empty notification and other things I find hard explaining. Any way to circumvent this problem? My goal here is to have the fan speeds adhere to the temperature thresholds I have set in the config. I appreciate everyone's input and help. PS: I'm completely new to EC editing and all this deep hardware controls.

kerem

2026-02-26 00:33:37 +03:00

closed this issue
added the
Stale
label

kerem commented

2026-02-26 00:33:37 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 11, 2020):

This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed

@github-actions[bot] commented on GitHub (Dec 11, 2020): This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed