***Official***Z68X/P67A-UD7 Club/Discussion/Info**

[Kingleo]

I have posted this about 10 times now on different threads without a reply... I might be going in the wrong direction and just looking for some input.

IMO: P67/H67 was a stopgap with the intention of getting SB to retail faster.
With Z68 coming out right on the heels of the new production schedule for P67,
where is the market for these boards now?
With this kind of timetable, would you still want a P67 over a Z68? why?

[thebanik]

I have posted this about 10 times now on different threads without a reply... I might be going in the wrong direction and just looking for some input.

IMO: P67/H67 was a stopgap with the intention of getting SB to retail faster.
With Z68 coming out right on the heels of the new production schedule for P67,
where is the market for these boards now?
With this kind of timetable, would you still want a P67 over a Z68? why?

For starters Z68 would be a costlier platform overall.

[TheHardCase]

I have posted this about 10 times now on different threads without a reply... I might be going in the wrong direction and just looking for some input.

IMO: P67/H67 was a stopgap with the intention of getting SB to retail faster.
With Z68 coming out right on the heels of the new production schedule for P67,
where is the market for these boards now?
With this kind of timetable, would you still want a P67 over a Z68? why?

Quote: The chipset, which is said to include integrated Intel HD graphics with support for both digital and analogue outputs, is designed to offer performance overclocking features for Sandy Bridge processors.

The chipset will allow for 'performance over clocking of processor, memory, and processor integrated graphics,' with Intel clearly hoping to capture the performance enthusiast market with this revision.

Hope this helps...

[PatRaceTin]

I notice

my 2600K can bench @ 5.4GHz with 1866Mhz 8-8-8-24 @ 1.60V setting
<Kingston 2000C8 (elpida hyper)>


but It got BSOD @ 5.4GHz with 2133Mhz 9-11-9-28 @ 1.62V setting
<G.Skill 2133C9-11-9-28 @ 1.60V (PSC40nm)>

same setting

[Kingleo]

thanks..
just trying to figure out what to do when its time to replace this board. Thought z68 would make a good HTPC when 2011 is released.

[C-N]

I notice

my 2600K can bench @ 5.4GHz with 1866Mhz 8-8-8-24 @ 1.60V setting
<Kingston 2000C8 (elpida hyper)>


but It got BSOD @ 5.4GHz with 2133Mhz 9-11-9-28 @ 1.62V setting
<G.Skill 2133C9-11-9-28 @ 1.60V (PSC40nm)>

same setting

Try

CAS Latency Time 9
tRCD 11
tRP 9
tRAS 28

tWL from 7 to 8

All rest auto & std performance level @ 1.64v

If it works you can reduce vdimm & tighten things up.

[kbk_75]

I am still unable to update the BIOS on my P67A-UD7.

Qflash and FlashSPI say the BIOS file is invalid and @BIOS reads the BIOS file and then crashes. What do I do?

[C-N]

I am still unable to update the BIOS on my P67A-UD7.

Qflash and FlashSPI say the BIOS file is invalid and @BIOS reads the BIOS file and then crashes. What do I do?

You tried this version of @BIOS?

http://download.gigabyte.us/FileList...gbt_atbios.exe

[nijel]

idk mine scales just fine, maybe you are using it too much? you can't really expect 4.8ghz on auto vcore lol. It kinda hits a limit at 4.5ghz-4.8ghz for me. One of my chips does it fine at 4.8ghz the other wont at 4.5ghz. Of course you can just change the vcore but then the voltage doesn't scale.

Yeah, you are right. I'm just trying to 24/7 maximize the chip for my cooling setup. Wish we had more options to precisely control the voltage. I guess I'll settle down or try another board when the time comes. Unfortunately only UD7 has the features I need. They better tweak the LLC.

[Lanek]

I am still unable to update the BIOS on my P67A-UD7.

Qflash and FlashSPI say the BIOS file is invalid and @BIOS reads the BIOS file and then crashes. What do I do?

As said early, use @bios ver 2.1 and don't forget to remove the old and install the new one before flash ( or it will bring you back an error ) ( i have got the same crash with @bios before try to uninstall it and reinstall the good one ) ....


Anyway. someone tried the last F7f beta bios ?

[eva2000]

use this app and do it in windows

http://download.gigabyte.us/FileList...gbt_atbios.exe


once you flash it make sure you also copy this new bios to your backup bios by hitting ALT+F12 during PC startup

Ran into same problem http://i4memory.com/f90/gigabyte-p67...49/#post140444 - just a question guys @bios works fine in winxp right ?





Have yet to install windows xp heh

[Eldonko]

I use @bios in W7 and it is fine so i assume it will be ok for XP. The new one from GB I mean, the one on the disk doesnt work and q flash doesnt work. Bit of an oversight on that one I think.

[andressergio]

Ran into same problem http://i4memory.com/f90/gigabyte-p67...49/#post140444 - just a question guys @bios works fine in winxp right ?

yes eva it works on xp

[Lanek]

Ran into same problem http://i4memory.com/f90/gigabyte-p67...49/#post140444 - just a question guys @bios works fine in winxp right ?

