Hard drive "crashing"

7007hp4573

Distinguished
Jan 10, 2012
7
0
18,510
I bought a SAMSUNG HN-M101MBB 1tb hard drive a few months ago to use in my acer aspire 5535 laptop. At random times the drive will stop working and everything freezes like the drive has been removed. If i leave the laptop like that for a few minutes it reboots and says "Operating system not found". I have tried formatting the drive but that didn't work. I checked it for errors and found nothing. Is there something i can do about this without replacing the drive?
 
Check your SATA cables. I have had in the past instances of SATA cables with loose connections doing the same thing. SATA cables don't cost much, try replacing the one on the drive with another if you have one, or buy a new better quality cable.
 
Does the BIOS detect the drive every time you boot it up?

I would try to boot the OS disc and get into the recovery console and running a "fixboot" and then "fixmbr" and see if this fixes your problem
 
Everything works fine until it freezes. There are no errors on the drive and the BIOS detects it. It just happens randomly while using it.
 
So you noticed the problem started after you replaced the hard drive and thats why you suspect the drive as the culprit?
After the computer freezes up it gets you the operating system not found message? And then does it eventually correct itself or are you spending 90% of your life reinstalling windows over and over! lol

There could be a problem with the logic board and not the platters themselves which could cause communication problems. May i recommend running DFT or another HDD test to check for bad blocks or other eminent failures?
 
The computer freezes up then i usually hold the power button to reboot. If i don't reboot it i get a BSOD then it reboots but the hard drive doesn't work until i turn the laptop off and back on again. I have tried seatools for dos but the drive crashed about 2 minutes into the test and stopped windows booting so i had to use startup repair. Rebooting always solves the problem for a while then it happens again. I think tests that take a long time will just cause damage like the last one did.