PC won't boot after adding drive

chobe

Distinguished
Jul 31, 2010
25
0
18,540
Just successfully installed new Samsung EVO 960 M.2 on Gigabyte Z270N - works fine, boots, etc. When I readd original harddrive with Win 10 OS, system will no longer boot - cannot get into bios/uefi to reselect M.2 as boot drive. I can hear a slight clicking sound (remnant of DOS error/beep codes?) and system just hangs.

Wanted to avoid clearing BIOS until I heard back from community....please help!
 
Solution
OK, think I got it....Don't know if it was the MBR on the drive or just that Windows didn't like two drives with OS and boot record. Anyway, problem was solved by using Diskpart to clean, create new primary partition, and format drive. Again thanks for the suggestion but I think we can mark this issue closed!
UNHOOK all your drives other than the M.2 SSD to see if you can still get into the BIOS and/or bootup.

It's odd that your HDD would cause a problem at the same time as you installed the M.2 SSD though, so I wonder if the M.2 SSD failed and it's creating issues with starting up.
 

chobe

Distinguished
Jul 31, 2010
25
0
18,540
Thanks for your help Photonboy; I removed the harddrive and rebooted. It still would not boot so I cleared the bios (removed cell battery). Rebooted again and system loaded off of M.2 and booted fine.

Next, I reinstalled harddrive cleared bios again as preemptive move. On reboot I selected boot option and was given choice of using Windows Boot Manger with harddrive, or the Samsung EVO. I selected the EVO. On reboot I'm prompted to insert OS media and cannot get passed that point as I'm reluctant to reinstall Windows again when it's obviously already installed.

Any more thoughts?
 

chobe

Distinguished
Jul 31, 2010
25
0
18,540


 

chobe

Distinguished
Jul 31, 2010
25
0
18,540
OK, think I got it....Don't know if it was the MBR on the drive or just that Windows didn't like two drives with OS and boot record. Anyway, problem was solved by using Diskpart to clean, create new primary partition, and format drive. Again thanks for the suggestion but I think we can mark this issue closed!
 
Solution