mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-26 00:56:01 +03:00
[GH-ISSUE #239] nbfc causing APCI "event 13" Error (HP elitbook 8770w + windows 10) #211
Labels
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nbfc-hirschmann#211
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rezpower on GitHub (May 10, 2017).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/239
This was happening before creators update, but not a real issue. I have been using nbfc for long now and
the error was nothing to worry about. Now I am getting a ton of the same error coming up is system log.
I updated to latest version tonight and the problem is still here. If I uninstall problem is gone! Can you help
me figure out what is causing the error and eventually a way to fix it?
@hirschmann commented on GitHub (May 10, 2017):
These ACPI errors occur because NBFC accesses the EC directly instead of evaluating ACPI methods via the Windows ACPI driver. This is kind of a hack, but unfortunately on many notebooks the only way to control the fan(s).
As long as NBFC doesn't cause any negative side effects, you can safely ignore those error messages.
@rezpower commented on GitHub (May 10, 2017):
Thanks a lot for the fast reply. Yes, the ACPI error was something I was totally ignoring for a long time as it did not have any negative side effect. But after the windows creators update my laptop keyboard randomly stops working and non of the keys work anymore. Even restarting the laptop dose not solve the problem. I have to shutdown the computer and turn in back on and it works again and the ACPI errors have jumped from few ( accruing in a distant manner) , to a lot of them (10's or 20's successive ones).
@deathnoise commented on GitHub (Jul 2, 2017):
try to raise the EcPollInterval by 100 in your XML NBFC profile file, save it, restart the laptop.
Repeat the same procedure until the problem is gone.. I had similar HW issues with my G751JT: https://github.com/hirschmann/nbfc/issues/234#issuecomment-312468720
See if that helps.
If you set the aforementioned value too low it may cause different hardware problems, if you set it too high - the fans are gonna slow down even if you set them on 100% speed in NBFC and that's because the stock EC will take over the control over them, instead of NBFC.
In other words - NBFC needs to keep writing the values to the EC repeatedly and fast enough in order to maintain the control over the speed of fans, but it shouldn't write it too fast (when EcPollInterval is set too low), or it's gonna cause problems.
So if you are having issues - you need to tune it by yourself using trial and error approach, raising it incrementally by 100 ms and testing the stability of the setup.
@rezpower commented on GitHub (Aug 2, 2017):
Thanks a lot for the reply. I did change the EcPollInterval value my 100 ms and went up and down from the original 3000 value to as low as 300 and up to 4000. the changes made some change to the amount of errors I was getting and in some cases there were no errors at all at least on startup. But as soon as I run games or cpu intensive software (for which i need nbfc) erros come back and at some point the keyboard become non functional and the only solution to fix it is to turn off pc and turn it back on.
I still really hope that someone will find a solution as without nbfc my notebook run very hot and I'm sure it will be damaged soon as it happened before using nbfc. (had to replace the motherboard)
@github-actions[bot] commented on GitHub (Dec 11, 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