How to Check Memory Usage in Windows with Task Manager

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

To check memory usage in Windows with Task Manager, press Ctrl + Shift + Esc, select Processes, and sort by Memory to find the largest users. Open Performance > Memory to see total RAM, available memory, cached memory, and committed virtual memory. Use Details > Commit size for deeper troubleshooting.

The instructions apply to Windows 10 and Windows 11, although Task Manager labels, grouping, and layout can vary by version, edition, build, and device. Microsoft describes Task Manager as a built-in monitor for resource consumption, including memory; see Microsoft’s Task Manager and system-configuration guidance.

#	Preview	Product	Price
1		Webroot Premium 2026 with Allstate Identity Protection | 10 Device, 1 Year | Antivirus and Internet...	$79.99	Buy on Amazon

Key takeaways

• Processes > Memory identifies applications and processes with the largest current physical-memory working sets.
• Performance > Memory shows the broader RAM picture, including installed memory, in-use memory, available memory, cached memory, committed memory, and hardware-reserved memory.
• High memory usage by itself is not proof of a problem; persistent slowdowns, very low available memory, heavy paging, crashes, or continuous process growth are more meaningful warning signs.
• Committed memory is not the same as RAM usage: committed virtual memory can be backed by physical RAM, the page file, or both.
• Details > Select columns > Commit size can reveal virtual-memory consumption that the ordinary Processes memory column does not fully show.
• Do not terminate unfamiliar Windows, security, or system processes merely because they use a lot of memory; close the associated application normally or investigate the process first.

What does memory usage mean in Windows?

Memory usage describes how Windows, applications, services, drivers, and cached data are using the computer’s memory resources. Most people mean physical RAM usage, but Task Manager also displays related measurements for virtual memory, kernel memory, cache, and hardware-reserved memory.

That distinction matters because several different problems can look like “high memory usage”:

Popular on Amazon

Sale

Webroot Premium 2026 with Allstate Identity Protection | 10 Device, 1 Year | Antivirus and Internet Security Software, Advanced Dark Web Monitoring, Password Manager | NEW [Online Code]

• IDENTITY THEFT PROTECTION for up to 10 family member's mobile phones, laptops, desktops, Chromebooks and tablet, safeguards your personal and financial information with rapid alerts on identity threats.
• ADVANCED DARK WEB MONITORING: Get notified if your personal data is found in a data breach or your credentials are compromised.
• UP TO $1 MILLION in expense reimbursement for stolen funds and out-of-pocket costs due to identity theft including up to $150k for 401(k)/HSA saving accounts
• 24/7 US-BASED SUPPORT with identity restoration experts to help restore your stolen identity or mitigate fraud on your accounts.
• ANTIVIRUS, Anti-phishing, malware, ransomware protection against existing and emerging threats.

$79.99

Buy on Amazon

• High physical RAM use: applications and Windows are using most of the installed RAM.
• High application usage: one program, browser, game, or service has a large working set.
• High commit usage: programs have reserved substantial virtual memory backed by RAM and/or page-file capacity.
• A possible memory leak: one process keeps growing over time without a matching increase in workload.
• Insufficient RAM: the computer regularly runs out of readily available memory during normal work.
• Kernel or driver usage: paged pool or non-paged pool memory is unusually large.

Windows may use otherwise available RAM for caching recently used data and code. That cache can often be reclaimed when applications need memory, so a high percentage alone does not establish that Windows has a memory problem.

How do you open Task Manager?

The fastest way to open Task Manager is to press Ctrl + Shift + Esc. If Task Manager opens in its compact view, select More details to show the full tabs.

You can also open Task Manager using any of these routes:

• Right-click the Start button and select Task Manager.
• Open Start and search for Task Manager.
• Press Ctrl + Alt + Delete, then select Task Manager.

Microsoft documents these opening methods and Task Manager’s resource-monitoring role in its Windows system-configuration tools documentation.

