A CPU meter glued to 100% makes the whole PC feel broken - fans loud, everything a half-second behind. But high CPU is a reading, not a culprit. Something is asking the processor to work, and the test is simply to find out who, whether they should be, and whether the processor itself is running at full speed while it tries.
Open Task Manager with Ctrl + Shift + Esc, go to the Processes tab and click the CPU column header so the hungriest process sits on top. Now do the part most people skip: watch for a full minute. Spikes are normal life - a program launching, a page loading. The fault is the name that never leaves the top. That name, plus the clock speed on the Performance tab, decides everything that follows.
A healthy PC touches 100% CPU for seconds at a time constantly. The test is duration: keep the Processes tab open during the exact task that feels slow. If one process holds 25, 40, 60% without letting go while nothing visibly progresses - a stuck render, a frozen sync, a scan that never ends - you have found a suspect with a name and a face.
Note the figure and the name in your symptom line. chrome.exe at 38% sustained for 10 minutes is evidence; CPU was high is not.
Right-click the process and open its Properties or file location. Read the publisher: a signed Microsoft, Google or Adobe binary in its proper folder is a citizen; an unknown name in a temp folder deserves suspicion. Honest rule: never end or delete a process you have not identified - half the scary names in Task Manager are Windows itself doing scheduled work.
Now check the Performance tab, CPU page: it shows the current speed beside the base speed. If the CPU reads 100% while running at, say, 0.79 GHz against a 3.40 GHz base, the processor is not overwhelmed - it is throttled, crawling to protect itself from heat or a power limit. Chasing processes on such a machine is a waste of an afternoon; the heat test in this set is the right next page.
The reverse also matters: 100% at full clock speed with the fan calm usually means a genuinely busy or stuck program, not a hardware cry for help.
If the top entry is System or System interrupts rather than a named program, the load lives in kernel and driver land - a misbehaving device driver, a failing disk forcing retries, a network or USB device shouting for attention. Programs did not cause it and reinstalling them will not cure it. Note it, check drive health next, and treat recently changed drivers as prime suspects.
Watch the video for the minute-by-minute reading of a busy CPU and how the real owner gets named.
Watch Full VideoNo. First check whether a scan is running and whether it completes. A scan that runs for twenty minutes and stops is health. A scan stuck for hours, restarting daily, is a symptom - of a corrupt file it keeps choking on, or a drive it cannot read. Test the scan; do not shoot the guard.
Not by default. Identify it first: right-click, open file location, read the publisher in Properties. Windows itself runs dozens of oddly named processes. Only an unidentified binary in a strange folder, with no publisher, earns real suspicion - and even then the test is a Defender scan, not a manual delete.
Probably not. If the load is your own task - a render, a compile, a game - finishing at full speed, the meter is reporting work, not distress. The method only convicts load that is sustained, unexplained and matched by the PC actually feeling slow.