SSDs wear out by writing, and in November 2026 two graphics-driver bugs showed how easily a background process can write far more than it should. Nvidia's 621.35 hotfix driver fixed a problem where writes to a file called nvlog.nvlgstg could happen continuously in the background, and Neowin reports that a similar bug affected AMD's Radeon drivers earlier in the month before AMD released a fix. If your drive light never stops flickering, or your SSD's total writes are climbing faster than you'd expect, here's how to find the culprit with tools that come with Windows or from Microsoft. This guide is based on Microsoft's tools and documentation.
Step 1: Get a quick answer in Task Manager
Press Ctrl + Shift + Esc to open Task Manager.
On the Processes page, select the Disk column header to sort by disk activity.
Watch for a minute. A process that sits at the top with steady activity while you're doing nothing is worth investigating.
Task Manager shows combined reads and writes, and it won't tell you which file is involved. For that, move on to Resource Monitor.
Step 2: See writes per process and per file in Resource Monitor
Resource Monitor is built into Windows and is the quickest way to separate writes from reads.
Press Windows + R, type resmon and press Enter.
Open the Disk tab.
In Processes with Disk Activity, select the Write (B/sec) column header to sort by writes.
Tick the box next to a suspicious process. The Disk Activity pane below then shows only that process, with the full path of each file it's reading or writing.
The file path is often the giveaway. A log file in a driver folder, a cache folder for a launcher or a browser profile tells you where the writes are going. In the Nvidia case, the file reported was nvlog.nvlgstg.
Step 3: Record everything with Process Monitor
If the writes come in bursts, or you want proof over a longer period, use Process Monitor, Microsoft's free Sysinternals tool. Microsoft describes it as an advanced monitoring tool that shows real-time file system, registry and process/thread activity, with filtering and logging to a file. Microsoft lists version 4.13, published on 5 November 2026.
Download Process Monitor from Microsoft Learn (linked below), extract it and run it (Procmon64.exe on a 64-bit PC). Windows will ask for administrator permission.
Open Filter > Filter... and add a rule: Operation is WriteFile, then Include. Select Add and OK.
Let it capture for a minute or two, then stop the capture with Ctrl + E.
Open Tools > File Summary to see which files received the most writes, then double-click an entry to see the matching events.
Process Monitor captures a lot of data very quickly and uses memory as it goes, so don't leave it running for hours. Capture for a short time, stop, then look.
Step 4: Use Process Explorer for running totals
Our Process Explorer guide covers Microsoft's other Sysinternals tool. You can add I/O write columns in View > Select Columns to see how much each process has written since it started, which is useful for spotting a slow but constant writer.
Step 5: Fix it
What you do depends on what you find:
A graphics driver. Update to the fixed version. See our reports on the Nvidia 621.35 hotfix and the AMD Radeon driver fix.
A game launcher, browser or sync tool. Check its settings for cache, logging or sync options, update it, or move its cache to another drive.
Windows Search indexing or an antivirus scan. These can be busy for a while after big changes, such as a Windows update, and should settle down.
Something you don't recognise. Search for the exact process and file name before deleting anything, and run a malware scan.
Step 6: Check your SSD's health
Once you've fixed the cause, check how much has been written to the drive and its health status. Our guide to checking SSD health explains how to read total host writes and compare them with your drive's rated endurance (TBW).
Our verdict
Start with Task Manager's Disk column, then use Resource Monitor's Disk tab sorted by Write (B/sec) to see the process and the exact file it's writing. For intermittent writes, or to prove it over time, capture a short Process Monitor log filtered to WriteFile and use File Summary. Fix the cause, which is often a driver or app update, then check your SSD's health so you know how much endurance you have left.