How do you check which apps use the most memory?

To find the applications and processes using the most memory, open Task Manager, select Processes, and sort the Memory column from largest to smallest.

1. Press Ctrl + Shift + Esc.
2. Select More details if the compact view is displayed.
3. Select the Processes tab.
4. Find the Memory column. If the column is not visible, maximize the window or adjust the column layout.
5. Select the Memory heading once or twice until the largest values appear at the top.
6. Review the entries under Apps, Background processes, and Windows processes.

The Processes tab is a live list, so values can change while programs work. Microsoft describes the tab and its resource information in its Task Manager support-tools documentation.

How should you interpret the largest process?

The largest Memory value is a useful starting point, but the largest process is not automatically defective or the root cause of a slowdown. The value generally reflects a process’s resident physical-memory working set at that moment, not every allocation associated with the process.

A process’s working set can include memory shared with other processes, and Windows may account for shared resources in ways that make simple comparisons misleading. The total of all visible process values also will not necessarily equal the headline memory figure because Windows uses memory for the kernel, drivers, cache, and other system functions.

A browser is a common example. A browser may show separate processes for tabs, extensions, graphics processing, and browser services. Expand the browser’s grouped entry when possible, and compare individual tabs or extensions rather than assuming that one browser process represents the entire browser workload.

What is the safest way to close a memory-heavy app?

Save your work and close a recognized application through its normal interface before using End task in Task Manager. Repeatedly ending a program can cause unsaved-data loss, interrupted downloads, or application corruption.

Do not randomly end entries such as System, Registry, Service Host processes, security software, Desktop Window Manager, or Windows Shell components. If an unfamiliar process is consuming memory, research its identity, check which application installed it, update or repair the associated software, or restart Windows rather than terminating it blindly.

How do you see total RAM and available memory?

For the overall state of the computer’s memory, select Performance > Memory in Task Manager. Leave the page open while launching the problem application or reproducing the slowdown, then compare the percentage with the detailed figures beneath the graph.

1. Open Task Manager with Ctrl + Shift + Esc.
2. Select Performance.
3. Select Memory in the left pane.
4. Observe the graph and the figures shown below or beside it.

Depending on the Windows release and device, the page may show total installed memory, current use, available memory, memory speed, form factor, slots used, hardware-reserved memory, committed memory, cached memory, paged pool, and non-paged pool. Microsoft notes that Task Manager’s appearance can vary between Windows versions even though the underlying information comes from the same Windows sources.

What do In use, Available, Committed, and Cached mean?

The figures on Performance > Memory describe different parts of Windows memory management. The exact placement and available labels can vary, but these are the practical meanings.

Microsoft explains working sets, available memory, committed bytes, and paged and non-paged pool memory in its Windows performance troubleshooting documentation.

Is 90% memory usage bad?

90% memory usage is not automatically bad. A high percentage becomes meaningful when the computer is sluggish, applications freeze or crash, disk activity rises because Windows is paging, Available memory remains very low, Commit usage approaches its limit, or one process continues growing without a corresponding workload.

There is no universal consumer cutoff such as 80% or 90% that determines whether a Windows PC needs more RAM. Workload, installed RAM, background services, page-file capacity, drivers, and the computer’s symptoms all matter.

Microsoft’s server troubleshooting guidance uses specific Available MBytes thresholds in a particular diagnostic context: below 10% is treated as a warning, while below 1% or 500 MB is treated as critical in that context. Those figures are not universal rules for every Windows 10 or Windows 11 PC; the Microsoft troubleshooting page should be read with that server-monitoring context in mind.

Use symptoms and trends rather than one snapshot

A normal high-memory situation often changes with your workload: memory rises when applications open, falls after a large application closes, and the computer remains responsive. A concerning situation persists after the workload ends, returns after every restart, or becomes progressively worse during ordinary use.

