The Maximus Formula Thread - Help/OCing/Guide/Rampage conversion

Many P5E users need to know what has been added in bios that is working and what is not.
1)Can you monitor more voltages?
2)Can you adjust more voltage options?
3)Have you all memory timings available of Rampage?
4)Are these settable?
5)Only second gigabit is excluded or and something else?

Quote:

---

Originally Posted by ericab

hey Grn?

today i ordered the Corsair Dominator 8500's :yepp:

hell yeah. (thx for advice)

---

I think you will be very happy with them

Quote:

---

Originally Posted by TheOriginalTB

Ok time for some of my findings with this mod (BIOS 0219).

Logitech mouse in the outmost USB port nearest the LAN - the BIOS hangs at USBINIT - moving the mouse to another USB port and it boots perfectly.

FSB 452 gives 448MHz, 551 gives 551, and 553 553MHz

Multiplier reverts back to std. when loading an OC profile, making the board unable to boot. Must select the correct lower multiplier after loading the OC Profile. This is only an issue when running lower multiplier than default.

NB temps are reported lower, doubt it's because the NB actually runs cooler..

CPU temps seems to be reported more realistic than on the 0907 MF BIOS - which gave me silly low temps. (like 9 deg at boot)

The board still overvolts like crazy on FSBTT, NB, RAM, and others.

Performance:

This BIOS IS slightly faster than the latest MF bios. With the same settings both read, copy and write were higher, but not by much - the latency however is about 1ns better.

Overclocking:
I have not been able to overclock more than with the MF BIOS, but this is probably due to my cpu more than the board.

With the MF bios I was able to run 500MHz FSB, with the RF bios I'm not even able to boot at 480MHz - major drawback..

Now I'm able to use all memory dividers - with the MF there were some dividers that wouldn't boot at all.

Software:
Windows do not need a reinstall - however Everest no longer detects NB voltage, SB voltage and vcore is reported wrong. (1.1 when actual 1.50)

But all in all - I think this will be a very good board with more matured RF BIOS's.

---

Set Legacy USB Support to enable
Grab the latest Everest 4.20.1307 Its a beta but it works great with this board.
On the MF I wasnt able to boot past 505 FSB now with RF bios I can boot 530FSB. Once you get the settings tweak'd I'm sure you can clock higher

with this mod, can come back to original p5e bios after turn on a rampage ? simply question :)

Yes you can change to P5E back (even to Maximus Formula is possible i think)

There is a known bug with usb glitch in X38.
I do not know how exactly appears.
Can someone describe it and tell if it has been fixed here?
The only that i can tell is that when leaving legacy support system hangs at
Windows when loading.

what are the old and what are the new revisions at now ?

Quote:

---

Originally Posted by iadstudio

idk, it might be more than that. I fried 2 sets of the new revision on my board and the old Ballistix I had were just fine. My voltage never went over 2.1v

I think there is something with the new Ballistix revisions that lets this board kill them at even modest voltage.

---

Quote:

---

Originally Posted by ericab

damn now i m worried if my warranty is voided, becasue i put the thermaltake memory heatpipes on mine... :confused:

---

I would just run your mem between 800-950, I dont even think you can notice the performance gain from 950+ on these DDR2's.

I notice the gains in timings way more than mhz. Drop it down to 900 and you can easily hit 4-4-4-10

and with only 2 sticks you can maybe hit 4-3-4-9 at 900mhz or less

Quote:

---

Originally Posted by Sources

what are the old and what are the new revisions at now ?

---

idk. As soon as they changed from the 2 sided sticks to the single sided ones, I stopped using them. There are a few threads around here dedicated to Ballistix. You might find some info there.

Quote:

---

Originally Posted by Grnfinger

Set Legacy USB Support to enable
Grab the latest Everest 4.20.1307 Its a beta but it works great with this board.
On the MF I wasnt able to boot past 505 FSB now with RF bios I can boot 530FSB. Once you get the settings tweak'd I'm sure you can clock higher

---

Legacy mode IS anebaled, also tried to disable it - same issue.

Can I use the new beta Everest on my current licence?

Tred to set everything as conservative as possible, but still no post at anything above 480 MHz FSB.

Quote:

---

Originally Posted by Spyrus

Many P5E users need to know what has been added in bios that is working and what is not.
1)Can you monitor more voltages?
2)Can you adjust more voltage options?
3)Have you all memory timings available of Rampage?
4)Are these settable?
5)Only second gigabit is excluded or and something else?

---

1) Yes, they are in the BIOS, but not in Everest and such.
1) Yes, the same as all of you with Maximus and Rampages.
3) Yes, the same as above. We literally have a Maximus now, minus volt LEDs, that second LAN and some temp sensors like NB and SB. They are all listed, but show weird results (-64ºC and such)
4) You can see it in the BIOS, but even if it is activated you will see anything in Windows (of course, it isn't really there :D)

Ok clear, have to inform my P5E friends.

Hi

Anybody here experienced this im not able to boot if I put memory in B channel the 2 on the right of the board, tried crucial ballistix 2 x 1024 44412, mushkin 2x2 gigbyte 6400 44412, and a pair og kingston ordinary brand, if I put both in A channel it boots fine but then no dual channel, its off course a Maximus formula board, just hangs at DET DRAM.

Kr Menty

wasup, and is necessary make a usb stick bootable with the hp tool :confused: or can format in windows and then only copy the afudos and the bios :shrug:

Quote:

---

Originally Posted by Renegade5399

Hey guys, heads up if you have DDR2 800 or 1066 Tracers 1GB sticks:

Link

Crucial has removed X38 and X48 from the compatible chipsets list for these sticks. Call them up yourself and ask them. On 3/7/08 the Engineering department invalidated the compatibility spec. The lady I had on the phone said she saw a "note in the system" dated 3/7/08 stating this.

---

That's so weird. I've never had any problems with my Ballistix on this board. If anything, 4x1 has been a lot better on X38 than on 680i.

mine actually ran great at 1130 2.15v, but one day I turnad it on and was getting errors. Happened twice. Always the new revision. idk if there was some kind of ripple or voltage anomaly, but the new revision sticks did not like my board.

Are your sticks single sided or double sided?

It seems my Ballistix have crapped out as well.
My system has been stable for weeks, running 24h Prime95 blend, 12 hour OCCT ram 12h, OCCT cpu 12h, to about 500% coverage on HCI memtest (ran 2 threads, 1500 MB on each).

Now, after I tried tightening the timings, and I went back to my stable OC Profile, it's not working anymore.
I get errors in HCI Memtest after like 10-20% and nothing I do with volts seem to have any influence at all.
The sticks have been running at 2.14v (BIOS) and 2.22v (Everest) all the time.

Oh well, I have ordered 2 sticks of 2GB Mushkin eXtreme Performance (XP2-8500).
Hopefully these will work better :)

