100% Disk Usage on a Gaming PC: Fix the Stutter

Task Manager says Disk 100%. The game still loads, but the first thirty seconds of every match are a slideshow, textures pop in late, and alt-tabbing out takes four seconds. Nothing crashes, so it is easy to blame the game, the GPU driver, or the fact that the machine is three years old.

100% disk active time is a measurement, not a diagnosis. A healthy NVMe drive pinned at 100% while it moves 3 GB/s is doing its job. The same figure on a drive moving 2 MB/s with requests queued up is a saturated device that cannot keep up - and that is the condition that produces stutter in games. The job is to tell those two apart, then find what is queueing the requests.

Step 1: Confirm the Disk Is Actually Saturated

Task Manager's Performance tab shows one number that matters more than the percentage: response time at the bottom of the disk panel. Open Task Manager with Ctrl + Shift + Esc, go to Performance > Disk, and play for two minutes.

• Active time near 100% with response time above 100 ms - the drive is the bottleneck. Keep reading.
• Active time 100% with response time in the single digits - the drive is working normally. Your stutter is elsewhere: check GPU and CPU frame times instead.
• Active time spikes to 100% only at load screens - normal streaming behaviour, not a fault. See the load-time comparison in SSD versus HDD load behaviour.

For real detail, open Resource Monitor: press Win + R, type resmon, and select the Disk tab. Sort by Total (B/sec) to see which process is doing the writing, and watch Queue Length in the bottom panel. A queue that sits above 2 for more than a few seconds means requests are arriving faster than the device completes them.

Step 2: Know What Your Drive Should Be Doing

These are the rough ceilings that make the numbers interpretable. If your drive is at 100% active time and nowhere near its class's throughput, something is issuing tiny random requests rather than large sequential ones - which is what a failing drive, a thrashing page file, or a badly behaved background service all look like.

Games are random-read heavy and increasingly demand NVMe-class random throughput, because they stream assets while you play rather than loading a level once. A game installed on a 7200 rpm drive will show 100% disk usage constantly and still stutter, no matter what you disable in Windows.

Step 3: Identify the Process, Not the Symptom

In Task Manager's Processes tab, click the Disk column header to sort descending. The process at the top while the stutter happens is your answer. In practice it is nearly always one of these five, in this order of frequency:

1. Windows Update or Delivery Optimization downloading a cumulative update in the background.
2. Antimalware Service Executable scanning a freshly downloaded or updated game.
3. Steam, EpicGamesLauncher, or Battle.net verifying files or downloading a patch you did not ask for.
4. System - which usually means the page file is thrashing because RAM is short.
5. SearchIndexer or SysMain re-indexing after a large install.

Fix 1: Stop the Update Storm During Play

Pause updates rather than disabling the service: Settings > Windows Update, then Pause updates for one week. This is reversible, unlike the service tweaks floating around forums that leave the machine unable to patch afterwards.

Then cap background delivery: Settings > Windows Update > Advanced options > Delivery Optimization > Advanced options. Set the download percentage limit and the upload limit, and switch on Limit how much bandwidth is used for downloading updates in the background. Uploading update fragments to other PCs is the setting most people never notice, and it keeps the disk busy long after the download finished.

On a metered or slow connection, also set the active hours so Windows does not decide to install during your evening session: Settings > Windows Update > Advanced options > Active hours.

Fix 2: Exclude the Game Library from Real-Time Scanning

Every file a game reads while streaming assets is a candidate for a real-time antivirus check. On a large library this shows up as sustained disk activity with nothing obviously running.

1. Open Windows Security from the Start menu.
2. Go to Virus & threat protection > Manage settings.
3. Scroll to Exclusions and choose Add or remove exclusions > Add an exclusion > Folder.
4. Select the folder that holds your games - for example the Steam library folder, typically C:Program Files (x86)Steamsteamappscommon.

Only exclude folders you created yourself and know the contents of. Excluding an entire drive is a common shortcut that quietly removes protection from your downloads folder as well.

