starred/nbfc-hirschmann

Fork 0

mirror of https://github.com/hirschmann/nbfc.git synced 2026-04-26 00:56:01 +03:00

[GH-ISSUE #234] NBFC 1.5.0 is shutting down my laptop randomly #206

New issue

Closed

opened 2026-02-26 00:32:01 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 00:32:01 +03:00

Owner

Originally created by @deathnoise on GitHub (May 5, 2017).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/234

..without showing any information, whatsoever. And by that I don't mean the Windows restart. What I mean is that it literally switches off my laptop, instantly (power off), after some random time. It doesn't matter if I'm gaming or if the laptop is idling on the Windows desktop. It might be a couple of minutes, an hour or a day and then, suddenly, it goes off.

After going back to the 1.4.2 version of NBFC everything works just fine. No restarts for more than a week, now.

I've got Asus G751JT, with Haswell 4720HQ processor.

Originally created by @deathnoise on GitHub (May 5, 2017). Original GitHub issue: https://github.com/hirschmann/nbfc/issues/234 ..without showing any information, whatsoever. And by that I don't mean the Windows restart. What I mean is that it literally switches off my laptop, instantly (power off), after some random time. It doesn't matter if I'm gaming or if the laptop is idling on the Windows desktop. It might be a couple of minutes, an hour or a day and then, suddenly, it goes off. After going back to the 1.4.2 version of NBFC everything works just fine. No restarts for more than a week, now. I've got Asus G751JT, with Haswell 4720HQ processor.

kerem

2026-02-26 00:32:01 +03:00

closed this issue
added the
Stale
label

kerem commented

2026-02-26 00:32:02 +03:00

Author

Owner

@hirschmann commented on GitHub (May 7, 2017):

Please post a NBFC service log, see https://github.com/hirschmann/nbfc/wiki/Files-and-directories-overview

@hirschmann commented on GitHub (May 7, 2017): Please post a NBFC service log, see https://github.com/hirschmann/nbfc/wiki/Files-and-directories-overview

kerem commented

2026-02-26 00:32:02 +03:00

Author

Owner

@deathnoise commented on GitHub (Jun 6, 2017):

It's even worse with the newest (1.5.3 beta) version. I've got a shutdown just after a couple of minutes from the time I've installed the NBFC.

There is nothing in the logs, except this:
NbfcServiceLog.txt

But I've got this in the Event Log, right before the shutdown:
http://i.imgur.com/J1LY15k.png

Oh, and 1.4.2 is also shutting down my computer. Just not so often. It may take weeks or a month.

@deathnoise commented on GitHub (Jun 6, 2017): It's even worse with the newest (1.5.3 beta) version. I've got a shutdown just after a couple of minutes from the time I've installed the NBFC. There is nothing in the logs, except this: [NbfcServiceLog.txt](https://github.com/hirschmann/nbfc/files/1055372/NbfcServiceLog.txt) But I've got this in the Event Log, right before the shutdown: http://i.imgur.com/J1LY15k.png Oh, and 1.4.2 is also shutting down my computer. Just not so often. It may take weeks or a month.

kerem commented

2026-02-26 00:32:02 +03:00

Author

Owner

@hirschmann commented on GitHub (Jun 8, 2017):

Random shutdowns are usually caused by an incompatible config (the G751JT is not officially supported), or incompatibilities with other software, see https://github.com/hirschmann/nbfc/wiki/FAQ#are-there-any-known-incompatibilities-with-nbfc

@hirschmann commented on GitHub (Jun 8, 2017): Random shutdowns are usually caused by an incompatible config (the G751JT is not officially supported), or incompatibilities with other software, see https://github.com/hirschmann/nbfc/wiki/FAQ#are-there-any-known-incompatibilities-with-nbfc

kerem commented

2026-02-26 00:32:02 +03:00

Author

Owner

@deathnoise commented on GitHub (Jul 2, 2017):

With your help I've been able to pinpoint the problem and solve it. I've got VOLTGROUND profile for G751JT, for NBFC.
It turns out that the EcPollInterval has been set to a wrong value. It's been set to "300" by the author of the XML profile. It looks like the correct value may differ from one unit of laptop to another, even if it's still the same model (G751JT/JY) of the laptop. Some other guy has reported, that in his case the correct value that guarantees stable work is equal to "400".
In case of my G751JT, after I've raised the aforementioned value to "700" - everything works great (for me), even with the newest version of NBFC.

I think it's a good idea to add this (more descriptive) information to your FAQ, in case someone is gonna have similar problems in the future. Like - "if your laptop is acting weird - try to raise the ECPollInterval value by 100, save it and restart your laptop. Repeat it over and over again until the problem is gone".

Or maybe even implement an option in NBFC to correct/raise EcPollInterval automatically for the user by "100" (and save it), after every sudden, "dirty" shutdown that has been detected?
You can create blank, temporary file with NBFC on startup to detect dirty shutdowns..

Anyway.. I've found some useful information on asus rog forums:

Then I have tried setting it to minimum, which means 100ms. But this isn't good either because writing too often in the EC Table left me with some weird values written all over the registers. These values can make your notebook act weird, and I have some personal exampleslike: the fans start bursting into full speed, the battery led starts blinking orange, the battery is not detected, the notebook goes into sleep mode by random, or the battery capacity isn't showing correctly. Most of these problems are repaired by resetting the Embedded Controller by pressing and holding the power button for 10 secs until the battery led shuts off and starts again. Now, after I have found what did cause some of the biggest troubles I have found that a Poll Interval of 500ms is just right to avoid any of them.

similar story from the voltground forums:

EC poll rate is 400 ms. With 500 ms sometimes my fans slow down because stock EC takes their control, and at poll rate < 300 ms I had some weird behavior, like fans that go suddenly crazy, battery non detected, or shutdown. So, the profile is yet WIP.

Except that 400 and 500ms values didnt work for me, either..
"500ms" value and lower have been causing the same problems for me (blinking battery led, random shutdowns, battery not detected, wrong battery capacity values). But when I've set the value to "700" everything works OK (now I'm testing "600")
Which leads me into thinking that EVEN in the case of some official profiles that are bundled with NBFC - most of the people are not gonna have any problems, but SOME of them may encounter them.
And these problems may not be reproducible on some other machines, even if these are the same models, coming from the same series. Different OS/BIOS versions? I don't know.

