Solved it, but seems it's not 100% solution.
Open CMD as admin, type:
powercfg.exe -h off
I also used the vbs sript here. How to Add Shutdown and Restart Shortcuts to Windows 8 to add shortcuts for Restart/Shutdown/Log off to the Start screen.
After first reboot it was fine. At second try it hanged again. Tried 2 more time and it rebooted fine. Tried to shut down but it took 1 minute . I am still troubleshooting this.
The second issue is related to bios i think. It is supposed to show Windows 8 logo but it shows the bios picture while loading Windows 8. I will report the issue directly to Intel Visual BIOS team.
Note: All existing Windows 7 drivers except USB 3 (Windows 8 has built in USB 3 drivers so it does not matter so much) works on Windows 8.
1 of 1 people found this helpful
I have Windows 8 Pro x64 running on my DZ68BC (BIOS 0037) with an AMD HD6700 video card. Which video card are you using?
The only glitch I have seen so far was a failed startup. After updating the Intel Rapid Storage to 184.108.40.2066 everything is now rock stable.
Windows 8 comes by default with version 8.x or something of the RAID driver, I can recommend the 11.2 driver. There is also a 11.5 driver but that has been pulled for QA reasons by Intel.
ASUS GeForce GTX 560 Ti. I have the 302.82 WHQL drivers but windows update shows a update:
"nVidia - Graphics Adapter WDDM1.2 - NVIDIA GeForce GTX 560 Ti"
Odd, i don't think that driver on windows update is newer then the offical one. I think it does not detect that the drivers is installed.
I don't use RST, neither the driver at install, nor the software in Windows.
Windows update for Video card doesn't work always 100% reliable. It is often worth to double check which driver is newer: Windows Update or the driver from the NVidia web site. Both AMD and nVidia don't publish their latest drivers on Windows update and require that you use their own website. As they have sometime strange numbering scheme's Windows will show an update for an older driver. My solution is to always check what is the best option and optional hide the driver from Windows Update (to prevent that it is installed automatically)
You can check Windows Device Manager if it shows:
Intel(R) ICH8R/ICH9R/ICH10R/DO SATA RAID Controller
and iaStorV.sys 220.127.116.119 Intel (Intel Matrix Storage Manager driver) in the driver details property dialog then you can upgrade to:
Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
iaStor.sys 18.104.22.1686 (Intel Rapid Storage Technology)
Makes sense as your DZ77GA-70K has the Z77 chipset.
Which driver file does it use (???.sys). This can be seen on the properties dialogbox in Device Manager when you right click on the controller and "driver" tab-page and the "driver details" button.
if you make a restore point you can always try if the 11.2 RST driver improves something for you, a restore point rollback will get you then back to the original Win8 driver.
1 of 1 people found this helpful
yep, same problems on my dz77ga-70k with Win8 RTM 64. USing latest 0049 BIOS.
Restarts and shutdowns hang, and work only on occasion no matter what bios or UEFI settings.
also sometimes receive a USBPORT.SYS BSOD, but likely due to driver incompatibility with board.
I have two EVGA GTX680's in SLI.... nvidia drivers 304.79 (beta) which are current and only ones that work with Win8 RTM do install, but upon reboot from driver installation if second card is in system, will show windows 8 load screen, then black screen, and bootloop after a few seconds.
Of course, these same drivers for Win7 ulltimate 64bit do the exact same... however prior WHQL drivers work fine in win7 with SLI enabled. So definetely something broken between current NVidia beta's in SLI for both win7 and win8 with this board.
Board runs awesome in win7 otherwise, just seems they have some compatibility updates and bug fixes they need to get ready for Win8.
From another forum:
It was a known problem in Release Preview
In Command Prompt (Admin) type this and press enter
bcdedit /set disabledynamictick yes
Reboot and report here if the issue still exists.
As per few forums, the issue has not been completely solved in RTM.
It seems to be working on the first look. But i have to restart some more times to find out.