Was my WD Blue Hard Drive DOA? won't run on new computer, freezes old computer as well

JohnTHDW

Distinguished
Oct 16, 2013
96
0
18,630
Hello everyone,

I've built a new system with a WD Blue 1 TB Desktop Hard Drive, after I built the system and first power up I started installing Windows 7 I noticed something wrong from the beginning, everything was slow, on the Windows installation " copying files" was stuck at 0% for a long time so I turned off the computer and proceeded to reinstall again, after that on the partition selection I got "Error 0x80070057 failed to format partition" and I couldn't reformat and install. Turned off, turn on again, then it was stuck at " setup is starting", then I turned it off again. Then went to bed.

Then today I proceeded to do everything again and instead I got this message:

"BOOTMGR is missing press ctrl+alt+delete to restart

I proceeded to reinstall windows again and still stuck, I changed sata cable, same problem. So then I decided to take the hard drive and add it to my old computer to see if I could re-format it, attached sata cable, power, then turn on computer and now this old computer is stuck at the windows logo after boot!!! then after I disconnected the Hard drive everything worked again, so I'm sure there's something wrong with the hard drive that's locking something, how can I diagnose it if I can't access it??

Any suggestions? maybe the HDD was DOA since I got it?

Thanks for all your help and suggestions.

 

JohnTHDW

Distinguished
Oct 16, 2013
96
0
18,630



The new computer never installed the OS, just initiated the process.

How can I delete partitions if I can't access the Hard drive?
 

JohnTHDW

Distinguished
Oct 16, 2013
96
0
18,630


I'm not confusing you, that's the message I got and I'm 100% sure Windows 7 never installed. I should have mentioned that I got that message after turning the computer without the Windows 7 disc in the DVD drive.
 

JohnTHDW

Distinguished
Oct 16, 2013
96
0
18,630



I'll try the second solution but I have the feeling the drive is faulty... I wish I could access it and try dban as last resort...
 

JohnTHDW

Distinguished
Oct 16, 2013
96
0
18,630
I was able to finally create the boot usb stick with data lifeguard tools in it,.



I did a quick scan on the drive and I got read element failure error 007.



Then I did a full media scan and after almost 2 hours I got :



Too many errors found, please contact technical support, error/status code 0225



Then I proceeded to do a quick zero writting, after this process I got no errors 0000, then I thought the drive was fixed and proceeded to do the quick scan again to check it but now this time won't finish, it's stuck and even ALT X won't kill the program, I runned it twice with no luck. This means the drive now is completely dead? what are my options now?




 

Akashdeep

Distinguished
Feb 9, 2011
938
0
19,160




As he says, its his new build, he should have the warranty (even RMA too) for sure.

Replace it.

(I don't know how people got such problems. In my life I have worked with more than 500 PC, but experienced only 1 Monitor damage(later fixed) and 1 Samsung HDD permanent damage.)
 

JohnTHDW

Distinguished
Oct 16, 2013
96
0
18,630
Today I decided to try the drive in my new PC and ran the boot usb with diagnostic tools and I got this message:

NO DRIVE FOUND - ERROR/STATUS CODE: 0120

But I still can see it in the BIOS.

Now it's getting worse because when I first built the PC the drive was detected and attempted to install windows before blocking completelty, now I guess is gone...
 

Akashdeep

Distinguished
Feb 9, 2011
938
0
19,160


Yesterday or few days before your HDD was fine. That doesn't mean it has to be fine today too.

I don't see any point fixing the thing which can be replaced as the warranty avails.
 
D

Deleted member 217926

Guest
Keep it civil guys. No need to beg for a best answer and no need to call out someone who does. It's not against any rules but it is bad forum etiquette.
 

Akashdeep

Distinguished
Feb 9, 2011
938
0
19,160


Thats I said.

I think the thread should be closed now, as none worked as the "Best Answer" to be selected practically.