I am running Windows 10 Home Edition on a Gigabyte Aorus motherboard. I have a Western Digital Blue 4TB spinning hard drive (connected with SATA) which seems to be functioning incorrectly.
In my task manager performance tab, I can see that the disk latency will suddenly jump from its usual 0-20ms to 3000ms or even 10000ms. The active time will freeze at 100% and everything on the computer becomes unbearably slow for about 1-2 minutes. I/O operations of even 50KB take about 30-45 seconds and some programs will stop responding or become very slow. After the 1-2 minute state of extreme slowness, the disk seems to return to its normal operation and the system functions normally. The laggy period begins again after 2-3 minutes of normal operation.
Images:
This is the disk entering its laggy state.
This is the disk leaving its laggy state.
I have opened resource manager and nothing seems out of the ordinary. I even watched the resource monitor while the disk enters its laggy state and noticed that there is very little change. No single process or application seems to be 'hogging' the disk or performing an excessive amount of operations.
Images:
Disk usage monitor while disk is in normal state
Disk usage monitor just after disk has entered laggy state
I have tried:
- rebooting (at least 10 times)
- performing a clean install/update of all motherboard SATA controller drivers
- checking disk health (WD disk health and windows chkdsk both say the disk is healthy and functioning properly)
- ensuring that physical hardware cable connections are tight and free of dust/debris
- making sure WD disk drivers are correct and up to date
- disabling Windows Superfetch, defender, antivirus, and Google Chrome caching
This disk issue does not seem to occur when I boot in safe mode, leading to the conclusion that something is malfunctioning on the system, not the disk.
If this question seems like a duplicate of the threads:
please note that I have tried all of the suggestions in these threads as well as numerous other threads from other forums and none have seemed to mitigate the problem. I would appreciate suggestions and possible solutions that have not already been discussed in these threads.