GIGABYTE Latest Beta BIOS

[Peakr]

Re: GIGABYTE Latest Beta BIOS

X79UD3.12N adds the 1.6.0.1702 oRom. Looks like both oRoms are present but when you boot it defaults to the 1.6.0.1702 and if you have the 3.5.1.1008 RAID drivers installed you get a BSOD. There is probably a way to swap the drivers out then flash the bios.

[dejanh]

Re: GIGABYTE Latest Beta BIOS

X79UD3.12N adds the 1.6.0.1702 oRom. Looks like both oRoms are present but when you boot it defaults to the 1.6.0.1702 and if you have the 3.5.1.1008 RAID drivers installed you get a BSOD. There is probably a way to swap the drivers out then flash the bios.

So how do we switch back and forth?

EDIT: GA-X79S-UP5 F4q BIOS has some serious problems.

1. This is an enterprise grade board with an server C606 chipset but we are now forced to use the regular RST OROM instead of RSTe OROM
2. There is no way to switch between the generic RST OROM and the enterprise OROM
3. The new CSM functionality is not explain, does not seem to serve any purpose, and disabling it crashes the UEFI BIOS on reboot and the setting just gets re-enabled again
4. The new release brings no resolution to the throttling problems on this board
5. It is still impossible to set tRC to anything higher than 32 manually (completly insufficient for high speed memory)
6. Support for 8 banks in 2133MHz configuration is not improved. Board still cannot boot with 8 banks of 2133MHz or higher memory in all banks regardless of chip
7. Disabling Turbo still prevents overclocking using the multiplier alone (this feature was working in versions F1 through F3)

Overall, very bad release.

[saudfial137]

Re: GIGABYTE Latest Beta BIOS

New BIOS:

GA-P67A-UD3-B3 - U1b
GA-P67X-UD3-B3 - U1a
GA-P67X-UD3R-B3 - U1c
GA-P67A-D3-B3 - U1d
GA-P67A-D3-B3 (rev.2) - Ua5
GA-P67-DS3-B3 (rev.2) - Ua1

- 11/12. Sep - 05.Oct 12

USB 3.0 still cause system unable to boot after updating to GA-P67A-UD3-B3 - U1b.

[johnny.pierogi]

Re: GIGABYTE Latest Beta BIOS

Like others, I am trying to OC an i7 3770k on a G1.Sniper 2 running Win7 x64. I have updated my BIOS to u1c from the official F5 release. While I *can* change the overclock multiplier in the u1c BIOS, after system boot the multiplier value still shows 35x in the CPU-Z utility.

I have read extensively through the posts in this thread, as well as those on other forums, and it's difficult to get the story straight. With the u1c BIOS some *do* seem able to OC an ivy bridge chip like the 3770k on a Z68 board like the G1.Sniper 2. What are you doing that I'm not?

Thanks to anyone who can point me in the proper direction on this issue. Judging by the number of posts in this thread and how many times it's been viewed, this must be a common problem.

Best, John

[Peakr]

Re: GIGABYTE Latest Beta BIOS

Like others, I am trying to OC an i7 3770k on a G1.Sniper 2 running Win7 x64. I have updated my BIOS to u1c from the official F5 release. While I *can* change the overclock multiplier in the u1c BIOS, after system boot the multiplier value still shows 35x in the CPU-Z utility.

I used to be able to change the "CPU Clock Ratio" to overclock using the multiplier but that no longer works. Now I have to enable "Intel Turbo Boost Technology" and manually set every multiplier. Definitely a pain in the arse. Of course it will depend on the type of CPU you have. Mine is unlocked so I should be able to just change the multiplier. It seems after nearly a year Gigabyte is still struggling with getting a decent bios with UEFI tech. I still have problems with waking my computer from sleep states as well.

[Amurtigress]

Re: GIGABYTE Latest Beta BIOS

Peakr: I am using the X79-UD5 with BIOS F13m and I've got a BSOD error when stresstesting my system with OCCT. After about 64-74 minutes into OCCT (64 bit mode with AVX support), sometimes later, I get a D1 stop error or 1e caused by storport.sys. I could narrow it down to certain iRSTe drivers. 3.0 and 3.1 are okay, 3.2, 3.5.0 and 3.5.1 cause this stop error in Win7 as well as in Win8 (3.5.1 only there). Does this new option rom in F13n potentially fix it?

Anyway, I am going to give it a shot.

[Peakr]

Re: GIGABYTE Latest Beta BIOS

