ASUS P8P67 Pro/Evo/Deluxe OC discussion thread

thank you crossg :)
would really love it if you could point me to that thread too if its not too much of a bother searching for it :)
will try what you suggested for sure..
thank you again :up:

Quote:

---

Originally Posted by Toolius

thank you crossg :)
would really love it if you could point me to that thread too if its not too much of a bother searching for it :)
will try what you suggested for sure..
thank you again :up:

---

This thread post 485. Click here

I just found it too :)
but thank you sooo much.. really appreciate it :)
i hope this fixes it :)
woooottt

Quote:

---

Originally Posted by crossg

This thread post 485. Click here

---

it´s not really working for me. i can run 1m without problems, but 32m always crashes at step 21.. but i am on vista 64.. i think it´s again an os problem, casue on XP i have no problems at all. :)

ok i think its getting better atleast.. thank you crossg !
i did what you said but i was still getting instant restarts. so then i upped VCCIO to 1.25v for my super talent 2000 c7 hyper (running right now at 1866 -8-8-8-24) as well as upped my upped my vrm frequency from 350 to 380 and it ran a few passes instead of just restarting instantly.
Then i upped my vrm frequency to 500 and it ran !!!
so i got i first run at 5.3ghz finallyyy !! woooottt
so here are my settings...
Cpu multi - manual - by per core - 53-53-53-53
Vcore 1.52
Dram - 1.65v
VCCIO - 1.25
Vrm Frequency - 500
phase control - manual - ultra fast

so thank you crossg .. :up:
will try some more but im just soo happy i got 1 full run. Untill now it would just shut down as soon as i hit calculate on super pi 1M and my vcore was over 1.5v .

Quote:

---

Originally Posted by rjkoneill

thats pretty much my summary there

offsets is screwed. would be good if they did it like the gigabyte AM3 boards where they show you the eventual vcore with the offset value taken into account.
either way im back on manual vcore settings which is a crying shame as i wanted it settling at 1v at idle.

