starred/nbfc-hirschmann

Fork 0

mirror of https://github.com/hirschmann/nbfc.git synced 2026-04-25 16:45:53 +03:00

[GH-ISSUE #175] NBFC 1.5.0 / Asus UX51VZ: Service Switches to "read only" after standby #157

New issue

Closed

opened 2026-02-26 00:31:53 +03:00 by kerem · 9 comments

kerem commented

2026-02-26 00:31:53 +03:00

Owner

Originally created by @juepi on GitHub (Jan 21, 2017).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/175

Hardware: ASUS UX51VZA (original, unmodified NBFC config)
OS: Win10 x64 v1607
NBFC: 1.5.0 (updated from 1.4.2)

Problem:
Sometimes after waking up the notebook from STD, NBFC service switches itself to "read only", leading to a running CPU fan. After manually switching the service to "Enabled" in the NBFC GUI, everything is fine.

Workaround:
Downgraded to version 1.4.2 where this problem does not exist.

Originally created by @juepi on GitHub (Jan 21, 2017). Original GitHub issue: https://github.com/hirschmann/nbfc/issues/175 Hardware: ASUS UX51VZA (original, unmodified NBFC config) OS: Win10 x64 v1607 NBFC: 1.5.0 (updated from 1.4.2) Problem: Sometimes after waking up the notebook from STD, NBFC service switches itself to "read only", leading to a running CPU fan. After manually switching the service to "Enabled" in the NBFC GUI, everything is fine. Workaround: Downgraded to version 1.4.2 where this problem does not exist.

kerem

2026-02-26 00:31:53 +03:00

closed this issue
added the
Stale
label

kerem commented

2026-02-26 00:31:54 +03:00

Author

Owner

@hirschmann commented on GitHub (Jan 27, 2017):

It's ok if the service switches itself to 'read only' before standby/hibernate, but it should actually restore the previous state after waking up from standby/hibernate.

Could you please post the service's event log entries for the last week:

Get-EventLog -LogName "Application" -Source "NoteBookFanControlService" -After $(Get-Date).AddDays(-7) | select TimeGenerated, Message

@hirschmann commented on GitHub (Jan 27, 2017): It's ok if the service switches itself to 'read only' before standby/hibernate, but it should actually restore the previous state after waking up from standby/hibernate. Could you please post the service's event log entries for the last week: ```powershell Get-EventLog -LogName "Application" -Source "NoteBookFanControlService" -After $(Get-Date).AddDays(-7) | select TimeGenerated, Message ```

kerem commented

2026-02-26 00:31:54 +03:00

Author

Owner

@juepi commented on GitHub (Jan 27, 2017):

Hello Stefan,

Attached the requested info (CSV format):
nbfc-events.zip

I've extended the time range to -10 days, as i've downgraded to 1.4.2 7 days ago (when i filed the bug). I've been running 1.5.0 a few days before that when i've sometimes experienced this problem (not always i think).

yours,
Juergen

@juepi commented on GitHub (Jan 27, 2017): Hello Stefan, Attached the requested info (CSV format): [nbfc-events.zip](https://github.com/hirschmann/nbfc/files/736246/nbfc-events.zip) I've extended the time range to -10 days, as i've downgraded to 1.4.2 7 days ago (when i filed the bug). I've been running 1.5.0 a few days before that when i've sometimes experienced this problem (not always i think). yours, Juergen

kerem commented

2026-02-26 00:31:54 +03:00

Author

Owner

@hirschmann commented on GitHub (Jan 31, 2017):

Thanks for the log.
Looks like you encounter the same error 1.4.2 as well, but it's not noticeable because unlike 1.5, 1.4.2 doesn't switch to read-only mode before standby/hibernate.

I couldn't reproduce this bug on my system and I haven't figured out why it happens yet.
Since 1.4.2 works fine for you, just stay at that version until the bug is fixed.

@hirschmann commented on GitHub (Jan 31, 2017): Thanks for the log. Looks like you encounter the same error 1.4.2 as well, but it's not noticeable because unlike 1.5, 1.4.2 doesn't switch to read-only mode before standby/hibernate. I couldn't reproduce this bug on my system and I haven't figured out why it happens yet. Since 1.4.2 works fine for you, just stay at that version until the bug is fixed.

kerem commented

2026-02-26 00:31:54 +03:00

Author

Owner

@juepi commented on GitHub (Feb 1, 2017):

Hi Stefan,

I've interpreted the logs the same way :)
Will stay on 1.4.2, as mentioned, works perfectly well for me!

thanks,
Juergen

@juepi commented on GitHub (Feb 1, 2017): Hi Stefan, I've interpreted the logs the same way :) Will stay on 1.4.2, as mentioned, works perfectly well for me! thanks, Juergen

kerem commented

2026-02-26 00:31:54 +03:00

Author

Owner

@plikojim commented on GitHub (Oct 5, 2017):

Hello to all,
I was writing by reading this interesting post and this program I thought would solve my problem asus UX51VZ
the fans always work 100% I tried versions 1.4.2 1.5 and beta 1.5.3 but the speed remains unchanged.
I can not do other tests apart from a possible downvolt that I would not do if possible
Thanks for your help
Ps Italian language :)

@plikojim commented on GitHub (Oct 5, 2017): Hello to all, I was writing by reading this interesting post and this program I thought would solve my problem asus UX51VZ the fans always work 100% I tried versions 1.4.2 1.5 and beta 1.5.3 but the speed remains unchanged. I can not do other tests apart from a possible downvolt that I would not do if possible Thanks for your help Ps Italian language :)

