Gigabyte GA-P67A-UD5 Discussion Thread

[OC Maximus]

profiles dont work at the moment and are not really needed with SB, you can basically max out the chip at whatever clock you want for all benchmarks lol

So True!

OCM

[Lsdmeasap]

Well, I give up!

I tried a vista disk, thinking maybe it's that Win7 setup, and still get the same.



As you can see, looked kinda like maybe a graphical error? So I switched to PCIE card thinking maybe the PCI I was using was messing with it, no change

I'll give it one more go with a clean win7 install, but I'm guessing it will be the same since my main bench setup I was trying with is a clean install and has only been used for reviews!

I wonder what is causing this, it must not like me at all, or is wanting to stop me from getting at 110+ Bclk

Hurry up and update SetFSB somebody!

[C-N]

my bclock also went to 107 from 104 with new bios

My board/rig is exactly the same on f6d, it gets into windows @ 105.4 but will lock up. 104.3 is all!!! I can hold stable with an extra 0.01 vcore.

[flesheatinvirus]

f6c with the new easytune gets me about 104-104.5 so far which is better then it was.

[Falkentyne]

Well I got my SB 2600k today, and my UD5, and I was just floored. Not only was I getting sub 10 sec superpi 1m at 4 ghz (which was the same mhz I had on my QX9650, except that was 11.7s), but stuff was just much faster...

And I was even GAME STABLE at 5 ghz at 1.4v with HT on. Black Ops was flying... I enabled cpu pll overvoltage just for safety...no idea how it is with it off... superpi 1m was about 7.6sec....

I even *GAINED* overclock on my HD 6970...AND on top of that, my PCP&C fan isnt spinning up as high as it did on my P5WDH with the QX...guess the 1.1 PCIE was holding back my overclock big time...

But what's up with the temps?

I bought a venemous-X, and my temps were like 88C on cores 2 and 3 on prime95 small FFT at 5 ghz...I ended the test after 20-30 seconds or so..., since I figured if it doesn't error out right away on small FTT, I'm stable if i keep the temps lower, and I don't like those temps....

Those temps aren't normal are they?

I wonder why I don't have a "solid" mount on my Venemous-X...anyone know? everything is mounted as perfect as can possibly be....but it seems like the the screw 70lbs clamp just isn't clamping the HS down like it apparently should, so it swivels like a TRUE (no wobbling, though...)

Also, the board sometimes failing to boot, even at STOCK settings, (but user defined voltages, etc) and claiming an overclock error, is sort of annoying.... like if you set 34x100 and manually set a voltage like cpu 1.22v and vtt 1.10v, you may get a double boot and overclock error (or a power down) after a restart, while if everything is "stock/auto" in the bios, that never happens....

[ProStreetCamaro]

Well I got my SB 2600k today, and my UD5, and I was just floored. Not only was I getting sub 10 sec superpi 1m at 4 ghz (which was the same mhz I had on my QX9650, except that was 11.7s), but stuff was just much faster...

And I was even GAME STABLE at 5 ghz at 1.4v with HT on. Black Ops was flying... I enabled cpu pll overvoltage just for safety...no idea how it is with it off... superpi 1m was about 7.6sec....

I even *GAINED* overclock on my HD 6970...AND on top of that, my PCP&C fan isnt spinning up as high as it did on my P5WDH with the QX...guess the 1.1 PCIE was holding back my overclock big time...

But what's up with the temps?

I bought a venemous-X, and my temps were like 88C on cores 2 and 3 on prime95 small FFT at 5 ghz...I ended the test after 20-30 seconds or so..., since I figured if it doesn't error out right away on small FTT, I'm stable if i keep the temps lower, and I don't like those temps....

Those temps aren't normal are they?

I wonder why I don't have a "solid" mount on my Venemous-X...anyone know? everything is mounted as perfect as can possibly be....but it seems like the the screw 70lbs clamp just isn't clamping the HS down like it apparently should, so it swivels like a TRUE (no wobbling, though...)