im not having much luck with this board so far. :(

---

my Gigabyte P67A-UD4 had proper offset too. it actually shows the proper vcore next to it, and lets you set "auto" "normal" or minus/plus and actually works right.

and I wish they would provide more info on what the phase controls *really* do, like with gigabyte they show you the pistons moving so you can see how many phases are active. but we just get regular, medium, fast, ultra fast. and then more ambiguous standard, optimized, extreme. what's the difference between Extreme and Manual: Ultra Fast anyways?

Quote:

---

Originally Posted by LeetMiniWheat

my Gigabyte P67A-UD4 had proper offset too. it actually shows the proper vcore next to it, and lets you set "auto" "normal" or minus/plus and actually works right.

and I wish they would provide more info on what the phase controls *really* do, like with gigabyte they show you the pistons moving so you can see how many phases are active. but we just get regular, medium, fast, ultra fast. and then more ambiguous standard, optimized, extreme. what's the difference between Extreme and Manual: Ultra Fast anyways?

---

Extreme = All phases on all the time
T.Probe = Some phases are shut down based on temperature
Manual = Some phases are shut down based on current. Ultra Fast means the phase count is as sensitive as possible to increases in current.

(all that is my personal opinion, based on the info on the manual and BIOS)

i'm confused about phase controls..

looks T.Probe is great option for overheating but what about phase control?
extreme or manual+ultra fast?

extreme = more temp?
manual+ultrafast= a risk of cant open/close phase fast enough so blowup a phase or cpu?
whats max vrm heatsink temp for 7/24?

:confused: :confused: :confused: :confused:

Quote:

---

Originally Posted by aytacaksel

manual+ultrafast= a risk of cant open/close phase fast enough so blowup a phase or cpu?

---

Definitely not, the worst possible thing that could happen would be instability, not any damage to the CPU or the phases. In theory (unfortunately I can't think of any scientific way to test it on practice) Manual + Ultra Fast should be the best setting for 24/7 OCs: you get very fast response to current bursts, but still save some power and strain on the VRM.

Quote:

---

Originally Posted by Splave

anyone succesfully using 2133 at 7-8-7 7-9-7 or even 8-8-8? boots windows but wont 32m at all

---

I booted xp with my stt 2200 c8 at 2133 7-7-7-21 and was able to run 1M and thats about it:down:

32m locked up right away and I tried up to 1.76v

Guys i cannot run sli on this board P8P67-Deluxe :confused:. Any ideas how to make SLI work ?

Quote:

---

Originally Posted by chispy

Guys i cannot run sli on this board P8P67-Deluxe :confused:. Any ideas how to make SLI work ?

---

Do u use Win7 SP1? If yes, pls go back to vanilla Win7 and install the SP1 pack separately. I've found this works for my MIVE, SLI just wont work on stripstreamed win7 SP1.

I see the pro/evo/deluxe boards got a new bios on asus' website, but not the sabertooth...... what gives? Anyone know of a beta bios possible that is better then this damn 1305?

Quote:

---

Originally Posted by l0ud_sil3nc3

I booted xp with my stt 2200 c8 at 2133 7-7-7-21 and was able to run 1M and thats about it:down:

32m locked up right away and I tried up to 1.76v

---

my ADATA XPG+ v2.0 2200C8 needs 1.825v vdimm, and 1.2875v to pass 32M at 2133 7-8-7-24-1T-74.
7-7-7-24 is no go.

Quote:

---

Originally Posted by chispy

Guys i cannot run sli on this board P8P67-Deluxe :confused:. Any ideas how to make SLI work ?

---

reinstall windows sorry :(

I have memtest reporting 73MHz bclock and 4xxMHz while I'm at 100MHz bclock in the EFI, RAM set at 1333 (so 666).

What the heck is going on?

old memtest having a hard time reading the correct speeds ?

I have non stop random BSOD when browsing while I am LinX stable. I don't get it... Please if you guys can get me sorted..

ram settings @ spd (and 1T) 1.65V

bclk 100
cpu multi 46x
TPU, EPU, spread spectrum, VT, turbo, EIST, C1E, C3, C6 all disabled
VRM fixed freq @ 350
LLC : extreme
Phase control : extreme
Duty control : extreme
PLL overvoltage : enabled
Vcore 1.35V
other voltages auto

7 x64 SP1

Try auto for most settings you manually set (LLC, VRM) and it will prolly work... no idea either why you use PLL overvoltage enabled to get just 4.6...

Quote:

---

Originally Posted by Pacha

I have non stop random BSOD when browsing while I am LinX stable. I don't get it... Please if you guys can get me sorted..

ram settings @ spd (and 1T) 1.65V

bclk 100
cpu multi 46x
TPU, EPU, spread spectrum, VT, turbo, EIST, C1E, C3, C6 all disabled
VRM fixed freq @ 350
LLC : extreme
Phase control : extreme
Duty control : extreme
PLL overvoltage : enabled
Vcore 1.35V
other voltages auto

7 x64 SP1

---

try this:
bclk 100
cpu multi ;per core 46x
turbo, EIST, C1E, C3, C6 all enabled
VRM fixed freq @ 350
LLC :auto or high
Phase control : standard
Duty control : T Probe
PLL overvoltage : Auto

@Pacha: Memtest86+ 4.2 detects all clocks properly here. Are you using the latest version?

Quote:

---

Originally Posted by Leeghoofd

Try auto for most settings you manually set (LLC, VRM) and it will prolly work... no idea either why you use PLL overvoltage enabled to get just 4.6...

---

I tried PLL overvoltage enabled as with disabled I also had crashes.
I've raised the vcore to 1.375V. If it crashes I'll try with LLC and VRM auto.

Quote:

---

Originally Posted by danielkza

@Pacha: Memtest86+ 4.2 detects all clocks properly here. Are you using the latest version?

---

I have memtest86+ 4.20 also. I don't understand what's the issue.

Quote:

---

Originally Posted by coolhandluke41

try this:
bclk 100
cpu multi ;per core 46x
turbo, EIST, C1E, C3, C6 all enabled
VRM fixed freq @ 350
LLC :auto or high
Phase control : standard
Duty control : T Probe
PLL overvoltage : Auto

---

I don't want to use EIST and the C States, but I'll try LLC Auto, phase control standard and duty control on T probe.

Quote:

---

Originally Posted by Pacha

I tried PLL overvoltage enabled as with disabled I also had crashes.
I've raised the vcore to 1.375V. If it crashes I'll try with LLC and VRM auto.



I have memtest86+ 4.20 also. I don't understand what's the issue.




I don't want to use EIST and the C States, but I'll try LLC Auto, phase control standard and duty control on T probe.

---

that's why you crashing ..you need turbo/EIST,don't worry about C states ..once you past 4.5 they won't work

It's rather that I'd like to remain at full speed, I don't care a lot if C-states are on or off in fact.

Anyway, after having crashed at 4.7G (LynX stable and browsing crash) with previous settings, I'm back to
LLC auto
VRM auto
PLL overvoltage auto
phase control standard
duty cycle on t.probe
vcore at 1.35V

Let's see if it doesn't crash.
I don't understand why turbo and EIST are needed? I don't catch why the chip is stable in stability test and crashes when cruising in idle?

Quote:

---

Originally Posted by owikh84

Do u use Win7 SP1? If yes, pls go back to vanilla Win7 and install the SP1 pack separately. I've found this works for my MIVE, SLI just wont work on stripstreamed win7 SP1.

---

Thank you , that fix it and now i can run SLi. appreciate it for the help :). SLI runs fine now :)

hows your board doing now Angelo ? I still have the same 5600 OC with the 1502 bios...was it an inferior mount ?

Quote:

---

Originally Posted by Pacha

It's rather that I'd like to remain at full speed, I don't care a lot if C-states are on or off in fact.

Anyway, after having crashed at 4.7G (LynX stable and browsing crash) with previous settings, I'm back to
LLC auto
VRM auto
PLL overvoltage auto
phase control standard
duty cycle on t.probe
vcore at 1.35V

Let's see if it doesn't crash.
I don't understand why turbo and EIST are needed? I don't catch why the chip is stable in stability test and crashes when cruising in idle?

---

you crashing under light load because your V dips to low (you have to be above 1.016~ 1.024V min. on offset mode) LLC have a lot to do with it ,for 4.7 you may have to increase V

@pacha: maybe u pump too much V into for "only" 4,6ghz. At SB less is more ;)

I had BSOD just after boot at 4.6 1.3V so I crancked up the vcore directly to 1.35V, maybe 1.325 would have been enough, I'm too much used to crank the vcore or vgpu +0.3V from stock as a limit lol, that's not really needed here.
Anyway, I'm at 4.6G 1.35V right now with the changes I made, and no BSOD so far, I'll see within 24h if it crashes or not, otherwise I'll try with 1.325V or something.

Quote:

---

Originally Posted by coolhandluke41

you crashing under light load because your V dips to low (you have to be above 1.016~ 1.024V min. on offset mode) LLC have a lot to do with it ,for 4.7 you may have to increase V

---

Apparently, it doesn't get low like that as I don't use turbo nor EIST, CPU-Z shows 1.35V ±0.02V through time, be it 0% or 100% load on the cpu. It's note like I was idling at 1.6G and there was too much vdroop.

if u have another crash pls post the BSOD Code

I will. Thanks.

For what it is worth, my board shuts down instantly 2 or 3 times while browsing the internet when I get home from work. After a couple complete shut downs it starts up and runs 100% no matter what I do, game, bench or stability test.

I thought it was a fluke or power issue at the wall but it does it EVERY day for the last month or so. Same exact thing every day, very odd.

Quote:

---

Originally Posted by tool_462

For what it is worth, my board shuts down instantly 2 or 3 times while browsing the internet when I get home from work. After a couple complete shut downs it starts up and runs 100% no matter what I do, game, bench or stability test.

