This post is more than 5 years old
43 Posts
0
328757
Windows 10 build 9926 unusually high CPU utilization on Venue 11 Pro 7130 i3
Setting how other Venue 11 Pro 7130 owners were having good success in running the Windows 10 preview, I today performed an in place upgrade from 8.1 to 10 build 9926 (the one with Continuum, which is great) but I'm having the issue of a constant high CPU load between 50 and 99 percent, with no obvious culprit in the task manager. Before setting out to format and perform a clean install I wanted to ask if anyone else had been experiencing this issue.
EDIT: the unusually high load seems to be sparked by a process called Windows Driver Foundation - user mode driver framework, whose executable is wudfhost.exe.
A complete reinstall didn't help.
EDIT 2: should someone encounter the issue, completely disabling the service named "Windows Driver Foundation - user mode driver framework" helped, with seemingly no ill effects, even though after the odd restart it may need to be disabled again.
As a disclaimer, I'd like to point out how generally it is never a good idea to go mucking into services.msc.
Crazy_Goat
25 Posts
0
January 24th, 2015 22:00
Some information regarding my experience with the Windows 10 Preview, both pre-and-post Cortana on a Dell Venue 11 Pro:
So with all of that said - what was the solution?
Fresh install.
Here are the steps to getting the best installation of Windows 10 on a Venue 11 Pro (as I know it - from my experience).
Now - a word of caution. Unlike the earlier builds of Win 10 - my connected standby sessions drain about 1,500mW/hr. This is what I saw in Win 8.1 no matter what I tried - I wonder if there's some kind of driver issue - and needs replacing. My sleep study reports show no offenders - everything is running for less than 1% of the sleep cycle, but the hardware isn't going down to C3 sleep state, which is where the power drain is coming from. Seems like a chipset driver of some kind of malfunctioning - I'll do a trace and try to isolate the issue.
Other than this - everything has been MUCH more stable. Sleeping (though draining battery) are rock solid consistent, I don't have the high CPU usage in the WDF service anymore, and the active stylus is working exactly as it should.
I'm going to shut it down between uses for now - and keep testing and see if there's a chipset driver or something that fixes this.
epelleg
4 Posts
1
January 27th, 2015 07:00
I wish I had seen your post earlier. You need to let this process run. It optimizes and compresses drivers after installation. It took a day or two of use with my Surface Pro 3 (i5 8GB) to finish. It took a little longer on the Dell Venue 8 Pro. Trust me it WILL finish and then your computer will be ready to use, and should be working properly.
Fabri91
43 Posts
0
February 6th, 2015 10:00
To summarize what I've found out for now:
I performed a clean startup, i.e. no non-MS services enabled (can be done from msconfig), followed by restarts enabling all those services one after the other (they should be at most a dozen) and it appears that the Realtek Sound Service is the culprit. Disabling it solves the problem most of the time with no apparent ill effects.
When it comes up the process is easily killed via task manager with, again, no apparent ill effects, but this surely isn't the optimal way.
Crazy_Goat
25 Posts
0
January 24th, 2015 17:00
Also - my tablet is hemorrhaging battery power in sleep again. The first windows 10 preview was fantastic and fixed all my issues with 8.1 when it came to connected standby. With this new preview, battery consumption is through the roof again.
Powercfg's sleepstudy shows cortana is keeping the system from entering the low power state.
Crazy_Goat
25 Posts
0
January 24th, 2015 17:00
I can confirm this issue. I have had the OEM 8.1 pro install, a fresh 8.1 pro install from disk, as well as the first win10 tech preview - and haven't seen this issue till now. I see the same high CPU utilization by the WDF user mode driver framework.
I also have a black screen when resuming from sleep - which I have also seen in 8.1 installs. Seems like the drivers are woefully out of date. Gotta love how you cannot install drivers directly from Intel and are at Dell's mercy
Fabri91
43 Posts
0
January 25th, 2015 01:00
This has to be the mother of all posts, thank you very much for the time taken to write it!
One question, though: in which category is the SM Bus Controller you mentioned?
EDIT: regarding the Connected Standby drain, as a workaround for when you positively cannot close a session I'd suggest disabling it via registry edit. Resuming from S3 standby is a bit of a fuss (you have to either press the windows button on the tablet or close and reopen the keyboard, and then touch the display or a key), hibernation is reliable.
Crazy_Goat
25 Posts
0
January 25th, 2015 07:00
The SM bus controller will automatically be exposed in device manager since it won't have a driver. It'll have a little yellow exclamation point on its icon. I think it'll be under unknown devices.
Once installed its recognized as an Intel Series 8 chipset device.
Fabri91
43 Posts
0
January 25th, 2015 07:00
Got it, after I bit the bullet and did a clean install again it, this time according to your procedure, it showed up nicely.
You were right, the flickering at first was horrible, as in a window of one second each five seconds of a functional screen. Disabling panel auto-refresh solved it, as you said.
Crazy_Goat
25 Posts
0
January 25th, 2015 19:00
Excellent. Glad I'm not crazy. There are reports on the Windows 10 Insider Forum about folks with Surface Pro 3's with the same insane flickering - so it's not just us. Very glad my procedure works!
I have tried using the Dell Supplied Chipset drivers as well as even more recent drivers sourced directly from Intel - and nothing is allowing the system to enter the low power state in hardware. There's no offenders keeping it awake - it just fails to enter the power saving state on the Core i3 chip.
Because of that - I enabled hibernation, and left connected standby enabled. Changed it to go into hibernation when I press the button and are mobile - and go into connected standby when I'm plugged in (or docked).
Working great for me so far - solves all my issues.
Crazy_Goat
25 Posts
0
January 27th, 2015 09:00
Good catch! Upon re-installing, this wasn't ever an issue - so it must be after you do an in-place upgrade. Some people have reported it running amok and never stopping - so know where to draw the line, I suppose.
Fabri91
43 Posts
0
January 28th, 2015 11:00
And it's back: after the latest Windows updates WDF returned. I'll just let it run this time and see if it disappears.
Fabri91
43 Posts
0
January 28th, 2015 12:00
It disappeared when in control panel I agreed to "finish installing drivers", which in my case was a the control center for MS mice and keyboards.
Fabri91
43 Posts
0
January 29th, 2015 12:00
It returned after the latest BIOS updates, which include an update of the Management Engine firmware. Device manager after installing also the newest audio drivers shows no missing drivers, so this time there is no obvious alternative to letting it run.
Dgriff
3 Posts
0
January 29th, 2015 15:00
Thanks for the help. The flickering was driving me nuts trying to figure it out. On mine, number 6, was under Intel Graphics/Properties/Power
Relief, now I can move on.
stevecoops
1 Message
0
February 5th, 2015 08:00
How did you enable hibernation? I can't seem to do it on my tablet.