I am running Windows Home Server 2011 in my house. Have 4 pc's attached to it and each does backups to the server nightly. One of my machines uses the UEFI bios instead of MBR and the rest use MBR. As you might have guessed the UEFI machine is having the bsod when trying to boot the recovery media. I have an ASUS ROG G20AJ with windows 8.1 64bit professional installed but this issue isn't even at the point of windows it's about the recovery media and its ability to boot my machine.
When i try to boot the machine using the restore cd I got with my server or the updated media I created via the usb key you can make both situtation during the splash screen start up. It's the screen that looks like windows 7's bootup screen the machine must be loading drivers because that is where I get the BSOD. Snbsp;FWIW, I have been able to boot this pc up using windows 8, 8.1, and windows 10 media. The same thing going on now happens when I try and windows 7 media. I gather since the recovery environment from WHS 2011 is based on windows 7 that's why.
I read on the web that you disable secure boot in the bios and this problem goes away. For me this was not the case. I spoke with ASUS about it and their reply to me was get updated media for the Bare Metal Restore. I cannot find anything newer than creating the media via usb key or using the dvd that my server comes with.
Like I said the other 3 machines using MBR all boot fine from the media. I do have the latest hotfix applied which updates my WHS2011 installation to support UEFI bios's and GPT partitions. That's why I say the flash drive usb key is updated recovery media cause as far as I know that is newer than what came with my Server originally.
It feels like a driver issue but I cannot see which one. I am able to press f8 if I hit that before picking the os architecture. I see the screen where you can select 32 bit or 64 bit. Once I make a choice it goes to splash screen then a BSOD. I can before hitting one of those options press f8 and select safe mode but it does the same thing. This one really has me stumped.
NOTE: I have disabled Secure boot and it did not fix the issue. Verified in the bios secure boot disabled and PK unloaded.