******Gigabyte GA-P67A-UD4 Discussion Thread******

[Gaul]

F5 Final............... any bugs ?
DID touch bios show the same numbers on BIOS ?

[Frost_Bite]

I'm away on work travel right now, but as soon as I get home I plan on putting F5 final through its paces. I've seen quite a few posts regarding it as the best BIOS for the UD4-B3 going right now so I have nothing to lose but a few minutes to give it a shot.

I'll post some numbers up soon, and in the meantime keep posting results if you are on F5 final and find it to be a better bios than the others.

Thanks

[FL00D]

F5 Final............... any bugs ?
DID touch bios show the same numbers on BIOS ?

Yh, enabling CPU PLL Overvoltage causes reboot loops. I have sent Lsdmeasap a PM regarding the issue but he hasn't replied yet.

[Frost_Bite]

That's odd. I know a couple people who have flashed to this BIOS and did not have this problem. Did you ensure the keep DMI data option was disabled and to do a complete CMOS reset after flashing the BIOS?

Let us know what you hear and I'm hopeful this is an isolated case (no offense).

[FL00D]

That's odd. I know a couple people who have flashed to this BIOS and did not have this problem. Did you ensure the keep DMI data option was disabled and to do a complete CMOS reset after flashing the BIOS?

Let us know what you hear and I'm hopeful this is an isolated case (no offense).

What... really?! Bloody hell... Keep DMI data was disabled and I even shorted the clear_cmos jumper after flashing the BIOS. Are you sure that those people use CPU PLL Overvoltage?

Anyway, sth might be wrong here since every time I flash to a new BIOS it seems that I need a bit more Vcore than before to maintain the same OC. (4.5GHz) I always use QFlash to flash the BIOS. What should I do... reflash?

Cheers,

[Gaul]

First test F5




Still GOT BSOD on Browsing

[bluestang]

So do any of you guys rely on just SVID to work properly to do you OC?
Meaning just set CPU volts to Auto, set RAM volts to proper spec, everything else to stock volts, and then just start upping the multi?

[Andrea deluxe]

First test F5




Still GOT BSOD on Browsing

bha...


try 1.420v (set 1.4500v)

[Gaul]

bha...


try 1.420v (set 1.4500v)

is that possible no BSOD on Hyper PI but BSOD on Browsing ?
agrrrhhh !!

[Bullet92]

Of course it is. It's usually like that.

[FL00D]

That's odd. I know a couple people who have flashed to this BIOS and did not have this problem. Did you ensure the keep DMI data option was disabled and to do a complete CMOS reset after flashing the BIOS?

Let us know what you hear and I'm hopeful this is an isolated case (no offense).

I've just asked one of my mates who has the same board and he said he'd had the exact same problem. At the moment if Internal CPU PLL Overvoltage is enabled it causes a 3-cycle boot loop upon start.

[Fatbird]

I've just asked one of my mates who has the same board and he said he'd had the exact same problem. At the moment if Internal CPU PLL Overvoltage is enabled it causes a 3-cycle boot loop upon start.

r u powering the rig up from cold? i meant u have to switch on the PSU first before pressing the power button

[FL00D]

r u powering the rig up from cold? i meant u have to switch on the PSU first before pressing the power button

No. Why would I do that?

[bluestang]

Man, OCing these 2600k's are alot different than the 45nm Wolfdales I'm use to!

So here is where I'm at so far...F5 BIOS and I'm relying on the SVID and VRD12 system to work like it should. I have all of the following either off or disabled -- XMP, Real Time Ratio Change in OS, Turbo Boost, C1E, C3/C6, EIST, LLC. Internal PLL Voltage is enabled, HT On, DRAM at 1.60v and all other volts an Auto.

With this my voltages set for me by SVID (Auto CPU Vcore) it works out to this (Multi / BIOS / CPU-Z idle / CPU-Z load):

34x / 1.200 / 1.176 / 1.176 / ?
38x / 1.315 / 1.284 / 1.284 / ?
40x / 1.320 / 1.284 / 1.284 / ?
45x / 1.340 / 1.308 / 1.308 /1.248-1.260 (Prime/LinX Stable) highest core temp 58C (25C ambient)
50x / 1.360 / 1.332 / 1.332 / 1.320 (Prime Crashes)

The highest I tried/dared myself to boot at with with manual Vcore was 52x, LLC On with 1.425 BIOS and I got into Windows, idle was 1.416, passed 32M Super PI (6m48.141s) but crashed system instantly in Prime.