I thought it was a fluke or power issue at the wall but it does it EVERY day for the last month or so. Same exact thing every day, very odd.

---

Maybe due to overheat? Check the temp monitoring in bios some points are set to 90c at default. I set them higher like 100c or turned off.

Quote:

---

Originally Posted by Pacha

I had BSOD just after boot at 4.6 1.3V so I crancked up the vcore directly to 1.35V, maybe 1.325 would have been enough, I'm too much used to crank the vcore or vgpu +0.3V from stock as a limit lol, that's not really needed here.
Anyway, I'm at 4.6G 1.35V right now with the changes I made, and no BSOD so far, I'll see within 24h if it crashes or not, otherwise I'll try with 1.325V or something.




Apparently, it doesn't get low like that as I don't use turbo nor EIST, CPU-Z shows 1.35V ±0.02V through time, be it 0% or 100% load on the cpu. It's note like I was idling at 1.6G and there was too much vdroop.

---

no..this was for reference in case you want to go offset mode
BTW..try to clear cmos,disable spread spectrum,run your RAM @ stock

RAM is already at stock settings. No BSOD so far, so I guess the BIOS parameters made it. I'll focus on oc the RAM if it remains stable one or two days more.

Quote:

---

Originally Posted by owikh84

Maybe due to overheat? Check the temp monitoring in bios some points are set to 90c at default. I set them higher like 100c or turned off.

---

No temp related stuff on in the BIOS. It crashes a couple times right away in the day no matter what. Once it boots up the 3rd time or so, can LinX/Furmark all night long no problems.

Hi, i just bought ASUS P8P67 pro bios 1204 and trying to pas @i5 2500K > 5.4GHz Vcore 1.54v
i ve a problem after boot up message like this :

CPU over voltage error!
press F1 to continue.

if press F1 go to bios, i checked Vcore can't more than 1.53v
any idea's dude?thx alot for helping me, i appreciate that

Quote:

---

Originally Posted by r3sy4

Hi, i just bought ASUS P8P67 pro bios 1204 and trying to pas @i5 2500K > 5.4GHz Vcore 1.54v
i ve a problem after boot up message like this :

CPU over voltage error!
press F1 to continue.

if press F1 go to bios, i checked Vcore can't more than 1.53v
any idea's dude?thx alot for helping me, i appreciate that

---

go into the bios>advanced mode>fans and voltages>click cpu voltage>choose ignore and you will be good to go.

got somebody impressions with the 1502 bios against the 1204 ?

Quote:

---

Originally Posted by r3sy4

Hi, i just bought ASUS P8P67 pro bios 1204 and trying to pas @i5 2500K > 5.4GHz Vcore 1.54v
i ve a problem after boot up message like this :

CPU over voltage error!
press F1 to continue.

if press F1 go to bios, i checked Vcore can't more than 1.53v
any idea's dude?thx alot for helping me, i appreciate that

---

advance/monitor/CPU voltage/ignore

Quote:

---

Originally Posted by l0ud_sil3nc3

go into the bios>advanced mode>fans and voltages>click cpu voltage>choose ignore and you will be good to go.

---

Quote:

---

Originally Posted by coolhandluke41

advance/monitor/CPU voltage/ignore

---

thx mate, problem solved :)

Quote:

---

Originally Posted by Sauron_Vie

got somebody impressions with the 1502 bios against the 1204 ?

---

good question, I'm curious too.


How does 1502 compare to 1204? I'm thinking of trying it.

hah BSOD again... took a while before happening this time but it happened.

I'm back to 2T on the RAM to see how it goes, and lowered vcore to 1.34 instead of 1.35V. I'm still LinX stable, I guess it should even do it with less V. I'll see if it :banana::banana::banana::banana:s again, otherwise I'll put LLC on High or Ultra High et see.

BSOD Code as mentioned ?

Quote:

---

Originally Posted by Pacha

hah BSOD again... took a while before happening this time but it happened.

I'm back to 2T on the RAM to see how it goes, and lowered vcore to 1.34 instead of 1.35V. I'm still LinX stable, I guess it should even do it with less V. I'll see if it :banana::banana::banana::banana:s again, otherwise I'll put LLC on High or Ultra High et see.

---

i get linX stable from dropping 1.35 to 1.34

but when you do a prime95 blend, it fails within 2hrs

Quote:

---

Originally Posted by Sauron_Vie

BSOD Code as mentioned ?

---

I totally forgot that one. I have no log in bluescreenview, though the BSOD is dumping memory to disk each time.

Nevermind, I installed WinDbg as I did on XP before. Here's what the dump says :

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 0000000000002088, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: fffff800028a9edd, address which referenced memory

Debugging Details:
------------------

READ_ADDRESS: 0000000000002088

CURRENT_IRQL: 0

FAULTING_IP:
nt!KiProcessExpiredTimerList+9d
028a9edd 49 dec ecx

DEFAULT_BUCKET_ID: VISTA_DRIVER_FAULT

BUGCHECK_STR: 0xA

LAST_CONTROL_TRANSFER: from 0000000000000000 to 0000000000000000

STACK_TEXT:
00000000 00000000 00000000 00000000 00000000 0x0


STACK_COMMAND: .bugcheck ; kb

FOLLOWUP_IP:
nt!KiProcessExpiredTimerList+9d
028a9edd 49 dec ecx

SYMBOL_NAME: nt!KiProcessExpiredTimerList+9d

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP: 0

BUCKET_ID: INVALID_KERNEL_CONTEXT

MODULE_NAME: Unknown_Module

Followup: MachineOwner
---------

Quote:

---

Originally Posted by McLaren__F1

i get linX stable from dropping 1.35 to 1.34

but when you do a prime95 blend, it fails within 2hrs

---

That may sound idiot, but with all my previous rigs I always had enough stability with 30mins prime for any office and gaming use (though it's been a few years I've not played a game), hence I don't get why LinX stable would mean idle or very light load applications to lead to BSOD.
I'm not folding nor using any app of the sort loading the 4 cores all the way for many hours, so I don't see any reason to have 8 hours prime stability like some do here.

