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

[stasio]

F4 BIOS is out.

[Hondacity]

thats what i was waiting for

i hope the llc options are now there...

change log?

[dejanbinladen]

-fix bug with DVID (LLC disabled)

[Calathea]

Any link to f4 bios?

[Mafio]

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

[stasio]

Any link to f4 bios?

Link in my sig.

[Demo]

Im using F4 now I dont really know if its good or bad since its the first bios I tried!

Now this is odd, If i enable HT. CPU-Z sees 2 cores 4 threads, if i disable HT i get 4c/4t.. what seems to be causing this?

Windows task manager also shows 4 cpu graphs only.

With HT on device manager shows 8 processors listed.

[Calathea]

thanks I might need a hand with 1600 c6 GTs on this board later on... SB isn't exactly boot--> get beer :O

[Mafio]

hyper are still a no go...
anyway it seems a bit more stable than f3 and still strong in 3dm01.

F3 97200 :: F4 97276

[Calathea]

Wow, 1060 7-7-6. I can't post with 1:8 divider... maybe it's a cpu thing?

[Mafio]

Wow, 1060 7-7-6. I can't post with 1:8 divider... maybe it's a cpu thing?

play with VTT and System Agent voltage (i used 1.2 and 1.005 volt), i'm able to do this kind of frequency with all of my Hyper kits and all my CPUs.
the problem is that on this board there is no way to make a damn super-pi 32m, after 1 or 2 seconds windows freeze.
still waiting for a bios that finally fix this issue, but i'm quite sure we will never see it........gigabyte is focused on touch bios crap, they have no time to fix the load of problems that their p67 have.

[Hondacity]

good to know f4 didn't kill 01 score lol

[Demo]

After shorting the clear CMOS swtich is it expected for the board to automatically power up ?
Also spamming alt+f12 should flash the backup with the main bios right? I dont seem to get that option.. and how do I verify the bios version on both chips?

[Hondacity]

you should have the board off..and the power supply off...before you clear the cmos...

so: it shouldn't automatically power up

[Falkentyne]

you should have the board off..and the power supply off...before you clear the cmos...

so: it shouldn't automatically power up

Yes make sure the board is off (you already know that) and the power supply is also turned off or unplugged. If you want to do a proper clear,
wait 60 seconds after turning the board off, and press the power button after you unplug the power supply, to clear the +5 vsb.

[Demo]

Yeah thats what I do, the Stider Gold is a little pain though it has no power switch at the back.. why silverstone left that out is beyond me!

I using manual voltage right now and 1.371 volts seems to be sticking even if i just feed it 1.320v

Using F4 bios.

EDIT:


Setting the bios to normal with an offset of -0.015 still gives me a VID of 1.371v under realtemp 3.67 but it gives me an error in just a min with the smallFTT test.

[Hondacity]

enhance built strider gold series , enhance built antec tpq1200, no switches...lol

[Demo]

Im really confused about setting the voltages on this board, no matter what i choose I always see 1.381 VID under ReatlTemp 3.67.. How do I determine what voltage is actually getting fed to my processor?

I've mimicked the automatic voltages defined at 4.5Ghz which is 1.360 under bios, it fails if I manually type in voltages even with LLC.. I've also tried a +0.010 to +0.025 offset using "Normal" voltage and im still getting errors in prime95 smallFTT, pure auto makes it work.

[Hondacity]

actual voltage: multimeter
et6: reads voltages..not actual but close
cpuz: reads voltages..same as et6
aida64: reads voltages..same as et6

[Demo]

Right now I have Vcore on my bios at "NORMAL" and the VID it gives is 1.360v
Booting into windows and checking with realtemp 3.67 shows me a VID of 1.3811, putting load on the processor moves it to 1.3861
I have the DVID under the bios at +0.050, so that means 1.360 + 0.050 = 1.41vcore ?

I seem to be instantly getting errors on Prime95 SMALLFTT test..
I have PLL over voltage enabled, went as high as 1.200v on VTT/QPI
RAM is at 1333Mhz 9-9-9-24-2T

And this is just 4.8Ghz, Im at a loss on what to do.. I've tried to make the chip POST and enter bios upto 52x and it can post.. I must be doing something wrong ? Im using bios F4.
All of this voltage is seen by CPU-Z as 1.2000v

Having the voltage set to auto also gives me 1.360 in bios and 1.3811 in realtemp but it shows about 1.068 something on CPU-Z

[Falkentyne]

You're using the wrong cpu-z. There is an updated 1.57.1 something that reads the vcore properly.. Your CPU-Z is showing the VTT. I don't think the updated cpu-z is on their page since it's beta...if you use the search, you may find it, but I know a link was posted a few weeks ago in the UD7 thread.

You're right about the DVID, it SHOULD be 1.41v, since it's VID+offset, but you're also getting vdroop.

Try setting a DVID of +0.08 instead of +0.05, and see if that helps. That should compensate for the vdroop.

Of course the proper answer would be to use LLC, but seems like you can't use LLC with dvid anymore....

[Falkentyne]

Im really confused about setting the voltages on this board, no matter what i choose I always see 1.381 VID under ReatlTemp 3.67.. How do I determine what voltage is actually getting fed to my processor?

I've mimicked the automatic voltages defined at 4.5Ghz which is 1.360 under bios, it fails if I manually type in voltages even with LLC.. I've also tried a +0.010 to +0.025 offset using "Normal" voltage and im still getting errors in prime95 smallFTT, pure auto makes it work.

Realtemp does NOT show vcore at all. VID is not the same as vcore.
It shows the VID which the processor tries to request as an "Auto" voltage.
Look for the updated cpu-z 1.57.1 beta, or use hwinfo32 to see the voltages.

[Demo]

You're using the wrong cpu-z. There is an updated 1.57.1 something that reads the vcore properly.. Your CPU-Z is showing the VTT. I don't think the updated cpu-z is on their page since it's beta...if you use the search, you may find it, but I know a link was posted a few weeks ago in the UD7 thread.

You're right about the DVID, it SHOULD be 1.41v, since it's VID+offset, but you're also getting vdroop.

Try setting a DVID of +0.08 instead of +0.05, and see if that helps. That should compensate for the vdroop.

Of course the proper answer would be to use LLC, but seems like you can't use LLC with dvid anymore....

I'll get a hold of that new CPU-Z, under the bios LLC can be enabled with DVID.. by using 0.080 i might hit the mid 80's since with +0.050 im getting 77-78c

EDIT:

Any power saving feature on this board that I can easily enable w/o any stability issues?

[Calathea]

Gaaaah so frustrating. This mobo has to be the least user friendly board ever. Got pi32m to loop 16 before it froze, now I can't boot with 2133 again.

[Mafio]

Gaaaah so frustrating. This mobo has to be the least user friendly board ever. Got pi32m to loop 16 before it froze, now I can't boot with 2133 again.

lol, welcome to the club