• Probably normal: memory rises while applications are open, Cached memory is substantial, and the PC remains responsive.
• Possibly insufficient RAM: the same workload repeatedly leaves little Available memory and causes frequent paging or slow application launches.
• Possibly a memory leak: one process continually grows during normal use and does not release memory after its workload finishes.
• Possibly a driver or kernel problem: Non-paged pool memory is unusually large or keeps increasing.
• Possibly a virtual-memory problem: Committed memory approaches the commit limit or an application reports an out-of-memory error.

How do you find a possible memory leak?

A memory leak is better identified by continuous growth over time than by a single high memory reading. A large application can legitimately need substantial memory during a demanding task, while a leaking process keeps retaining memory after the task has ended.

1. Open Task Manager > Processes and sort by Memory.
2. Record the largest relevant process and its current Memory value.
3. Use the computer normally for approximately 15 to 60 minutes.
4. Check whether the same process keeps growing without a corresponding workload.
5. Close and reopen the application, then observe whether its usage resets.
6. Restart Windows and repeat the observation if the problem returns.

This test can reveal suspicious growth, but Task Manager alone may not establish the cause. Microsoft recommends more specialized analysis, including VMMap and Windows Performance Toolkit tools, for difficult application or service memory-leak investigations; see Microsoft’s memory-leak troubleshooting guidance.

How do you check Commit size for a process?

Use the Details tab and enable Commit size when the suspected problem involves virtual-memory exhaustion or a process whose ordinary Memory value looks modest compared with overall commit usage.

1. Open Task Manager and select Details.
2. Right-click any column heading.
3. Select Select columns.
4. Enable Commit size, if the option is available.
5. Select the new Commit size column to sort processes.

The exact menu wording and available columns can vary by Windows version. Commit size is different from the ordinary Processes Memory value: the Memory value is useful for comparing current physical-memory working sets, while Commit size helps show virtual-memory allocations that may be backed by RAM and page-file capacity.

Microsoft specifically warns that the default process memory figure may not be the right measure when investigating virtual-memory problems and recommends examining commit size in its application and service memory-leak guidance.

What should you do when memory usage remains high?

Work through the least disruptive actions first, then escalate if the same pattern returns.

1. Close unused applications and browser tabs. Save work and close programs normally rather than ending unfamiliar processes.
2. Check browser extensions. Expand the browser’s process group and disable or remove extensions that correlate with unusual growth. Use the browser’s own task manager where available.
3. Restart Windows. A restart clears temporary process state and can distinguish a one-time condition from a recurring problem.
4. Review startup apps. In Task Manager, select Startup apps and disable unnecessary programs that launch automatically. Do not disable security or hardware utilities without understanding their purpose.
5. Install Windows and application updates. Also update graphics, storage, network, and security-related drivers when a driver or hardware component may be involved.
6. Run an antivirus or antimalware scan. Malicious or unwanted software can create abnormal background activity.
7. Allow Windows to manage the page file. Change page-file settings only when a documented diagnostic reason requires it; manually reducing page-file capacity can worsen commit pressure.
8. Use Resource Monitor. Compare process Commit, Working Set, and hard faults for a more detailed built-in view.
9. Test the RAM. Use Windows Memory Diagnostic or a suitable diagnostic supplied by the computer or memory manufacturer if crashes, memory-related stop errors, or hardware instability are suspected.
10. Consider a hardware upgrade. If normal workloads regularly exhaust Available memory and the device supports an upgrade, adding physical RAM may be the durable solution. If memory is soldered or otherwise non-upgradable, reducing workload or replacing the device may be necessary.

Microsoft identifies startup programs, outdated software, background applications, and insufficient hardware as possible contributors to poor performance in its Windows performance-optimization guidance.

How do you use Resource Monitor after Task Manager?

Resource Monitor provides a more detailed built-in view when Task Manager does not explain the memory problem.