@pacha: how many v do u use @Vccio ?

Auto for VCCIO and all other voltages except vcore and vdimm

I'm back with another BSOD so 1.34V doesn't seem to do just fine, and problem doesn't come from 1T/2T on the RAM.

I've just set LLC on ultra high. I'll see, but knowing that with Extreme LLC it crashed also...
I don't get it. Or there's not enough vcore and as it's unstable sometimes it dips too low even in idle when I'm at 4.6G all the time. I don't know.
Or this has to do with VCCIO not high enough or something maybe, but it's just very logical seeing the asus guide and guys values round here.

Bump VCCIO to 1.1 and try SA also ;)

try following:

cpu pll overvoltage: disabled
llc: regular
vccsa: 0,86250
vccio: 1,1
cpu pll: 1,575
pch: 1,10

speaking of 1T/2T, I got my G.Skill 2133MHz stuff down to 1T and is 2 days stable now!!!

my previous gigabyte board and "A" batch SB wouldn't run 1T for more than a few days before degrading. I think I may stay at 4.6GHz/1.35v or 4.7GHz/1.376v since I'm afraid of degradation again.

Quote:

---

Originally Posted by Sauron_Vie

try following:

cpu pll overvoltage: disabled
llc: regular
vccsa: 0,86250
vccio: 1,1
cpu pll: 1,575
pch: 1,10

---

BSOD again, I'm trying your suggested settings. Will report asap.


EDIT : I guess CPU PLL @ 1.575 is far too low, BIOS report 1.8 @ auto. I put in your settings and got BSOD right before win7 desktop.

I'm back with auto LLC, auto VRM, vcore 1.35V, vccio 1.1 (a little higher than auto), vccsa auto, pch auto, cpu pll auto. I'll see if raised vccio keeps the BSOD away.

ok, mine is stable with these settings @4,6ghz.. only differnece i use offset mode for vcore and add vid for turbo ;) before win7 desktop appears turbo mode is actived.. so event u need also to add some turbo vid

No BSOD but total freeze a few secs before...

I put vccio back to auto, and cranked up vcore to 1.375V. If it fails I don't know where to look at... I have turbo disabled btw.

EDIT : prime stable 30 min with above settings.

Quote:

---

Originally Posted by Pacha

No BSOD but total freeze a few secs before...

I put vccio back to auto, and cranked up vcore to 1.375V. If it fails I don't know where to look at... I have turbo disabled btw.

EDIT : prime stable 30 min with above settings.

---

Why do you have turbo off? isnt that how these CPU's OC?? I have turbo "enabled" in my BIOS, should I disable it?

Turbo is working if you let the CPU settings at stock and want it to auto oc one or more cores depending on the application and the load, or it will bump the freq from the EIST reduced stock freq. As the speed is already much higher intel specs for turbo it won't turbo anyway.
I want to run full speed all the time, old school, no laptop CPU behaviour. I don't mind about the 10 watts added to idle consumption, I'm not using a lot of electricity here for the rest and don't pollute the planet cycling so I don't care.

Quote:

---

Originally Posted by Leeghoofd

hows your board doing now Angelo ? I still have the same 5600 OC with the 1502 bios...was it an inferior mount ?

---

Sorry for the late reply my good old friend . i have tried to resurrect my board. But its dead and no way to bring it back to life. I dont know exactly what happenned , I was running LN2 on 2600k and on HD6950 Crossfire LN2 too, when suddenly the board shut off comletely :( , now the board wont turn on no matter what i do , as i have troubleshoot for a couple of days until not available. The cpu fan tries to spin and lights come on for a second then it shuts off completely , its dead. Im getting an UD7 next while i try to rma this one. Will keep you updated.

Mine Pro B3 is dead too...
My assumption is that VRM's are the problem, cos when i unplug the 8pin cable the PSU is starting, when it's plugged there is no go...:shrug:
I'll replace it with Delux one, thinking with more VRM's it should live longer :rofl:

Quote:

---

Originally Posted by DStealth

Mine Pro B3 is dead too...
My assumption is that VRM's are the problem, cos when i unplug the 8pin cable the PSU is starting, when it's plugged there is no go...:shrug:
I'll replace it with Delux one, thinking with more VRM's it should live longer :rofl:

---

Yes, that's usually an indication of power VRM. Back in late '09 early '10, my MSI Eclipse Plus did the same thing to me after running the system OCed overnight. It had the same behavior as what you described. Though I think it may also had something to do with the kind of PSU you have or use. My PSU killed two of the same model boards, then I had to return it for fear it would do the same to the third one. Never problem since then.

vcore @ 1.375V seemed to do the trick. No more BSOD since then with LLC, auto VRM, vccio 1.1 , vccsa auto, pch auto, cpu pll auto.

Thank you guys for suggesting vccio 1.1, it seems it was indispensable to have light load stability.

edit : BSOD yesterday evening... I was in fact at vccio auto. I cranked up vcore to 1.38V and vccio to 1.1 this time. I'll see...

Just an FYI
This may have been mentioned before but the random BSOD's at stock idle while browsing the web were driving me nuts. Just did a test with C states enabled and auto and found that auto supplies a little more Vcore in EIST and does not BSOD. Enabled causes random BSOD's.

Left CPU Z shows voltage with C states set to Auto. Right shows voltage with C states enabled in Bios. Pretty sure I've seen voltage drop below 0.900 when set to enabled. Auto does not drop below 0.992. The last bsod frigged up a Blu-ray disc while burning, which can get expensive if it continues.:(

Short question concerning this motherboard series from Asus, is there a way of spotting an actual b3 board _without_ powering it up?

I'm about to pull the trigger on a deluxe model and will put it on water from the start, that's why I don't want to notice that I have to send the board back after installing everything...

Quote:

---

Originally Posted by p2501

Short question concerning this motherboard series from Asus, is there a way of spotting an actual b3 board _without_ powering it up?

I'm about to pull the trigger on a deluxe model and will put it on water from the start, that's why I don't want to notice that I have to send the board back after installing everything...

---

Should have a big sticker on it saying B3 :)

