How to Fix High Memory Usage and Severe Memory Leaks in Windows

High memory usage can make Windows feel slow, cause applications to stop responding, and increase storage activity as the operating system relies on the page file. A true memory leak is more specific: a process or driver repeatedly allocates memory without releasing it, so usage continues to rise until the process is restarted or the underlying fault is corrected.

The following troubleshooting process applies to Windows 10 and Windows 11. The goal is to distinguish normal RAM use from a leak, identify the responsible application or driver, and correct the cause without making unnecessary system changes.

First, Confirm That Memory Usage Is Actually a Problem

Windows deliberately uses available RAM for applications, file caching, and other system functions. Cached memory can be released when another program needs it, so a high percentage by itself does not prove that anything is wrong.

High usage deserves investigation when one or more of these symptoms occur:

• Available memory remains very low during ordinary use.
• An application’s memory consumption rises continuously while it is idle.
• The system becomes progressively slower after hours or days of uptime.
• Closing an application does not release the expected amount of memory.
• Windows displays low-memory warnings or applications close unexpectedly.
• Storage activity increases sharply because Windows is paging data to disk.
• The non-paged pool grows unusually large, which may indicate a driver leak.

A demanding workload is not necessarily a leak. Video editing, virtual machines, large games, software development tools, and browsers with many active tabs can legitimately consume most of the installed RAM. The important distinction is whether memory use corresponds to the workload and falls again when that workload ends.

Identify the Process in Task Manager

Press Ctrl + Shift + Esc to open Task Manager. If it opens in the simplified view, select More details. On the Processes page, select the Memory column to sort processes from highest to lowest usage.

Check whether the top entry is an application that is currently performing useful work. Browsers may list tabs, extensions, and graphics services as separate processes, while launchers and communication tools may continue running after their windows are closed.

Do not end an unfamiliar process solely because its name is unclear. It may be part of Windows, a hardware driver, antivirus software, or an application service. Instead, right-click it and use options such as Open file location, Properties, or Go to details. For a Service Host process, choose Go to services where available to see which Windows services are associated with it.

The Performance page provides a broader view. Select Memory and note the values for In use, Available, Committed, Cached, Paged pool, and Non-paged pool. A large cache is generally less concerning than steadily increasing committed memory or an expanding non-paged pool.

Look for Growth Over Time

A single Task Manager reading cannot reliably confirm a leak. Record the suspected process’s memory use, leave the computer under a consistent workload, and check it again at regular intervals. Continuous growth while the program is idle is more meaningful than a temporary spike.

For more detail, press Windows + R, enter resmon, and open the Memory tab in Resource Monitor. Useful columns include:

• Commit: The amount of virtual memory Windows has committed to the process.
• Working Set: The process’s physical memory currently resident in RAM.
• Private: Memory assigned to that process that cannot be shared with another process.
• Hard Faults/sec: The rate at which requested data must be retrieved from storage rather than physical RAM.

Hard faults are not hardware faults, and occasional activity is normal. Sustained hard-fault activity combined with low available memory and poor responsiveness indicates memory pressure, but there is no universal numerical threshold that applies to every PC.

Restart the Suspected Application

If one nonessential application is consuming excessive memory, save any open work and close it normally. Confirm in Task Manager that all related processes have exited, then reopen it. If memory returns to normal but begins climbing again, the application, one of its plug-ins, or a related background service is a likely cause.

A reboot can restore performance by clearing allocated memory, but it should be treated as a temporary diagnostic step rather than a permanent repair. Note how long the problem takes to return and what actions were performed before the increase began.

Update, Repair, or Reinstall the Application

Check the application’s built-in updater or official support page for a newer version. Review available release notes for relevant crash, stability, or memory-management fixes. If the problem began immediately after an application update, check whether the developer provides a newer corrective release or an officially supported way to return to the previous version.

