Did my SSD corrupt my MOBO Boot Sector?

[dankcik09]

Just put a new Crucial SSD in my SATA3 connector and now it seems my computer wont boot to windows anymore. My Samsung EVO 850 SSD that runs my OS is still being detected, but when I go to select that drive to boot off of, it comes up with a bios message "Reboot and Select proper Boot device." Which when I hit F11 to go to boot priority it goes back to this exact same screen.

When I installed the new SSD I simply removed the power and sata cable and placed them into the new SSD. I took out the old HDD which was having problems, blue screening. I did not move any of the cables from the other drives.

Could it have fried my boot sector on my mobo? Because in Bios it still shows my Samsung Evo SSD as detected, but it can't find an OS. And I highly doubt it deleted the OS off the drive. But this is an issue I've never had before so I have very little to go off of.

Going to see if its just the drive by installing my OS on the new Crucial SSD and see if it takes, then I can rule out that its my boot sector and that the issue is my Samsung Evo SSD. However I'm sceptical because nothing was changed prior to the new install and everything went to crap once i started up the computer with the new SSD.

 

[dankcik09]

 

[dankcik09]

Going to follow this advice.

"
MI
MichaelChubbychu replied on
Like many, I ran into this problem as well after getting a 2nd HD, and used the "unplug/repair" method outlined in the comments. One issue I ran into was that the HD that WIN7 was on was not being detected and therefore unable to have the issue fixed.

Turns out, in the disk management utility you can right click and "mark drive as active". after you do that, it'll then detect your drive and you can go on your way.

Thanks guys!"

 

[dankcik09]

F I X E D

 

[indsup]

It doesn't seem like your following what everyone is saying. Your os is on your old drive not the ssd. When you put in the repair disk it will always show what ever drive in the machine as C. That does not mean that it has the os on it. You need to go with what i said earlier and clone from the old drive to the ssd. The only other way that you can fix this is remove other drives and do a complete os install on the ssd. Reinstall the other drives and go into your bios and check and make sure ssd is set to be the boot drive and you should be off and running. The one thing you have been missing is that if you had the old drive in the machine it would boot. If you did not it would not. That means it holds the os NOT the ssd.
Windows install will allow you to take ahci drivers from a thumb drive to install. Download those and put them on a thumb drive to make sure you have them. If i remember w7 doesn't have them as part of the install disk. Maybe some of the later install disks it did but it has been a while can't say it does for sure either way. This could be the cause if your whole problem in the first place.

 

[dankcik09]

It doesn't seem like your following what everyone is saying. Your os is on your old drive not the ssd. When you put in the repair disk it will always show what ever drive in the machine as C. That does not mean that it has the os on it. You need to go with what i said earlier and clone from the old drive to the ssd. The only other way that you can fix this is remove other drives and do a complete os install on the ssd. Reinstall the other drives and go into your bios and check and make sure ssd is set to be the boot drive and you should be off and running. The one thing you have been missing is that if you had the old drive in the machine it would boot. If you did not it would not. That means it holds the os NOT the ssd.
Windows install will allow you to take ahci drivers from a thumb drive to install. Download those and put them on a thumb drive to make sure you have them. If i remember w7 doesn't have them as part of the install disk. Maybe some of the later install disks it did but it has been a while can't say it does for sure either way. This could be the cause if your whole problem in the first place.

Already fixed. I had to go to disk management and right click the C drive to "Active" for it to show up in the Windows Repair Startup driver menu.

 

[D3athStalker]

I ran into this problem, unexpectedly. It gave me no error or anything, I just happened to get into disk management and found that my 2TB gaming HDD was set as a sytem reserved partition.
The boot and some other stuff was attributed to my C: drive, on which I had the OS installed. This was fine, but the system reserved being in the 2TB drive was not fine. And I thought, how the heck was I booting up then?
I checked my booting order and priorities, turned out the first HDD to be booted was not the C: drive, but the 2TB one. This explained why I could still access windows. To confirm, I force booted C:, and it showed up with an error: "BOOTMGR is missing."
Now I had to find a way to get the system reserved partition into the C: drive. One way is what is mentioned by Fret.
The one I used is done with the command prompt (boot in from your HDD, run cmd as administrator, run as admin is must, or it will not let you do what the command does). Copy paste THIS command:
bcdboot c:\windows /s c: /f ALL
What this does is toss all the system reserved partition files from the unintended disk into the C: drive and now your disk management should show C: drive as possessing the system partition as well, with that label having disappeared from the unintended drive.
More info on the command can be found by typing "bcdboot" without quotes. I will just say that /s represents the source disk containing the partition of system reserved, and ALL means that both the BIOS and (in the more modern systems) UEFI files will be copied.
This is how I fixed the problem. Just make sure you run the command prompt as an admin. I am only posting this here in case someone has trouble using the original method stated by Fret here.
Good luck!