All in all - the problem has been solved :)
https://rog.asus.com/forum/showthread.php?58501-Making-of-quot-Official-NotebookFanControl-G751JY-Profile-quot
http://www.voltground.com/haven/threads/92/#post-413

@deathnoise commented on GitHub (Jul 2, 2017): With your help I've been able to pinpoint the problem and solve it. I've got VOLTGROUND profile for G751JT, for NBFC. It turns out that the EcPollInterval has been set to a wrong value. It's been set to "300" by the author of the XML profile. It looks like the correct value may differ from one unit of laptop to another, even if it's still the same model (G751JT/JY) of the laptop. Some other guy has reported, that in his case the correct value that guarantees stable work is equal to "400". In case of my G751JT, after I've raised the aforementioned value to "700" - everything works great (for me), even with the newest version of NBFC. I think it's a good idea to add this (more descriptive) information to your FAQ, in case someone is gonna have similar problems in the future. Like - "if your laptop is acting weird - try to raise the ECPollInterval value by 100, save it and restart your laptop. Repeat it over and over again until the problem is gone". Or maybe even implement an option in NBFC to correct/raise EcPollInterval automatically for the user by "100" (and save it), after every sudden, "dirty" shutdown that has been detected? You can create blank, temporary file with NBFC on startup to detect dirty shutdowns.. Anyway.. I've found some useful information on asus rog forums: > Then I have tried setting it to minimum, which means 100ms. But this isn't good either because writing too often in the EC Table left me with some weird values written all over the registers. These values can make your notebook act weird, and I have some personal exampleslike: **the fans start bursting into full speed, the battery led starts blinking orange, the battery is not detected, the notebook goes into sleep mode by random, or the battery capacity isn't showing correctly**. Most of these problems are repaired by resetting the Embedded Controller by pressing and holding the power button for 10 secs until the battery led shuts off and starts again. Now, after I have found what did cause some of the biggest troubles I have found that a Poll Interval of 500ms is just right to avoid any of them. similar story from the voltground forums: >EC poll rate is 400 ms. With 500 ms sometimes my fans slow down because stock EC takes their control, **and at poll rate < 300 ms I had some weird behavior, like fans that go suddenly crazy, battery non detected, or shutdown**. So, the profile is yet WIP. Except that 400 and 500ms values didnt work for me, either.. "500ms" value and lower have been causing the same problems for me (blinking battery led, random shutdowns, battery not detected, wrong battery capacity values). But when I've set the value to "700" everything works OK (now I'm testing "600") Which leads me into thinking that EVEN in the case of some official profiles that are bundled with NBFC - most of the people are not gonna have any problems, but SOME of them may encounter them. And these problems may not be reproducible on some other machines, even if these are the same models, coming from the same series. Different OS/BIOS versions? I don't know. All in all - the problem has been solved :) https://rog.asus.com/forum/showthread.php?58501-Making-of-quot-Official-NotebookFanControl-G751JY-Profile-quot http://www.voltground.com/haven/threads/92/#post-413

kerem commented

2026-02-26 00:32:02 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 12, 2019):

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 12, 2019): 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