I have almost the same build:
Gigabyte Z77X-UP5-TH
Core i7 3770K
Gigabyte Geforce 670 4GB
4x8GB Corsair Vengeance DDR3 1600 RAM
2x Samsung 840 Series 120GB SSDs
Seagate Barracuda 3TB
Seagate Barracuda 1TB
Samsung CD/DVD Optical Drive
TP Link TL-WDN4800 Wifi Adapter
Corsair HX750 80Plus Gold Power Supply
Corsair Carbide 500R case
LG Flatron monitor (not sure what size or model - stole from family PC which is over 5 years old)
Attempting to Dual-boot Mountain Lion and Windows 8. (Posting entire build in case there's something wrong with something seemingly insignificant).
I have had both Windows 8 and Mountain Lion running just fine without the graphics card working but trying to get the graphics card working has been a real pain, even in Windows. I'm thinking it might be a faulty board, but I want to make absolutely sure before I go and return it.
The BIOS also can't decide whether the send the graphics through the 670 or HD4000. Previously I've had to switch the DVI cable from one to the other until I found the signal, but now I've set it up with a VGA from the mobo and a DVI from the 670 and I just change the input on the monitor. The monitor doesn't support HDMI. When I power up it's pretty much 50/50 whether the BIOS flash screen and Chimera boot screen will appear on one input or the other, but neither Windows or ML will display from the 670. If the BIOS screen shows on the VGA, then Win8/ML will continue to display via the mobo VGA, but if the BIOS screen displays on the DVI channel from the 670 both Windows and ML will display their boot screens for a second or two, and then I'll get no output from either the HD4000 or the 670.
Right now I've disconnected my Windows drives and am attempting to reinstall Mountain Lion for about the 8th time. The Unibeast install went fine but when I boot it up it hangs on the grey boot screen with infinitely spinning wheel. With -v it hangs on [IOBluetoothHCIController][start] -- completed. Any combination of GraphicsEnabler=Yes/No, PCIRootUID=0/1, darkwake=0, -f or -F gives me the same thing. I can only boot in Safe mode with -x. Deleting certain graphics kexts by using Terminal to navigate to the Extensions folder while running off the Unibeast drive as suggested
here screwed up my install last time I tried it and I had to start from scratch. I'm sick of having to reinstall over and over and from now on I'm not going to do anything by guessing - I need someone to tell me that it's fine to do what I'm doing.
So my first question is this: Should I proceed in Safe Mode and run the Multibeast settings as described in the first post here?