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

[dinos22]

hey peeps

i got a few bios updates for UD4/5/7 which should sort this S3 multiplier dropping to 35x after exiting sleep mode

give it a crack

I tested UD7, it works, just enable S3 in bios

http://filefactory.com/file/b5167da/n/Desktop.zip

[dinos22]

my bclock also went to 107mhz from 104 with new bios

[wekktor]

what does pll override do? I have it disabled, why should I enable it? Thx!

[Gaul]

One site/person's opinion?

yup....

[OldChap]

anyone explain ?

Sandybridge maximum safe voltages

Core Voltage - Not recommended too exceed 1.38v, doing so could kill the CPU, we therefor recommend a range of 1.325-1.350v if overclocking.
Memory Voltage - Intel recommend 1.50v plus/minus 5% which means upto 1.58v is the safe recommended limit. In our testing we have found 1.65v has caused no issues.
BCLK Base Clock - This is strictly a NO, anyone using base clock overclocking could/will cause damange to CPU/Mainboard. (Set manually to 100)
PLL Voltage - Do not exceed 1.9v!!

here : http://forums.overclockers.co.uk/sho...3#post18190523

These numbers are all derived from the intel spec (data)sheet

[danielkza]

These numbers are all derived from the intel spec (data)sheet

There's nothing on the datasheet about safe core voltages.

[dinos22]

that website is just pulling it out of its arse without any real world testing it cannot be concluded that this or that voltage is safe, Intel limits didnt mean with any other gen of product, it's actual user testing here and other forums that really tells the story anyways

time will tell

[godsfist]

With AHCI enabled I freeze during the reboot process at "detecting IDE drives" on both F6 and F7B?

