New
#1
C Drive 100% Usage Hang
I posted this issue in a couple of other threads and thought it was fixed. I'll start a new one to focus in on the issue. At various times the C drive (HDD SATA) usage will go to 100% and stay there for many minutes. Eventually it will come back down to normal, but if you had tried any mouse clicks while it was pegged, it can take up to 15 min. to settle and execute things. I ran CCleaner to clear out any left over files from browsers, the system, and Windows apps. I then set up CHKDSK to run on restart. CHKDSK found no issues. Then I ran SFC /SCANNOW which came back with no integrity violations. DISM SCANHEALTH showed no store corruptions and DISM RESTOREHEALTH competed successfully. CHRYSTALDISKINFO showed only the one reallocated sector for the drive. The driver for this HDD is shown to be current and Windows troubleshooting shows the drive is operating properly. Looking at Task Manager, it appears there are three things that will make the drive show 100%.
1. FireFox v. 110.0.1 and its 13 processes can send the drive to 100%, but sometimes releases it.
2. Norton360 can also send the drive to 100%, but drops off quickly if a process accesses the drive.
3.NTOSKML.EXE will send the drive to 100% every time and once there, the usage stays at 100% even if the process isn't using any resources.
The only other issue I see with this drive is boot up will state the drive may not be available, to press the space bar to continue with the boot up, which completes normally. It also states to check with the drive maker, who has nothing posted about this particular drive model. The system runs just fine when the drive isn't consumed, but hangs when it is. I'm at a loss as to a fix, but if this continues, I'll likely replace the system, since it's 14 years old. Just not in the mood for migration to a new one. Thanks is advance for listening. I wonder what other diagnostic tools I could use to identify the culprit.
- - - Updated - - -
After four hours:
I restarted the system and launched Chrome along with Task Manager to watch the system. NTOSKML.EXE will send the drive to 100% and the disk response times will go over 100,000 ms. If Chrome was accessed during this time, it would rise to the top of the process list, but the disk stayed at 100% and Chrome and TM both went to "not responding" for many minutes. Eventually, Chrome responded and things settled down to normal. I didn't launch FireFox during this period. Lacking any other guidance, I will restore a MR system image from before the last CUM update and see what happens.
Last edited by jamis; 08 Mar 2023 at 18:12. Reason: added text