[GH-ISSUE #1105] dpc latency spikes when notebook fancontrol service running read-only or enabled on HP zBook G5 x360 #946

New issue

Closed

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

kerem commented

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

Owner

Originally created by @000masa000 on GitHub (Mar 19, 2021).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/1105

Running HP zBook Studio G5 x360 2018 with i7 8850 6-core 32 GB RAM and 2x 1TB SSD drives. Using primarily for audio creation and real-time performance after years with a MBP. Struggled with clicks and pops caused by DPC Latency and finally found a good method by disabling turbo, abandoning my older but fine RME Fireface 400 for a USB RME UCX and running CPU at fixed maximum clock 2.6 GHz. However the fans as programmed by HP kick in at 50 and are super loud and whiny even at 60 C the disturbance is completely unuseable in live recording settings, so it is a big disappointment to have made the plunge into the Windows based hardware world. So thrilled to finally discover Notebook Fancontrol and a working config (HP zBook Studio G3). However, as soon as the service is active in either read-only or enabled mode, LatencyMon shows a big increase in latency events which are mirrored by audible breakdowns in the real-time audio. I am aware this reopens an old issue from a couple of years ago, but I guess that had to do with a non-working config. Any help tracing this would be most kindly appreciated. It seems ACPI.sys is the affected process.

I would be happy to tackle this issue but am not sure where to begin, since the program does in fact work, how is its functioning interfering with or somehow engaging and distracting the Windows process?

Thanks for helping,
best wishes
Marc Sabat
masa@plainsound.org

Originally created by @000masa000 on GitHub (Mar 19, 2021). Original GitHub issue: https://github.com/hirschmann/nbfc/issues/1105 Running HP zBook Studio G5 x360 2018 with i7 8850 6-core 32 GB RAM and 2x 1TB SSD drives. Using primarily for audio creation and real-time performance after years with a MBP. Struggled with clicks and pops caused by DPC Latency and finally found a good method by disabling turbo, abandoning my older but fine RME Fireface 400 for a USB RME UCX and running CPU at fixed maximum clock 2.6 GHz. However the fans as programmed by HP kick in at 50 and are super loud and whiny even at 60 C the disturbance is completely unuseable in live recording settings, so it is a big disappointment to have made the plunge into the Windows based hardware world. So thrilled to finally discover Notebook Fancontrol and a working config (HP zBook Studio G3). However, as soon as the service is active in either read-only or enabled mode, LatencyMon shows a big increase in latency events which are mirrored by audible breakdowns in the real-time audio. I am aware this reopens an old issue from a couple of years ago, but I guess that had to do with a non-working config. Any help tracing this would be most kindly appreciated. It seems ACPI.sys is the affected process. ![Screenshot 2021-03-19 232906](https://user-images.githubusercontent.com/34196907/111848496-72498b00-890b-11eb-85b5-65fff155745e.png) ![Screenshot 2021-03-19 233043](https://user-images.githubusercontent.com/34196907/111848500-72e22180-890b-11eb-9452-4af53bb96756.png) ![Screenshot 2021-03-19 233239](https://user-images.githubusercontent.com/34196907/111848501-72e22180-890b-11eb-9ff7-96ae47280bd3.png) I would be happy to tackle this issue but am not sure where to begin, since the program does in fact work, how is its functioning interfering with or somehow engaging and distracting the Windows process? Thanks for helping, best wishes Marc Sabat masa@plainsound.org

kerem

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

closed this issue
added the
Stale
label

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Sep 17, 2021):

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 (Sep 17, 2021): 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