Quote:

---

Originally Posted by wez

Should have a big sticker on it saying B3 :)

---

Well yes but I've heard that in some cases there's a sticker on the package but inside is a b2 board so how do I really tell? Different serial numbers? :confused:

Quote:

---

Originally Posted by p2501

Well yes but I've heard that in some cases there's a sticker on the package but inside is a b2 board so how do I really tell? Different serial numbers? :confused:

---

ASUS SATA Verifier ;)

http://event.asus.com/2011/mb/Identi...ted_SATA_port/

Quote:

---

Originally Posted by getyasome

ASUS SATA Verifier ;)

http://event.asus.com/2011/mb/Identi...ted_SATA_port/

---

Thanks, but as I've asked: is there possibly a way of knowing without booting it?

Quote:

---

Originally Posted by p2501

Thanks, but as I've asked: is there possibly a way of knowing without booting it?

---

http://event.asus.com/2011/mb/Identify_B3_Motherboards/

Note the no2 way.

Quote:

---

Originally Posted by DStealth

Mine Pro B3 is dead too...
My assumption is that VRM's are the problem, cos when i unplug the 8pin cable the PSU is starting, when it's plugged there is no go...:shrug:
I'll replace it with Delux one, thinking with more VRM's it should live longer :rofl:

---

Hi again,
Just let you know the f%#^&n board killed my CPU too...
To sad, it was a good one :
1.49V x54 SuperPI @air + 1300rmp Fans
http://img228.imageshack.us/img228/3...i1m5400.th.jpg

Now with Delux board there's no go again :(


Edit: It goes, but it's stunted @ Q-code 00

Quote:

---

Originally Posted by neven

http://event.asus.com/2011/mb/Identify_B3_Motherboards/

Note the no2 way.

---

Sooo basically it's just the sticker. :shrug:

Quote:

---

Originally Posted by DStealth

Hi again,
Just let you know the f%#^&n board killed my CPU too...
To sad, it was a good one :
1.49V x54 SuperPI @air + 1300rmp Fans
Now with Delux board there's no go again :(


Edit: It goes, but it's stunted @ Q-code 00

---

Instead of the Deluxe I've now ordered the pro version of the board... :mad:

How many dead pro boards do we have now?

Quote:

---

Originally Posted by p2501

Sooo basically it's just the sticker. :shrug

---

Actually my box doesn't have stickers and it says rev B3 in 5 or 6 places. sides of the box not shown.

Quote:

---

Originally Posted by crossg

Just an FYI
This may have been mentioned before but the random BSOD's at stock idle while browsing the web were driving me nuts. Just did a test with C states enabled and auto and found that auto supplies a little more Vcore in EIST and does not BSOD. Enabled causes random BSOD's.

Left CPU Z shows voltage with C states set to Auto. Right shows voltage with C states enabled in Bios. Pretty sure I've seen voltage drop below 0.900 when set to enabled. Auto does not drop below 0.992. The last bsod frigged up a Blu-ray disc while burning, which can get expensive if it continues.:(

---

I've had 2 cds to the bin due to these BSOD... :down:
I don't use EIST and as the CPU is stable when full loading it, I think that sometimes vcore dips too low at idle as it's not fully stable and moving around ±0.025V which is quite high, and when it hits the too low value for full speed with a light load I get BSOD.

I guess this board needs vdroop mod as I my Commando did, which helped in this regard.

Those who have stability at idle is because they use EIST with offset mode to crank up the idle voltage, but without EIST you just can't prevent the board to vdroop at idle full speed at have enough vcore for light load stability.

you using offset or manual voltages ? upping the vcore a tiny bit more ?

How does the PLL overvoltage work? Is the voltage applied under load or idle?

I am stable at 45x, offset 0.080, LCC disabled and PLL is also disabled. I need a boat load of vcore above 46x, and was thinking if better to enable the PLL overvoltage instead of rising the offset?

