Windows 10: Not BSOD but constant freezing with drive spiking at 100% usage

Background:
For the past few weeks or so I was on W8.1 on my SSD and Arch Linux on my SSHD. However now when loading up Arch I get a { DRDY } error presumably on the SSHD, and W8.1 crashed very soon after logging in. I noticed that sometimes that the computer does not freeze until I open up a game (Total War 2). TW2 had been working fine previously. I would go ahead and reset/refresh my main W10 drive but I'm not sure if that's the issue. I have never gotten a BSOD just a freeze then sometimes black screen with a mouse.

What I've tried:

• I consistently virus scanned with Malwarebyte's and Defender to find nothing.
• I hoped upgrading to W10 would fix the issue, but it did not.
• /sfc scannow
• SMART check (no issues)
• check Task Manager/used Proc Explorer (or variants) can not see cause of disk usage spike

What I believe could be the issue:

• I want to say the drives are failing, but I'm honestly dumbfounded.
• I've read it's possible to the SATA cables.

Any ideas?

EDIT: Tried creating another user account, and so far no issues with the new account. Also added some logs, if more are needed I can add them.

EDIT 2: TW2 crashed it again

:)

 

why is win 10 spiking my disc usage to 100%

I am having the same issue. My hard drive goes to 100% and completely freezes the computer. I tried the steps above and they did not fix the problem. I notice that the disc usage spikes to 100% whenever I open File Explorer. What can I do to fix this
problem?

 

Changed SSD and HDD and still having high disk usage

Hi thanks for your reply ,

No Chrome and Norton aren't causing the high disk usage all the time . Actually , there is nothing causing it to go to 100% for 24h . The disk usage spikes up with a variety of applications that go on the top of the usage lisk in the task manager . It is
really weird , the PC got wiped clean 5 times !! The 6th was when I replaced the HHD !! It is driving me crazy

 

Partounian, welcome to the forums. It is difficult to say without the proper documentation. It could be your hard drive, or several other things.

Please upload the BSOD Posting instructions Screenshots and Files - Upload and Post in Ten Forums - Windows 10 Forums.

 

Added the zip and some more helpful info.

 

Partounian, first you have no dump files. Please configure your system for Small Minidumps. https://www.tenforums.com/tutorials/5...dows-10-a.html Make sure you have a folder in C:/Windows/ named Minidump.

You have had quite a few errors relating to Office 2016 and Skydrive sync. I would try to uninstall and reinstall Microsoft Office 2016.
If you would like to check your hard drives, please run Seatools for DOS http://www.sevenforums.com/tutorials...s-how-use.html Please run the Short and the Long test. Also run Check Disk http://www.sevenforums.com/tutorials...isk-check.html . Let me know the results of those tests.

 

I don't believe there'd be a dump as there is no actual BSOD. (I did however set to minidump) Just freezing/crashing. All test results reported fine. I also don't have Office installed whatsoever.

 

Ok, it's been a while but I had a clean install on my main drive, but shortly after the crashes started again. I removed my secondary hard drive from having a drive letter and it does not crash anymore. Any reason to why this is happening? Or how can I fix it?

 

First, congratulations for solving your problem. The honest answer to your question is I am not sure. However, I believe there must be an issue with the drive. By removing the drive letter, it means Windows can not 'see' the drive and therefore cannot use it. For some reason, it appears, if Windows tries to read/write to it is when the BSOD occurs. That is the only explanation I can offer at the moment. I would assume the drive is bad or there is something on the drive that causes the BSOD.

I am assuming that you ran the hard drive diagnostic test and the drive passed, correct?

 

Thank you. I was honestly surprised to see that it fixed the issue. Yup, the tests all showed up with no issues. I've also always had Malwarebyte's and Defender on my computer which haven't really spotted anything.

 

It doesn't have to be malware. It could be an incompatible program or a bad driver on the second drive causing it. But, congratulations for figuring it out. Well done.