My MSI board is very sensitive to ESD interference. I even bought a new case and made sure to do everything meticulously, thinking it was the mickey mouse case I first bought. It also doesn't know the difference between S4 and S5 power states. I had to enable a setting (worded greenly... but I can't remember what it said) that shuts down all power except standby for ATX "power good" signal, no power to video card, busses or anything. Off means off, not "touch the case" and have the discharge interpreted as a power button press lol.
I discharge myself every time I go near this computer. It's properly grounded and all, the interference comes from the electrons going through ground I think. Jay (Jayz2cents) showed a computer he built that had a similar problem. If he touched the case his display would black out. That stopped when my Assrock video card died and I replaced it, but the other ESD problems remained.
This board has a terrible UEFI boot implementation. It actually has no EFI boot vars, the only way to boot from UEFI is by path. It's not just me, because it was later added to an Arch Linux wiki. I had to discover this for myself when I couldn't get a bootloader to work on this board.
If you use the option --removable then GRUB will be installed to esp/EFI/BOOT/BOOTX64.EFI (or esp/EFI/BOOT/BOOTIA32.EFI for the i386-efi target) and you will have the additional ability of being able to boot from the drive in case EFI variables are reset or you move the drive to another computer. Usually you can do this by selecting the drive itself, similar to how you would using BIOS. If dual booting with Windows, be aware Windows usually places an EFI executable there, but its only purpose is to recreate the UEFI boot entry for Windows. If you are installing GRUB on a Mac, you will have to use this option. Some desktop motherboards will only look for an EFI executable in this location, making this option mandatory, in particular with MSI boards. If you execute a UEFI update, this update might delete the existing UEFI boot entries. Therefore, it is a potential fallback strategy to have the "removable" boot entry enabled.
On the other hand, that's nice and simple and I don't mind at all. It has no choice but to work that way. If I lost the data on my stupid FAT32 /boot partition I could simply copy the bootloader data there from an archive to fix it, and it would boot.