I found, that Service host is eating too many CPU resources:
How to know, what does it doing?
procexp64.exe
shows even less information (no child process list).
Shutting down this process causes no apparent damage.
I found, that Service host is eating too many CPU resources:
How to know, what does it doing?
procexp64.exe
shows even less information (no child process list).
Shutting down this process causes no apparent damage.
Capture a xperf trace of the CPU usage:
xperf -on latency -stackwalk profile -buffersize 2048 -MaxFile 2048 -FileMode Circular && timeout -1 && xperf -d C:\HighCPUUsage.etl
and when you open it in WPA and expand the stack, you probably see that the UPNP service waits (highlighted in red).
So stop that service to fix the issue.