Well I don't use OCCT for stress testing so I'm not too familiar with it. I think you need to separate out the OC from the RSTe driver issue first by running at stock speeds and making sure the drivers are working and then you can work on your overclock. I think if you want to use the new bios you'll have to do a reinstall but I'm not certain. You might try to uninstall the RSTe drivers/gui and install the 16.6.2.1002 drivers/gui. You might have to force install the raid driver to do this. Then reboot the computer and flash to the new beta bios with the 1.6.0.1702 option rom. I haven't tried this myself but it just might work. I personally use the 3.5.0.1005 oRom and the 3.5.1.1009 drivers/gui combo and haven't had any problems other than waking from sleep I occasionally get a BSOD and I'm still not certain if this is a driver issue or bios issue but the BSOD seems to be storage related if I recall correctly. I haven't had time to test this.

[stasio]

Re: GIGABYTE Latest Beta BIOS

New BIOS:

GA-Z77X-UP7 - F5g

- Enhanced memory capability (CL12 compatibility ;Adds Read/Write Slew Rate setting)
- 08.Oct 12

[Deboyzfun]

Re: GIGABYTE Latest Beta BIOS

I love the new bios 11v for Gigabyte GA-X79-UD7, but fan control isn't working on cpu, it only cuts it in half most other bios before 11o I can lower my fan down too 1229 rpm, as low as I can go now is 2300, which makes my fan noisy.

[Amurtigress]

Re: GIGABYTE Latest Beta BIOS

@Peakr:

I just flashed F13n on my X79-UD5. It does not BSOD 7B on me on booting but it still has me baffled. The controller in RAID mode is not a C600 anymore with &dev_2826 anymore but a regular ICH10R compatible &dev_2822....
What the heck...is Gigabyte removing a feature there to make a difference to the new C606 boards?

Frankly I don't even know what features I'd be missing if any at all...

Edit: Just saw dejanh's post that already mentions this. Sowwy.

[stasio]

Re: GIGABYTE Latest Beta BIOS

New BIOS:

GA-X58A-UD7 (2.0) - FD

- 3TB+ HDD support
- 09.Nov 12

[dejanh]

Re: GIGABYTE Latest Beta BIOS

@Peakr:

I just flashed F13n on my X79-UD5. It does not BSOD 7B on me on booting but it still has me baffled. The controller in RAID mode is not a C600 anymore with &dev_2826 anymore but a regular ICH10R compatible &dev_2822....
What the heck...is Gigabyte removing a feature there to make a difference to the new C606 boards?

Frankly I don't even know what features I'd be missing if any at all...

Edit: Just saw dejanh's post that already mentions this. Sowwy.

Yeah, I already mentioned this and worse yet for the C606 owners our board just got our RAID "downgraded" from server chipset to (as you said) "regular ICH10R compatible &dev_2822". This is effing crap...especially since the GA-X79S-UP5 has so many problems as is...so far the worst motherboard purchase made to date, ever, period.

I found a new problem too...if you use Intel RAID you cannot boot SAS RAID, and if you use SAS RAID, you cannot boot Intel RAID. They are mutually exclusive. This is implemented completely incorrectly and just plain broken. I don't even get why we have to be limited to only using the legacy ROMs when we should really have RAID management for both RSTe and SAS implemented in the UEFI management tool as an alternative.

A few years ago I stopped buying Gigabyte because of these types of problems and behavior, and it took me a very, very, long time to even consider a Gigabyte board as a viable option for any of my systems. Now I'm being pushed in the same direction again of giving up on Gigabyte. If all of the critical issues that I have reported with the GA-X79S-UP5 are not resolved soon (throttling, memory compatibility, removal of RSTe, no ability to manage and boot from both SAS and RSTe RAID) I honestly won't have any choice but to stop using Gigabyte boards all together again, and make it a point to strongly recommend to others to stay away from these boards.

I'm extremely frustrated with the problems and the fact that it has now been 3 weeks since I reported the first problems and not even an admission or a single comment from anyone in Gigabyte has been provided. All I got is denial and more denial.

[Amurtigress]

Re: GIGABYTE Latest Beta BIOS

@DejanH:

The standard RST mode at lest has an advantage, Win7 supports it without a driver disk upon installation. And it has fixed my D1 BSOD problem. I just refuse to believe it's an overclock problem...now with RST drivers 11.2 I don't get any such problems when running OCCT.

Speculation warning...I have seen a thread of the ASUS Rampage4 doing the same D1 error in storport.sys. Is it possible that Intel recommended this due to a recently discovered hard bug? Maybe we should keep an eye open what the other boardmakers are going to do with their X79 boards...
Initially the X79 was supposed to have SAS too. But Intel disabled it and removed the feature from the specs, due to a too low yield of chips with good SAS ports, and reserved SAS solely for the C606 chipset...it is entirely possible that there is more trouble with that controller. Maybe an enterprise specific feature causing it, and now requiring this to be disabled.
Remember, only RSTe drivers 3.2 up to 3.5.1 are affected in my case. 3.0 and 3.1 work.

