CPU Usage - Windows Driver Foundation

AlbanRampon · 06-03-2019, 10:52 AM

Quote:

Originally Posted by stvlada

Another test:
1. Windows 10 1709 with DisplayLink 8.5.3459.0 is working just fine.
2. Windows 10 1809 with DisplayLink 8.5.3459.0 has issues with WUDFHost and CPU and CPU fan usage.

After two days of testing several releases of Windows and DisplayLink drivers, it is obvious that DisplayLink is not compatible with any Windows releases after 1709.

Hello,

I have created a case to look into that.

It is wrong to claim you are less secure. Security updates and feature updates on Windows 10 are separate. Both Windows 10 v1803 and v1809 are still in support. The most recent Windows 10 v1903 is only starting to deploy now.

Regards,
Alban
Ref 30130

elmorekevin · 06-12-2019, 02:29 PM

Any update on this case? I have been struggling to resolve these issues as well. Subscribing...Thanks!

stvlada · 06-19-2019, 07:07 PM

I've left Windows Update running, and I got Windows 1703 updated to 1803 version automatically by Windows Update.
Therefore WUDFHost start utilizing CPU fan again. I've decided to install DisplayLink USB Graphics Software for Windows ALPHA 9.2 Alpha just to verify whats going on.
This time again same issue.

I have attached ZIP file from Diagnostic tool.

elmorekevin · 08-01-2019, 01:45 PM

Alban,

Any new information you can share from case 30130?

Thanks,
Kevin

AlbanRampon · 08-08-2019, 07:43 AM

Hello Kevin, stvlada,

We have sourced a machine identical to stvlada.
From what we can see, the CPU usage is not high, nor is it significantly different than on the previous version of Windows 10. The difference in CPU load is marginal. The results observed in our labs are in line with screenshots received from stvlada.
What has visibly changed is that Microsoft added a label in Task Manager, and that label says high... but nothing else is running, and computing any pixel and encoding them does cost some resource, whatever the connection mode and whether you can see it in Task Manager or not. On my machine, yesterday I saw Task Manager as High on that label at with 4% CPU, leading us to believe that that label shows relative power, not absolute power.

The problem we see is the fan change, despite the lack of significant change of CPU load between these versions of Windows 10.
The fan is supposed to be controlled by temperature. Temperature tends to come from computing load, from total power usage (not relative to other apps).
We don't yet understand why the fan behaves very differently, when the load is similar. It suggests there's something else.

The next step is for us to consult with Microsoft for advice on profiling what triggers the fan: is there a load invisible in Task Manager, is the marginal CPU difference really warrant that fan impact, is there another component counted in that power label, or something else...

Kind regards,
Alban

stvlada · 08-08-2019, 05:16 PM

Alban, thank you for your feedback and through explanation. It would be nice to figure out what triggers the fan spinning.
If internet browsers are used, like Chrome, it is obvious that WUDFHost will starts kicking into the load/heat and fan will be triggered. Those symptoms are usually not there when laptop is not connected to the dock station.

When we can expect to get an answer from Microsoft and more details on investigation from their end?

08-08-2019, 07:43 AM	#5
AlbanRampon Senior Member Join Date: Sep 2015 Posts: 1,685	Hello Kevin, stvlada, We have sourced a machine identical to stvlada. From what we can see, the CPU usage is not high, nor is it significantly different than on the previous version of Windows 10. The difference in CPU load is marginal. The results observed in our labs are in line with screenshots received from stvlada. What has visibly changed is that Microsoft added a label in Task Manager, and that label says high... but nothing else is running, and computing any pixel and encoding them does cost some resource, whatever the connection mode and whether you can see it in Task Manager or not. On my machine, yesterday I saw Task Manager as High on that label at with 4% CPU, leading us to believe that that label shows relative power, not absolute power. The problem we see is the fan change, despite the lack of significant change of CPU load between these versions of Windows 10. The fan is supposed to be controlled by temperature. Temperature tends to come from computing load, from total power usage (not relative to other apps). We don't yet understand why the fan behaves very differently, when the load is similar. It suggests there's something else. The next step is for us to consult with Microsoft for advice on profiling what triggers the fan: is there a load invisible in Task Manager, is the marginal CPU difference really warrant that fan impact, is there another component counted in that power label, or something else... Kind regards, Alban __________________ Alban Rampon Senior product manager, universal docking stations and accessories Where to download the latest DisplayLink drivers How to clean up a corrupted installation How to report issues to DisplayLink for a speedy resolution

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

06-12-2019, 02:29 PM	#2
elmorekevin Junior Member Join Date: Jun 2019 Posts: 2	Any update on this case? I have been struggling to resolve these issues as well. Subscribing...Thanks!

08-01-2019, 01:45 PM	#4
elmorekevin Junior Member Join Date: Jun 2019 Posts: 2	Alban, Any new information you can share from case 30130? Thanks, Kevin

08-08-2019, 05:16 PM	#6
stvlada Junior Member Join Date: Feb 2019 Posts: 26	Alban, thank you for your feedback and through explanation. It would be nice to figure out what triggers the fan spinning. If internet browsers are used, like Chrome, it is obvious that WUDFHost will starts kicking into the load/heat and fan will be triggered. Those symptoms are usually not there when laptop is not connected to the dock station. When we can expect to get an answer from Microsoft and more details on investigation from their end?