Extensions and plug-ins can also be responsible. Start the application without optional add-ons where possible, or disable them in small groups. Browser users should review extensions, close unusually demanding tabs, and use the browser’s own task manager if it provides one. Re-enable components one at a time until the problem returns.

If updating does not help, use the application’s repair option under Settings > Apps > Installed apps, if available. Otherwise, uninstall it, restart Windows, and install a fresh copy from the official source. Back up application settings and project files before removal.

Check Drivers and the Non-Paged Pool

Drivers operate at a lower level than ordinary applications and can consume memory that is not clearly attributed to a process. A steadily growing Non-paged pool value in Task Manager can point to a driver or kernel component rather than a desktop program.

Consider recent changes first. If the issue appeared after updating a graphics, network, storage, audio, printer, or peripheral driver, check the device manufacturer’s support page for a corrected release. Prefer drivers supplied by the PC, motherboard, GPU, or device manufacturer over downloads from unofficial driver sites.

To inspect a driver, open Device Manager, expand the relevant category, right-click the device, and select Properties. The Driver tab shows its provider, date, and version. If the problem began after an update, Roll Back Driver may restore the previous version. The button can be unavailable if Windows no longer retains that package.

Advanced diagnosis of kernel memory can involve Microsoft tools such as PoolMon, but interpreting pool tags requires care. Before using low-level tools, collect the non-paged pool value, driver versions, recent update history, and the hardware involved. That information is useful when consulting the device manufacturer or Microsoft support documentation.

Reduce Unnecessary Startup Activity

Disabling startup applications does not repair a leak inside software that must remain running, but it reduces baseline memory use and helps isolate background programs.

Open Task Manager, select Startup apps, and review programs that launch when signing in. Common optional entries include game launchers, chat tools, update helpers, cloud clients, and peripheral utilities. Disable only items you recognize and do not need continuously. Avoid disabling security software, storage drivers, accessibility tools, or hardware services without understanding their purpose.

Restart Windows after making changes and compare memory use under the same conditions. If the problem disappears, re-enable entries individually or in small groups to identify the responsible software.

Use a Clean Boot to Isolate Background Software

If Task Manager does not reveal an obvious cause, a clean boot can determine whether a third-party service is involved.

1. Press Windows + R, enter msconfig, and press Enter.
2. Open the Services tab and select Hide all Microsoft services.
3. Select Disable all to disable the remaining third-party services.
4. Open Task Manager from the Startup tab and disable nonessential startup entries.
5. Restart Windows and check whether the memory problem returns.

If memory use remains normal, restore services and startup entries in groups until the issue reappears. Keep a record of every change. After troubleshooting, return to System Configuration and restore the normal startup settings.

Scan for Malware

Malicious software can consume RAM and CPU while disguising itself with a name similar to a legitimate Windows component. A familiar-looking filename does not prove that a process is safe; its file location and digital signature also matter.

Open Windows Security, select Virus & threat protection, choose Scan options, and run a Full scan. If suspicious behavior continues, consider Microsoft Defender Offline scan, which restarts the PC and checks for threats outside the normal Windows session.

A reputable second-opinion scanner may provide an additional check, but download it only from its official website. Do not run several real-time antivirus products simultaneously, because their background scanning components can conflict and increase resource use.

Keep the Page File Enabled

The page file extends the system’s commit capacity and supports crash dumps and workloads that cannot remain entirely in physical RAM. It does not fix a leak, and paging is much slower than accessing RAM, but disabling it can cause applications to fail sooner when memory is under pressure.

For most systems, the safest configuration is Automatically manage paging file size for all drives. To check it, press Windows + R, enter sysdm.cpl, and select Advanced > Performance Settings > Advanced > Virtual memory > Change.

There is no single page-file multiplier that is correct for every computer. The appropriate size depends on installed RAM, workload, free storage space, and crash-dump requirements. A manually fixed size can impose an unnecessary storage cost or leave too little commit capacity. Unless a specific application or support document requires a custom value, allow Windows to manage it.

