Windows 10: [help] Disk keeps jumping to 100%

So for the past couple of months, my PC has been having a problem where on startup and even afterward the disk %(viewing through task manager) would spike at 100% and either stay like that for a few minutes or eventually drop to zero, only to do it again later. I'm not sure where I'm going wrong here as I've tried numerous solutions, from disabling skype entirely, to setting the ACHI from "1 to 0" to even disabling Sysmain(formerly known as superfetch). Currently, after I disabled sysmain, it kept jumping back to 100%. Right now, I haven't seen many spikes but now all my applications take slightly longer to open and say (Not responding) before opening. This bug has been plaguing my computer for months now and it's especially annoying when it takes a few minutes to open google chrome, or randomly spikes when I'm doing something important(slowing my PC to a crawl) I can hear the PC become audible when it does this too. What I'm hoping for is that someone is experiencing similar problems and they've found a long term solution. I plan on getting an SSD someday but I currently can't get one.

[Note] I am running windows10, and I have a 1 TB hard drive.

submitted by /u/functionpumpkin
[link] [comments]

:)

 

My disk use keeps jumping back to 100% despite doing all suggested service modifications and registry edits.

<Original title: Disk use in windows 10>

My disk use keeps jumping back to 100% despite doing all suggested service modifications and registry edits.

 

Clean install, disk usage at 100%

I've seen that article. and I am in fact not running that driver. I followed the steps and it does not appear in the list.

 

high/100% disk usage

I have two possibilities, both of which happened to me:

• I had a hard drive that was failing. The tip was that the performance graph showed that the disk utilization would jump to 100% and stay there for a second, then fall back.
• Something about Chrome was causing 100% disk utilization. I don't remember how I tumbled to that, but when I uninstalled Chrome the problem went away instantly. This seems unlikely, but it's worth a shot.