PC got blue screen and is stuck on EFI screen, in need of help.

[InfamousMango]

I built a PC a year ago and everything was working fine, until today, my PC crashed, i rebooted it and the blue screen popped up, i restarted it when i read the first 3 sentences since this is the first time that this has happened. It showed the msi bios screen and once it got after that there was a black screen and in the top right it said:

EFI Shell version 2.31 [4. 653]
Current running mode 1.1.2
map: Cannot find required map name.

Press ESC in 1 seconds to skip startup.nsh, any other key to continue.

the counter goes from 5 to 1 and then it just stops at 1 and does nothing, my keyboard and mouse don't function and i cant get into the bios, booting from a different hard drive and switching sata ports have no effects. My specifications are:
AMD FX 6300
Sapphire AMD R9 270X Dual-X
MSi 970-g43
Radeon entertainment memory (8 GB)
1 256 GB SSD
1 1TB HDD
500 watt modular corsair PSU
Microsoft Windows 7 UltimateN

I have tried switching drives and ports and no effect, can't get into bios since keyboard does not work anymore before boot (because of motherboard drivers). I am a little worried as to what I should do. I have seen other people have the same problem and they got it easily fixed, If anyone could figure out the problem I would love that.

 

[dextermat]

Hi,

Some just switch sata port and worked, other har to repair or reinstall windows

see threads here

http://www.tomshardware.com/answers/id-2196846/motherboard-find-required-map.html

http://www.tomshardware.com/forum/366241-31-startup-problem-stuck-screen

good luck

 

[InfamousMango]

Switching sata ports as I said in my first comment did not work and since I don't know how to get into the bios, I'm not sure how I can repair Windows

 

[InfamousMango]

I do know how to get into the bios, it is just that the keyboard doesn't work anymore before Windows boots, so I can't type any commands in EFI

 

[InfamousMango]

Thanks for your reply to help, but I fixed it myself by leaving the cmos battery out of the motherboard for a few hours and that did the trick. What caused the problem was that when i installed msi fastboot for my pc, it was trying to make the gpu do something that it could not, if i had an msi card, then there would have been no issue.