Repair Windows Components

If high usage appears to involve a Windows component, install pending Windows updates and restart the PC. If system files may be damaged, open Terminal (Admin) or Command Prompt (Admin) and run these commands in order:

DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow

DISM checks and repairs the Windows component store, while System File Checker verifies protected system files. These tools do not cure third-party application leaks, but they can correct damaged Windows components. Restart after the scans complete and review any messages they report.

Monitor Slow or Intermittent Leaks

For a problem that takes hours or days to develop, use Performance Monitor. Press Windows + R, enter perfmon, and add counters relevant to the suspected process, such as ProcessPrivate Bytes, ProcessWorking Set, and MemoryAvailable MBytes. A Data Collector Set can record values over time for later review.

Microsoft Sysinternals Process Explorer is another option for inspecting process trees, private bytes, handles, loaded components, and executable signatures. Download Sysinternals utilities only from Microsoft. A growing handle count may indicate a resource leak even when the immediate RAM increase is modest.

When documenting an issue, record the process name, executable path, software and driver versions, Windows version, time since startup, memory values, and the steps that trigger the growth. This is more useful to a developer or support technician than a screenshot showing only the overall memory percentage.

Test RAM When Crashes or Corruption Are Also Present

Defective RAM usually causes crashes, corrupted files, installation failures, or application errors rather than steadily increasing memory consumption. However, memory testing is appropriate when instability remains after software causes have been addressed.

Press Windows + R, enter mdsched.exe, and choose Restart now and check for problems. Save all work first. After Windows restarts, results may appear in a notification or can be reviewed in Event Viewer under the MemoryDiagnostics results.

If errors are reported, return any memory overclocking or XMP/EXPO settings to motherboard defaults before testing again. Also check that the modules are installed in the recommended slots. Testing one module at a time can help isolate a faulty stick, but power off and unplug the PC before opening it. Persistent errors may involve the RAM, motherboard slot, memory controller, firmware settings, or module compatibility.

When More RAM Is the Appropriate Fix

Additional RAM is useful when legitimate workloads regularly exhaust physical memory and no process shows leak-like growth. It will not correct faulty software; it may only delay the point at which a leak causes problems.

Before purchasing memory, observe peak usage during a representative workload and confirm that paging coincides with poor responsiveness. Then check the motherboard or PC manual for supported memory type, capacity, module arrangement, and speed. Laptop memory may be soldered or have only one replaceable slot, while desktop systems may require matched module placement for the intended memory-channel configuration.

How to Check RAM Compatibility With Your Motherboard and CPU

A Practical Troubleshooting Order

1. Confirm that the system is experiencing low available memory or worsening performance, not merely using RAM for cache.
2. Sort processes by memory use and identify whether one application is growing.
3. Restart, update, repair, or reinstall the affected application and test without extensions.
4. Review recent driver and Windows updates, especially if the non-paged pool is increasing.
5. Disable optional startup programs or perform a clean boot.
6. Scan for malware and repair Windows system files if appropriate.
7. Leave the page file system-managed while diagnosing the underlying cause.
8. Collect long-term data for slow leaks and test physical RAM if crashes or corruption are also occurring.
9. Consider a RAM upgrade only when normal workloads genuinely exceed the installed capacity.

A methodical approach prevents unnecessary reinstalls and hardware purchases. Measure what is growing, change one variable at a time, and confirm the result under the same workload. If the issue cannot be resolved, the collected process names, memory trends, driver versions, and reproduction steps will make further support considerably more effective.

Sources and verification

For specifications and platform-specific details, verify the current documentation for your exact hardware and software version. The following official or manufacturer resources are useful starting points:

• Microsoft — Find and Fix Memory Leaks in Windows
• Microsoft — Check for Memory Leaks with Performance Monitor
• Microsoft Sysinternals — RAMMap