Official ASUS X38 Boards: P5E, P5E3 - Info/BIOS Thread

[joe.denice]

Ok my new Rampage Formula arrived in the mail. I needed a new board for my rig as my Maximus Formula is going into my buddy's rig. It shipped with bios 0219 and everything is running just fine now.

[Prodigys]

I did the switch from P5E to Rampage yesterday, no problems at all with flashing the bios etc...
Everything works just fine, now I finally can read some voltages in windows, and a lot of ram tweaks came available in the bios, I LIKE !

Also my vdroop is lovely, I got with my Q6600 on 4Ghz idle 1.384Vcore, and load also 1.384Vcore ! Only the vdrop is 1.4000 set in bios and get 1.384, but I don't mind...

About the overvolting thing off the P5E, now I can read the voltages I can say the P5E overvolts the ram with 0.09, so if you set 2.2 you get 2.29 !

Hopes this a little bit helpfull .

[screwtech02]

So is there a conclusion that the Rampage bios is any better than the Maximus bios for a Q6600??? I'd like to push my setup a little more to say 3.8/4.0 and try and keep the 8gb, that's the reason im a askin....

[STaRGaZeR]

So is there a conclusion that the Rampage bios is any better than the Maximus bios for a Q6600??? I'd like to push my setup a little more to say 3.8/4.0 and try and keep the 8gb, that's the reason im a askin....

Why don't you try it? None of us will give you a more exact answer to that question than yourself

[Brick_top]

Hi everyone, Yesterday I flashed my Asus p5e with the rampage formula bios but now when I boot I receive the message that it has detected an overheat in OPT1, if I go into the hardware monitor option in the bios I see some red numbers at 125ºC. Is there any way to flash back to my regular bios?

[karl_eller]

I did the switch from P5E to Rampage yesterday, no problems at all with flashing the bios etc...
Everything works just fine, now I finally can read some voltages in windows, and a lot of ram tweaks came available in the bios, I LIKE !

Also my vdroop is lovely, I got with my Q6600 on 4Ghz idle 1.384Vcore, and load also 1.384Vcore ! Only the vdrop is 1.4000 set in bios and get 1.384, but I don't mind...

About the overvolting thing off the P5E, now I can read the voltages I can say the P5E overvolts the ram with 0.09, so if you set 2.2 you get 2.29 !

Hopes this a little bit helpfull .

Are you sure about the overvolting RAM bit? Because as far as I know, the P5E boards don't actually have a sensor to read vDIMM, which means the Rampage BIOS is probably just pulling a voltage out of it's ass

And that's some pretty decent vDrop and vDroop. I'm getting about 0.05v vDrop and another 0.05v vDroop on my P5E, which is a bit of an ass sometimes.

Hi everyone, Yesterday I flashed my Asus p5e with the rampage formula bios but now when I boot I receive the message that it has detected an overheat in OPT1, if I go into the hardware monitor option in the bios I see some red numbers at 125ºC. Is there any way to flash back to my regular bios?

The Rampage boards have a couple of extra temp sensors compared to the P5E, so it's just the BIOS trying to read a temp sensor that isn't there. Simply disable that temp sensor in Hardware Monitor, and you should be fine.

Eller

[mk-ultra]

Hi everyone, Yesterday I flashed my Asus p5e with the rampage formula bios but now when I boot I receive the message that it has detected an overheat in OPT1, if I go into the hardware monitor option in the bios I see some red numbers at 125ºC. Is there any way to flash back to my regular bios?

just go into your hardware monitor bios page and put all those wacky extra temps on "ignored"

to flash the original bios back use the same procedure as the RF ones, but use the 605 or whatever bios you want


for the ram overvolt with the rampage bios, i get:

|2.24  | 2.26  | 2.28  | 2.30  |< BIOS "set to"
|2.336 | 2.352 | 2.368 | 2.384 |< Everest
|2.291 | 2.313 | 2.332 | 2.351 |< DMM 
| .045 |  .039 |  .036 |  .033 |< RF Bios Error

NOTE: everest gives same reading as the bios hardware monitor page

so it looks like RF bios is exaggerating the actual overvolt the P5E already have, it's .05v overvolt, i can't remember what it gave me with the P5E bios but as far as i can remember i don't think i needed 2.30 to get to 2.35.

