Computer Won't Start Up after EFI Shell appears

Alloy Way

Reputable
May 14, 2015
23
0
4,510
Computer Specs
-AMD FX-8350
-GTX 960 4GB
-MSI 970 Gaming Motherboard
-600W EVGA Bronze Certified
-8GB Ram (2x4gb)
-1TB Western Digital Hard Drive

My computer was acting up lately so I decided to reset the entire pc. Reset as in delete everything I possibly could off of it. I began resetting it and as soon as it hit 66% it said it was unable to reset my computer. Since then I have been stuck with the computer either bringing me to the EFI Shell or constantly restarting after black screening after the BIOS Screen. While in the EFI Shell it won't let me give the command "startup". It will only let me "exit" to the bios screen. I played around with the bios settings for around an hour changing boot settings and EFI settings to Legacy settings and etc. but nothing seems to work. I can't start up my computer at all past that point. Please help.
 
Solution
Sorry I may misunderstand but here goes.

My mothers computer was doing the same thing. I tried reinstalling and it got "stuck" and would not reinstall. I even took it apart and ran hardware checks and nothing was out of place. (was reinstalling from a partition drive).

I used a old windows CD to get into the reinstall menu and discovered dozens of partitions on the hard drive. I deleted all but the main one. Removed the old windows CD and again attempted to reinstall from the partition drive. It worked this time.

Never seen this issue before.

mf2780

Distinguished
Oct 16, 2010
94
0
18,660
Sorry I may misunderstand but here goes.

My mothers computer was doing the same thing. I tried reinstalling and it got "stuck" and would not reinstall. I even took it apart and ran hardware checks and nothing was out of place. (was reinstalling from a partition drive).

I used a old windows CD to get into the reinstall menu and discovered dozens of partitions on the hard drive. I deleted all but the main one. Removed the old windows CD and again attempted to reinstall from the partition drive. It worked this time.

Never seen this issue before.
 
Solution