New
#21
That's all one thread, and it's relatively strange, as if the kernel is trying to map info into the user-mode address space of a process whose threads are themselves not running for some reason, as if they've been suspended.
The svchost to which this thread belongs is the "DcomLaunch" instance - that's visible from your first screenshot. There are multiple services in there by default:
svchost.exe 708 DcomLaunch, PlugPlay, Power
Your own machine may well be different (check by running TASKLIST /SVC).
If you temporarily split up those services into their own svchost instances, it'll become easier to gauge which service spawns the CPU chewing thread, and hence where to focus the troubleshooting. To split off the services into their own svchost instances, on an elevated (run as admin) CMD prompt:
SC CONFIG Power TYPE= OWN
SC CONFIG PlugPlay TYPE= OWN
Reboot, and then check which of the services is blasting the processor.