Have yet to install windows xp heh

Should work, then you will be able to flash normally with Qflash ( it's really a F3 bios bug )


Just tried F7f bios, first funny thing is the Bclock who was set automatically at 99.8mhz with previous bios is now at 100.3mhz... the second thing is voltage drop seems lower ( without LLC ) and more stable ..

my setup is stable with my 24/7 settings for 5ghz, so i hope it overclock better or same of the F7f.

[kbk_75]

Thanks guys. I installed the newer version of @bios over the older one, which was a mistake. Uninstalled the previous version, installed the new version and managed to flash my bios to f7e, no problems at all.

[Lanek]

Thanks guys. I installed the newer version of @bios over the older one, which was a mistake. Uninstalled the previous version, installed the new version and managed to flash my bios to f7e, no problems at all.

No worry i have do the same the first time, and i was going crazy to search what happend.


Guys, i have a doubt on how i set the voltage if it's the soft CPUZ or Hwinfo who are buggy or me who set something wrong, i have some strange reading from thoses 2 softs.

Vcore: 1.5V in bios ( just for test purpose ) CPU PLL overvoltage enabled ( reported as 1.488 on windows )
LLC: auto
Multi: 50x
Turbo: Disabled
All other setting in AUtO ( EIST; C1 states etc )

HWinfo when idle :


CPUz when idle before and after test it( 1.488Vcore, normal with 1.5V set in bios )


HW info max load


CPU-z Max load




I believe this is just the software who are confused by the different voltage / different states and don't update it enough fast, so don't show the 1.488Vcore and they read not well the voltage. but i was ask me if the voltage set on max load is not using the "turbo one " or something like that.

[C-N]

@ Lanek

LLC Auto is giving you the same as standard, set it to level 1 to eliminate the droop although by the looks of it you have a nice chip that may only need 1.38v for 5GHz. The reason the voltage is not reduced at rest using the C states is because you have gone above vid. if you want it to reduce leave vid normal & + - voltage with the dynamic vid.

[Lanek]

Lol nice point: i understand now why i had so much trouble for stabilise at 54x multi ... my vcore was still too low even when i was up it. You just have save me from some future headache.

I have test it again, but this time with real time Vcore read...

LynX idle = 1.48V
bench start and vdrop occurs when clock raise
LynX Load = 1.38V
then the first run is complete, clock decrease and vcore reincrease to 1.48V

Little question anyway... as i don't remember the last time i have play with DVID, it's standard Vcore +0.1 +0.2 etc ? sorry i absolutely don't remember how work this setting.
.

( in addition, yes this chip is 2h Lynx stable with thoses settings, and many hour on different games ( im never enough patient for make run Prime or Lynx for 4-5hours lol )

[nijel]

Got new chip today, fourth in a row, second c-batch, and looks like this one scales Vcore perfectly:

Vcore = Auto, LLC = Level1

Clock         3.4GHz       4.7GHz
SVID          1.232V       1.356V
idle          0.984V       0.984V
13% load      1.200V       1.248V
26%           1.224V       1.284V
39%           1.236V       1.320V
51%           1.236V       1.344V
63-100%       1.236V       1.356V

Don't think this one gonna BSOD at low loads, but we'll see. So far so good. Next step - optimizing Vcore without braking the good scaling.
Glad it's not the board giving me troubles.

[OC Nub]

3dm05@ 5415, GTX460sli, lots of vcore



Uploaded with ImageShack.usmhz, GTX460 sli, lots of vcore

[andressergio]

3dm05@ 5415, GTX460sli, lots of vcore



Uploaded with ImageShack.usmhz, GTX460 sli, lots of vcore

jeeeze Tom thats so good

congraaaaaaaaaaaaatsssss my friend

[OC Nub]

Thank you.

[dinos22]

had the board not wanting to change bclock at all this morning. I flashed the bios again and it works fine now. If you see the board acting up a bit try flashing the bios just in case its corrupted (especially if you push the board crazy like some of us do hehehe)

[sin0822]

had the board not wanting to change bclock at all this morning. I flashed the bios again and it works fine now. If you see the board acting up a bit try flashing the bios just in case its corrupted (especially if you push the board crazy like some of us do hehehe)

yup i found this helped with memory clocks as well, for some reason my settings wouldn't stick so i flashed and it worked perfectly.

[Lanek]

I believe my board do it by itself, each time i push to far, freeze in 3Dmark11, reboot i got a niiice " Checksum error, can't load HPA, ..." reflash with backup bios ( 3third times tonight in 1 hour, )... ( sometimes even without OC )

What i have find is flash using @bios, then reflash using Qflash with the same new bios ( F7e or f ) ... look like it stabilise a bit the thing about this " auto reflash " .

If someone have a fix for this will be good ..

Anyway someone can indicate to me how use Dynamic Vid ? set to normal and then ? how work this value, it's SVID +0.20 voltage or Stock +0.xx or need use - 0.xx ) Don't want to come with 2Vcore or try boot with 0.4V.