ASUS P8P67 Pro/Evo/Deluxe OC discussion thread

[dany74q]

Asus have finally put the 1305 bios in their servers , though I hear there are several problems .
Should one update the deluxe from 1254 to 1305 ?

[Leeghoofd]

the answer is simple : Do you have problems now ? if not do not update... if so give it a try...

[dany74q]

No problems , but if it enhances the oc capabilities as it says - would be nice to go higher than 4.8 for 24/7 .

[Leeghoofd]

Beleive me the OC is CPU and not board limited... it finally solved the Cold booth with my sabretooth, Dlx performance seems on par... CPU still tops out at 4.7 daily ( heat) and 5.2 when benching...

[some_one]

No problems , but if it enhances the oc capabilities as it says - would be nice to go higher than 4.8 for 24/7 .

I could be wrong but AFAIK the enhancement (4.) in 1305 is to set C3/C6 to disabled when set for auto. You can easily set them yourself to disabled manually in previous versions if it helps but expect higher idle temps/power.

Description 	P8P67 Deluxe 1305 BIOS
1. Enable the display of Intel PCH revision BIOS Setup Screen for the ease of recoginization for B3 stepping chipset.
2. Enable support for ROG BIOS Print
3. Enhance SAS card compatibility
4. Enhance auto rule for better performance.
5. Support new version AI-SuiteII(must work with new AI-SuiteII)
6. Enable support for onboard Bluetooth disable capability.
7. Enable support of "Wait For 'F1' If Error" option to allow user to ignore BIOS warnings during POST.
  	

Version 1204
Description 	P8P67 Deluxe 1204 BIOS.
1. Reduce boot time if clear RTC.
 
  	
Beta Version 1053
Description 	P8P67 DELUXE 1053 BIOS
1. Enable support of "Internal PLL Overvoltage" item to allow better CPU Turbo Ratio overclock capability with D2 Stepping processors.


Version 1003
Description 	P8P67 DELUXE 1003 BIOS
1. Update CPU ratio item to allow automatic activation of Intel Turbo Boost when CPU Ratio is above the Intel specification.
2. Enhance PCH native SATA performance.
3. Enhance USB 3.0 / PCIE performance.
4. Enhance USB 3.0 compatibility under BIOS setup screen.
5. Enhance USB compatibility.
  	

Version 0804
Description 	P8P67 DELUXE 0804 BIOS
First release Bios

[ZenEffect]

**WARNING*** FLASHING BIOS IS AT YOUR OWN RISK, DO NOT TRY TO BACK FLASH TO ON B3 BOARDS WITH EARLIER BIOS THAN THE BOARD WAS SHIPPED WITH

backflashing procedure for all asus p8 series boards with AMI EFI bios

download
http://www.ami.com/support/downloads/amiflash.zip

use the utilities in the aptio folder. i used the x64 win flash cuz im lazy but it works. remember to program all blocks. might get an error verifying the blocks during the last segment, but it will reboot. just re-flash via ez-flash after.

FYI I did brick my board flashing from 1253 to 1305 in EZ FLASH. I do not know if this is a side effect of the previous back flashing so this is all at your own risk (i have a chipmax2 so flashing a bad bios is no prob for me.. board is alive and kicking)

[danielkza]

Same RAM, same issues. P8P67 isn't the board I had hoped it to be. Will be RMA'ing for a GB UD4 B3 next week.
Crazy motherboard

I'd probably have picked up an Asrock or Biostar board to save myself some money if I new I'd be having so many problems

@l0ud_sil3nc3:

I had settled for very similar settings (2133 8-10-8-28 1.65V) until I found out that reboots would fail if I shut down right after stressing the RAM (ex: starting Prime95, letting it run for some minutes, rebooting = failed boot with hang @ DRAM LED).

So I decided to do some more testing, and then I ran into the tRCD problem. Can you try booting DDR3-2133 @ tRCD 9 (I could reproduce the problem even after relaxing other timings quite a bit) and see if anything like what I experienced happens? That way I'd rule out a problem exclusive to my board.

[Godmyster]

So are the P8P67 Pro having ram issues? becauase im thiking of going for the P8P67 Normal version.

Still dont know what ram to go for atm.

[danielkza]

So are the P8P67 Pro having ram issues? becauase im thiking of going for the P8P67 Normal version.

Still dont know what ram to go for atm.

I don't believe there are enough significant differences between the (regular) P8P67 and the PRO that would make the problem exclusive to the latter. You'd have to wait for someone with a similar kit and a P8P67 to confirm it tough.

[danielkza]