I changed from ASUS to Gigabyte because the P6T Deluxe V2 having had some stupid not so big problems, so I ended up with the absolutely wonderful X58A-UD7 V1. And now Gigabyte backstabs me. One should assume that the newer X79 boards with C606 are more mature than my first generation X79-UD5 is...

A list of my problems with the UD5:

1) It was very hard to enable Strap 1.25 (fixed now)
2) Vdroop was buggy (fixed since F13i)
3) Onboard LAN maxed out at 25 mbits on my 50 mbits DSL line, and throughput was very inconsistent. An add-on PRO/1000 card worked fine, just like a Realtek. Gigabyte Taiwan claimed they cannot reproduce the problem, but three weeks later it was fixed in a beta.
4) Razer Copperhead mice worked on and off, their support in the BIOS was broken twice by now. Not like it mattered...
5) Marvell SATA controllers are a pain int he ass with detecting optical drives. All work in RAID mode, some don't in AHCI and initially none worked in IDE mode. (what the..? Has improved but...yah right)
Optical drives are still not found with Windows' generic drivers in RAID mode, but are found with Marvell's drivers.

WHAT is it that Gigabyte does not get peripherals right? A new platform having problems in their core components, okay, forgivable, but peripherals that were used over and over on other board models?!

The only good thing in the mess is that Gigabyte does listen at times, contrary to ASUS. And that they keep working on problems, as the F13 BIOSes prove with their fixes. Other makers would have abandoned the boards probably.

[dejanh]

Re: GIGABYTE Latest Beta BIOS

@DejanH:

The standard RST mode at lest has an advantage, Win7 supports it without a driver disk upon installation. And it has fixed my D1 BSOD problem. I just refuse to believe it's an overclock problem...now with RST drivers 11.2 I don't get any such problems when running OCCT.

Speculation warning...I have seen a thread of the ASUS Rampage4 doing the same D1 error in storport.sys. Is it possible that Intel recommended this due to a recently discovered hard bug? Maybe we should keep an eye open what the other boardmakers are going to do with their X79 boards...
Initially the X79 was supposed to have SAS too. But Intel disabled it and removed the feature from the specs, due to a too low yield of chips with good SAS ports, and reserved SAS solely for the C606 chipset...it is entirely possible that there is more trouble with that controller. Maybe an enterprise specific feature causing it, and now requiring this to be disabled.
Remember, only RSTe drivers 3.2 up to 3.5.1 are affected in my case. 3.0 and 3.1 work.

I changed from ASUS to Gigabyte because the P6T Deluxe V2 having had some stupid not so big problems, so I ended up with the absolutely wonderful X58A-UD7 V1. And now Gigabyte backstabs me. One should assume that the newer X79 boards with C606 are more mature than my first generation X79-UD5 is...

A list of my problems with the UD5:

1) It was very hard to enable Strap 1.25 (fixed now)
2) Vdroop was buggy (fixed since F13i)
3) Onboard LAN maxed out at 25 mbits on my 50 mbits DSL line, and throughput was very inconsistent. An add-on PRO/1000 card worked fine, just like a Realtek. Gigabyte Taiwan claimed they cannot reproduce the problem, but three weeks later it was fixed in a beta.
4) Razer Copperhead mice worked on and off, their support in the BIOS was broken twice by now. Not like it mattered...
5) Marvell SATA controllers are a pain int he ass with detecting optical drives. All work in RAID mode, some don't in AHCI and initially none worked in IDE mode. (what the..? Has improved but...yah right)
Optical drives are still not found with Windows' generic drivers in RAID mode, but are found with Marvell's drivers.

WHAT is it that Gigabyte does not get peripherals right? A new platform having problems in their core components, okay, forgivable, but peripherals that were used over and over on other board models?!

The only good thing in the mess is that Gigabyte does listen at times, contrary to ASUS. And that they keep working on problems, as the F13 BIOSes prove with their fixes. Other makers would have abandoned the boards probably.

That's all good and well, but I have a C606 board, the GA-X79S-UP5, so unless as you said Intel has identified a "hard" bug with RSTe and therefore recommended that all C606 chipset users be "downgraded" to standard RST, then this change is a pure mistake. As it stands right now I do not believe that this is the case. I think that this is just a plain-as-day oversight. Somebody made a global change to a bunch of UEFI BIOS in the latest beta releases without actually considering which chipset each respective board uses.

As for the SAS business, again, C606 chipset on my board does allow SAS, but again as I said the implementation is bad because it cannot be used simultaneously with RSTe RAID except from the OS (booting on both at the same time with both in RAID mode is not possible).

[Amurtigress]

Re: GIGABYTE Latest Beta BIOS

@DejanH

No arguement there, the boot issue is wrong. Makes one wonder...I'd assume the X79 and C606 are pin-compatible...maybe they made a mistake with the chipset's wiring or so...I was merely venting about the problems that my UD5 has and prolly also the UD3/7...