Built a new system a couple of months ago, here are the specs:
Intel I7 3770k ivy bridge with corsair h100 cooler (originally used stock intel cooler)
Intel DZ77GA-70k extreme board
32GB of 1600 DDR3 Corsair Venegenace RAM (tested with memtest OK)
PC Power&Cooling MKII silencer 950 (1000w) PSU
(2)x EVGA Geforce GTX680 2GB in SLI
(1) Samsung 830 256GB SSD
(2)x Western Digital 1TB HDD
Coolermaster Cosmos II case, LG bluray sata burner, HP ZR30w monitor on displayport
Originally, I had installed Windows 7 Ultimate 64bit on the machine... ran flawless, no issues on current NVidia 301.xx WHQL driver. I originally ran at stock processor speed, and eventually overclocked using the autotuner in the bios to 40/45 (4.0ghz main/4.5ghz turbo). Ran rock solid, voltage was fine, temps were perfect even per core.
It wasn't until I tried updating to 304.79 were I ran into the SLI bootup bug which causes the machine to bootloop (a combination of those drivers and the 004x Intel bios for this board were the cause of it)
Since then, I've wiped that partition and installed Windows 8 Pro RTM (final build) which of course also did the same thing with those NVidia drivers, 304.79 as they did in Win7.
Now that Nvidia has released the 306.02 betas yesterday officially, the drivers work correctly with Win8 Pro RTM (for the most part).
However, it still appears since Adobe Flash is integrated into Win8 now for IE10, there is an occasional IRQL_NOT_LESS_OR_EQUAL_TO (NVLDDMKM.DLL) BSOD visiting any specific flash-based page (such as youtube or adobe flashes page itself)
Of course, that's a NVidia issue, so I've reported it to NVidia as a bug.
Now, for the intel issues with this board and windows 8:
My system ran fine in Win7 either overclocked or not. However, if I overclock in Windows 8, it will continuously crash with random reasons, majority of them related to CLOCK_WATCHDOG_TIMEOUTS errors (reffering to a issue with CPU cycles/reports). This will mainly happen within the first few minutes of starting a cpu/gpu intensive game.
Once I set the machine back to stock CPU speeds, the error goes away and they run without any BSOD.
So there's obviously a BIOS issue with overclocking in Win8 that doesn't occur in Win7, or its that Win8 is more resource sensitive to overclocking. I haven't been able to determine that yet.
There was also an occasional random "USBPORT.SYS" BSOD and a occasional "IRQL_NOT_LESS_OR_EQUAL_TO" BSOD. Now, the usbport.sys error has not occurred since installing NVidia's new 306.02 beta drivers yesterday. So it may have been conflicting resources between usb and the gpu's without the drivers. I'll assume that has been resolved. The random "IRQL_NOT_LESS_OR_EQUAL_TO" may have also been attriobuted to overclocking or flash problem (though these specific occurences did not reference NVLDDMKM.DLL driver. Though it seems remained, and has yet to occur after setting back CPU to stock settings.
Another issue appears to be with shutting down Windows 8... sometimes it hangs at a restart/shutdown, sometimes it doesn't. IT appears to be doing it less since I used the "powercfg -h off" from the commandline. Not sure if its directly tied to hibernation, but it seems to shutdown correctly more often, but still has an occasional issue. No problems shutting down or restarting in Win7 with this systemboard, possibly AHCI or chipset drivers require updating?
And lastly, it was a interesting time trying to get Windows 8 to install correctly with UEFI conflicts between boot devices. It takes some patience and tinkering to get it to boot to the installer, and then recognize the correct drive to install on. Not always, I've reinstalled it several times to test different things, but sometimes UEFI seemed to have problems with the installer.
I know there's not much intel can do about overclocking issues, except I believe its the bios causing conflicts with windows 8 when overclocked, not overclocking issues themselves (my temps were fine, no issues previously with same settings as in windows 7), but there's obviously some other kinks that need to be worked out as they occur whether overclocking is on or not.
just my 2 cents and bug report to provide to the intel support team !http://communities.intel.com/images/emoticons/happy.gif|___jive_emoticon_name=happy|jivemacro=emoticon|class=jive_macro jive_emote|src=http://communities.intel.com/images/emoticons/happy.gif!
I'd recommend anyone else having newly-found issues with Windows 8 RTM (final build) to post them here as well.
EDIT: It appears ALL the mentioned crashes may have been related to overclocking. However, even the slightest overclock causes them. So overclocking on this board within Windows 8 appears to be not functional and buggy. Tested settings again on Win7 partition, no issues.