Windows won't boot when a WD Green 1tb HDD is plugged in

[kaoruslp]

I have a Western Digital Green 1tb HDD (WD10EADS) which I had windows 7 installed. It automatically upgraded to Windows 10 last night and it was fine. I was able to boot into windows. Then I decided to do a clean install of W10. I installed using a USB, installation was fine, and then when it restarted after installation, it gets stuck on a black screen with a blue windows logo with spinning dots beneath it.

So I tried another HDD, a 250gb Seagate HDD and it worked. I installed W10 fine and was able to boot into it. So I plugged the WD Green HDD back in to use as a secondary drive. Once I plugged it in, and start up the system, it gets stuck at the same black screen with spinning dots.

So I tried installing on the Seagate HDD while the WD HDD was plugged in. It installs, and then gets stuck at the black screen again. Once I unplugged the WD HDD, it boots in fine while the Seagate is still the primary drive.

So I come to the conclusion that there's some kind of issue with the WD HDD, but it worked fine when it upgraded from W7 to W10 but not a clean install... Also I plugged the WD HDD into my other PC which was already running W10 and my other PC was fine. So now I am conflicted... What exactly is going on...


Edit:
I have a Antec 430W power supply, I had my suspicion on the PSU but it doesn't make sense. It didn't boot when I had only the WD plugged in. It did boot when I had the Seagate plugged in. It doesn't boot when I have both of them plugged in.

 

[Colif]

its because both drives are win 10 installs. The UEFI boot method used by win 10 doesn't look at the boot order normally to decide what to boot from, it looks for a file name.. and both drives have that file name on them so it then may rely on the boot order in bios. I am not sure, it may choose a new drive each time. Its why having win 10 on two drives in one pc is troublesome.

Primary/secondary means nothing on SATA, there is no number 1 port as such. IT all depends on the boot method. Win 7 uses the boot order to decide, Win 8 & 10 look for a file name in a hidden part of hdd.

Which do you want to use as main drive? take that one out and boot from USB, if you can. Run the installer until step 13 here: http://www.tenforums.com/tutorials/1950-windows-10-clean-install.html
delete all the partitions and then exit out of installer. this will leave drive blank
put boot drive back in.

is the other pc an upgrade from win 7? if so, it uses old boot method and won't boot from the WD install as its not first in boot order.

 

[kaoruslp]

@Colif

Sorry if I didn't mention this, but I never have two instances of Windows 10 installed on both drives. For example, if I have windows 10 on the Seagate HDD, I have deleted everything on the WD HDD during installation (when you get to choose which drive to install Windows 10 to). And even then, when I just have the WD HDD installed, and not the Seagate one, it will not boot.

And my other PC has a clean install of W10.

 

[Colif]

ok, put WD in other pc and run this on it: http://support.wdc.com/downloads.aspx?lang=en
its a Western Digital program designed to test hdd.

there is a seagate tool as well but that drive isn't being a pain.

 

[D_Know_WD]

Hi there kaoruslp,

Sorry that you are facing some issues with your WD drive.

Is the OS drive the only one attached to the system during OS installation? (no matter which drive you used)

My suggestion would be to boot up Ubuntu, reformat your WD drive and see if the issue persists. Here's a thread on Ubuntu Live CD: http://www.tomshardware.co.uk/forum/267999-32-recover-data-mode
In case the issue persists, you can attach it to another system and try to test it with the WD's DLG tool as Colif already suggested.

Let us know how this goes,
D_Know_WD