**[OFFICIAL]** GIGABYTE Z77X Owners Club/Discussion/Info (All Model's Welcome)

[acebmxer]

F11b for Z77X-UD3h may have killed my board. I flashed main bios and it flashed successfully and it prompted me to shut down or reboot, I choose shut down and then I cleared the cmos via push button on motherboard. Powered the board back up and all I get is the Gigabyte logo and nothing else no peeps or anything. Debug LED shows code 64. I shut the system system down and try to boot from backup bios via bios switch. I still just get a Gigabyte logo and no peep debug led shows 64. I shut the system down pulled the power cord and help clear cmos button for 1 min still no go.

Help!!!!!!

[dinos22]

is your backup bios still the old bios?

there is one think you can try

short pins 6 & 7 on the MBIOS and try and get it to force recover. Try starting with pins shorted or try shorting after it turns on

strange that backup bios is doing the same thing, sounds as though you also flashed main to backup bios :S

pins 6 and 7 are the two middle legs of the bios that are on the opposite side of that while marker (which indicates pin1 or first leg of the IC)

[stasio]

All OK now.

[acebmxer]

Yes sorry for late reply. All is ok now. Had to do a full cmos clear along with disconnect EVERYTHING except for psu power cable keyboard and monitor connected to igpu, and 1 stick of ram finally it posted.

[sin0822]

okay cool. next time you can corrupt the main BIOS also by just holding down the power button and releasing it at a certain time, and pressing it down again. i forgot how to do it.

[chawks2]

If you have an SSD plugged into the port SSATA5 that will interfere with the mSATA port. As port 5 and the mSATA port are on a switch, so you can use either or.

ATA port 5 is "Empty", but yet the mSATA RunCORE SSD is still not found. Escalated to GByte support, I have another one I will test, so maybe this one went bad??

[sin0822]

perhaps, i don't have an mSATA drive to test Did you try re-seating it?

[chawks2]

perhaps, i don't have an mSATA drive to test Did you try re-seating it?

Yes. Nothing wrong with the mSATA drive as I have tested it in my mDELL Atom laptop. Works perfect. Thought maybe it had something to do with an EXT4 partition, removed it, but still no luck.

[sin0822]

you can RMA the board, however perhaps it is a BIOS setting. Dd you try GB support?

[voronus]

Thanks for the suggestion. Flashed to F11a but no luck. I believe Windows 7 installs the VIA drivers itself? I installed all motherboard drivers on the Gigabyte CD anyway.

I think I will try to reinstall windows with components plugged into different ports this time. You never know it may work!

I have been in touch with Gigabyte and apparently this is a known issue with the VIA chip on the UD3 and Windows 7. Not sure why it only happens on some boards, must be a specific combination of hardware. The reply from Gigabyte for those that are interested:


Definitely the ports which work OK for your customer are Intel chipset based.
The problem is related with Windows 7 limitation and VIA VT800 USB 3.0 chip support. We strongly advise to connect any USB device(s) to the Intel controlled USB port(s) (located below the RJ-45 LAN port) before the VIA USB 3.0 controller driver is installed.
The link for this driver is:
http://download.gigabyte.eu/FileList...r_via_usb3.exe

[chawks2]

you can RMA the board, however perhaps it is a BIOS setting. Dd you try GB support?

I have an open case with them. Their answer was to try a different mSATA card in the board (as if I have tons of these lying around). My last response was to provide confirmation the drive was working properly in my ATOM mDELL.

If anyone has mSATA working it may make sense to keep track of ones with issues etc.

STEC 4G mSATA DEF does not work in it's current capacity on this board (UDH5) with F5 BIOS (not changing BIOS because have no other issues)

[sin0822]

interesting i never has an y issue with the VL800, I just plug into those ports or intel. Perhaps uninstall the VLI driver?

I know the UD3H uses the VLI controller, while the UD5h and Sniper 3 use the hub, which is different.

BTW here is my G1.Sniper 3 review: http://www.xtremesystems.org/forums/...)&goto=newpost

[stasio]

UD5H...F8 is out.

[chawks2]

interesting i never has an y issue with the VL800, I just plug into those ports or intel. Perhaps uninstall the VLI driver?

I know the UD3H uses the VLI controller, while the UD5h and Sniper 3 use the hub, which is different.

Nice review on the Sniper.

It's not detecting any mSATA drive in the BIOS period. I'm not even getting a chance to play around with drivers because the drive is missing. I will try my RunCORE as a final test, Gbyte support had me remove all my drives (loaded optimized defaults), still no drive whatsoever.

[deNordic]

Why my UD5H stuck when i enter bios after my o/c settings fail? X48-DQ6 used to stuck when in bios also. Is there any idea?

[stasio]

Clear CMOS.

[ZenEffect]

I experienced this on UD3 + UD5. USB would freeze in bios and fans would spin up indicating a lock. Clear CMOS works but there is a better way. The trick is to get it to go into the safety mode while retaining your information so you can adjust your overclock. I experienced this only when setting the memory slightly too tight.

1. Power on PC
2. Switch power off @ psu during post. Try to get it when the post code says 45, though ive done it at 15 and it works 90% of the time... 100% @ 45
3. Wait 1 second
4. Power on PSU
5. Hit power button

The bios will go into the failed oc recovery mode at default clocks and timings. I have not ever experienced a lockup/hang in this mode. From there, your OC settings are retained but not actually applied.

If you set memory timings during this then save and quit, sometimes you experience a 51 hang. Just hit the reset button and it will go into "failed oc" mode (not failed oc recovery.) immediately save and quit and if your timings are good it should post properly.

just my 2cents on this matter and how i get around it

[sin0822]

yea if your OC isn't stable an OC recovery doesn't' kick in then you will freeze in the UEFi. it seems that the UEFi puts a load on the CPU possibly like 30% or 50% even as the BIOS CPu temp isn't idle temp.

[acebmxer]

Sin maybe you can talk with your contacts over at gigabyte as they may listen to you, I tried to talk with Gigabyte but just got the run around.

Issues I am having.

1. Samsung green ram will not clock past 2133. Ram has been proven to overclock up to 2400-2600 even 2800. At first if you selected anything higher then 2133 it would select that option but would not apply it. Now it apply it but will not boot. I have set vdimm up to 1.7 vtt to 1.200 and imc to 1.195-1.200 and timings up 13 13 13 32 1t and still nothing. The only thing I get are what sound like 10 or so short fast beeps.
2. Only the 2 usb3.0 ports below the ethernet port work for my keyboard and mouse in bios for the back ports. I can use the front panel usb2.0 headers. I bought a $2.50 2 port usb 2.0 pci front panel adapter just for the keyboard and mouse.
3. The UEFI bios will lock up on me when overclocking. Now that I see your comment about Uefi putting a load on cpu, makes some sense as I dont think the system was stable yet when it was locking up. But I do believe it was locking up while the system was stable.
4. Come to find out the issue I had a few days ago did not turn out to be a bad flash or corrupt bios but just the fact after a flash the system does not like my usb3.0 flash drive connected to front panel header. After the first boot its ok and doesn't care its only after flashing the bios.

All my hard ware is in my sig under main rig.

[chawks2]

2. Only the 2 usb3.0 ports below the ethernet port work for my keyboard and mouse in bios for the back ports. I can use the front panel usb2.0 headers. I bought a $2.50 2 port usb 2.0 pci front panel adapter just for the keyboard and mouse.

I have seen similar unusual behavior with the USB ports on the UD3H ONLY (on the keyboard USB ports). The UD5H does not seem to have this issue. Additionally, I had navigated to the Intel site and downloaded the newest USB3 drivers available. However, obviously this does not do anything for the VIA chipset USB3 drivers (which I believe is the issue).

3. The UEFI bios will lock up on me when overclocking. Now that I see your comment about Uefi putting a load on cpu, makes some sense as I dont think the system was stable yet when it was locking up. But I do believe it was locking up while the system was stable.

The only time I have seen this occur was when either the chip can not handle the multiplier, OR there is not enough vCore+. Someone in this thread mentioned to up the Voltage to "Xtreme" in the 3D frequency power settings (?). This had allowed me on the UD5H to get to x48, but there was instability (similar to what you explain). Rock solid @ 47. Have not played with the voltage settings any further.

4. Come to find out the issue I had a few days ago did not turn out to be a bad flash or corrupt bios but just the fact after a flash the system does not like my usb3.0 flash drive connected to front panel header. After the first boot its ok and doesn't care its only after flashing the bios.

This sounds like a compatibility issue with the USB3 drive, maybe double check the connectors and/or try a different one on the board and/or if you have another mobo lying around test out the USB3 drive to confirm there are no issues with it.

[acebmxer]

So far with the testing that I have done with my cpu it is stable upto 4.7ghz with HT on at 1.26v llc set to turbo, 4.8ghz ht off at 1.26v llc set to turbo and that 20 LinX passes max memory. I can boot to 49x but too much heat and vcore to get stable.


As for the usb drive it has worked just fine with my x58a-ud5 and x58a-oc but they didnt have front panel usb3.0. I have not tried the flash drive in the back panel usb3.0 ports but who wants to reach around their every time. The drive is a Corsair Flash Voyager 8gb usb3.0 drive.

[garysteel]

HELP ¬!!

Just built my new system, GA-Z77X-UD5H Wifi, with i3570K, and cannot get the beast to power up, I've stripped the board out , 1 stick of memory and the cpu and nothing!! apart from the power up button on the motherboard which just flashes..

Pulling hair out as can't find any help on this.

Grateful for you advice

Gary

[C-N]

Have you cleared the CMOS ? its like the board is in hibernate/sleep or something.

You could also try switching to the other bios.

Oh & when asking for help you should have a sig so people can see what u got

#### Edit #####

Oh yeah & welcome to XS you long time lurker you..... 2006 & this is your 1st post?

[garysteel]

Have you cleared the CMOS ? its like the board is in hibernate/sleep or something.

You could also try switching to the other bios.

Oh & when asking for help you should have a sig so people can see what u got

#### Edit #####

Oh yeah & welcome to XS you long time lurker you..... 2006 & this is your 1st post?

HI and thanks for coming back,

yup tried the bios switch..same thin dead and just the flashing onboard power switch next to reset and cmos.
I've not uploaded my sig with bits as its just the motherboard , CPU and and enermax suppy 650W, which i've just plugged back into my old system which sprang into life.

If it was that the bios was too old to for the ivybridge...I expect it would at least still do something...thinking the board is dead but really looking for some knowledge here.

Long time member, good board.

PS will work on Sig once this thing boots

Cheers
G

[voronus]

2. Only the 2 usb3.0 ports below the ethernet port work for my keyboard and mouse in bios for the back ports. I can use the front panel usb2.0 headers. I bought a $2.50 2 port usb 2.0 pci front panel adapter just for the keyboard and mouse.

Do the ports work for you in Windows?

I have the same issue, but they dont work for me in windows either. Gigabyte told me it was some issue with the VIA chip in Windows 7. The fix is meant to be to install the VIA drivers while having things connected to the Intel ports (next to the Ethernet port). Didn't work for me though and I am now RMAing my board after trying lots and lots of different things to no avail.