Does anyone help me? please...
I just finished my new p8p67 Pro B2 with 2600k cpu system and the pc wont boot... the cpu led is red. No any beep code from bios? what's happened?
(it's off 1 time and restart again...:()
I have G-skill RJ-X 1600 4*2 memory SATA3 640*2 ANTECH TPQ1000 and GTX 580.

Thanks

Quote:

---

Originally Posted by rapin

Does anyone help me? please...
I just finished my new p8p67 Pro B2 with 2600k cpu system and the pc wont boot... the cpu led is red. No any beep code from bios? what's happened?
(it's off 1 time and restart again...:()
I have G-skill RJ-X 1600 4*2 memory SATA3 640*2 ANTECH TPQ1000 and GTX 580.

Thanks

---

Welcome to the Club...just pray for your CPU

http://www.xtremesystems.org/forums/...&postcount=969
:rolleyes:

some quirks I've found with this board...

1. voltage during loading seems inconsistent. with or without LLC, the VCore with 1 or 2 cores loaded is much lower than with 4 cores loaded. shouldn't this be the opposite since VDroop would be more noticeable with more current? for example, with 1-2 cores loaded I've seen as low as 1.336v-1.344v, but with 3-4 cores loaded I've seen generally 1.376v. but even goes as high as 1.396v-1.40v if the load is light. this to me seems backwards.

Edit: so to be clear here, my non-LLC voltage range for 4.6GHz is 1.33v-1.400v, that's quite a large range... but doesn't decrease proportional to more load, it decreases proportional to LESS load. so, since my CPU needs 1.35v for stable 4.6, it's getting both too much volts and not enough volts during different workloads.

2. LLC doesn't really seem to adjust load volts properly. enabling LLC seems to generally just give a flat all around voltage increase with not so much difference during load, compared to using no LLC and higher volts. for example, 1.396v idle compared to 1.376 idle without LLC. if I just increase non-LLC volts without to reach 1.396, sure there is a bit more load drop, but not significantly different. gigabyte seems to have done LLC better than Asus. they don't overshoot the mark, and they don't drop more than 0.010.

additionally, (related to the above quirks with LLC) it seems that setting too high of a LLC to reach the target stable load volts ends up with idle 1.6ghz power savings clocks going below the stable mark (<1.000v) which essentially makes LLC kind of worthless.

Has anyone else seen similar results?

Quote:

---

Originally Posted by crossg

Left CPU Z shows voltage with C states set to Auto. Right shows voltage with C states enabled in Bios. Pretty sure I've seen voltage drop below 0.900 when set to enabled. Auto does not drop below 0.992. The last bsod frigged up a Blu-ray disc while burning, which can get expensive if it continues.:(

---

I'm pretty sure anything below 1.025v-1.050v will be unstable at 1600mhz. (read that somewhere, but can't remember where) and in my testing it seems anything below 1.00v is definitely dangerous to run. (risk of BSOD for sure). you might want to loosen up the LLC a bit and increase volts like I've had to do.

Any tips on how to oc my ram on this board?

My idle voltage drops to around 0.96V and I have experience no BSODs so far.

I need some serious help dealing with a BSOD, code 0x124... I am using an offset mode with LLC off and other settings are default except fixed ram timings.

After many try outs, I seem to pass Small FFTs for 14h. However, the Blend test fails with a BSOD after about 4h. I suspect, there must be an issue with RAM voltage or something, but clueless what to change.

I also pass the LinX with AVX with 3072Mb of RAM, but also tried running with a full RAM usage and the LinX failed also with the same BSOD code.

Any help is appreciated.

Quote:

---

Originally Posted by ghmz

I need some serious help dealing with a BSOD, code 0x124... I am using an offset mode with LLC off and other settings are default except fixed ram timings.

After many try outs, I seem to pass Small FFTs for 14h. However, the Blend test fails with a BSOD after about 4h. I suspect, there must be an issue with RAM voltage or something, but clueless what to change.

I also pass the LinX with AVX with 3072Mb of RAM, but also tried running with a full RAM usage and the LinX failed also with the same BSOD code.

Any help is appreciated.

---

What is your RAM kit, and at what speeds and timings are you running it? It indeed seems your memory is not stable.

Quote:

---

Originally Posted by danielkza

What is your RAM kit, and at what speeds and timings are you running it? It indeed seems your memory is not stable.

---

I have this RAM. Running rated timings which are 9-9-9-24-2N, 1.5V.

Having problems with multipler staying at 41 when its set in bios . When running prime 95 i notice that it defaults back to 3500mhz (34x103 fsb) . It doesnt default if i use the 40x multipler . Trying to figure out why its doing this on this board . Cooling is adequate as its not going past 63c in this room.

2600k
crucial memory
Asus P8P67 M

Ai Overclock Tuner - manual
Bclk/peg freq - 103.0
By All Cores (Can Adjust In OS) , currently set at 41
Internal PLL Overvoltage - AUTO
Memory Freq (1090mhz)
Offset Mode sign (-)
CPU Offset Voltage 0.020
DRAM Voltage (1.50)
VCCIO Voltage 1.00000
PCH Voltage (AUTO)
Load Line Calibration (AUTO)
-----------------------------------

Ai Tweaker / CPU Management
CPU Ratio (AUTO)
Enhanced Intel Speedstep Technology (ENABLED)
Turbo (ENABLED)
---------------------------------
Turbo Mode Parameters
Long Duration Power Limit (AUTO)
Long Duration Maintained (AUTO)
Short Duration Power Limit (AUTO)
Additional Turbo Voltage (AUTO)
Primary Plane Current Limit (AUTO)
________________________
Advanced\CPU configuration
CPU ratio = Auto
Intel adaptive thermal monitor - disabled
Hyper threading - enabled
Active Processors (ALL)
limit CPuid maxium disabled
Execute disable bit - enabled
Intel virtualization tech = disabled
Enhanced Intel Speedstep Technology (ENABLED)
Turbo Mode -enabled
CPU C1E, (AUTO)
CPU C3 Report (AUTO)
CPU C6 report (AUTO)

I´ve got some serious issues going on my P8P67 WS Revolution.

When I run 3DMark Vantage / 3DMark 11, I get a message "Nvidia display driver stopped responding and has recovered"

Tried everything, GTX480, GTX580 and 9600GT card. Still same problem.
Tried to switch PSU from Corsair HX620 -> Corsair AX850. Still same problem.
Re-installed Win7 Ultimate SP1 and still got the same problem.

Sometimes I can run 3DMark for 30sec, sometimes a couple of minutes.
The most strange thing is: Can run Unigine Heaven benchmark for 30min without any trouble.

Everything is at stock 2600K, 16GB Vengeance 1866MHz...

Anyone?

Quote:

---

Originally Posted by Darkstormz

I´ve got some serious issues going on my P8P67 WS Revolution.

When I run 3DMark Vantage / 3DMark 11, I get a message "Nvidia display driver stopped responding and has recovered"

Tried everything, GTX480, GTX580 and 9600GT card. Still same problem.
Tried to switch PSU from Corsair HX620 -> Corsair AX850. Still same problem.
Re-installed Win7 Ultimate SP1 and still got the same problem.

Sometimes I can run 3DMark for 30sec, sometimes a couple of minutes.
The most strange thing is: Can run Unigine Heaven benchmark for 30min without any trouble.

Everything is at stock 2600K, 16GB Vengeance 1866MHz...

Anyone?

---

You have the latest drivers?

Quote:

---

Originally Posted by ghmz

I need some serious help dealing with a BSOD, code 0x124... I am using an offset mode with LLC off and other settings are default except fixed ram timings.

After many try outs, I seem to pass Small FFTs for 14h. However, the Blend test fails with a BSOD after about 4h. I suspect, there must be an issue with RAM voltage or something, but clueless what to change.

I also pass the LinX with AVX with 3072Mb of RAM, but also tried running with a full RAM usage and the LinX failed also with the same BSOD code.

Any help is appreciated.

---

raise ur vcore a little ;)

