Windows 10, high load from WUDFHost.exe Windows Driver Foundation - User-mode Driver

[ed34567]

Got the same issue here with the Anniversary update and WUDFHost.exe, specifically the process loading the Intel 520 driver dll's.
Updated the Intel drivers to 21.20.16.4574 and the DisplayLink to 8.1.843.0 but still getting the problem. It's actually making Edge unusable.

This is on a Dell Latitude E5470 and a Targus ACP71EU dock.

[EyalBkk]

Same issue with Windows Driver Foundation hogging the CPU. Latest displaylink driver just installed. Running 2 external screens with Lenovo Yoga 3 (i7 5500U + 8GB ram).

Can we have an update on expected next step and timeframe to solve this?

[AlbanRampon]

Hello,

I have been notified that engineering has now been able to reliably reproduce it on a model of machine.
They are now working on understanding the problem.
There are a few leads they are following, one of them is linked with memory. Result of the investigation will be telling what will help and a timeline.

If I understand that 50% CPU is considered high, having 5% would leave still 95% free... If a computer is struggling with 5% CPU usage, then there is something else at play!
Unfortunately the system gauge doesn't give any obvious information about where the bottleneck is.

WUDFHost, as its name indicates is a process hosting other processes (Windows User Mode Driver Framework). One of the hosted processes is the DisplayLink Manager process. This has changed from a separate DisplayLink User Agent, DisplayLink Manager approach because we are now using the Microsoft standard USB driver.

Kind regards,
Alban

[fstx]

I don't use the display connections on my dock at the moment, just the ethernet and usb ports.

When using SysInternals procmon to see what WUDFHost.exe is doing, I see that it repeatedly accesses the registry key HKLM\SOFTWARE\DisplayLink\NivoManager.

[AlbanRampon]

Originally Posted by fstx

I don't use the display connections on my dock at the moment, just the ethernet and usb ports.

When using SysInternals procmon to see what WUDFHost.exe is doing, I see that it repeatedly accesses the registry key HKLM\SOFTWARE\DisplayLink\NivoManager.

Hello,

If you don't use the video, then a high load would have a different reason. What is high?
Ethernet and audio are also going through the same physical DisplayLink chip.
Also, whether you use a video output or not, the chip is on the USB so Windows will talk to it.

Kind regards,
Alban

[fstx]

Originally Posted by AlbanRampon

Hello,

If you don't use the video, then a high load would have a different reason. What is high?
Ethernet and audio are also going through the same physical DisplayLink chip.
Also, whether you use a video output or not, the chip is on the USB so Windows will talk to it.

Kind regards,
Alban

High load is anything that spins up the CPU fan. But I was relating behaviour that seems wrong to me. Your forum does not allow me easily include a screenshot, so I just paste some of the events from procmon below. Procmon keeps rolling with events like these,
about 5 loops per second.