Also, the board sometimes failing to boot, even at STOCK settings, (but user defined voltages, etc) and claiming an overclock error, is sort of annoying.... like if you set 34x100 and manually set a voltage like cpu 1.22v and vtt 1.10v, you may get a double boot and overclock error (or a power down) after a restart, while if everything is "stock/auto" in the bios, that never happens....

Strange I came from a Q9550 at 4.3 to the 2600k at 5.0 and I didn't see hardly any difference in black ops. Maybe a couple fps but I was already averaging 90 to 140fps as it was at 1920X1200 with every setting maxed out.


As for temps if you can grab the hsf and swivel it then that doesnt seem right. My silver arrows locks down super tight. At 5.0 and 1.43 volts in bios I top out around 83c in prime95 if I let it run for a while.

Have you updated the bios yet? I used to get those OC errors when rebooting with earlier bios versions.

[Falkentyne]

Using f6d...

I always get an error if I power off the board completely and switch off the PSU. It powers on for about 4 seconds, powers off, powers on again, gets halfway through post, powers off, powers on, complains about some overclock failed, then I set the settings again and it loads...this is repeatable too...

And this even happens if I underclock....like 100x30...

[TurboDiv]

Same garbage happens to me too !!!

I got Prime95 version 26.4 SmallFFTS for 4(four) hours stable at 4.9 ghz(2600K) than memtest for 1 hour with memory at its rated speed 2133mhz, all stable. Than I get happy that this is my 24/7 clock and when i shut down the system for 30 minutes and decide to boot up - CLOCKS FAILED and the thing reverts back its BCLK from 100.0mhz to 99.8mhz and memory to 1333mhz CL9, but the CPU remains at 49x99.8mhz ~4.9ghz. So i have to go into the bios, set all settings, save and exit and than it loads fine. But this is everytime, so annoying, for about a week now ! Gigabyte, look into this please.

[flesheatinvirus]

Switch back to f6c or f6a and see if that issue remains. I am currently running f6c with zero issues so far and I push it to the max benching beyond 5.5.

[TurboDiv]

There is something strange going on. I'm wondering when you update your bios, do you shut down the system and unplug the power cord and than, do you press RESET CMOS button for 10 seconds ? In the Asus thread ppl experienced cold boot issues also and their fix was to take out the battery and press the RESET CMOS button for 10 seconds. I have never done that since i updated my UD5, like 5 times now. I think ill try that tonight after work.

ps: also im on F6A.

[flesheatinvirus]

No I never reset CMOS, I just load failsafe setting. I flash in stock settings then load opt and then build what ever profiles required. Removing the batt will drain any constant down enough to wipe settings though I would think it is generally not reqiured. Give it a shot as it can't hurt.

[C-N]

Same garbage happens to me too !!!

I got Prime95 version 26.4 SmallFFTS for 4(four) hours stable at 4.9 ghz(2600K) than memtest for 1 hour with memory at its rated speed 2133mhz, all stable. Than I get happy that this is my 24/7 clock and when i shut down the system for 30 minutes and decide to boot up - CLOCKS FAILED and the thing reverts back its BCLK from 100.0mhz to 99.8mhz and memory to 1333mhz CL9, but the CPU remains at 49x99.8mhz ~4.9ghz. So i have to go into the bios, set all settings, save and exit and than it loads fine. But this is everytime, so annoying, for about a week now ! Gigabyte, look into this please.

I would say its just unstable.

Every chip I have ever had burns in & will require more & more vcore than it did when it was fresh. The burn in / extra vcore will stop when the chip settles & you will have long term stability. The amount of vcore required & the time it takes to settle depends on how you run it in. If you go easy it may take months & move very little if you are like me & thrash it it can move a lot but settle in 2 weeks.

Try another .01v vcore & see if that solves it...... for now!!!

[Falkentyne]

I would say its just unstable.

Every chip I have ever had burns in & will require more & more vcore than it did when it was fresh. The burn in / extra vcore will stop when the chip settles & you will have long term stability. The amount of vcore required & the time it takes to settle depends on how you run it in. If you go easy it may take months & move very little if you are like me & thrash it it can move a lot but settle in 2 weeks.

Try another .01v vcore & see if that solves it...... for now!!!

How is this unstable, when THE SAME THING HAPPENS TO ME at 100x30 ? that's an UNDERCLOCK.