Quote:

---

Originally Posted by DualCore

wasup, and is necessary make a usb stick bootable with the hp tool :confused: or can format in windows and then only copy the afudos and the bios :shrug:

---

You need to use the HP utility and the DOS image; after you put on afudos and the bios image and if you want you can create a .bat file that starts automatically afudos with the correct parameters.

You can not format from Windows a removable volume as a system one.

Quote:

---

Originally Posted by Brama

You need to use the HP utility and the DOS image; after you put on afudos and the bios image and if you want you can create a .bat file that starts automatically afudos with the correct parameters.

You can not format from Windows a removable volume as a system one.

---

yup, you can even create the bat in dos with the following commands

copy con afu.bat
afudos /iINSERTROMNAMEHERE /n /pbnc

ctrl + z

now you have a afu.bat! :up:

Quote:

---

Originally Posted by ZenEffect

yup, you can even create the bat in dos with the following commands

copy con afu.bat
afudos /iINSERTROMNAMEHERE /n /pbnc

ctrl + z

now you have a afu.bat! :up:

---

I was never able to boot from my USB stick; this force me to use it as a HD and boot from my Win98 CD to access it

Hi there guys,


I have to give this bios thing a run...

I´m using 0505 bios basically because with 0907 on experiments if i got the det ram thing and had to clr cmos or on/off (sometimes reset just didnt work!) only way to get it to boot again would be taking out the ram and reinserting old corsair twinx 6400. too much of an assle.
If i had sold those corsair rams i guess i would be screwed up!!


0505 is pretty much more stable, guess what?? for the rest is all together the same, even oc´ing.

My transcend axeram 1200 likes juice, so im feeding it 2.3vbios (2.4 everest) for 1173 (440x8 fsb strap 400) T 5-5-5-15, subtimmings all auto, static enabled, clocktwister strong, and enabled 0 (yes, ho hangs by mixing static read and performance enabled 0)

but i can only reach everest read 9.890 at 50.5 ns

Do you guys think i should give bios rampage 0219 a go?

somehow i feel i still need some more feedback days.

Quote:

---

Originally Posted by Mentaly

Hi

Anybody here experienced this im not able to boot if I put memory in B channel the 2 on the right of the board, tried crucial ballistix 2 x 1024 44412, mushkin 2x2 gigbyte 6400 44412, and a pair og kingston ordinary brand, if I put both in A channel it boots fine but then no dual channel, its off course a Maximus formula board, just hangs at DET DRAM.


Kr Menty

---

if its bios 0907 u prob have to swipe rams altogether and on blue slot 1 just to have a propper boot, then revert back to these ones

Quote:

---

Originally Posted by ZenEffect

yup, you can even create the bat in dos with the following commands

copy con afu.bat
afudos /iINSERTROMNAMEHERE /n /pbnc

ctrl + z

now you have a afu.bat! :up:

---

I wonder how many people here will remember basic dos pre-year 85 ?

ahahahahah prob not too many. I grew on that, which makes me quite old lolololol



greets

Quote:

---

Originally Posted by askimo

I was never able to boot from my USB stick; this force me to use it as a HD and boot from my Win98 CD to access it

---

neither did i, probably have to use a partitioning ap to create a primary one on the pen then format with system? i wonder. ill try

guess i might be SOL also since i have the 1066 crucial ballistix tracers too. so for everyone that has these ram sticks, are the single sided or double sided no longer compatible. and are the single sided sticks the revision? talk about some BS these companies cant get their compatibilities straightened out BEFORE they release their products.

in the mean time my sticks seem to still work. im goin to kick them down to 800 with a low voltage and possible tighten the timings to compensate for this disaster

I wouldn't be surprised to see some lawsuit at some point, either at Asus or the memory chip makers. This is not acceptable.

I know that even if I get my formula board running again, I doubt I'll buy Asus again. Never have I had so many problems with a motherboard. I've never spent this much money on a board before either... just proves that you don't always get what you pay for. I'm wishing I had went for that $67 Abit board (after rebates).

Does anyone who done the rampage mod using crossfire ??
Trying to get my 3870:s to work, can see both cards in CCC but Gpuz says Ati crossfire is Disable.

Any tips ??

Quote:

---

Originally Posted by Turbodream

Does anyone who done the rampage mod using crossfire ??
Trying to get my 3870:s to work, can see both cards in CCC but Gpuz says Ati crossfire is Disable.

Any tips ??

---

@ turbodream. make sure that crossfire is enabled in ccc if it is and does not work, reload the drivers.

@ ninogui. try hitting f8 on the post screen when you boot and select the usb stick as the boot device.