Does anyone else find Offset Mode kind of useless? It is nice because the vCore can lower while idle, but the voltage for single-threaded loads is over 0.1V lower than for multi-threaded ones, which makes my life quite a bit harder.
My CPU is stable for 20 passes of LinX with AVX @ 4.8GHz, offset +0.1V (~1.4V on load, LLC off), but if I switch from 4 to 1 thread, I get a fail at the second pass. I'd need to raise the offset way more than I'd like to get full stability.

[jcniest5]

**WARNING*** FLASHING BIOS IS AT YOUR OWN RISK, DO NOT TRY TO BACK FLASH TO ON B3 BOARDS WITH EARLIER BIOS THAN THE BOARD WAS SHIPPED WITH

....remember to program all blocks...

By "ALL" blocks, you mean use options /P /B /N /E all together or just use the single /K?

[some_one]

the voltage for single-threaded loads is over 0.1V lower than for multi-threaded ones

The Sandy Bridge VID does seem to work differently than the older generation in that with loaded cores it can increase. For instance if I run Linx/AVX @4.6GHz, VID will be 0.03V higher with 4 cores than running on just one core or one thread. If your using Regular LLC ie standard Intel spec, then the loadline drop should be much more than 0.030V with 4 cores vs one core meaning your Vcore should be higher for one core than 4 cores. Sounds like something weird is going on if your seeing 0.1V less with one core vs 4 cores.

If you had LLC set to Ultra High or maybe High even, then it might be possible that there could be less Vcore for single threads. LLC is set to auto and not Auto right?

You seem to have a high offset 0.1V are you not using the extra turbo VIDs? If not, give them a go and see if it makes a difference but please make sure your old offset you put in is reduced, say to 0.010V. If you have a really good chip you might even be able to use a negative offset depending how high you want to OC.

[danielkza]

The Sandy Bridge VID does seem to work differently than the older generation in that with loaded cores it can increase. For instance if I run Linx/AVX @4.6GHz, VID will be 0.03V higher with 4 cores than running on just one core or one thread. If your using Regular LLC ie standard Intel spec, then the loadline drop should be much more than 0.030V with 4 cores vs one core meaning your Vcore should be higher for one core than 4 cores. Sounds like something weird is going on if your seeing 0.1V less with one core vs 4 cores.

If you had LLC set to Ultra High or maybe High even, then it might be possible that there could be less Vcore for single threads. LLC is set to auto and not Auto right?

You seem to have a high offset 0.1V are you not using the extra turbo VIDs? If not, give them a go and see if it makes a difference but please make sure your old offset you put in is reduced, say to 0.010V. If you have a really good chip you might even be able to use a negative offset depending how high you want to OC.

I had completely ignored the 'Additional Turbo Voltage' option thinking it was only meant to be used with Auto voltage. I had not experienced much with LLC as I thought it wouldn't make much sense with offset mode, but I'll try more combinations now.

Thanks for the input, SB is kind of alien to me considering I only OC'd on LGA775 before

[McLaren__F1]

Heres my ASUS RMA status

[ZenEffect]

By "ALL" blocks, you mean use options /P /B /N /E all together or just use the single /K?

p/b/n/c but i used the win flash utility thats packaged with it and its just a check box

[LagunaX]

Been using bios 1305 and the resume from sleep issue with PLL overvolt on is still there.
Still no fix yet?

[danielkza]

Been using bios 1305 and the resume from sleep issue with LLC overvolt on is still there.
Still no fix yet?

You mean PLL overvoltage? I remember reading somewhere Intel is the only one that could fix it. They said it's a 'documented problem', but they offered no timeframe for when it's getting fixed.

[LagunaX]

So there are other boards out there by Gigabyte, Biostar, MSI, etc. that can hold say a 4.8-5.0ghz overclock and resume from sleep just fine unlike Asus then, huh?

[danielkza]

So there are other boards out there by Gigabyte, Biostar, MSI, etc. that can hold say a 4.8-5.0ghz overclock and resume from sleep just fine unlike Asus then, huh?

Only if you're lucky enough to get a CPU that can do that without PLL OV. And I retract my last statement, apparently Intel does plan to fix sleep with PLL OV. someday. But until they provide the updated microcode/firmware/whatever, there's not much board manufacturers can do about it.

http://hardforum.com/showthread.php?t=1579942

[Peter949]

Heres my ASUS RMA status

Same for me. Hoping I get 1204 bios in my b3. Not liking 1305.

[Falkentyne]

Only if you're lucky enough to get a CPU that can do that without PLL OV. And I retract my last statement, apparently Intel does plan to fix sleep with PLL OV. someday. But until they provide the updated microcode/firmware/whatever, there's not much board manufacturers can do about it.

http://hardforum.com/showthread.php?t=1579942

Yeah,well people should know better than to complain and want to switch motherboards because of S3 sleep not working when overclocked.

You would think four years of this would teach people a lesson...But I guess not.

