How to Fix 100% Memory & Disk Leak in Windows 11 (24H2): Complete Step-by-Step Diagnostic Guide

#tutorial #windows #tech

Following the rollout of Windows 11 24H2, numerous desktop and laptop users have reported severe system degradation characterized by Task Manager displaying continuous 95% to 100% memory utilization or pinned SSD storage activity even when idling. Unlike standard application consumption, these persistent resource bottlenecks often stem from low-level kernel driver Non-Paged Pool exhaustion, runaway SysMain prefetching, unclosed File Explorer thread handles, or corrupt virtual pagefiles. Here is a definitive diagnostic manual to isolate and permanently resolve these leaks.

Step 1: Diagnosing Non-Paged Pool Kernel Memory Leaks

Open Task Manager (Ctrl + Shift + Esc) and click on the Performance tab, followed by Memory. Examine the figure listed under Non-paged pool. On a healthy Windows installation, this value should remain between 250MB and 600MB.

If your Non-paged pool exceeds 2GB, 4GB, or continually expands until your system freezes, a third-party kernel driver is failing to release allocated memory back to the operating system. The most frequent culprits are outdated network adapter drivers (particularly Killer Network Service and older Realtek PCIe controller suites).

Fixing Network Driver Pool Leaks in the Windows Registry:

- Press **Win + R**, type `regedit`, and press Enter.

- Navigate to: `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Ndu`.

- Double-click the **Start** DWORD value on the right-hand pane.

- Change its value data from **2** (Automatic) to **4** (Disabled) and click OK.

The Windows Network Data Usage Monitoring Driver (NDU) frequently triggers infinite buffer accumulation under high-throughput fiber downloads. Disabling this background telemetry service halts pool exhaustion immediately without impacting network speeds.

Step 2: Calibrating SysMain and Superfetch Disk Thrashing

The SysMain service (formerly known as Superfetch) is designed to preload frequently launched binaries into unused RAM to speed up launch times. While beneficial on traditional spinning mechanical hard drives, SysMain frequently mismanages rapid read/write cycles on modern NVMe solid-state drives, generating continuous 100% active disk time spikes.

# Run in administrative PowerShell to disable aggressive disk prefetching:
Stop-Service -Name "SysMain" -Force
Set-Service -Name "SysMain" -StartupType Disabled

Disabling SysMain on systems equipped with an SSD reduces background storage write cycles by multiple gigabytes daily while preventing random system stutter during background indexing.

Step 3: Resolving File Explorer (explorer.exe) Memory Leaks

A documented bug in recent Windows 11 feature revisions causes explorer.exe to fail to deallocate memory when closing tabs or previewing media directories containing thousands of high-resolution images. To resolve shell caching leaks:

    Setting Area

    Tweak Action

    Expected Result

Folder Options
Check "Launch folder windows in a separate process"
Isolates desktop shell from file navigation crashes and memory bloat.


Privacy History
Clear File Explorer history cache
Flushes corrupt thumbnail caches and stale pointer handles.


Windows Search Indexer
Rebuild Search Index in Control Panel
Eliminates infinite looping within SearchIndexer.exe database files.

Step 4: Recreating a Corrupted Virtual Memory Paging File

When Windows encounters severe disk spikes upon booting, the hidden pagefile.sys structure on your primary boot partition is frequently fragmented or corrupted. Rebuilding a clean virtual memory allocation restores normal commit limits:

Press Win + R, type sysdm.cpl, and navigate to the Advanced tab.
Under Performance, click Settings, then switch to the Advanced tab.
Under Virtual memory, click Change.
Uncheck "Automatically manage paging file size for all drives".
Select Custom size: configure the Initial size to 1.5x your physical RAM capacity (e.g., 24576MB for 16GB RAM) and the Maximum size to 3x physical RAM.
Click Set, apply the changes, and reboot your PC.

System Verification and Performance Monitoring

Following a reboot, launch Task Manager and confirm that idle memory consumption stabilizes between 15% and 25% (on 16GB/32GB configurations) with Non-paged pool allocations safely below 450MB. Disk activity should immediately drop to 0% during idle operation, restoring peak responsive computing speed.

Originally published on Tech Boss (How to Fix 100% Memory & Disk Leak in Windows 11 (24H2): Complete Step-by-Step Diagnostic Guide) — Explore interactive performance diagnostics, real-time benchmarks, and technical engineering advisories at imtechboss.com.

DEV Community