Sporadic Reboot - EFI Shell - Cannot find required map name!

Neil79 · 29 Oct 2021 at 21:37

EFI Shell Version 2.31 [4.655]
Current running mode 1.1.2
Map: Cannot find required map name

Press Esc in 5 seconds to skip startup.nsh, any other key to continue

Having this really odd issue whereby I can have no problems for weeks, and can spend hours upon hours in games. But the odd time I'll be watching a movie online or Youtube, the system restarts and I get the above issue.

Turn the computer off, back on, works fine

Windows 10 : i7 4790k : 16GB : RTX 2070 : Samsung SSD 1TB

smogsy · 29 Oct 2021 at 22:33

as an EX MVP @Neil79

most common causes of this are

1. Low battery for BIOS chip on motherboard (looses charge & loses settings for windows mapping)
2. PC boot to fast and cannot find windows drive (can try turning off fast boot)
3. Master boot record have a corrupted file or a file on verge of corruption. Would try sfc /scannow in cmd (admin) then do a FIXBOOT in Recovery console

the odd part of your issue is it restarting can you post your Event log from windows to find the original cause of your PC crash? ideally critical & error sections

then I maybe able to help you further please @ me for quicker response

My guess is RAM/HDD issue

Neil79 · 30 Oct 2021 at 00:10

Windows Resource Protection found corrupt files and successfully repaired them.... So that's 3 done

Cheers for the help!

smogsy · 30 Oct 2021 at 09:34

@Neil79 feel free to ping me back if you have issue still

Neil79 · 30 Oct 2021 at 11:19

smogsy said:
@Neil79 feel free to ping me back if you have issue still

Nice one mate!

I had a look through the BIOS and not only were all my sata ports disabled for some reason ( apart from the SSD one ), it was also set to boot from the USB Mouse Wireless first. So now they are all enabled, and SSD is set to the first priority with the USB stick removed... Perhaps it was trying to boot from the stick?

smogsy · 30 Oct 2021 at 11:53

Neil79 said:
Nice one mate!

I had a look through the BIOS and not only were all my sata ports disabled for some reason ( apart from the SSD one ), it was also set to boot from the USB Mouse Wireless first. So now they are all enabled, and SSD is set to the first priority with the USB stick removed... Perhaps it was trying to boot from the stick?

its very possible, it should Try fail & move on. but maybe the Wireless Mouse stick has bootable code which is was trying which it would not recover from