kerem commented

2026-02-26 00:31:54 +03:00

Author

Owner

@juepi commented on GitHub (Oct 6, 2017):

Hello Plikojim,

This sounds like a hardware defect to me. Even without NBFC the fans in my UX51VZ were practiallcy never spinning at 100% (they were always running, but at low speeds). I assume an defective EC would also explain why NBFC is not working..

Yours,
Juergen

@juepi commented on GitHub (Oct 6, 2017): Hello Plikojim, This sounds like a hardware defect to me. Even without NBFC the fans in my UX51VZ were practiallcy never spinning at 100% (they were always running, but at low speeds). I assume an defective EC would also explain why NBFC is not working.. Yours, Juergen

kerem commented

2026-02-26 00:31:54 +03:00

Author

Owner

@plikojim commented on GitHub (Oct 6, 2017):

so there's nothing left that downvolt I think ...
other solutions?
I just replaced display 400 € :(

@plikojim commented on GitHub (Oct 6, 2017): so there's nothing left that downvolt I think ... other solutions? I just replaced display 400 € :(

kerem commented

2026-02-26 00:31:54 +03:00

Author

Owner

@juepi commented on GitHub (Oct 7, 2017):

To be honest, i have no idea what you mean with "downvolt"..
if you think of placing a resistor in the fan's power cable, i think this is not a proper solution, as the fans cannot spin at the required speed if your notebook is under heavy load, thus your CPU / GPU will probably overheat.

Maybe you should check BIOS settings and also see if you can upgrade the BIOS (this also often re-flashs the EC afaik). Also make sure that you have the ASUS ATK software package installed, i think this one also has something to do with the EC.
AND of course, check that your CPU is idle. My ASUS Smart Gesture bullshit software sometimes hangs and causes 100% CPU load, in which case the fans also spin up of course ;)

hth,
Juergen

@juepi commented on GitHub (Oct 7, 2017): To be honest, i have no idea what you mean with "downvolt".. if you think of placing a resistor in the fan's power cable, i think this is not a proper solution, as the fans cannot spin at the required speed if your notebook is under heavy load, thus your CPU / GPU will probably overheat. Maybe you should check BIOS settings and also see if you can upgrade the BIOS (this also often re-flashs the EC afaik). Also make sure that you have the ASUS ATK software package installed, i think this one also has something to do with the EC. AND of course, check that your CPU is idle. My ASUS Smart Gesture bullshit software sometimes hangs and causes 100% CPU load, in which case the fans also spin up of course ;) hth, Juergen

kerem commented

2026-02-26 00:31:54 +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

kerem referenced this issue

2026-02-26 00:31:56 +03:00

[GH-ISSUE #194] Client endpoint configuration '*' was not found in 0 endpoints. #173

kerem referenced this issue

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

[GH-ISSUE #568] Successfully building on Linux doesn't create a Linux/bin folder. Workarounds in related issues and versions 1.4.2, 1.4.4, 1.5.0, 1.5.3-beta and 1.6.1-beta1 all seem to fail in various ways. #514