PC unable to boot after failed SSD transition

December 26, 2015 at 16:00:31
Specs: Windows 10
I just recently picked up a Kingston 128GB v300 ssd, after having some problems trying to install, format, and read the drive, i went into bios hoping to get it to recognize. After searching for a bit the only thing i did was swap the boot order of my drives- so the kingston would boot first rather than my main drive. After this, even with the ssd removed i am unable to enter bios or even get output on any monitors (ive tried multiple). If it helps, i have a Gigabyte z97-gaming MB, hopefully thats not the problem.

See More: PC unable to boot after failed SSD transition

Report •


#1
December 26, 2015 at 19:48:41
Try getting into the bios with no drives connected.

Report •

#2
December 26, 2015 at 20:43:07
That would be my suggestion too. With no drive connected you should more easily get into BIOS and see if there was something not set correctly in BIOS. Check primary graphics designation as well to make sure it is correct. If you cannot get into BIOS still, reset CMOS by unplugging the machine and moving the CMOS jumper from the stand by location to the clear location and back again before plugging in again. Immediately after go back into BIOS, set time, date, CPU, RAM, Graphics, etc. Then shut down, plug in only SSD drive, go back into BIOS and set the drive as Bootable and then as second in boot order after DVD drive. Then do a clean install of Windows including partitioning and formatting (quick format only for SSD drives). By installing with only the one drive connected you prevent Windows from installing boot partition or other parts on the other drive so that the drive contains all that is needed to boot. Once install is complete, reconnect your storage drive and configure if needed.

You have to be a little bit crazy to keep you from going insane.


Report •

#3
December 26, 2015 at 22:15:12
You're '. . . unable to. . . get output on any monitors. . . '? Sounds like something other than the boot order. Maybe something happened while you were in the case disconnecting the drive. Could you have jarred an add-on card loose or maybe forgotten to reconnect something?

Report •

Related Solutions


Ask Question