Windows 10: Why does CPU usage spike to 100% when launching Task Manager?

If you’ve ever launched Task Manager only to watch your CPU usage hit 100% and stay there, you may have wondered why this sudden mystery spike in system resource usage occurs. After all, Task Manager is a lightweight program that you can run with little impact on system performance on most machines. In this post, […]

This article Why does CPU usage spike to 100% when launching Task Manager? first appeared on TheWindowsClub.com.

read more...

 

high cpu usage when task manager is open

hi, i have done a clean boot and sfc clean-image restore etc nothing out the ordinary my computer is up to date also i use a program called open hardware to monitor mt temps / usage and it never is pinned near 70-100% there is spikes upon launching games
etc but i assume that's normal even when i bring open the task manager and its using up to 30-40% cpu usage in other programs showing cpu usage it isn't as high as what windows task manager is telling me

 

Audiodg.exe Spikes Cpu Usage

Every 5 minutes or so audiodg.exe spikes my cpu usage to about 50% and any audio im playing cuts out and then comes back a second or 2 later. The video is completely fine and it's not a problem with
my USB Headset. audiodg.exe stays at low cpu usage when it's not spiking.

Solutions I've tried:

1. turning off audio enhancements
2. reinstalling lan, and audio drivers
3. turning off HPET
4. lowering the sound quality in control panel
5. DPC Latency checker (no change when spiking)

None of these solutions work. Please help.

 

100% CPU usage in task manager after upgrading to W10

Thank you Krishna for quick response however it is neither of those reasons. I think it is a bug, it only shows 100% cpu usage but everything works ok . Never had this issue before only started after i updated from windows 7 to 10. The procantage usage
of cpu on some applications jumps from 5 to 70% in example : the task manager was "using" 80% of cpu and that just can't be right. Having said that i think the task manager's cpu usage shows wrong data (its bugged) somehow.