Quote:

---

Originally Posted by McLaren__F1

You have the latest drivers?

---

Yes I do, still the same trouble...

Quote:

---

Originally Posted by Leeghoofd

you using offset or manual voltages ? upping the vcore a tiny bit more ?

---

manual mode. I don't know what to expect as default voltage when using offset mode as you can't set default vcore but only offset value.

Quote:

---

Originally Posted by LeetMiniWheat

some quirks I've found with this board...

1. voltage during loading seems inconsistent. with or without LLC, the VCore with 1 or 2 cores loaded is much lower than with 4 cores loaded. shouldn't this be the opposite since VDroop would be more noticeable with more current? for example, with 1-2 cores loaded I've seen as low as 1.336v-1.344v, but with 3-4 cores loaded I've seen generally 1.376v. but even goes as high as 1.396v-1.40v if the load is light. this to me seems backwards.

Edit: so to be clear here, my non-LLC voltage range for 4.6GHz is 1.33v-1.400v, that's quite a large range... but doesn't decrease proportional to more load, it decreases proportional to LESS load. so, since my CPU needs 1.35v for stable 4.6, it's getting both too much volts and not enough volts during different workloads.

2. LLC doesn't really seem to adjust load volts properly. enabling LLC seems to generally just give a flat all around voltage increase with not so much difference during load, compared to using no LLC and higher volts. for example, 1.396v idle compared to 1.376 idle without LLC. if I just increase non-LLC volts without to reach 1.396, sure there is a bit more load drop, but not significantly different. gigabyte seems to have done LLC better than Asus. they don't overshoot the mark, and they don't drop more than 0.010.

additionally, (related to the above quirks with LLC) it seems that setting too high of a LLC to reach the target stable load volts ends up with idle 1.6ghz power savings clocks going below the stable mark (<1.000v) which essentially makes LLC kind of worthless.

Has anyone else seen similar results?


I'm pretty sure anything below 1.025v-1.050v will be unstable at 1600mhz. (read that somewhere, but can't remember where) and in my testing it seems anything below 1.00v is definitely dangerous to run. (risk of BSOD for sure). you might want to loosen up the LLC a bit and increase volts like I've had to do.

---

I can see we're more and more to find the same non sense in how this board is operating and seeing how many guys here have LynX stability but light load BSOD, I regret I've not bought a Gigabyte... P8P67 or Commando, years apart but hands together in the crap..

Quote:

---

Originally Posted by ghmz

I need some serious help dealing with a BSOD, code 0x124... I am using an offset mode with LLC off and other settings are default except fixed ram timings.

After many try outs, I seem to pass Small FFTs for 14h. However, the Blend test fails with a BSOD after about 4h. I suspect, there must be an issue with RAM voltage or something, but clueless what to change.

I also pass the LinX with AVX with 3072Mb of RAM, but also tried running with a full RAM usage and the LinX failed also with the same BSOD code.

Any help is appreciated.

---

Same weirdness and dumb behaviour of the board, confirmed. So many guys here with "rock stability" but BSOD 0124 when browsing or so :rolleyes:

Quote:

---

Originally Posted by Sauron_Vie

raise ur vcore a little ;)

---

As suggested by LeetMiniWheat I would say also that LLC at auto (which may correspond to low value) and higher vcore do the trick, at least it's better. Push the vcore too high for LynX stability, and even if it's too high for load and idle, it's high enough to prevent BSOD with light load of 1-2 cores.

Quote:

---

Originally Posted by LeetMiniWheat

some quirks I've found with this board...

1. voltage during loading seems inconsistent. with or without LLC, the VCore with 1 or 2 cores loaded is much lower than with 4 cores loaded. shouldn't this be the opposite since VDroop would be more noticeable with more current? for example, with 1-2 cores loaded I've seen as low as 1.336v-1.344v, but with 3-4 cores loaded I've seen generally 1.376v. but even goes as high as 1.396v-1.40v if the load is light. this to me seems backwards.

Edit: so to be clear here, my non-LLC voltage range for 4.6GHz is 1.33v-1.400v, that's quite a large range... but doesn't decrease proportional to more load, it decreases proportional to LESS load. so, since my CPU needs 1.35v for stable 4.6, it's getting both too much volts and not enough volts during different workloads.

2. LLC doesn't really seem to adjust load volts properly. enabling LLC seems to generally just give a flat all around voltage increase with not so much difference during load, compared to using no LLC and higher volts. for example, 1.396v idle compared to 1.376 idle without LLC. if I just increase non-LLC volts without to reach 1.396, sure there is a bit more load drop, but not significantly different. gigabyte seems to have done LLC better than Asus. they don't overshoot the mark, and they don't drop more than 0.010.

additionally, (related to the above quirks with LLC) it seems that setting too high of a LLC to reach the target stable load volts ends up with idle 1.6ghz power savings clocks going below the stable mark (<1.000v) which essentially makes LLC kind of worthless.

Has anyone else seen similar results?




I'm pretty sure anything below 1.025v-1.050v will be unstable at 1600mhz. (read that somewhere, but can't remember where) and in my testing it seems anything below 1.00v is definitely dangerous to run. (risk of BSOD for sure). you might want to loosen up the LLC a bit and increase volts like I've had to do.

---

This is about the weirdest thing ever.
Can you try clearing CMOS with the power unplugged?
Every board that uses fixed (not auto and no offsets) voltages, and with C1e, C3, C6 disabled, should NOT be raising the voltage at load for any reason; vdroop (loadline slope) is supposed to lower the vcore at load on an even slope and it's been that way ever since the Pentium 4 was introduced and VRD 8.x, instead of the P3's always fixed voltage.

If you're getting increased vcore at load, and you're not using offsets and not using LLC, then either the BIOS or the board is defective somehow, because that's not how vdroop is supposed to work.
It's like the board is giving you LLC ultra high, even though you have it disabled...

