Guide · Windows 11 and 10

High memory usage in Windows: what is actually using your RAM?

A high memory percentage is often normal. Here is how to read the numbers, find the program or driver that really is the problem, and skip the myths.

Updated 5 October 2026 · 5 min read

Is high memory usage actually a problem?

Often it is not. Windows treats unused RAM as wasted RAM, so it fills memory with a cache of files and programs you used recently and hands it back the moment something needs it. A high percentage in Task Manager can be a healthy PC doing its job.

Memory is a problem when you also see one of these: programs slowing down or closing, a "your computer is low on memory" warning, constant disk activity while you do nothing, or a commit charge that sits close to its limit (explained below). If none of those apply, you do not need to fix anything.

In use, standby, modified, compressed: what the numbers mean

Task Manager splits memory into a few groups. Open it, go to Performance and choose Memory.

• In use: memory that programs, drivers and Windows itself are using right now. It includes compressed memory, which Windows squeezes to keep more in RAM instead of writing it to disk.
• Modified: pages that changed and are waiting to be written to disk. Microsoft notes that several hundred megabytes typically stay on this list.
• Standby: cached copies of data that is already safely on disk. Windows can reuse it instantly, so it counts as available.
• Free: memory holding nothing at all. It is normally small, on purpose.

Task Manager's Cached figure is the modified and standby lists together with the system cache. Available is what Windows can give to a program right away, which includes standby. That is why "free" being small is normal, and why "available" is the number to watch.

Commit: the limit that really bites

Commit charge is the total memory programs have been promised, whether or not it is in RAM at the moment. The commit limit is your RAM plus the page files. If the charge reaches the limit, allocations fail, and that is when programs crash or Windows warns you. In Task Manager it is the Committed pair at the bottom, such as 14.2/31.7 GB. If you are regularly within a few gigabytes of the limit, you are short on memory. See how big your page file should be for how the limit is made.

Find what is using it

1. Task Manager, Processes tab. Sort by Memory. Browsers are often the largest, so check the browser's own task manager as well (Shift + Esc in Edge and Chrome) to see which tab or extension it is.
2. Details tab. Right-click the column header, choose Select columns, and add Commit size. Working set is what is in RAM now; commit size is what the program asked for.
3. Resource Monitor. Run resmon, open the Memory tab and watch Hard Faults/sec. Sustained high values mean Windows is reading from the disk because RAM is short.
4. RAMMap. This free Microsoft Sysinternals tool shows RAM by type, by process and by file, including the standby list by priority.

The numbers in Task Manager's process list should roughly add up to the In use figure. If a few gigabytes are missing, look at the kernel: the Paged pool and Non-paged pool values on the Memory page. A non-paged pool that keeps growing points to a driver, and this guide shows how to find it.

Spotting a leak

A memory leak is a program that keeps taking memory and never gives it back. The signature is a steady climb over hours that does not fall when the program is idle or you close its windows. A big number alone is not a leak: a video editor or a game legitimately uses a lot. Note the program's commit size in the morning and again in the evening. If it only goes up, restart that program, update it, and report it to its maker if it returns.

What helps, and what is a myth

What helps:

• Closing or restarting the one program that is growing.
• Updating drivers and apps, since many leaks are fixed in later versions.
• Trimming what starts with Windows, so fewer programs sit in memory all day.
• Keeping the page file enabled.
• Adding RAM, if commit is regularly close to the limit with your normal work.

What is a myth:

• "RAM cleaner" and "memory booster" tools. Forcing programs to give up memory they are using makes them read it back from disk, so the PC feels slower for a moment, and the gain fades.
• Emptying standby memory as a routine. Standby is cache that makes your next file open faster. Windows refills it immediately. It helps in rare cases, such as a game that stutters because the cache crowded out free memory, and almost never as a habit.
• "Free memory should be high". It should be low. Available memory is what counts.
• Turning off memory compression or the page file. Neither is a general speed-up, and the page file also backs crash dumps.

In Cosmo Cleaner

Release 1.2.0 adds a Memory tab that shows the same breakdown live, without opening four tools. The Overview draws one bar with in use, modified, standby (split into core, normal and reserve priority), compressed and free. Commit is shown against its limit with a forecast, once it has moved steadily for about five minutes.

The Processes view ranks programs by working set and private bytes and can show only leak suspects. Kernel pools lists pool tags for the kernel side. Diagnostics collects Windows Memory Diagnostic results, hardware memory errors reported by WHEA, low-memory events and stop errors, which helps when the real problem is faulty RAM. Modules lists your RAM sticks, their speed, and gives a hint when XMP or EXPO may be switched off.

The Tools view includes the commands people reach for, such as trimming working sets or emptying low priority standby. Each one says what it does, and the page states plainly that none is a lasting speed-up. A standby guard exists but is off by default.

Questions