Now, is it worth trying to see what my highest boot into Windows multi is just for kicks? I'm comfortable with a 4.5GHz 24/7 cruncher now, but 5.0GHz would be nice!

Also, anyone here running a 5.0GHz 24/7 with C1E, C3/C6, and EIST enabled? With or without LLC?

Thanks!

[jwfowble]

I flashed my GA-P67A-UD4-B3 with bios F5 (thought I'd give touchbios a try) and noticed something odd with speedstep started happening. Maybe most people disable the Cstate, EIST, and SpeedStep features, but I noticed that after returning from sleep things ran a little slower than my 4.5 GHz 2500k CPU should. Upon further investigation with RealTemp, i7 turbo GT app, and CPU-z I could see that, after the computer went to sleep (presumably S3 as the bios is set to do) that the multiplier became locked at 16x and never jumped up again until I rebooted. I cleared the bios back to failsafe defaults and re-flashed with F5 and had the same thing happen. Maybe I'm just unfortunate, but I thought I'd report it in case anyone else has encountered this problem. My overclock is prime95 stable but sleep may put special stresses on the system for all I know.

I'm headed back to F4 bios to see if that clears things up. After a few runs of the touchbios program it stopped launching (well, the process crashed and seemed to keep 25% of my CPU occupied until I manually killed the process).

[Andrea deluxe]

just flashed to F6A..... and testing....

[jwfowble]

I flashed my GA-P67A-UD4-B3 with bios F5 (thought I'd give touchbios a try) and noticed something odd with speedstep started happening. Maybe most people disable the Cstate, EIST, and SpeedStep features, but I noticed that after returning from sleep things ran a little slower than my 4.5 GHz 2500k CPU should. Upon further investigation with RealTemp, i7 turbo GT app, and CPU-z I could see that, after the computer went to sleep (presumably S3 as the bios is set to do) that the multiplier became locked at 16x and never jumped up again until I rebooted. I cleared the bios back to failsafe defaults and re-flashed with F5 and had the same thing happen. Maybe I'm just unfortunate, but I thought I'd report it in case anyone else has encountered this problem. My overclock is prime95 stable but sleep may put special stresses on the system for all I know.
I'm headed back to F4 bios to see if that clears things up. After a few runs of the touchbios program it stopped launching (well, the process crashed and seemed to keep 25% of my CPU occupied until I manually killed the process).

Just an update on my 16x multiplier lock after resuming from sleep (in case anyone encounters this).
F4 bios didn't change the 16x multiplier nor did adjusting most of the various EIST/C1 and S1/S3 sleep states. I had manually re-entered all my overclock settings so I went back to system defaults and noticed things resumed from sleep just fine. I went back to F5 bios and am headed back up in overclocking with similar bios settings except with Real Time Multiplier Changes in OS set to disabled and things are working fine with sleep resume up to 42x so far. I'll keep playing with things and report back if I ever find what setting seemed to be the trigger.... right now I'm thinking unstable OC (though fine for 2 hr prime95) or real-time multiplier change in OS being enabled. Weird.

Update: And the culpret seems to be that enabling real time multiplier change in OS caused the multiplier to lock to 16 after sleep. It's a bios option I only did after deciding to try the touchbios program, which became buggy and crashed every time I tried to start it after only a few uses. I can't think of any reason to enable this outside of trying a windows-based overclocking program so I won't miss it.

[hersounds]

F6A link available please?

[stasio]

F6A link available please?

http://forums.tweaktown.com/gigabyte...beta-bios.html

[hersounds]

thanks again stasio

[FL00D]

just flashed to F6A..... and testing....

Hey up mate,

Is it any good?

Cheers,

[Andrea deluxe]

Hey up mate,

Is it any good?

Cheers,

no issues here!

same clock @ same voltage.

[dejanbinladen]

any news over F5, differences in bios or something ???

[stasio]

GA-Z68X-UD4-B3 - F9c

-improve boot loop issue/cold boot start
-01.Sep 11

[Demo]

I just flashed F5 last night, I dunno.. probably nothing has changed.. whats supposed to be fixed with F6A?

EDIT:

My other PC with the same motherboard always gets a bios check sum error usually after from a shutdown or If I add in/change harddrives, updated it already to F5 official and also with the back up bios to F5... this PC is not overlocked and is always running with the "optimized defaults" configuration, its actually just running as sa server ( doing nothing net )

with a 2600K, Corsair 1866Mhz 8GB ram ( only running at 1333Mhz to avoid issues ) 750Watts silverstone PSU, some 9500GT for display..

Is the bios chip or the motherboard it self defective?