Windows 10: Very high disk usage not attributed to any task in Task Manager

I have a machine whose disk is nearly always running at 99-100% usage (according to Task Manager) even though no individual tasks appear to be responsible. For instance there might be three tasks running at 0.1MB/s and the rest at 0MB/s, but the disk (a 7200GB 3.5 inch one) is still at its limit and the responsiveness of my desktop is still very poor. Does anyone have an explanation for this and (hopefully) a solution?

:)

 

pc performance suffered after storing it for 2 weeks

Hi Jerpai,

Is the PC connected to the internet? When you go into task manager > performance are the disk usage and network or wifi usage very high?

Can you post a picture of task manager (can use snipping tool click on start and write snipp and launch tool to make picture of the task manager)

Let me know,

David

 

Fan Runs Constantly on Sony Vaio Laptop After Upgrade to Windows 10

Hi,

If the fan is running continously,then I owuld suggest you to check the Task manager to see if any service/process is consuming more resources. Right-click on the start button and then select task manager. See if any CPU usage, Memory usage or Disk usage
is high. If yes, then check under that coulmn for process that is consuming more resources. If it is any third party application or not a system criticalprocess, right click and select 'End process' to check if that makes any changes.

 

Hi, try Process Explorer (free) - easy to find- which gives a more comprehensive view.

Also make sure the actual data transfer rate is appropriate. Some hardware issues can give rise to very low transfer rates which may cause this sort of problem.

You can test the disk if, for example, you boot from a bootable medium rather than Windows in your case as you have this problem presently, such as Kyhi's bootable DVD/flash drive available from the top of the Software and Apps section here.

Also try using the Resource Monitor (link at the bottom of the task manager/performance tab)

 

Thanks for the sensible suggestions. The problem seems to have quietened down now of its own accord, so I guess the cause will remain a mystery until the next time it happens.