Quote:

---

Originally Posted by Falkentyne

This is about the weirdest thing ever.
Can you try clearing CMOS with the power unplugged?
Every board that uses fixed (not auto and no offsets) voltages, and with C1e, C3, C6 disabled, should NOT be raising the voltage at load for any reason; vdroop (loadline slope) is supposed to lower the vcore at load on an even slope and it's been that way ever since the Pentium 4 was introduced and VRD 8.x, instead of the P3's always fixed voltage.

If you're getting increased vcore at load, and you're not using offsets and not using LLC, then either the BIOS or the board is defective somehow, because that's not how vdroop is supposed to work.
It's like the board is giving you LLC ultra high, even though you have it disabled...

---

this baffles me too because this isn't how vdroop is supposed to work. but this happens only with offset voltages (and I don't believe C-states are related). manual voltage is alright but nowhere near as tight as gigabyte. (but gigabyte's have their own slew of problems...) I can stay between 1.352v and 1.364v with manual mode, but offset ranges between 1.336 and 1.40v during loading and about 1.072 idle. (read from CPUZ VID)

I'm starting to think it's not even worth it to keep offset on anymore and just let it stay at 1.35-1.36 all the time. though I am rock stable for almost a week now, but my chip is getting more voltage than it needs. Asus needs to fix their offset to work better like gigabyte. (and the LLC) though I don't regret trading in my P67A-UD4 for P8P67 Deluxe. Asus definitely made a superior product this time around. but every P67 board has it's own set of issues.

<Edited multiple times>

First time Asus mobo user here also and probably might use EVGA next if they get around to releasing their boards. Asus just has too many problems.

Quote:

---

Originally Posted by Peter949

First time Asus mobo user here also and probably might use EVGA next if they get around to releasing their boards. Asus just has too many problems.

---

I wouldn't count on that. Rumor has it, EVGA's mobo team up and left. (multiple sources from this) and then mysteriously another brand started popping up with almost identical designs to EVGA's X58 boards. so apparently they jumped ship. (I forget what brand it was though) I was a loyal EVGA board customer for awhile myself until I realized this. and the P67 delay only proves this further. if you look at their photos of it, there's no innovation compared to the last P55 model. it's just a P55 remake with a P67 chip slapped in, nowonder they can't get it to work right in order to release a product.

i am a little bit confused to read that some members have mich trouble with the asus boards., so i can only spreak for myself, and i have really not a trace of problems with the pro versions. meanwhile i changed to the b3 rev.. also no problems at all.
maybe it depends also at my combo CPU - RAM - MOBO that mine is running without any probs. some friends of mine bought at first the giga´s.. meanwhile they changed to asus cause the gigas are also not exactly brilliant either, are they ?? ;)

Quote:

---

Originally Posted by Sauron_Vie

raise ur vcore a little ;)

---

Didn't help. Increase from +0.080 to 0.090. Crashed during the night. I know it's getting enough voltage for a 45x.

do u guys use only the offset function or r u using offset & additional turbo vid ?

Quote:

---

Originally Posted by ghmz

Didn't help. Increase from +0.080 to 0.090. Crashed during the night. I know it's getting enough voltage for a 45x.

---

Do you call that an increase, 0.010 ? I give up...:rofl: no idea why you run LLC off... just leave it on AUTO... try upping VCCIO to 1.15. The dimms are 100% okay ?

Quote:

---

Originally Posted by Sauron_Vie

i am a little bit confused to read that some members have mich trouble with the asus boards., so i can only spreak for myself, and i have really not a trace of problems with the pro versions. meanwhile i changed to the b3 rev.. also no problems at all.
maybe it depends also at my combo CPU - RAM - MOBO that mine is running without any probs. some friends of mine bought at first the giga´s.. meanwhile they changed to asus cause the gigas are also not exactly brilliant either, are they ?? ;)

---

I switched from Gigabyte p67 to Asus p67 too and I agree they have problems. but none are perfect. they all have problems of their own. but Asus is still superior in features.

Quote:

---

Originally Posted by Darkstormz

I´ve got some serious issues going on my P8P67 WS Revolution.

When I run 3DMark Vantage / 3DMark 11, I get a message "Nvidia display driver stopped responding and has recovered"

Tried everything, GTX480, GTX580 and 9600GT card. Still same problem.
Tried to switch PSU from Corsair HX620 -> Corsair AX850. Still same problem.
Re-installed Win7 Ultimate SP1 and still got the same problem.

Sometimes I can run 3DMark for 30sec, sometimes a couple of minutes.
The most strange thing is: Can run Unigine Heaven benchmark for 30min without any trouble.

Everything is at stock 2600K, 16GB Vengeance 1866MHz...

Anyone?

---

I did a clean install without SP1, and the issue is gone. But as soon as I install SP1, boom! Display driver stopped blabla....

Quote:

---

Originally Posted by Darkstormz

I did a clean install without SP1, and the issue is gone. But as soon as I install SP1, boom! Display driver stopped blabla....

---

I've seen that issue 5 times today, but it's because I'm pushing my Cpu and Gpu's to their limits and 3DMK 11 really stresses the card more than the cpu. Happens on my 980X rig as well so it's probably vid card related. Right now I'm using beta 270.51 drivers but any driver so far has done the same when pushed.

Quote:

---

Originally Posted by LeetMiniWheat

I switched from Gigabyte p67 to Asus p67 too and I agree they have problems. but none are perfect. they all have problems of their own. but Asus is still superior in features.

---

u r right :) and i think asus is one of the stablest of the big 4

Quote:

---

Originally Posted by Leeghoofd

Do you call that an increase, 0.010 ? I give up...:rofl: no idea why you run LLC off... just leave it on AUTO... try upping VCCIO to 1.15. The dimms are 100% okay ?

---

0,08 or 0.09 is for my taste much too much. can´t understand why some guys pump so much voltage into. i can run mine for 4,6ghz with 0,02 and a little add turbo vid ;)