I never said they sucked.  I'm looking for the answer so we can get this thing fixed up for everybody who might be having trouble with it.  UEFI is new and the kinks haven't been worked out but end users like myself are saddled with trying to cope with the issues that are coming up.  I'd like to be able to boot my system each and every time I power up without watching the bios cycle repeatedly before being able to hang onto the boot drive and load windows all the way.

I was just thinking about something else.  When I initially set this board it also wouldn't allow me to select between my optical drives either so I had to unplug the sony to force it to see the pioneer which I want as my boot optical drive.  I also have my boot ssd plugged into the lowest sata port number and it still was ignored until I unplugged all of my hard drives and forced it to repost.  This bios doesn't have consistent behavior during the boot process and I really hope that can be corrected soon.  Also what is with the z87 ftw logo screen that keeps popping up during the post process?  Sometimes it will just flash up there for just a split second and other times it just hangs up there like the bios has paused for a few seconds.  I haven't made a relationship between the length of time the logo screen is there versus being able to complete the boot process because it doesn't seem to matter. 
 
I've been building my own pc's since the days of 5x86 and have seen many different configurations and problems.  I have used motherboards from abit, aopen, ecs, dfi, biostar, msi, asus, foxconn, shuttle, gigabyte, bfg tech and evga and have used both the ami and phoenix bios and I have never had problems like this before.  This is the first bios I've ever used that wouldn't allow me to see and select my attached drives.  This one forces me to unplug everything except for the boot and optical drive that I want to use to boot from.  If I have both my sony and pioneer bdrw's attached it will only see the sony.  If I unplug the sony then it will see the pioneer.  Once it has the optical and ssd in the boot menu and I save it I can replug everything back in and the boot order remains intact.  Trying to select a boot drive with just hard drives attached has the same issue.  If we can't get these things resolved then evga needs to replace this one with a different chipset.

I had to leave for a little while and when I came back and restarted it post looped 3 times before it loaded windows.  I'm thinking about naming this thing Forest Gump's box of chocolate because each time I hit the power button I don't know what I'm going to get.

Well today the first boot took 6 post loops before the bios allowed windows to load.

Well this morning it took 2 post attempts before it loaded windows.  I just keep a note pad in front of me every time I hit the power button so I can jot down what happens.  Also yesterday evening while playing bf3 it froze up on me for the first time and was slow to respond to hitting the reset button which I pushed 5 times before it reposted itself.  It took 3 post loops for it to load windows after that.  Now I'm thinking about placing a picture of Forest Gump on my tower.  This is just plain stupid that the bios cannot post and load windows on the first try.

- Hi,
 
reading this really hurts. ^^ You should start asap an RMA + call them (EVGA). This hardware-issue is on chapter but the service is one another! I have no problems with my Z87-Classified (and i7-477K). - From the first boot on...
 
Good luck!
- C.
 
P.S. Thank you for your reminder. I installed the bios-update on switch 02.

Well this morning it went through 16 post loops before it allowed windows to boot.  6 times it stalled on the 2nd z87 ftw screen showing debug code A2.  Look at how many people are coming by and reading this thread.  Do not waste your money on this motherboard unless you want problems like this one to plague you on a daily basis.  Before evga sent me this one they said that they'd test it extensively to make sure that it was solid and well this one will boot eventually but it doesn't handle lots of drives being attached to it.  EVGA next time you test something how about configuring it like the customer and then see how it behaves.  I asked evga to let me step up to the z97 ftw when the first one demonstrated that it would not behave right so I could avoid more of these problems and they said no.   This mb is the second problematic z87 ftw and it was a replacement for a nforce 780i sli that had died and they no longer have which required me to buy a new cpu.  So to recap this is the second z87 ftw that doesn't work right and this is not sitting well with me anymore.

I just tried to launch the evga e-leet tuning utility just to check and it immediately reset my machine and caused the bios to begin the repost process.  EVGA this motherboard is junk!

This stupid board keeps on post looping so I've tried rolling back the bios on both sides to 1.10.  I tried 0.05 and it bsod's and then 1.06 which I found online but it trashed the bios side it was on so I rebooted on the 1.10 to my flash drive then switched back to the bios 1 side and reflashed it with 1.10.  If you guys run into a problem with trashing a side then remember to boot off a flash drive on the good side and once the post is done and the dos has loaded then execute the update file and then switch to the bad bios side before pressing Y to flash and it will reprogram the bad side.  With that said I'm aggravated with the board to say the least.

Well I shut it down and plugged in the 6 pin auxiliary power connector and rebooted.  It post looped 8 times before it came up so no change there.  I must say that the power connector location and orientation was not thought out properly.  Having it facing downward instead of out makes it difficult to reach.  I had to unscrew my power supply and move it in order to reach it.  Although I don't run sli at the moment I thought I'd try it just to be able to rule it out as a factor in this problem.  To be honest this is terrible and nobody should have to deal with a problem like this with a new motherboard.  Seeing that this is the second one in a row that is behaving this way I'm having a difficult time believing that the bios alone is at fault.  I'm going to stay with bios 1.10 for now and see how it behaves.

It's not power related however I plugged in the 6 pin auxiliary power supply connector just to be sure.  It behaves like the bios and the chipset are not communicating properly.

Have you attempted reinstalling the chipset driver, to see if that would help? I know it shouldn't have an effect on the boot, but as I stated, it is very strange to have two motherboards show up and have the exact same issue, and no one else complaining about it.

I'm starting to discover some additional relationships between the two bios versions.  If bios 1 is an older version or trashed then bios 2 with 1.10 works.  I have also discovered that if I try to flash bios 1 with 1.04 and 1.05 that neither of them will work on bios 1 and both result in a FF debug led code.  However with both of them on bios 1 bios 2 with 1.10 seems to work properly and will boot my machine.  Now why is that?  Why did evga ship the board with 1.01 on bios 1 and 1.10 on bios 2?  If this is the required relationship then why no documentation for the end user to inform us of this requirement?  It shouldn't matter what version is on either side as they are supposed to be independent of one another however what I'm seeing suggests otherwise.  EVGA would you care to comment about this?  I have already requested bios 1.01 from evga so I can return the board to its original relationship but I was told that they no longer had that version available.  This has the worst motherboard manual I have ever seen and it has no real information for the end user to draw from.

What bios update started supporting the 4790k, because the classified didn't become supported until bios 1.08, and if that is true with the bios of the FTW, then that is why you can't get a post with 1.04/1.05 more than likely. 1.01 isn't going to have many features, as all motherboards require an update right from the factory when they are first release, or so it would seem, but flashing a bios that doesn't support the cpu may be the issue. (not the overall issue, just the 1.04/1.05 issue).

I played around with bios 1 side and cycled it several times and 1.09 finally booted the system after it quit showing ff and started post cycling.  It took 4 post loops before it decided to let windows load so here I am.  It will hang on a restart which is what 1.10 addresses so I'm going to step it back up to 1.10 and try it with both side using the same bios version.