Tom's Hardware Forums » Overclocking » General Discussions » Asus P5K-E OCing (0906 BIOS)
 

Asus P5K-E OCing (0906 BIOS)

Add a reply



 Word :   Username :  
 
Bottom
Author
 Thread : Asus P5K-E OCing (0906 BIOS)
 
Resident Jerk
Profile: Faithful Poster
More Information

http://i39.photobucket.com/albums/e189/cnumartyr/P5K-EOC.jpg

So these are the most basic settings for overclocking. And yes this is for people who have read the guide numerous times and have some idea of what they are doing.

http://i39.photobucket.com/albums/e189/cnumartyr/P5K-EOC2.jpg

The MOST important things to note for the upcoming 45nm is this. CPU VTT is changing to a stock of 1.1v and a maximum of 1.4v.

Other than that everything should be the same. I love the new BIOS and it's options.

The 0906 brings OFFICIAL support for 45nm for the P5K-E and a lot of fun new options. The ONLY draw back is the vDrop issue. It drops voltage as much as 0.11v from the BIOS setting. The maximum in the BIOS is 1.7v so you can still get in the high 1.5s-1.59ish.

Anyways.. Asus has a pretty simple BIOS.. I do like it.

Edit: Fixed First link.


Message edited by cnumartyr on 01-18-2008 at 10:22:06 PM

---------------
TeamBAG Member
Related Pr oduct
Register or log in to remove.

Master-de-bater
Profile: Eternal Poster
More Information

I am bothered by the Load-line calibration.

According to Anandtech, removing the Vdroop is a bad thing:

Quote :

The CPU VID setting establishes the absolute maximum allowable processor supply voltage experienced during transient conditions and is not the target idle voltage. We hope this statement draws attention to this important distinction, as many believe the opposite to be true - a mistake all too commonly made. Together, Vdroop and Voffset ensure that the peak CPU supply voltage seen during heavy to light loading changes remains well below the established maximum. If you determine that 1.17V, as in the case above, is not sufficient for maintaining CPU stability under load, simply increasing the CPU VID does correct the problem. Let's now examine how the system responds if we remove Voffset.



This means that Vdroop ensures that the CPU VID isn't exceeded.

Quote :

So what happens when we remove both Voffset and Vdroop? The answer is simple - bad things. Although the difference between the maximum positive and negative peak overshoot are the same, severe violations to the CPU VID limit occur. If you're asking yourself what's the problem with this, consider the case of a CPU VID of 1.60000V - because the user feels this is the absolute maximum CPU voltage that they will allow. Just how high do you think CPU voltage will go after leaving a heavy load condition? We can't be sure without knowing more of the details, but we can certainly conclude that it will be well in excess of 1.6V. If you've ever run a benchmark only to have your system crash right as it finishes then you have experienced the consequences of this poor setup.



Removing it is a terrible thing, apparently.

Quote :

Finally, let's take one last real-world look at the consequences of removing Vdroop. ASUS' implementation of this feature, labeled as Load Line Calibration and included with their latest line of motherboards, is particularly worthy of our attention for a number of reasons. The first is that setting lower voltages with this option enabled actually results in a condition in which the CPU voltage under load is higher than the idle voltage. Imagine our confusion as we desperately struggle to understand why our system is Prime95 stable for days yet continues to crash under absolutely no load. What's more, in spite of the absence of droop and for reasons unknown, enabling this feature artificially raises our CPU's minimum stable core voltage at 4.0GHz from 1.28V to about 1.33V. As a result, our system uses more power under load than is otherwise necessary. Our efforts to reduce our processor's supply voltage backfired - instead of lowering the system's total power consumption we managed to affect a 20W increase.



Finally anandtech points out the load line calibration is a bad thing.

Source: http://www.anandtech.com/cpuchipse [...] i=3184&p=5

So what's what?


---------------
"Nvidia, the Way It's Meant to be PAID Played! - Corrado
*Lesbian Lover Club* - founder Assman
Resident Jerk
Profile: Faithful Poster
More Information

Considering that on this BIOS when I set the VID to 1.525 in the BIOS and I get 1.416 in Windows and a drop to 1.400 during Load, I think it will be ok.. and not spike over VID.

In addition, I've known plenty of people who pencil mod and remove vDroop all together.

Also- LoadLine Calibration is different on the P35 and X38 (I think). Previously it was known as the Voltage Damper on the P35. Either way I've never noticed it having a bad effect on my CPU or board.


---------------
TeamBAG Member
Master-de-bater
Profile: Eternal Poster
More Information

