nkyadav
Howdy, folks.  Been a while.
 
So, I'm trying to clean install Windows 10 on my machine as listed below in my signature - the only things that have changed are the monitors, everything else is pretty much as listed.
 
The Corsair and Intel Cherryville 520 SSDs are on the Marvell SATA III ports, Corsair being primary, Intel being secondary.  I install Win 10 to the Corsair, with all other HDs (except the Intel) being disconnected (the beauty of hot swap bays in the Level 10 GT).  I can have my BIOS set up pretty much any way that I want, default options, my optimized settings, Dummy OCing on / off, Turbo on / off, SATA mode set to AHCI, the last BIOS released being installed, and Win 10 installs fine.  However, the following scenario happens every time regardless of how I start my install - default settings, optimized settings, selected optimized settings....
 
To enable Hyper-V in win 10, you have to go to Programs and Features --> Turn Windows features on or off, and enable it from there.  If Virtualization Technology is not enabled in the BIOS it will not let you enable the Hyper-V Platform part of the feature.  If I have installed Win 10 with optimized settings, both are enabled, so I can immediately enabled all facets of Hyper-V.  If I have used the default settings, with leaves Execute Disable Bit enabled but disabled Virtualization Technology, then I have to reboot the computer, go into the BIOS, and enable VT before trying to enable all facets of Hyper-V.  Either way, I enable it all, and go to reboot.
 
Here is where it gets interesting.  If I have Execute Disable Bit enabled, then after enabling Hyper-V and rebooting, the system goes into a boot loop, eventually throwing me into Automatic Repair.  If I disable Execute Disable Bit, then the system will be able to boot fine.  However, with Execute Disable Bit disabled, Hyper-V Manager will run, but when you try to load a VM, you get an error message stating that both VT and EDB have to be enabled.
 
Now, here comes the tricky part.  If I go back and enable Execute Disable Bit, the system will not hang, but in fact boots up - but Hyper-V still thinks that EDB is disabled.
 
Ive been trying this every single day for multiple hours per day for the last week, trying to see if any particular BIOS setting is affecting it, if allowing it to update drivers after install affects it, if installation of any programs affects it - all to no avail.  So, I've started researching - and I've found that the X58 platform made by other manufacturers (particularly GigaByte) has had many a problem with Hyper-V, dating back to Win Server 2008 days.
 
The most poignant one that I found, which seems to explain the problem best, is this thread:  - it seems that Gigabyte had to release a BIOS that addressed a particular facet of their implementation of VT on that platform so that Hyper-V would not fail.
 
So, with all that said - is it a possibility that our X58 mobos also are susceptible to this phenomenon, and that it has somehow just slipped through the cracks?
 
I realize that this is by no means a new mobo, nor a very powerful system - it does what I want it to, and what I need it to, and yes, I could go out and spend several hundreds of dollars on a new mobo, RAM, and CPU and have a much more up to date system - but I would like to get it working as I have it right now, if at all possible.
 
So, eVGA gurus - what should I tackle next to get this working?  And what other info would you like for me to pass on in here to help the troubleshooting process?