• July 17, 2017
    Announcement: New site design for Microsoft Community

    In July, Microsoft will roll out the first of ongoing site improvements aimed to modernize Microsoft Community and help customers get the most out of their community experience.

    • During the roll out period, you may see the old or new site design depending on your location

    • We expect the roll out to finish by 31 July

    Note: Past private message conversations will not move to the new site design. Please save any private messages you would like to keep.

     Learn more about the upcoming site improvements in this thread.

    Thank you for being part of Microsoft Community!

 
Question
Applies to
326 views

ProfSvc consumes 100% of a thread in win 8.1

JO
JoeDoucette asked on

Hi,

I'm running win 8.1 -- not sure exactly when this started -- this is an upgrade from win7->win8. I notice my CPU frequency never drops below max anymore. I've traced this back to svchost.exe/netsvcs. Setting affinity to a single core gives me 1 core at 100% all the time.

I've tried creating another user profile & logging in under a cold boot as that admin user -- no change. I've tried uninstalling antivirus software -- no change. Booting to safe mode (even with networking) does get me back down to idle. I'm able to suspend svchost.exe (netsvcs) in resource monitor and see the cpu go back to idle.

Any guesses for next steps to resolve this? Best guess I'd had was a new user profile, but that was unsuccessful, so I'm at a loss at what else to try. A screenshot of resource monitor is below. Any advice would be greatly appreciated..thanks!

    - Joe

1 person had this question

Abuse history

The answered status icon Answer
JO
JoeDoucette replied on

Of course I'd sort it out right after posting...

I used process monitor to figure out what it was doing. Turns out an infinite loop of looking for HKLM\System\CurrentControlSet\Control\Nls\CustomLocale\virtualization. I tried creating that as an empty string, and then it polled for C:\Windows\Globalization\virtualization.nlx.

Turns out this is a broken Intel Proset driver. Removed it & the system is back to normal. Who would have figured a network driver would spam a user profile service? Sigh....

    - Joe

1 person found this helpful

Abuse history

progress