[C-N]

How is this unstable, when THE SAME THING HAPPENS TO ME at 100x30 ? that's an UNDERCLOCK.

Was only my opinion based on the most likely cause.... You got something constructive to add then go for it.

[Falkentyne]

C-N: you're more experienced than to just blame a chipset/bios issue on an unstable overclock; you know better than that

The Asus boards are experiencing the exact same issues btw.

I don't have anything useful to add. But I did mention several posts above that the problem has nothing to do with stability /overclocking at all...

Apparently asus just got a beta bios out to some people that fixed this over 20 cold boot tests...

[dinos22]

i agree with C-N, not stable and the fact OC fails at low clocks basically confirms that, you will have to tweak more!

it seems not all IMCs are the same and it may require more tweaking to get it going

testing memory with 32M SuperPi would also be a good start but not a 100% guarantee to check stability, also try linpack

[TurboDiv]

Just for kicks i lower the multiplier from 49 to 48 with the same voltages and the same cold boot problem happened...

ps: Same cold boot bug with 47 multi with same voltages for 4.9ghz.

[Falkentyne]

i agree with C-N, not stable and the fact OC fails at low clocks basically confirms that, you will have to tweak more!

it seems not all IMCs are the same and it may require more tweaking to get it going

testing memory with 32M SuperPi would also be a good start but not a 100% guarantee to check stability, also try linpack

It's a known bug, though.
The same thing happens at 30x100, which is an underclock. No way to be unstable at an underclock with all auto voltages except manually setting vcore to 1.22 and vtt to 1.1....(which match the auto voltages).

Please check out the asus thread for more information. Asus admitted there are cold boot /double boot problems. The Gigabyte boards have exactly the same problems as the Asus boards, but they have a BIOS out to fix it.

Remember the old 975X problems? (Although these are a lot worse...)

Someone without the beta bios (dunno which board) said he fixed the cold boot problem by setting memory timings manually instead of auto...probably worth a try...

[C-N]

C-N: you're more experienced than to just blame a chipset/bios issue on an unstable overclock; you know better than that

The Asus boards are experiencing the exact same issues btw.

I don't have anything useful to add. But I did mention several posts above that the problem has nothing to do with stability /overclocking at all...

Apparently asus just got a beta bios out to some people that fixed this over 20 cold boot tests...

Lol well my greatness! Tells me as you & turbo are the only ones with an issue & the rest of us are fine its a stability or incompatability issue rather than a bios issue.

Use the template on post 1 and post up your settings & full hardeare specs, lets see if we can sort this thing out.

[enkie]

Has anyone else been getting this "main bios checksum error" and have it reflash itself back to the backup bios, which is still F2 for me? For some reason its happened to me 6-7 times already and Ive only had the board for about a week. It happens at random times overclocked and not overclocked, it did it this morning on a cold boot up at 4.8, yesterday it happened on the second boot up after just flashing to F6c with it still on factory defaults.

Hello,
same problem for me with the bios f6a and f5x bsod and although it is stable on lin-x avx, prime 95 v26.4 , no problem with the bios f2. A friend has the same problems with the f6a


Is that beta bios are all buggy ?

[C-N]

I did mention several posts above that the problem has nothing to do with stability /overclocking at all...

Apparently asus just got a beta bios out to some people that fixed this over 20 cold boot tests...

It's a known bug, though.
The same thing happens at 30x100, which is an underclock. No way to be unstable at an underclock with all auto voltages except manually setting vcore to 1.22 and vtt to 1.1....(which match the auto voltages).

Maybe it is a bug but only 2 of you have it but if it still happens on auto then maybe its a setting issue. I would try auto settings again but select standard for performance enhance... see below

Heres my F6d 5GHz template

### MB Intelligent Tweaker ###

Advanced Frequency Settings:

CPU Clock Ratio .......................................[ 50

> Advanced CPU Core Features

CPU Clock Ratio .......................................[ 50
Internal CPU PLL Overvoltage...........................[ Disabled
Real Time Ratio Changes In OS .........................[ Disabled
Intel(R) Turbo Boost Tech .............................[ Disabled
Turbo Ratio (Core 1)...................................[ Auto
Turbo Ratio (Core 2)...................................[ Auto
Turbo Ratio (Core 3)...................................[ Auto
Turbo Ratio (Core 4)...................................[ Auto
Turbo Power Limit (Watts)..............................[ Auto
Turbo Current Limit (Amps).............................[ Auto
CPU Cores Enabled ............................ ........[ All
CPU Multi Threading....................................[ Enabled
CPU Enhanced Halt (C1E) ...............................[ Disabled
C3/C6 State Support ...................................[ Disabled
CPU Thermal Monitor ...................................[ Disabled
CPU EIST Function .....................................[ Disabled
Bi-Directional PROCHOT ................................[ Disabled

<

BCLK/DMI/PEG Clock Control ............................[ Enabled
BCLK/DMI/PEG Frequency Control ........................[ 1002
System Memory Multiplier (SPD) ........................[ 21.33

Advanced Memory Settings:

System Memory Multiplier (SPD) ........................[ 21.33
Performance Enhance ...................................[ Standard
DRAM Timing Selectable (SPD) ..........................[ Quick
Channel Interleaving ..................................[ Enabled
Rank Interleaving .....................................[ Enabled

Channel A Timing Settings:

##Channel A Standard Timing Control##

CAS Latency Time ......................................[ 9
tRCD ..................................................[ 10
tRP ...................................................[ 9
tRAS ..................................................[ 30
tRC ...................................................[ 27
tRRD ..................................................[ 4
tWTR ..................................................[ 4
tWR ...................................................[ 8
tWTP ..................................................[ 19
tWL ...................................................[ 7
tRFC ..................................................[ 78
tRTP ..................................................[ 4
tFAW ..................................................[ 16
Command Rate (CMD) ....................................[ 1
IO Latency ............................................[ 2
Round Trip Latency ....................................[ Auto

Channel B Timing Settings:

##Channel B Standard Timing Control##

CAS Latency Time ......................................[ 9
tRCD ..................................................[ 10
tRP ...................................................[ 9
tRAS ..................................................[ 30
tRC ...................................................[ 27
tRRD ..................................................[ 4
tWTR ..................................................[ 4
tWR ...................................................[ 8
tWTP ..................................................[ 19
tWL ...................................................[ 7
tRFC ..................................................[ 78
tRTP ..................................................[ 4
tFAW ..................................................[ 16
Command Rate (CMD) ....................................[ 1
IO Latency ............................................[ 2
Round Trip Latency ....................................[ Auto

Advanced Voltage Control:

CPU

Load Line Calibration .................................[ Level 1
CPU Vcore .............................................[ 1.4
QPI/VTT Voltage 1.050v ................................[ 1.1
System Agent Voltage 0.925v ...........................[ 0.935
PCH Core 1.050v .......................................[ 1.050
CPU PLL 1.800v ........................................[ 1.64

DRAM

DRAM Voltage 1.500v ...................................[ 1.60
DRAM Vref 0.750v ......................................[ Auto
DRAM Termination 0.750v ...............................[ Auto
Ch-A Data VRef. 0.750v ................................[ Auto
Ch-B Data VRef. 0.750v ................................[ Auto
Ch-A Address VRef. 0.750v .............................[ Auto
Ch-B Address VRef. 0.750v .............................[ Auto

Miscellaneous Settings

Isochronous Support ...................................[ Disabled
Virtualization Technology .............................[ Disabled

[C-N]

Hey guys whats a good CPU waterblock these days?

OCM what you got?

I am looking at the Swiftech Apogee XT, looks a nice block but is it any good?

[flesheatinvirus]

I am using EKs new Supreme HF in Nickel finish for both chip and card. Fantastic performance and very pretty to look at.

[OC Maximus]

Koolance CPU-360.

Still benching my arse off with bios F6c and still can't find any issues other than the normal shutdowns with unstable overclocks. She fires right up after setting optimal settings following a crash.

[flesheatinvirus]

Me too. I have found no issues either with f6c so far and I have been slapping this chip around like a red headed step child all morning. Just pulled an incredible 3DM06 score for a 480GTX at 5615mhz no problem.