My Windows 11 Pro system becomes almost unusable whenever I download or extract large files. The SSD reaches 100% active time, response times exceed 1000 ms, and transfer speed drops to 0 MB/s. The System process often appears responsible. Usage briefly falls to 1% before spiking back to 100% repeatedly.
The problem happens consistently with large downloads or installations, such as Counter-Strike 2, and sometimes eventually clears up—but always returns. The SSD works normally when I boot Linux Mint from a USB drive, and it also behaves normally in Windows Safe Mode. CrystalDiskInfo reports the drive as healthy. I have tried pagefile changes, disabling services, registry tweaks, SATA driver updates, and repartitioning from Linux, but none solved it permanently.
I cannot wipe or format the C: drive because I need to preserve my files. The system uses an Intel Core i5-9400F, GTX 1060 6GB, 16GB RAM, a 512GB KingSpec P3 SSD, and Windows 11 Pro. What should I check next to identify and fix this issue?
3 Answers
A healthy result in CrystalDiskInfo does not completely rule out an SSD problem, particularly with a budget drive. Check the drive’s firmware, the Windows Event Viewer storage errors, and the SMART attributes rather than relying only on the overall health percentage. Make a backup before changing BIOS or partition settings, and consider testing with another SSD if the issue continues.
Since it works in Safe Mode and under Linux, the drive may not be failing mechanically; a Windows service, filter driver, indexing component, or storage utility could be causing the stalls. Indexing can sometimes produce this behavior, especially while large files are being created, so check whether Windows Search or another background scanner is active. A clean boot can help identify which service or driver is responsible.
Leaving the computer running overnight may allow some background work to finish, but it will not fix a recurring problem if the system stays stuck at 0 MB/s. Because the issue returns during every large download or extraction, I would focus on identifying the Windows driver or service involved instead of repeatedly repartitioning the disk.
I already left it running for an entire day without improvement, so it seems to be a persistent trigger rather than a task that simply needs more time.