So Vdroop is a bad thing? :??:


---------------
"Nvidia, the Way It's Meant to be PAID Played! - Corrado
*Lesbian Lover Club* - founder Assman
Resident Jerk
Profile: Faithful Poster
More Information

Evilonigiri wrote :

So Vdroop is a bad thing? :??:



Lol... I think it's overstated so much in the OCing world.

12-24mV is nothing to worry about.

When I was getting 48-100mV vDroop on my DFI I was worried.

vDroop is a normal and intended part of the motherboard. I use LoadLine because it is there. It was implemented by Asus engineers and said to be safe by people smarter than I at Asus.

I think people just like keeping voltages low, and the points we run at it's tough if it droops too much under load. I need 1.400 to be stable under load at 3.6 GHz. If I was having to set it at 1.45 volts I wouldn't be happy. Luckily I only have a 16mV Droop.


---------------
TeamBAG Member
Master-de-bater
Profile: Eternal Poster
More Information

Quote :

With Load Line Calibration disabled in BIOS, setting a CPU Voltage VID of 1.38750 resulted in a no-load voltage of about 1.34V and a full-load value of 1.28V. Enabling this feature and lowering the VID to 1.35000V produced a constant CPU supply voltage, regardless of load (or so it seemed), of 1.33V. Setting a lower VID resulted in a blue screen during Windows boot. Idle voltage was relatively unchanged at about 1.33-1.34V but the full-load voltage required increased by 50mV with no benefit. As you might guess, we recommend you leave this option disabled.



Quote :

Hopefully we've shown you enough to understand exactly why Voffset and Vdroop are important. Please give second thought to your actions if you're in the habit of defeating these essential system safeguards.



After all of the explanation and all, they concluded with the statement above.

Argh I'm so confused!

Without the load line calibration, you're VID would be higher? But because of the Voffset and Vdrop, the true voltage should be lower anyways right?


---------------
"Nvidia, the Way It's Meant to be PAID Played! - Corrado
*Lesbian Lover Club* - founder Assman
Resident Jerk
Profile: Faithful Poster
More Information

Evilonigiri wrote :


After all of the explanation and all, they concluded with the statement above.

Argh I'm so confused!

Without the load line calibration, you're VID would be higher? But because of the Voffset and Vdrop, the true voltage should be lower anyways right?



Nah... Load Line just eliminates some vDroop.

VID - vOffset (vDrop)= Windows Idle Voltage (WIV).
WIV - vDroop = Windows Load Voltage (WLV).

Your processor has to be stable at 100% or WLV...

I kind of look at it like this.. Ok.. VID is the max you want the processor to go to. The stock VID on my chip is 1.2875. I'm already running 1.416 so it's already over the VID.

What Load-Line and Pencil mods do is move the spike up basically. Instead of occuring from a lower voltage and spiking to the VID it starts higher and spikes over the VID. I'm not really concerned about this.. it's not spiking to 1.9v..

So let's say you set up this, assuming a 34mV Vdrop and 50mV vDroop, needing 1.400 volts to be stable at 3.6 GHz.

1) Without LL Cal: 1.400 Load and 1.450 Idle and 1.484 VID.
2) With LL Cal: 1.400 Load and 1.416 Idle and 1.45 VID.

In case 1 the voltage might spike to 1.47 volts. It never went over the VID though, right? In case two it spikes to 1.47 volts, but it passes the VID... What's worse?


---------------
TeamBAG Member
Master-de-bater
Profile: Eternal Poster
More Information

Oh now I get it. Thanks bunch cnumartyr!

So basically you just don't want the VID so high, that it right?

Oh and before I meant Vdroop, not vdrop.


---------------
"Nvidia, the Way It's Meant to be PAID Played! - Corrado
*Lesbian Lover Club* - founder Assman
Resident Jerk
Profile: Faithful Poster
More Information

Evilonigiri wrote :

Oh now I get it. Thanks bunch cnumartyr!

So basically you just don't want the VID so high, that it right?

Oh and before I meant Vdroop, not vdrop.




Kind of.. I meant it's going to take the same voltage to get something stable. The question (in my mind) is how high the voltage has to go after the Droop during idle conditions. The less the theoretical better.

It's going to spike all the same from load to unload.. but who cares? It might go over the VID, but we're already WAY over the VID.. :kaola:


---------------
TeamBAG Member

Go to:
Add a reply
  Tom's Hardware Forums » Overclocking » General Discussions » Asus P5K-E OCing (0906 BIOS)
 

Google Ads
Ad