Computers are *designed* to be used at stock speeds, and sleep was designed as a stock feature. Overclocking is a bonus, not a right. Manufacturers TRY to cater to us as best they can, but S3 has ALWAYS been problematic on overclocked systems. That's why Intel is in no hurry to fix something like this. They have far more important things to do on the queue list...when you're using PLL Overvoltage, you're running OUTSIDE the specifications of the system; it's not something that is exactly warranted (guaranteed). PLL is already erratically stable enough as it is, without throwing S3 into the picture.

Back in the core 2 days, there were problems with computers locking up from sleep, due to the chipset straps resetting and causing the RAM timings to be completely out of specification for the FSB (which was why the boards refused to resume; think of trying to run CAS 3 at 1000 mhz to see how that easily happens). This was later fixed in many boards, but in some cases it took months, in others, a year or more.

Now, something like VT-D, I can understand, since that's a non-K advertised feature that is SUPPOSED to work at all times...that I can relate to...

[danielkza]

Yeah,well people should know better than to complain and want to switch motherboards because of S3 sleep not working when overclocked.

You would think four years of this would teach people a lesson...But I guess not.

Computers are *designed* to be used at stock speeds, and sleep was designed as a stock feature. Overclocking is a bonus, not a right. Manufacturers TRY to cater to us as best they can, but S3 has ALWAYS been problematic on overclocked systems. That's why Intel is in no hurry to fix something like this. They have far more important things to do on the queue list...when you're using PLL Overvoltage, you're running OUTSIDE the specifications of the system; it's not something that is exactly warranted (guaranteed). PLL is already erratically stable enough as it is, without throwing S3 into the picture.

Back in the core 2 days, there were problems with computers locking up from sleep, due to the chipset straps resetting and causing the RAM timings to be completely out of specification for the FSB (which was why the boards refused to resume; think of trying to run CAS 3 at 1000 mhz to see how that easily happens). This was later fixed in many boards, but in some cases it took months, in others, a year or more.

Now, something like VT-D, I can understand, since that's a non-K advertised feature that is SUPPOSED to work at all times...that I can relate to...

Maybe I'm lucky, but in my admittedly short overclocking experience, I had no problems with S3.

My MSI P45 Neo-F woke up from S3 at least a couple times every day for 2 years while OC'd without major problems (it would hang if you woke it up right after sleeping, but it happened at stock speeds too), and so far my P8P67 PRO has been flawless @ 4.7GHz.

But (there's always a but), I'm on air, and hit my cooling limits already. If I were WC'ing I'd definitely be at least annoyed if I had to choose between S3 and the maximum attainable clocks. It's probably not fair to complain (as you mentioned, PLL overvoltage is definitely on the unsupported side of things), but this is XS, we won't put up with compromises without at least throwing a couple of (metaphorical) punches around

[Falkentyne]

Well I'm not saying people shouldn't complain (since that's what gets stuff added that we want. Just think it was just a few years ago that we didn't have CMOS reset BUTTONS on high end boards yet). I guess I mean them saying they're "fed up" and jumping ship to a different board that OTHERS are jumping ship away from, to the board that the first person is leaving...~_~

Seems like the only board that is performing absolutely flawlessly for everyone (besides defective boards) is the Maximus IV Extreme....Perfect LLC (measured with DMM) at 75%...except you PAY for that...big time...zero problems compared to what is affecting the P8P or GB boards...

Take out 1 of the PCIE x16 slots, throw a PCI slot on it and lower the price by 75, and I'd be making love to that board in bed, dressed as a significant other....

Heck, just throw an onboard X-fi like on the GB Assassin, and I'll even remove one of my packages for that board !!!

[fasterklander]

I just installed my new P8P67 EVO and updated BIOS from 804 to 1305 but never Boots on with OC.
I will reset and enter BIOS again and save config.

It runs at 5Ghz on AIR with 1.43v stable and 2133 for memory.

I'm now at 4.5Ghz ant 1.3v, but it don't Boot 1st time, :S

I don't like that every time that I start the system, I have to turn it off and turn on again, enter BIOS, save and exit.

Can ASUS solve it please ?

Any BIOS boot 1st time with OC¿?

Regards ^^

[tentp0le]

I just installed my new P8P67 EVO and updated BIOS from 804 to 1305 but never Boots on with OC.
I will reset and enter BIOS again and save config.

It runs at 5Ghz on AIR with 1.43v stable and 2133 for memory.

I'm now at 4.5Ghz ant 1.3v, but it don't Boot 1st time, :S

I don't like that every time that I start the system, I have to turn it off and turn on again, enter BIOS, save and exit.

Can ASUS solve it please ?

Any BIOS boot 1st time with OC¿?

Regards ^^

Try to enable "Power up by: PCIE" - this has solved it for me and many other since it was posted for the first time by an ASUS Tech.