T_Yamamoto
Lifer
- Jul 6, 2011
- 15,007
- 795
- 126
How did it get resolved?
http://forums.tweaktown.com/gigabyte/28441-gigabyte-latest-beta-bios-11.html#post274647
All of the Gigabyte bios revisions.. I put F8a on last night.. the world did not implode..which is great.. if you're the kind that thinks good news is the absence of catastrophy.
I'd propose that you might get no shutdowns anymore if you go with the most-reported solution, just setting the Base Clock (what everyone weirdly is calling the BLCK) to 100.1 and ditching those other tweaks you mentioned.with the changes i have posted. Now with 48 hours of use. I get about 3 shutdowns a day.
I'd propose that you might get no shutdowns anymore if you go with the most-reported solution, just setting the Base Clock (what everyone weirdly is calling the BLCK) to 100.1 and ditching those other tweaks you mentioned.
those are all beta.
OK guys, got my system up and running. Here are my current specs as of this posting:
- Gigabyte GA-Z77X-UD5H rev 1.0
- BIOS version F4 (came with board)
- Intel 3570k, using stock HSF
- 8GB of ADATA AX3U1600GC4G9-2G 2x4GB RAM (this was listed as compatible RAM on Gigabyte's site, the reason I chose it)
- Crucial m4 CT128M4SSD2 128GB SSD
- eVGA GeForce GTX275
- Windows 7 Home Premium SP1, all updates applied.
So far, so good. I have nothing else plugged into this motherboard except one set of front panel USB2 ports. External attachments are a Logitech G110 keyboard and G500 mouse attached to two of the USB3 ports on the back and ethernet plugged into the Intel NIC. I have not touched the BIOS at this point, just looked around. I have two monitors plugged into the GTX275, nothing plugged into the IGP ports. All drivers were downloaded from Gigabyte's website and everything installed properly. I have not installed any of the Gigabyte software yet.
Absolutely zero issues so far.
EDIT: I just tried updating the BIOS but cannot get the Q-Flash program to pull up the files on my flash drive even though it recognizes the drive. I installed @BIOS and was able to update to F5 successfully and without any issues, but it won't let me manually select the F6 file (gives an error) nor does the automatic download recognize a F6 version (just F5).
Also, I haven't touched overclocking yet, mainly because I'm not sure about temps right now. If I boot into BIOS, it's hovering around 38-40C. I installed the EasyTune5 program from Gigabyte, which shows temps, but in here it's showing me currently at 20C just sitting on the desktop typing this post. I know I'm clocked lower at the moment automatically, I'm guessing this doesn't happen in BIOS, hence the higher CPU temp there?
EDIT2: Decided to do the auto-tune in EasyTune5, it put me at 4.34GHz. It was testing all the way up to 4.66GHz but locked up, rebooted itself and configured it back down. I downloaded the CPUID hardware monitor to view temps and CPU-Z to view the speed. With it automatically clocked down to 1.65GHz, temps are hovering around 36-37C on average. I wanted to put some graphical load on it since that's my kind of stress testing, so I downloaded 3DMark11, but found out it requires DirectX 11 hardware, which I don't have. Didn't bother with 3DMark06, didn't feel like downloading 500+MB.
Still not a single shutdown or restart to be found (outside of the aforementioned auto-tune, which is to be expected). Every time my computer reboots after an update or program/driver install (which has been quite a few), I count off the seconds in my head. So far, on a normal boot (i.e. not during BIOS adjustment or Windows updates), it seems to post from the monitor picking up a signal to the Windows loading text in about 8-10 seconds. From the moment I see the Windows loading text to sitting at the desktop, it's averaging around 8-9 seconds, with the fastest load clocking in around 6 seconds one time. This is all counting in my head, but I'm doing the "one thousand one, one thousand two...", which I find to be pretty accurate.
EDIT3: I have my computer set to sleep after 1 hour so it wasn't on all night. Got up this morning and woke computer, it came right up, no issues to be found so far. I plan on stressing it a bit tonight if I have the time, will try to hook up my other hard drives and run a couple of games to see what kind of temps I'll get.
Please don't announce a solution if you're not sure it applies broadly. If you search this thread, and others offsite, you'll see numerous reports where BIOS firmware F8a still showed the symptoms, and often it was the Base Clock going to 100.1 that still solved the problem. Anyway, we need an actual, committed, and explicable solution from Gigabyte, so the pressure is still on.I had to do the bios updates manually.
So we are now at 24 hours of using bios F8a, on defaults, with no issues.
looks like we have a solution.
I'm on evening #2 with this build and still no issues. I did some cable cleanup and plugged in my two platter hard drives as well as an external hard drive. Been copying data back and forth, putting things in place, also installing some of my programs. No issues.
I finally figured out why I could update my BIOS from the flash drive, it's because I have one of those Sandisk drives with the U3 partition on it. The drive has two partitions on it and it was messing with the Q-Flash. I had to download a tool from Sandisk that would remove the U3 partition (haven't used diskpart in a while and didn't feel like fooling with it). Once I did that and got the drive to just one partition, Q-Flash finally worked and brought up the files on the disk. The F6 BIOS I was using still wouldn't work, though, something about the size. It was the same type of error that @BIOS was giving, something wrong with that file on Gigabyte's website.
Try F8a.. as I said, not exactly beta.. F4 and F6 are more like beta.. F8a would be like.. RC0..
I installed it and found the freezes/BSODs recurring without, as before, setting the Base Clock manually to 100.1. I had thought Gigabyte released F7 to address this obviously widespread problem, but apparently they are not being responsive. This is a really bad episode for their reputation, though they are so gigantic of a corporation that I doubt they care. (They are not the types, for example, who follow up Web reviews with manufacturer messages that reassure or offer RMAs.)BIOS F7 was officially released today for the UD5H.
I don't think it's official at all; just that the original poster, songokussm, has the ability to revise the thread title. It's a totally disagreeable decision here, though, even evidenced by songokussm's posts which throw down multiple guesses at what the solutions might be.Is it really solved?
I brough this MOBO before those many bad feedbacks, so when it gets my home I think I may have the same trouble.
I'd like to know if is this really how I may fix it, if it will have a problem.