Seongwoo Choi / Journal

How to find the process causing a slow PC using Task Manager: the order for reading three tabs

At a glanceWhen a PC suddenly slows down, open Task Manager first. This article explains how to narrow down likely causes by reading the Performance, Processes, and Details tabs in order, following Microsoft’s official documentation rather than testing on a specific PC.

Conceptual illustration for How to find the process causing a slow PC using Task Manager: the order for reading three tabs.
AI-generated editorial illustration; not a product screenshot.
In this article 5 sections
  1. 1. Check the overall load in the Performance tab
  2. 2. Find high-usage items in the Processes tab
  3. 3. Check the description and user in the Details tab
  4. 4. Four steps to check before ending a process
  5. Summary: the checking order

When a PC suddenly slows down, the first place to open is Task Manager. This article explains how to narrow down likely causes in Task Manager by reading the Performance, Processes, and Details tabs in order. This is not the result of testing directly on a specific PC, but an order based on Microsoft’s official documentation.

1. Check the overall load in the Performance tab

The Performance tab displays the computer’s overall CPU and memory usage in graphs. In the default view, the CPU graph shows the total load regardless of the number of logical processors. Right-click the CPU graph and select “Show kernel times” to display the loads of kernel processes and user processes in two different colors. Note which one is higher so it is easier to compare in the next step.

2. Find high-usage items in the Processes tab

The Processes tab lists apps and background processes, along with each item’s CPU and memory usage. Click the CPU or Memory column header to sort the list, and the items with the highest usage will move to the top.

Distinguish between two things here. A value that rises briefly and then falls may be normal activity. Microsoft’s support guidance also explains that a temporary increase in CPU usage is normal, but that if the high usage continues for a long time, you should find the underlying cause. Therefore, the next step is to check again whether the same item remains high after a few minutes.

3. Check the description and user in the Details tab

The Details tab lists running processes and provides additional columns such as user information, resource usage, and Description. When you cannot tell what something is from its name alone, checking the Description and User columns together can show which account the item is running under.

4. Four steps to check before ending a process

Microsoft’s documentation advises that if you can stop a process or turn off a related service, you should do so and then check whether the problem improves. It also advises that if a third-party app’s process is the cause, you should check with the app’s vendor to identify the cause. The order is therefore as follows.

  1. Check the name and description first. Do not end an unidentified system process.
  2. End only the app whose cause is clear, and watch for 1–2 minutes to see whether the same CPU or memory symptoms decrease.
  3. If they do not decrease, find the related service in the Services tab and check the app vendor’s materials.
  4. Save any unsaved work first. Ending a process may cause unsaved content within it to be lost.

Summary: the checking order

The order is: check the overall load in the Performance tab, sort items in Processes, check whether the issue persists, check the description and user in Details, then recheck after stopping the process. This order is a way to narrow down the cause and does not guarantee that a specific app is responsible. If you want to organize items that run automatically, also see Windows startup program cleanup: three steps to check before turning items off .

Source: Troubleshoot processes by using Task Manager (Microsoft Learn) , checked on October 29, 2026 KST. This document is for Windows Server, but it states that it also applies to Windows clients. Menu names and screens may vary depending on the Windows version. The CPU usage guidance was checked through a search summary for Guidance for troubleshooting high CPU usage (Microsoft Learn) .

Sources and original article

Read the Korean original on Naver

This article reflects public information available when it was written. Specifications, prices and schedules can change; check the linked official documentation.

This English edition was written and translated with AI assistance, with sources provided. For errors or additional information, please request a correction. Editorial policy