(I've already set start in msahci to 0 with regedit)

Didn't come across this with F3, annoying

[stasio]

With AHCI enabled I freeze during the reboot process at "detecting IDE drives" on both F6 and F7B?

(I've already set start in msahci to 0 with regedit)

Didn't come across this with F3, annoying

Try F7f.

[godsfist]

Boot with AHCI is still not perfect, sometimes with BIOS F7f (UD4) computer detect AHCI and is restarted.

Sounds like F7f is not up to it either.. oh well there's always F8

[stasio]

Sounds like F7f is not up to it either.. oh well there's always F8

Yeah,but after F7.

[Jupiler]

Guys,

I'm having serious problems with this board and I need some help.
I bought the board last week, along with a 2600k.

Since I installed it on wednesday, my board is acting weird (it's the least I can say).

The major problem is that it won't hold the VCore.
The board came with bios F3. After installing everything normally, I checked voltages in both bios and windows (using HWINFO, CPU-Z and ET6).

My cpu has these VID's at specific speeds :
3400Mhz : 1.225V
3500Mhz : 1.245V
3600Mhz : 1.275V
3700Mhz : 1.300V
3800Mhz : 1.325V
3900Mhz : 1.335V
4000Mhz : 1.340V
4100Mhz : 1.340V
4200Mhz : 1.340V
4300Mhz : 1.345V
4400Mhz : 1.355V
4500Mhz : 1.360V
4600Mhz : 1.360V

Now here's the problem.
After the first start, the bios reads the default VCore at 1.212V, which seems normal.
After booting into windows, VCore drops at various voltages, I've had 0.972V or 1.140V etc.... (this is to make a long story short).
Now, after a restart, the bios reads the same VCore as in windows, which seems kinda weird to me.
So, after, f.e., ET6 or CPU-Z read 0.972V, the bios, after a reboot, would give the same readings.

I went from bios F3 to F6, then F7b, F7f, then back to F3, now on F2, but the problem won't go away.

Here's an example with pics and screenshots (taken yesterday):

After reboot, VCore in bios reads correctly 1.224V :



Other settings in bios :



Then I booted into windows, and VCore drops to 0.972V (idle and load)



As you can see, VCore doesn't change at all and stays at 0.972V.

After a reboot, you can see that the bios reads the same voltage as in Windows, 0.972V



Then, I set Vcore manually at 1.320V :



But as you can on the pic below, Vcore still stayed at 0.972V :



I'm getting very frustrated with this board and I'm wondering what's causing this problem.
I reinstalled the CPU this afternoon, cleared CMOS and others, but the problem won't go away.

I'm considering returning the board and have it checked, unless the problem might be resolved very soon.
My first board upgrade in 2 years (coming from S775) and now this crap happens to me.

Anybody out here who might help me out?

[Gaul]

Then, I set Vcore manually at 1.320V :



But as you can on the pic below, Vcore still stayed at 0.972V :

well, must bad board i quess
rma it m8

this when i set manually 1.3200, with LLC enable

[simonmaltby]

I'm having a similar issue I think... My UD4 will not accept any change to vcore. I have come to the conclusion it's a bad board. so it's going back.

[[XC] Hicks121]

Guys,


Anybody out here who might help me out?

Hey big brother! You need to disable the last 5 settings on this bios screen. You have c1e & eist enabled.

[Jupiler]

Thx buddy,
but I tried every possible setting on this board since I got it.
The board simply hasn't worked correctly since day 1.
Already called the store and informed them about the problem.
They'll have it checked and I'll probably get a new one (as this is only a couple of days old).

[[XC] Hicks121]

Thx buddy,
but I tried every possible setting on this board since I got it.
The board simply hasn't worked correctly since day 1.
Already called the store and informed them about the problem.
They'll have it checked and I'll probably get a new one (as this is only a couple of days old).

Well that sux balls! When you get a new one, let me know if you need any help. I got this board down pat now. She is screaming along @ 47 x 100 with 1.4v in bios, running WCG @ 1.392v. Temps are topping out @ 55c on my h2o system.

[Jupiler]

Thanks my friend, much appreciated.

I noticed something weird earlier.

As I said before, the bios or windows wouldn't hold the VCore and after a reboot, the bios would report the same Vcore voltage as in windows.

Now, after I changed a setting and saved the settings, the system would sometimes shut down and reboot after a couple of seconds (mostly when changing C1E/EIST settings, or Isochronous "whateveritscalled")
After the reboot, the bios would give me the correct voltage (vcore set at Normal, DVID at AUTO or Normal).
Unfortunately, windows wouldn't and still report wrong voltages.

I had to repeat this, so the bios would read the correct voltage after another reboot.
Weird, but nothing I'm gonna worry much longer anymore.
The board is going back on wednesday.

If they give me a new board, I'm not sure if I would take another UD4. or try something else.
We'll see.

[dinos22]

uninstall ET6 in windows and clear cmos and follow these steps and see if it still does it please

http://www.youtube.com/watch?v=8ngyUrjuQ80

assuming your ram can run those clocks or drop the ram ratio lower if cant

### MB Intelligent Tweaker ###

Advanced Frequency Settings:

CPU Clock Ratio .......................................[ 45

> Advanced CPU Core Features

CPU Clock Ratio .......................................[ 45
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 ........................[ 1003
System Memory Multiplier (SPD) ........................[ 18.66

Advanced Memory Settings:

System Memory Multiplier (SPD) ........................[ 18.66
Performance Enhance ...................................[ Turbo
DRAM Timing Selectable (SPD) ..........................[ Auto
Channel Interleaving ..................................[ Enabled
Rank Interleaving .....................................[ Enabled



Advanced Voltage Control:

CPU

Load Line Calibration .................................[ Level 1
CPU Vcore .............................................[ 1.35
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.8

DRAM

DRAM Voltage 1.500v ...................................[ 1.66
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

[simonmaltby]

Thanks for this post dinos22.... I have had a go with your settings and my own issue remains.

I think my issue is different to others and I'm certain it must be a hardware fault. I have ordered another board which will be here tomorrow.

My issue is that any alteration to vcore will cause a bizarre result....
This is what I do, although I have tried many variations / bioses etc.

Clear CMOS for a nice fresh setup
Boot to Bios
Check settings (turbo and vcore) these show 1.188v vcore or 1.220 in the advanced voltage page (AUTO). Board reports Boot at 34 and Turbo at 35 - All as it should be.
Alter vcore (Tried all sorts but say 1.35v).
F10 and save - then re-boot
Comes back fine, but Vcore now reports as 0.98v and Board reports Boot at 34 and Turbo at 16???? WTF
If I then do F10 and save again... board will go into a power on and off cycle with no beeps or VGA

Just to add that if i leave Vcore on Auto and LLC to Enabled it works ok I can set turbo at 50 and boot into windows where vcore is reported as 1.38v
The chip will do 5.3+ on an asus P8P67 but needs 1.45 - 1.5v hence why i want to set the vcore manually.

[aytacaksel]

Thanks for this post dinos22.... I have had a go with your settings and my own issue remains.

I think my issue is different to others and I'm certain it must be a hardware fault. I have ordered another board which will be here tomorrow.

My issue is that any alteration to vcore will cause a bizarre result....
This is what I do, although I have tried many variations / bioses etc.

Clear CMOS for a nice fresh setup
Boot to Bios
Check settings (turbo and vcore) these show 1.188v vcore or 1.220 in the advanced voltage page (AUTO). Board reports Boot at 34 and Turbo at 35 - All as it should be.
Alter vcore (Tried all sorts but say 1.35v).
F10 and save - then re-boot
Comes back fine, but Vcore now reports as 0.98v and Board reports Boot at 34 and Turbo at 16???? WTF
If I then do F10 and save again... board will go into a power on and off cycle with no beeps or VGA

Just to add that if i leave Vcore on Auto and LLC to Enabled it works ok I can set turbo at 50 and boot into windows where vcore is reported as 1.38v
The chip will do 5.3+ on an asus P8P67 but needs 1.45 - 1.5v hence why i want to set the vcore manually.

if your chip able to hit 5.3ghz at 1.5v thats great. i can suggest some settings.

first enable all thermal functions c1/c3/c6/eist etc.
set blck 1002.
disable turbo boost.
enable internal pll overvolt.
keep ram 1333mhz and standard performance
set multipler 50x for now.
enable llc for now.
all voltages auto except vcore and dvid.
set vcore normal (not auto)
set dvid (1.500v - normal vcore voltage in bios), if your normal vcore is 1.365v at 50x. set dvid +0.135v. (normal vid + dvid = 1.500)

use dvid to adjust %100 load vcore. monitor with cpuz.

your vcore now dynamic. when cpu is idle cpuz or hwmonitor will report 0.900v and 16x. at %100 load you will see ~1.5v vcore.

use intel burn test for %100 load not prime.

[Lanek]

Not as i really care or it's a break deal for me, but do you know if the UD7 ( or other models ) will get EFI bios in future ( or the dual bios don't allow it on gigabyte ?

[simonmaltby]

set vcore normal (not auto)
set dvid (1.500v - normal vcore voltage in bios), if your normal vcore is 1.365v at 50x. set dvid +0.135v. (normal vid + dvid = 1.500)

This will cause the Turbo / vcore issue and just cycle power on boot.
Any adjustment to vcore or dvid causes the issue.

As I say I think it's hardware

[aytacaksel]

how many time cycle? did you try wait for 5 minute? sometimes thats happen and will be fixed when you stop change bios settings.

please try wait 5 minute at least if boot fail try drop multipler abit

[simonmaltby]

how many time cycle? did you try wait for 5 minute? sometimes thats happen and will be fixed when you stop change bios settings.

please try wait 5 minute at least if boot fail try drop multipler abit

With F3 Bios it never comes back, waited nearly 20 minutes. F7b does come back eventually with overclocking failed and then proceeds to revert the Bios back to F3
This happens with everything at stock too... so lowering multi is worthless