External drive 100% usage and beeping during specific tasks

roche28

Reputable
Apr 13, 2017
9
0
4,520
Hello, a while ago I had some issues with my PC, SSD stuck on 100% usage with 0 transfer rate, PC freezing, which were caused by faulty ram and a failing hard drive. That was solved, and I purchased a Maxtor M3 1TB external drive to replace the failing drive. Immediately I had issues with it, after a few days HD sentinel showed health to be 0% and the drive wouldn't even get detected when plugged in. So i returned it under warranty, and got a replacement one in a week. It was the same brand.
It worked fine for about half a year, but all that time it would beep during some specific tasks, like watching a video on Chrome, but not in Firefox, and I soon found out the beeping would occur when the drive would reach 100% usage. Most of the time it was with 0 transfer rate also. I didn't pay much attention to it, until HD sentinel showed 88% health a few days ago and 60% today, with some bad sectors on the disk. So now I'm wondering is it the high usage that is damaging the disk and if anyone has any ideas how to stop it. High usage occurs when watching videos in Chrome (even though it is on my SSD), during computation in AVL Fire (also the drive becomes unusable during that time, even though it is also on SSD and doesn't have anything to do with the external drive).
I've tried all the usual solutions, like stopping certain cervices, but no luck. Also I'm using Win 7. IF anyone has any ideas, I'd be grateful.
 
Solution
Well, it seems ram was again to blame, but this time both modules were fine. It seems one of them was out of place, and after removing and reinstalling them, everything is working fine. So if anyone is having similar issues, you might want to check every individual ram piece.

roche28

Reputable
Apr 13, 2017
9
0
4,520
Well, it seems ram was again to blame, but this time both modules were fine. It seems one of them was out of place, and after removing and reinstalling them, everything is working fine. So if anyone is having similar issues, you might want to check every individual ram piece.
 
Solution