Fix 3: Check Drive Health and Temperature

A drive that is dying often presents as 100% usage at low throughput, because it is retrying failed reads. Before you tune anything, rule that out.

• Open PowerShell as administrator and run Get-PhysicalDisk | Get-StorageReliabilityCounter | Format-List. Look at Temperature, Wear, ReadErrorsUncorrected and WriteErrorsUncorrected. Any non-zero uncorrected error count is a replacement signal, not a tuning problem.
• Run Get-PhysicalDisk on its own to see HealthStatus. "Warning" means the drive has flagged something itself.
• For NVMe, check the vendor utility or a SMART reader for Available Spare and Percentage Used. Spare dropping below 100% means blocks are already being retired.

Temperature matters more than people expect. NVMe drives throttle hard around 70 to 80 degrees Celsius, and a drive mounted under a graphics card in a case with poor airflow will hit that during long sessions. The symptom is throughput collapsing after twenty minutes of play while active time stays at 100%. A heatsink or a slot further from the GPU fixes it.

Fix 4: Rule Out Page File Thrashing

When physical RAM runs out, Windows writes pages to disk. If the process at the top of the Task Manager list is System rather than a named application, this is usually what you are looking at.

Check it in Resource Monitor's Memory tab: compare Commit Charge with Physical Memory. If commit is consistently well above installed RAM - say 20 GB committed on a 16 GB machine - the page file is doing real work and the disk will stay busy.

Two fixes, in order of effectiveness: close the browser while playing (a few dozen tabs is easily 4 GB), or add RAM. Increasing the page file only moves the problem around; it does not make a slow drive faster. Leave the page file on System managed unless you have a specific reason, and keep it on the fastest drive in the machine: System Properties > Advanced > Performance Settings > Advanced > Virtual memory.

Fix 5: Deal With Indexing and SysMain

SearchIndexer rebuilding after a big install or a Windows feature update can run for hours. Let it finish rather than killing it, because it restarts from the beginning. If it is stuck, rebuild deliberately: Settings > Privacy & security > Searching Windows > Advanced indexing options > Advanced > Rebuild. Narrowing the indexed locations to a couple of folders cuts the work substantially.

SysMain (formerly Superfetch) prefetches frequently used programs into RAM. On a hard drive it is a net win. On an SSD its benefit is small and it occasionally produces background read bursts. Test, do not guess: open services.msc, stop SysMain, play for twenty minutes, then decide. If there is no difference, leave it running - Microsoft's defaults are reasonable on modern hardware.

What Not to Do

The registry tweaks that circulate for this exact problem - disabling prefetch, clearing the Superfetch folder, turning off every service with "Windows" in the name - trade a small short-term reduction in background activity for slower application launches and an unpatched system. Defragmenting an SSD is worse: it adds writes without any read benefit and consumes the drive's endurance for nothing. Windows already runs TRIM on a schedule; leave it alone.

Third-party "game booster" utilities mostly duplicate what is above, and several install background services of their own, which is the opposite of the goal.

The Twenty-Minute Diagnostic Order

1. Play for two minutes with Task Manager open. Note disk active time and response time.
2. If response time is under 20 ms, stop - the disk is not your problem.
3. Sort the Processes tab by Disk and identify the top process by name.
4. Match it to Fix 1 to Fix 5 above and apply that one fix.
5. Re-test. If the top process changed, apply the next fix rather than stacking all of them.
6. Check drive health once per session - if error counters are non-zero, stop tuning and replace the drive.

Most machines are fixed by the first two steps, because most 100% disk reports are a background update or an antivirus scan competing with a game. The cases that resist are almost always either a hard drive being asked to stream a modern game, or RAM that is genuinely too small for what is running. Both have hardware answers, and no amount of Windows tuning substitutes for them.

If the stutter survives all of this and the disk is idle, the bottleneck has moved - see shader compilation stutter and the general Windows 11 stutter checklist for the next layer.

By the SavePoint editorial team · How we check our guides