When your PC freezes, fans spin loud, and apps lag, high RAM usage is often the cause. Task Manager shows a basic list of processes, but it hides the detail you need to find the real memory hog. The built-in Resource Monitor gives a clearer view—especially the Private memory column, which shows memory reserved by a single process and not shared with others.

Here is how to use the resmon command to find the hidden app eating your RAM.

Step 1: Open Resource Monitor

  1. Press Start.
  2. Type resmon.
  3. Click Resource Monitor in the search results.

You can also open Command Prompt and run:

text

resmon

If prompted by User Account Control, select Yes.

Step 2: Open the Memory Tab

In Resource Monitor, click the Memory tab at the top. This tab shows physical memory usage, process-level memory, and overall system memory pressure.

Look at the bottom section labeled Processes. It lists running apps and background processes with several memory columns.

Step 3: Sort by Private Memory

The key column is Private. This shows how much memory a process is using exclusively—memory that cannot be shared or freed by other apps. A process with high Private memory is a strong candidate for the RAM problem.

  1. Click the Private column header to sort from highest to lowest.
  2. Review the top entries. The process at the top is using the most exclusive memory.
  3. Check the Commit (KB) and Working Set (KB) columns for context. Private is the most useful for spotting a memory leak or runaway app.

Step 4: Identify the Process

Look at the Image and Description columns to identify the app. Common culprits include browsers with many tabs, background sync tools, game launchers, and apps with memory leaks.

If you do not recognize a process:

  • Right-click it and select Search online to identify it.
  • Check its PID and compare it in Task Manager if needed.
  • Do not end system processes unless you know what they do.

Step 5: Take Action

Once you find the top Private memory user:

  • Close the app normally if it is a user program.
  • Restart the app if memory does not drop.
  • Update the app if the high usage is a known bug.
  • Investigate further if a background service keeps growing over time.

Why Resource Monitor Beats Task Manager

Task Manager is fine for a quick look, but it groups memory into broad numbers. Resource Monitor shows Private memory per process, which makes it much easier to spot the single app consuming RAM without sharing it. That is the fastest way to find what is eating your memory.

Quick Summary

text

resmon

Then: Memory tab → sort by Private → identify the top process.

This takes under a minute and gives you a precise answer instead of a guess.