1. Press Windows + R.
2. Enter resmon.
3. Press Enter.
4. Select the Memory tab.
5. Sort the process list and compare Commit, Working Set, physical memory categories, and hard faults.

Resource Monitor’s layout can differ slightly between Windows releases. Use Resource Monitor as a follow-up to Task Manager, not as a reason to treat every hard fault or cached allocation as a failure.

When do you need advanced memory diagnostics?

Advanced tools are appropriate when a process or driver keeps growing, the cause is not visible in Task Manager, or the issue must be documented for development or support.

Microsoft’s memory-footprint documentation identifies VMMap, Windows Performance Recorder, Windows Performance Analyzer, and Performance Monitor as tools for deeper analysis. The following example is intended only for advanced users with the relevant Windows Performance Toolkit components installed:

wpr -start VirtualAllocation -filemode
wpr -stop Trace.etl
wpa.exe Trace.etl

Microsoft documents this trace-collection workflow in its memory and disk performance documentation. Ordinary Task Manager checks do not require these commands.

Can Task Manager test whether RAM is faulty?

Task Manager shows how memory is being used, but Task Manager does not fully test whether the physical RAM chips are reliable. If Windows crashes, displays memory-related stop errors, or fails during ordinary workloads, run Windows Memory Diagnostic or a hardware diagnostic from the computer or memory manufacturer.

A hardware test is especially appropriate when crashes occur across different applications, the problem remains after updates and restarts, or memory-related errors appear without a consistent high-usage process.

What is the practical diagnosis?

Use Processes > Memory to identify large current working sets, then use Performance > Memory to determine whether the whole system has low Available memory or high Commit pressure. If the two views do not appear to agree, check Details > Commit size and Resource Monitor rather than adding every process value together.

The right remedy depends on the pattern: close or repair a specific application, reduce startup and browser activity, update software and drivers, investigate a continuously growing process, test suspected hardware, or add RAM when the normal workload genuinely exceeds the device’s capacity.

Frequently Asked Questions

Why does Task Manager not add up to the total memory shown?

Task Manager’s visible process Memory values do not necessarily equal the total memory figure because Windows also uses memory for the kernel, drivers, cache, shared resources, and other system functions. Use Performance > Memory for the system-wide view and Details > Commit size when virtual-memory usage is the concern.

What is the difference between Memory and Commit size in Task Manager?

The Processes Memory value primarily helps compare a process’s current physical-memory working set, while Commit size shows virtual-memory allocations that are backed by RAM, page-file capacity, or both. Commit size is more useful when investigating virtual-memory exhaustion or a possible leak.

Should I end the process using the most RAM?

Do not automatically end the process using the most RAM. Close a recognized application normally after saving work, and investigate unfamiliar Windows, security, driver, or system processes before taking action because ending them can cause data loss or system instability.

How do I know whether I need more RAM?

You may need more RAM when your normal workload repeatedly leaves very little Available memory, causes heavy paging and slowdowns, and the pattern is not explained by one faulty or unusually growing application. Check whether the device supports an upgrade; soldered memory may make replacing the device the practical option.

Why does memory usage increase after leaving an app open?

Memory that continually increases without a matching workload can indicate an application or extension leak, although some applications legitimately cache data while working. Record the process over 15 to 60 minutes, close and reopen the application, and repeat after a restart to see whether the growth returns.

The Bottom Line

Bottom line: Start with Task Manager > Processes > Memory to find large process working sets, then check Performance > Memory for Available, Committed, Cached, pool, and hardware-reserved memory. High usage alone is not a diagnosis; persistent symptoms, low availability, commit pressure, or continuous growth determine whether further troubleshooting is necessary.

Quick Recap

SaleBestseller No. 1

Webroot Premium 2026 with Allstate Identity Protection | 10 Device, 1 Year | Antivirus and Internet Security Software, Advanced Dark Web Monitoring, Password Manager | NEW [Online Code]

$79.99