10:31:07.7011935 WUDFHost.exe 13160 RegOpenKey HKLM SUCCESS Desired Access: Maximum Allowed, Granted Access: Read
10:31:07.7012609 WUDFHost.exe 13160 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7013444 WUDFHost.exe 13160 RegOpenKey HKLM\Software SUCCESS Desired Access: Read
10:31:07.7014379 WUDFHost.exe 13160 RegCloseKey HKLM SUCCESS
10:31:07.7015207 WUDFHost.exe 13160 RegQueryKey HKLM\SOFTWARE SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7016392 WUDFHost.exe 13160 RegOpenKey HKLM\SOFTWARE\DisplayLink SUCCESS Desired Access: Read
10:31:07.7017298 WUDFHost.exe 13160 RegCloseKey HKLM\SOFTWARE SUCCESS
10:31:07.7018942 WUDFHost.exe 13160 RegQueryKey HKLM\SOFTWARE\DisplayLink SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7020779 WUDFHost.exe 13160 RegOpenKey HKLM\SOFTWARE\DisplayLink\NivoManager NAME NOT FOUND Desired Access: Read
10:31:07.7021925 WUDFHost.exe 13160 RegCloseKey HKLM\SOFTWARE\DisplayLink SUCCESS
10:31:07.7026075 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19 SUCCESS Desired Access: Read/Write
10:31:07.7027246 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19 SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7029168 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\Software SUCCESS Desired Access: Read
10:31:07.7029901 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19 SUCCESS
10:31:07.7030455 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19\SOFTWARE SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7031177 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS Desired Access: Read
10:31:07.7032101 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19\SOFTWARE SUCCESS
10:31:07.7032718 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7035197 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\SOFTWARE\DisplayLink\NivoManager NAME NOT FOUND Desired Access: Read
10:31:07.7036576 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS
10:31:07.7038434 WUDFHost.exe 13160 RegOpenKey HKLM SUCCESS Desired Access: Maximum Allowed, Granted Access: Read
10:31:07.7041241 WUDFHost.exe 13160 RegQueryKey HKLM SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7045469 WUDFHost.exe 13160 RegOpenKey HKLM\Software SUCCESS Desired Access: Read
10:31:07.7047906 WUDFHost.exe 13160 RegCloseKey HKLM SUCCESS
10:31:07.7049175 WUDFHost.exe 13160 RegQueryKey HKLM\SOFTWARE SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7051393 WUDFHost.exe 13160 RegOpenKey HKLM\SOFTWARE\DisplayLink SUCCESS Desired Access: Read
10:31:07.7052162 WUDFHost.exe 13160 RegCloseKey HKLM\SOFTWARE SUCCESS
10:31:07.7052990 WUDFHost.exe 13160 RegQueryKey HKLM\SOFTWARE\DisplayLink SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7055088 WUDFHost.exe 13160 RegOpenKey HKLM\SOFTWARE\DisplayLink\NivoManager NAME NOT FOUND Desired Access: Read
10:31:07.7056492 WUDFHost.exe 13160 RegCloseKey HKLM\SOFTWARE\DisplayLink SUCCESS
10:31:07.7058230 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19 SUCCESS Desired Access: Read/Write
10:31:07.7059278 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19 SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7060480 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\Software SUCCESS Desired Access: Read
10:31:07.7062546 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19 SUCCESS
10:31:07.7063505 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19\SOFTWARE SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7065572 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS Desired Access: Read
10:31:07.7067363 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19\SOFTWARE SUCCESS
10:31:07.7068287 WUDFHost.exe 13160 RegQueryKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS Query: HandleTags, HandleTags: 0x0
10:31:07.7073661 WUDFHost.exe 13160 RegOpenKey HKU\S-1-5-19\SOFTWARE\DisplayLink\NivoManager NAME NOT FOUND Desired Access: Read
10:31:07.7075117 WUDFHost.exe 13160 RegCloseKey HKU\S-1-5-19\SOFTWARE\DisplayLink SUCCESS

[fstx]

I installed DisplayLink 8.2 Beta For Windows 8.2 Beta 1.exe, and WUDFHost.exe is still misbehaving.

[spellinn]

Originally Posted by AlbanRampon

Hello,

I have been notified that engineering has now been able to reliably reproduce it on a model of machine.
They are now working on understanding the problem.

I can 100% reproduce the problem here, so do let me know if they want to run any diagnostics on my system (Dell XPS 13)

I'm using your latest Win10 drivers (8.1M0)

Cheers

Neil

[-=Markus=-]

Hello, I have the same problem.

I can't use my four USB screens.
I have update my computer with the last nvidia driver, and my problem is unchanged.

I work in the development of flight simulator, and it's logical for us to simulate any instruments between different screens.
And the top for a good interface utilisation, is the possibility to change rapidely by USB ports of screens.

I try to disconnect GPU / Graphic Card / Wudfsvc, but nothing happens.

My only option for the moment, is to remove physicaly one of the twice graphic card from my motherboard, for have 3 surround screens HDMI, and four USB sreens for plane instruments.
It's not envisageable.... .

The computer is very powerful :

OS : Windows 10 / version : 1607 / 14393.693
Proc : Intel i7-6700K
RAM : 64 Go
System : 64 bits processor x64

GPU : 2 X GTX Geforce Titan X SLI
Motherboard : Asus Maximus VIII Extreme

Sceens : 3 screens HDMI
1 screen VGA
4 screens USB Lilliput

Drivers Nvidia version : 378.49
Drivers DisplayLink : 8.1 M0


Can you give me a configuration tip? Or tell me if the next DisplayLink drivers will solve this compatibility problem? and when ?
Thank you

Best regards,

Markus

[bfcamara]

I can also reproduce in my system: Dell XPS 13 + Win 10 + 2 External monitors attached to a Targus doc. As soon as I start using my external monitors, the issue happens. Very annoying.