now i wish i could read the NB/fsb/pll volts with my dmm, cause the ones reported seems fishy

[INTREPID]

First, I'm not clear on why you're giving multiple voltages for bios, everest, DMM (for example, what are all these voltages:
2.24 - 2.26 - 2.28 - 2.30 < BIOS

Let's say you set the bios to 2.24 volts. You're saying the DMM reading is what? 2.291v? I just don't get this chart.

Second, Everest doesn't give voltages for RAM (at least not with my P5E 0605 bios). Everest only shows the SPD spec voltage, not the actual voltage. Does the P5E even have a Dim voltage sensor? Where are reading ram voltage in Everest?

Thanks.

for the ram overvolt with the rampage bios, i get:

2.24  - 2.26  - 2.28  - 2.30  < BIOS
2.336 - 2.352 - 2.368 - 2.384 < Everest
2.291 - 2.313 - 2.332 - 2.351 < DMM 
.45   -  .39  -  .36  -  .33  < RF Bios Error

[mk-ultra]

dude keep up with the thread!

this is using the rampage formula bios, i say it like 5 time in my post

first row is actual voltage set in the bios, obvious to me, maybe i should have been more explicit

and it was to bring real data, to Prodigys about the presumed overvolts of 0.09v

[INTREPID]

I know it's the Rampage bios.

I'm just a bit confused with your chart.

This would be clear:

Set in Bios: X Volts
DMM: Y Volts
Everest: Z volts

And, Everest shows dram voltage with the Rampage bios? Where? I've never seen actual dram voltage in Everest.

Sorry it I missed some posts here, but I hope you can clarify this. Thanks!

[mk-ultra]

with the RF bios it does give you ram voltage in everest, with the other voltages, it also gives FSB, NB , SB/SB1.5

just read my chart from top to bottom

[INTREPID]

Thanks for clarification.

[Brick_top]

thanks for your help, I have now disabled the sensors and the message is gone, for those to which this may happen and are ignorant to it like me, you have to disable all three sensors opt1, 2 and 3, for the warning to stop appearing, first I only disabled the sensors that were giving me the warning message but they kept giving it, I was only able to get rid of the message by disabling all three of them

[necron66]

It dosn't matter what Everest tells you your vDIMM is, as has been stated so manny times, the P5E has no sensor to read it!!!

[necron66]

And that's some pretty decent vDrop and vDroop. I'm getting about 0.05v vDrop and another 0.05v vDroop on my P5E, which is a bit of an ass sometimes.

With the RF BIOS, pencil mod from this thread and load line enabled, under load I'm getting 0.004v droop. http://www.i4memory.com/showpost.php...32&postcount=7

[mngdew]

This recent RF bios flashing killed my Crucial Ballistix memories.
OCCT and Prime 95 can't last a second, so I flashed back to P5E 0502. It still gave me the same problem despite of higher voltage to the modules.

[mk-ultra]

It dosn't matter what Everest tells you your vDIMM is, as has been stated so manny times, the P5E has no sensor to read it!!!

nobody said it did!

[necron66]

nobody said it did!

So why does so manny people keep refering to Aisuite and everest reading non existant sensors all the time?

[bobbobson]

Hey guys, has anyone flashed their P5E to the Rampage and uses sub-zero temps ? It seems NO temp programs can get the correct temperature

[EOD]

I think my earlier post on vdimm voltage was overlooked, so I will repost:

Special thanks to Karl eller for the post on vdimm points. I used my Fluke 177 digital meter and read the yellow and one of te blue marked readout point from his post.

When I set the vdimm in bios to 2.16v, I get a reading of 2.21v from the multi meter. However, when I set the vdimm to 2.18v in bios, I get a reading of 2.238v on the meter. And finally, when I set vdimm to 2.2v in bios, I get a reading of 2.25v on the meter. This makes it very hard for those without a multimeter to know the true vdimm.

I did find that my 1.40v vcore set in bios, which loads into windows at 1.38v as shown in CPU-Z, actually is 1.376v when metered while running Orthos.

I verified it with the Rampage bios just now. At 2.16v in bios I still get a reading of 2.21v on the mutimeter (Fluke 177 Digital meter), while Everest v4.40.1330 displays my vdimm at 2.22v

[INTREPID]

This is may be old news for some, but here is a quote from a post I found interesting:

Both coretemp and realtemp are accurately reading the DTS sensor on your cpu, and both will accurately show the distance from throttling (distance from tjmax). Converting those relative temps (from prochot#) to absolute temps require knowing tjmax. Intel will not divulge tjmax of desktops, probably because intel has said they may change batch to batch (ie even for silent revisions?). Coretemp is guessing tjmax of 105, because 45nm mobile cpus have tjmax 105, but intel has stated that is INCORRECT. Realtemp is guessing tjmax as 95, which is an educated guess based on real measurements of casing temps at idle, underclocked, undervolted, steady state, that according to intel specs should result in a near equlibrium between core/casing temps, ie within 1-2C. So you are probably better off using realtemp with tjmax of 95. That might be 1-2C off, but no way, no how is tjmax 105C reported by coretemp. Speedfan 4.34 latest beta uses a tjmax of 100, which reads between coretemp and realtemp. Personally I use either realtemp or speedfan with -5C calibration, I use 95 tjmax for mine, as I think that is most accurate. But anything in 95-97 +/- 1 or 2 would be hard to argue with.

More info at Anandtech : http://www.anandtech.com/cpuchipsets...spx?i=3251&p=4

RealTemp Info: http://www.xtremesystems.org/forums/...d.php?t=179044
RealTemp DL: http://www.xtremesystems.org/forums/...78#post2809778
CoreTemp: http://www.alcpu.com/CoreTemp/

[mngdew]

Figured out what the problems with my memories. I tired 3 different brands of memories, PDP, Cosair and Kingston. All failed OCCT memory test within 5 seconds.
So It wasnt' the memory module issue. When MF or RF bios' were installed they were reporting OPT_TEMP1 and TEMP3 overheat. Somehow, RF bios damaged NB's memory controller.
Now I need a new mobo.

[INTREPID]

Sorry to hear. But as I said when this started, I would never flash my MB with a different model bios. It's risky and in my opinion, the gains if any are minor. I have my E8400 clocked at 4.0 Ghz. with the P5E 0605 bios and I'm happy. You have to be willing to assume the risk when you overclock or flash modified or unofficial bios. Hope you're up and running again soon.

While we're on the subject of risk, I highly recommend you don't exceed 1.3625v with the E8400. It's a fragile 45nm cpu and I've read numerous posts of users where their CPU degraded. Forget that Intel states that the upper maximum is 1.45v. It's incorrect - users have ruined their E8400's at that voltage and lower. Use the maximum VID which is 1.3625v.

See "E8400 Crapped out! YAY!!!!" Thread: http://www.overclock.net/intel-cpus/...d-out-yay.html

Figured out what the problems with my memories. I tired 3 different brands of memories, PDP, Cosair and Kingston. All failed OCCT memory test within 5 seconds.
So It wasnt' the memory module issue. When MF or RF bios' were installed they were reporting OPT_TEMP1 and TEMP3 overheat. Somehow, RF bios damaged NB's memory controller.
Now I need a new mobo.

[karl_eller]

Figured out what the problems with my memories. I tired 3 different brands of memories, PDP, Cosair and Kingston. All failed OCCT memory test within 5 seconds.
So It wasnt' the memory module issue. When MF or RF bios' were installed they were reporting OPT_TEMP1 and TEMP3 overheat. Somehow, RF bios damaged NB's memory controller.
Now I need a new mobo.

Actually, what was most likely happening was that the RF BIOS was trying to read two temp probes (OPT_TEMP1 and TEMP3) that do not exist on your P5E board. The P5E board only has a temp probe for northbridge (as well as using the CPU's probe), while the MF and RF boards have a few extra (I think it's SB and Mofsets). Depending on how the probes work, when the BIOS is trying to read a probe that doesn't exist, it'd either read the minimum or maximum (which is what's probably happening here) temp that the BIOS's programmers figured it'd need to read.

Eller

[mngdew]

The problem got worse, and my system could not boot into the Windows.
So I swapped mobo with a real MF, and everything is back to normal.