PC Randomly crashes to startup.nsh after ssd install

Morbidvizions

Reputable
Oct 10, 2015
7
0
4,510
OK guys, so i built a pretty decent gaming rig a few months ago and i skimped on the ssd. Well now about a week ago i picked up a sandisk 120gb ssd and tried the cloning deal which didnt gto too well so i did a fresh instal of windows 8.1 pro then upgraded it to windows 10. Everything was running extremely good, super fast etc etc. well i got everything set up for the 3rd time and went to reboot like i have 50 or so times and this time it didnt boot. (Same prob i was having before the clean install). These are whats been done to the PC: There are 4 other HDD's, one of them is the old c: drive wiped and assigned to H:. I had to re-assign all the other drive letters for the HDD's to get them in order and thought that might be the prob, so i reset the cmos and that did nothing. The first time i had the ssd installed it was doing like a dual boot mode type deal as the old OS was still on the original C: drive. I wiped the original C:" drive and it was running fine until it just went to a black screen and when i rebooted i started having this same problem..... Anyway, back to THIS instance lol So this time as i said, everything had been booting fine and fast. i had just installed a few games and installed razer synapse when i had to reboot and it landed me back in this damn "Press esc in ... seconds to skip startup.nsh or continue.... Please help i am at my wits end here hahahaha Thanks in advance guys!
 
Solution
Happy to help! :) With dual reserved spaces it sounds like a conflict. You should only have one of 350mb in C:

Cloning is awesome but yes can be a pain when going from bigger to smaller disk vice versa is no problem. If you know the size of future disk's it's easier to size C: to fit the new one. Although i use macrium myself and it's usually a dream cloning vice. ?! :/

If you're still having problems in the future, make shure you only have one disk connected when installing as you did. And dont connect the clone drive until it's all up and running.

Hell of a job do! Congrats!! :)
Thank you very much for the reply!

I ended up doing that exact solution, only i had a backup image from macrium reflect that i had just made a few days ago. So i wiped the drive, Switched sata ports, and did my 3rd install all over (with no other drives connected), re-installed al my programs from browsing the image backup as if it was another drive, and it seems to be running fine again. Strange thing is, I had made a clone of the C: drive and when i went to clone it back the C: drive it said it was too large *(just my luck), so that was a pain. Also i noticed when i wiped the drive for the fresh install i saw that there were 2 partitions the were 450mb And im guessing they were system reseved partitions.... The only thing I can think of is that i didnt fully wipe the drive the last time and that caused some kind of conflict through the bios... Not sure as the first time this happened it was running great then just froze on a black screen, forced restart and startup.nsh. The second time everything was running great again and it did it when i restarted after restating at least 20-25 times lol so im not sure, we'll see if the ports fixed it or not. Thanks again for your help and ill be sure to post back here in a while for others, in case anyone else has this issue.
 
Happy to help! :) With dual reserved spaces it sounds like a conflict. You should only have one of 350mb in C:

Cloning is awesome but yes can be a pain when going from bigger to smaller disk vice versa is no problem. If you know the size of future disk's it's easier to size C: to fit the new one. Although i use macrium myself and it's usually a dream cloning vice. ?! :/

If you're still having problems in the future, make shure you only have one disk connected when installing as you did. And dont connect the clone drive until it's all up and running.

Hell of a job do! Congrats!! :)
 
Solution
Without a doubt I'll be using macrium from now on! I actually used Easeus ToDo to initially clone it. That could have been my problem. I just recently found macrium (in the last couple days, and I'm with you, I'll never go back. It works like an absolute dream. Being able to refrence my image backup like another hard drive is incredibly useful! Plus, now that I'm here on the forums, hopefully I'll get the chance to help others!
 
That's the spirit!

Now with all facts on the table YES you should use the same cloning software Before and after. And a sidenote even more impressive you'l got it running! :)