High CPU and RAM Usage: Find the Cause in 5 Steps

80% CPU with three open windows is not a hardware problem. It is a process nobody has ended.

“Why is my PC constantly running at 80% CPU and 80% RAM?” That is how one of the most common support cases of all begins. The fan spins up, windows respond sluggishly, and at first glance not much is open.

The actual case was a developer workstation at an agency: 64 GB RAM, a modern CPU, plenty of power in theory. The cause turned out to be mundane, but it was not where you look first. Here is the way to find the culprit systematically.

Why is usage high even though hardly anything is open?

Usually leftovers of programs you closed long ago keep running. Modern applications such as code editors, browsers, and chat and meeting apps consist of many individual processes. If one of them hangs, the window disappears, but the processes keep working in the background.

In the actual case, the editor window was closed. Even so, 28 background processes of that editor were still running, together taking up a large share of the processing power and several gigabytes of memory.

The second factor: the computer had been running for 23 days without a restart. The longer a system runs, the more such leftovers accumulate.

Step 1: How do I find the process that is really creating load?

Open Task Manager with Ctrl+Shift+Esc and sort under “Processes” by CPU, then by Memory. Important: expand the groups, because behind one program name there are often dozens of individual processes.

The Details tab is even more precise: there you see each process individually. Sort by “Name”, and it is immediately obvious when a program appears twenty or thirty times in the list.

Step 2: How do I read the PowerShell output correctly?

The CPU column in Get-Process is not a percentage but the total processor time in seconds since the process started. This is the most common misreading in diagnosis.

Get-Process | Sort-Object CPU -Descending | Select-Object -First 10 Name, Id, CPU, WS

A value of 60,000 for explorer only means that Explorer has used a total of about 17 hours of processor time over 23 days of uptime. That is normal. The current load is shown by this command:

Get-Counter '\Process(*)\% Processor Time' |
  Select-Object -ExpandProperty CounterSamples |
  Where-Object { $_.InstanceName -notin '_total','idle' } |
  Sort-Object CookedValue -Descending |
  Select-Object -First 10 InstanceName, @{n='CPU %';e={[math]::Round($_.CookedValue / $env:NUMBER_OF_PROCESSORS, 1)}}

And this is how you count how many instances of a program are running:

Get-Process | Group-Object Name | Sort-Object Count -Descending | Select-Object -First 10 Count, Name

If a program with 28 entries shows up there that you no longer have open, you have found the culprit.

Step 3: How do I end hung background processes?

First close normally, then end all remaining instances at once. In Task Manager under Details, select the process and click End task, or use a command to end all instances at the same time:

taskkill /f /im Code.exe

Replace Code.exe with the name from step 2. Caution: unsaved work in that program is lost.

In the actual case, CPU load dropped by about a third right away. The program could then be opened again as normal, without the leftovers.

Step 4: Why does a real restart help, and why isn't shutting down enough?

Beta

IT support that fixes itself.

supersupport.ai handles your 1st-level support fully automatically. Secure your spot on the waitlist now.

Join the Waitlist

With fast startup enabled, “Shut down” does not reset Windows. Only “Restart” does. When you shut down, Windows saves the kernel state and loads it again the next time you switch on. That is why Task Manager often shows uptimes of weeks even though the computer was “off” every evening.

You can see the actual uptime in Task Manager under Performance › CPU › “Up time”, or like this:

(Get-Date) - (Get-CimInstance Win32_OperatingSystem).LastBootUpTime

If it shows double-digit days: Start › Power › Restart. If you want to turn off fast startup, you will find it under Control Panel › Power Options › Choose what the power buttons do › Turn on fast startup.

Step 5: What if the load comes back after the restart?

Then the cause is a program that loads at startup, or an extension. Check in this order:

1. Startup: Task Manager › Startup apps. Disable everything that is not needed right away. In the actual case, a remote desktop management tool and a game platform were also running permanently.
2. Extensions: With editors and browsers, a single extension is often to blame. Many editors have their own process explorer (e.g. “Help › Process Explorer”) that shows which extension is doing the computing.
3. svchost processes with high memory: Expand them in Task Manager, and you will see which Windows service is behind it, often Windows Update, search indexing, or a driver service.
4. Updates: Update graphics and chipset drivers, finish Windows Update.

Is 80% RAM usage even a problem?

Not necessarily. Windows deliberately uses free memory as a cache so that programs start faster. It only becomes a problem when the computer becomes noticeably slow, the disk keeps working, or usage stays near 100%. High CPU load at idle, on the other hand, is almost always a sign that something is hung.

For internal IT teams, "the PC is slow" is one of the classics that eat up a lot of time and can almost always be solved with the same steps. See also 5 IT tickets you can solve in 60 seconds and 7 signs your IT support is overwhelmed.

How does SuperSupport help with slow PCs?

In the case described, the SuperSupport agent read the running processes, the current load, and the uptime directly on the device, found the hung background processes, and ended them after approval of the fix plan. Afterwards it measured the load again and recommended the overdue restart. What this looks like for internal IT and MSPs is shown on AI relief for IT teams and AI support for MSPs.

Frequently asked questions

Why is my CPU usage constantly high even though hardly any programs are open?

Often background processes of programs that are already closed keep running, for example helper processes of editors, browsers, or chat apps. On top of that come long uptimes without a real restart, during which such leftovers accumulate.

Is shutting down enough instead of restarting?

No, not with fast startup enabled. When you shut down, Windows saves the system state and loads it again the next time you switch on. Only “Restart” really resets the system.

What does the CPU column in Get-Process mean?

It shows the total processor time in seconds since the process started, not a percentage. A high value only means that the process has worked for a long time or a lot, not that it is creating load right now.

Is 80 percent RAM usage dangerous?

Not automatically. Windows uses free memory as a cache. It only becomes critical when the computer becomes noticeably slow, swaps a lot to the disk, or usage stays near 100 percent.

How do I safely end hung background processes?

First close the program normally. If processes remain, choose “End task” in Task Manager or end all instances with taskkill /f /im Program.exe. Unsaved work in that program is lost in the process.

Beta

IT support that fixes itself.

supersupport.ai handles your 1st-level support fully automatically. Secure your spot on the waitlist now.

Join the Waitlist