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

Quote:

---

Originally Posted by Eastcoasthandle

Do you have your ram at 2.224V from the bios or from Everest when going to 4-4-4-10? If not from the bios what voltage do you have set in the bios for Dram and northbridge?

---

I always refference the reported , effective voltages as reported by CMOS Power Management I wish many would follow this as it does get comfusing.

So YES, reported 2.24v by just about by PC Probe II and Everest. It may require a CMOS setting of 2.12v.

Should I try and flash back to 903 bios and see if I still get det dram error, or does it not allow me to do so using ez flash.

EZ-Flash (CMOS method) will not work, or didnt for me to revert back. The simplest way is Windows based ASUS Live Update. For XP x64 and server use v6.10x or compatable. under main options, check old BIOS to let it know you are recovering an olde BIOS ignoring the ROM date.

I never thought to try the DOS based EZ-Flash but I imagine it is the same as CMOS version, but worth a shot or plain old trusty AfuDOS with switches may work, I cant confirm that yet.

The 3rd is scarier then it sounds but I can say it works. attempting to reflach same BIOS rom you have now but cut PSU power off as it bigins to write new data. After a reboot, this promptes for the ASUS Crash Free BIOS Recovery Option. If you use this method, make sure you have only the ROM file you intend to flash on a CD or USB deivce by itself (no other BIOS ROM) or it will flash the first one it finds. It is fine to just use the CD too as it has origional BIOS v0402 as long you know your CPU will boot w/ it. As far as I know, this mobo was Penryn from day one anywayz.

If you do and you loose the DET_RAM, do let me know cause it didnt help for mine and any BIOS I was on form then on had quirks in it.

use afudos

make a dos bootable usb key, and use this file as it is the engineering software version of aufos.

http://www.xtremesystems.org/forums/...9&d=1205468995
copy the file mentioned above, and the rom image you want to flash to the usb key.

boot from usb key

in dos use


afudos /iROMNAMEHERE /n /pbnc

viola. :up:

1000000000x easier plus opens doors for more mods

Possible solution for some to eliminate "DET RAM" hang

Over the past few weeks of testing different OC configuations, I've being trying to completely eliminate the odd "DET RAM" hang. It only happends occasionally or some would say it appears when they start their system from a cold boot.

You can skip directly to PART 2 if your system is stable enough to pass hours of OCCT Mix and Prime Blend but still experiencing occasionl odd DET RAM hang during reboot or cold boot

Part I
What most people and I found about DET RAM hang issue is that the occasion for it to appear is related to the value of your FSB set accordingly. Usually people will starting to experience the first sign of DET RAM at around 440 ~ 450 FSB. And becouse everyone's system configurations are not identicle, there is not really a solution for all.

First thing to suggest is to check your CPU Vcore, make sure it's sufficient enough to pass 1hr CPU Prime/OCCT stress test.

Next we look at your NB and FSB voltages. FSB 1.40v bios set should be well enough to pass hours of Blend or Mix stress tests using Prime or OCCT even for the 65nm Q6600 G0 I've been testing with.

1.51v on the NB is a good starting point to troubleshoot the first sign of DET RAM hang, blue screen upon logging to windows, or blue screen/error detected/failure from Prime Blend or OCCT Mix.

As for CPU PLL, leave it at AUTO setting as the motherboard again overvolts in this area as well and AUTO setting will automatically scale with the given Vcore. Yes, auto setting is even enough to stable my 65nm Q6600 G0 at high 465+ FSB setting. If auto setting is good enough for 65nm quad, I believe it should be good enough for all 45nm cpu as they're even much easier to OC with given Vcore/CPU PLL.

Check your current Strap (266, 333, 400) and the ram divider set accordingly. This mobo works fairly poor using FSB 266 as opposed to its P35 chipset mobos. I'd recommend using 333 Strap for best overall system bandwidth. 400 Strap for further stability at high FSB setting but at the cost of overall system bandwidth.

Ram frequency/timings/relative given Vdimm: Make sure your desired given Vdimm is stable enough for its frequency and timings set. 2.12v bios set is a good starting point for OC DDR2-1066 modules as the mobo overvolts by ~0.8v which results in ~2.208v. Again each ram modules behaves differently, usually 5-5-5-15 for primary timings and rest subtimings set to AUTO or manually set to mobo's auto predetermined values are tight enough for daily use.

Part II
By adjusting my PCI-E Frequency from 110 to 112 finally solves the oddity of DET RAM hang or called the "black screen". This explains why no matter how high I've tried to raise the FSB voltage, CPU PLL voltage, SB voltage, loosen timings, higher CPU Vcore and higher Vdimm wouldn't completely eliminate DET RAM hang. If you are currently in the same situation where I was, I highly suggestion you try raising your PCI-E Frequency to a certain frequency that may aid you from getting DET RAM hang. Please note that this area isn't the priority when OC and it should only be overlooked when you're experiencing occasional odd DET RAM hang during reboot or cold boot but yet the system is stable under hours of stress tests.

RAMPAGE FORMULA 0219 BIOS.
Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 8
FSB Frequency : 465
FSB Strap to North Bridge : 333
PCI-E Frequency: 112 No more DET RAM hang ("Black screen")
DRAM Frequency: DDR2-1116
DRAM Command Rate : 2T
DRAM CLK Skew on Channel A : Normal
DRAM CLK Skew on Channel B : Normal
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 4 (TRCD)
RAS# Precharge : 4 (TRP)
RAS# ActivateTime : 10 (TRAS) TRAS = TRCD + TRP + 2 (4 + 4 + 2 = 10) For stability, this setting should not be set lower than this given formula.
RAS# to RAS# Delay : 3
Row Refresh Cycle Time : 35 (AUTO = 42)
Write Recovery Time : 6
Read to Precharge Time : 3

Read to Write Delay (S/D) : 8
Write to Read Delay (S) : 3
Write to Read Delay (D) : 5
Read to Read Delay (S) : 4
Read to Read Delay (D) : 6
Write to Write Delay (S) : 4
Write to Write Delay (D) : 6

Write to PRE Delay : 14
Read to PRE Delay : 5
PRE to PRE Delay : 1
ALL PRE to ACT Delay : 5
ALL PRE to REF Delay : 5

DRAM Static Read Control: Disabled
Ai Clock Twister : Stronger
Transaction Booster : Manual

C/P: A1 A2 A3 A4 A5 | B1 B2 B3 B4 B5
LVL: 07 07 07 07 07 | 07 07 07 07 07

Common Performance Level [7]

Pull-In of CHA PH1 Disabled
Pull-In of CHA PH2 Disabled
Pull-In of CHA PH3 Disabled
Pull-In of CHA PH4 Disabled
Pull-In of CHA PH5 Disabled
Pull-In of CHB PH1 Disabled
Pull-In of CHB PH2 Disabled
Pull-In of CHB PH3 Disabled
Pull-In of CHB PH4 Disabled
Pull-In of CHB PH5 Disabled

CPU Voltage : 1.46750 (1.452)
CPU PLL Voltage : AUTO (1.664-1.680)
North Bridge Voltage : 1.65 (1.680) *Note: high 1.65v NB is absolutely needed for hours of stability under Prime mix and OCCT blend stress tests. Using *8 multi Q6600 G0 at high FSB is indeed putting a lot more stress on the NB but also allows the system to gain greater amount of system bandwidth from using *9 multi of the same CPU frequency with relatively lower FSB.
DRAM Voltage : 2.12 (2.208)
FSB Termination Voltage : 1.40 (1.456)
South Bridge Voltage : 1.10 (1.12)
Loadline Calibration : Enabled
CPU GTL Reference : 0.63X
North Bridge GTL Reference : 0.67X
DDR2 Channel A REF Voltage : AUTO
DDR2 Channel B REF Voltage : AUTO
DDR2 Controller REF Voltage : DDR2-REF (1.104)
SB 1.5V Voltage : 1.5 (1.54v)

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

Possible solution for some to eliminate "DET RAM" hang

Over the past few weeks of testing different OC configuations, I've being trying to completely eliminate the odd "DET RAM" hang. It only happends occasionally or some would say it appears when they start their system from a cold boot.

You can skip directly to PART 2 if your system is stable enough to pass hours of OCCT Mix and Prime Blend but still experiencing occasional odd DET RAM hang issue during reboot or cold boot.

Part I
What most people and I found about DET RAM hang issue is that the occasion for it to appear is related to the value of your FSB set accordingly. Usually people will starting to experience the first sign of DET RAM at around 440 ~ 450 FSB. And becouse everyone's system configurations are not identicle, there is not really a solution for all.

First thing to suggest is to check your CPU Vcore, make sure it's sufficient enough to pass 1hr CPU Prime/OCCT stress test.

Next we look at your NB and FSB voltages. FSB 1.40v bios set should be well enough to pass hours of Blend or Mix stress tests using Prime or OCCT even for the 65nm Q6600 G0 I've been testing with.

1.51v on the NB is a good starting point to troubleshoot the first sign of DET RAM hang, blue screen upon logging to windows, or blue screen/error detected/failure from Prime Blend or OCCT Mix.

As for CPU PLL, leave it at AUTO setting as the motherboard again overvolts in this area as well and AUTO setting will automatically scale with the given Vcore. Yes, auto setting is even enough to stable my 65nm Q6600 G0 at high 465+ FSB setting. If auto setting is good enough for 65nm quad, I believe it should be good enough for all 45nm cpu as they're even much easier to OC with given Vcore/CPU PLL.

Check your current Strap (266, 333, 400) and the ram divider set accordingly. This mobo works fairly poor using FSB 266 as opposed to its P35 chipset mobos. I'd recommend using 333 Strap for best overall system bandwidth. 400 Strap for further stability at high FSB setting but at the cost of overall system bandwidth.

Ram frequency/timings/relative given Vdimm: Make sure your desired given Vdimm is stable enough for its frequency and timings set. 2.12v bios set is a good starting point for OC DDR2-1066 modules as the mobo overvolts by ~0.8v which results in ~2.208v. Again each ram modules behaves differently, usually 5-5-5-15 for primary timings and rest subtimings set to AUTO or manually set to mobo's auto predetermined values are tight enough for daily use.

Part II
By adjusting my PCI-E Frequency from 110 to 112 finally solves the oddity of DET RAM hang or called the "black screen". This explains why no matter how high I've tried to raise the FSB voltage, CPU PLL voltage, SB voltage, loosen timings, higher CPU Vcore and higher Vdimm wouldn't completely eliminate DET RAM hang. If you are currently in the same situation where I was, I highly suggestion you try raising your PCI-E Frequency to a certain frequency that may aid you from getting DET RAM hang. Please note that this area isn't the priority when OC and it should only be overlooked when you're experiencing occasional odd DET RAM hang during reboot or cold boot but yet the system is stable under hours of stress tests.

RAMPAGE FORMULA 0219 BIOS.
Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 8
FSB Frequency : 465
FSB Strap to North Bridge : 333
PCI-E Frequency: 112 No more DET RAM hang ("Black screen")
DRAM Frequency: DDR2-1116
DRAM Command Rate : 2T
DRAM CLK Skew on Channel A : Normal
DRAM CLK Skew on Channel B : Normal
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 4 (TRCD)
RAS# Precharge : 4 (TRP)
RAS# ActivateTime : 10 (TRAS) TRAS = TRCD + TRP + 2 (4 + 4 + 2 = 10) For stability, this setting should not be set lower than this given formula.
RAS# to RAS# Delay : 3
Row Refresh Cycle Time : 35 (AUTO = 42)
Write Recovery Time : 6
Read to Precharge Time : 3

Read to Write Delay (S/D) : 8
Write to Read Delay (S) : 3
Write to Read Delay (D) : 5
Read to Read Delay (S) : 4
Read to Read Delay (D) : 6
Write to Write Delay (S) : 4
Write to Write Delay (D) : 6

Write to PRE Delay : 14
Read to PRE Delay : 5
PRE to PRE Delay : 1
ALL PRE to ACT Delay : 5
ALL PRE to REF Delay : 5

DRAM Static Read Control: Disabled
Ai Clock Twister : Stronger
Transaction Booster : Manual

C/P: A1 A2 A3 A4 A5 | B1 B2 B3 B4 B5
LVL: 07 07 07 07 07 | 07 07 07 07 07

Common Performance Level [7]

Pull-In of CHA PH1 Disabled
Pull-In of CHA PH2 Disabled
Pull-In of CHA PH3 Disabled
Pull-In of CHA PH4 Disabled
Pull-In of CHA PH5 Disabled
Pull-In of CHB PH1 Disabled
Pull-In of CHB PH2 Disabled
Pull-In of CHB PH3 Disabled
Pull-In of CHB PH4 Disabled
Pull-In of CHB PH5 Disabled

CPU Voltage : 1.46750 (1.452)
CPU PLL Voltage : AUTO (1.664-1.680)
North Bridge Voltage : 1.65 (1.680) *Note: high 1.65v NB is absolutely needed for hours of stability under Prime mix and OCCT blend stress tests. Using *8 multi Q6600 G0 at high FSB is indeed putting a lot more stress on the NB but also allows the system to gain greater amount of system bandwidth from using *9 multi of the same CPU frequency with relatively lower FSB.
DRAM Voltage : 2.12 (2.208)
FSB Termination Voltage : 1.40 (1.456)
South Bridge Voltage : 1.10 (1.12)
Loadline Calibration : Enabled
CPU GTL Reference : 0.63X
North Bridge GTL Reference : 0.67X
DDR2 Channel A REF Voltage : AUTO
DDR2 Channel B REF Voltage : AUTO
DDR2 Controller REF Voltage : DDR2-REF (1.104)
SB 1.5V Voltage : 1.5 (1.54v)

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

@ kup

do you think performing the vdroop mod helped with o/c or o/c stability? i know you said you had a problem that was fixed by re-applying the mod, just curious about your thoughts on this matter. im trying to squeeze every last drop out of my rig.

Quote:

---

Originally Posted by XtremeTiramisu

Possible solution for some to eliminate "DET RAM" hang

---

I'm sill not getting a clear answer from the peepz experiencing this DET_RAM issue.

I am talking about fresh after BIOS flash and clearing of CMOS. For the ones experiencing this, are you guys on hacked RAMPAGE BIOS or BETA v0907 and above?

has anybody on and only on final BIOS experiencing this at all? Is anybody on and ONLY on BERA BIOS v0901 - v0903 experiencing this as well. (excluding those who even flashed once to v0907 and back to something else)

I'm trying to clear up or compile some statistis on this when and aftering flashing of BETA BIOS v0907.

Mine did this ONLY on and since v0907. It never did that on v0903 and below for over 4months of many OC tests ewach stock and OC and vatious RAMs.

ThanX!

Right now I am on bios 1004. I will flash to bios 903 tomorrow and see if it helps. If it does not I will do the Rampage mod. If it still does not work I will try to RMA it to Asus.

Well after messing round with my new , 2nd SE mobo, I found out it is very picky on its beta v0903. Yet, if and if once setteled out, it is fine for the day. Even works in S3 mode on my 5:6 divider. My old one never did that on any BIOS version except v0903 but it was hit or miss. most days it would just fail to resume.

I still cant use FSB strap manual to 400 and is pick if I set RAM freq. to something equal of 1:1, but 5:6 is cool even to 500FSB for my DDR1200. It is also very picky if I try to enable Performance Booster, even to just (0) when at 480+ FSB in 5:6 CPU/RAM. Ai Clock Twister @ "Strong" is iffy, too unstable to Prime for long, but that's to be expected with an already high OC.

Removing the X38 IHS proved good. Idle temps went down by -1c (AR5 is not completely set in yet), but loading is lower by almost -4c. It is helping SB by 1c too, but this is mainly due to 80mm fan off ThermalRight RAM sinks. A draft blows right down into it and under the ROG badge.

For the hardest hang up, I had to clear CMOS and tap atx pwr periodically for almost 1min. this was enough to discharge caps of stored energy. It would then fire right up and let me load my profile save. When it did hang, it was sometimes during IDE_DET or mostly during Intel Matrix RAID detection. swopping a single SATA disc as IDE mode didnt matter here.

EDIT: Here's the weird thing, now after I got it back in order, it takes a longer time to detect my RAID array on Intel. Is this possable to hard crashing on RAID disc.

Otherwise, it's doing OK so far on day 2 of testing.

Quote:

---

Originally Posted by ZenEffect

@ kup

do you think performing the vdroop mod helped with o/c or o/c stability? i know you said you had a problem that was fixed by re-applying the mod, just curious about your thoughts on this matter. im trying to squeeze every last drop out of my rig.

---

I think it did. It definitely made it more stable. With LLC and the vDroop mod I the vCore would go a tiny bit over bios set values on Load. :up:

Quote:

---

Originally Posted by cajer

I can not put any fans on my nb or sb because my 9800GX2 commpletly covers my SB and my TRUE's fans compelety cover my NB. :( Any other ways to cool my NB and SB?

---

well perhaps uou dont need to install fans on the NB or SB if you remove the cooling pipe option that comes with the mobo. just get rid of them and install a couple of HR05SLI/IFX thermalright sinks there and you should see a good temperature drop. and yes they are a tight fit but i have managed a way around it by rotating things around and i believe that you can do it too. consider that i have a 120 U-Extreme, 2 HR05 and a HR03plus on my 8800GTS. so it definitely can be done and with good effect too.

Quote:

---

Originally Posted by Nuckin_Futs

Has anybody else removed their X38 chipset IHS for added cooling efforts on NB? I did it for now to see how I like it just like we used to do with our A64's. It's already added a 2c drop and it hasnt even set in yet (using AS#5) I used OEM cooing for now till I get the correct mounting for my HR-05-SLI. It screws down just fine without the slab of plated copper inbetween. If needing it for leveling, one can lap the inside and reseal but w/ AS cement.

Oh ya, I finally got my mobo back and it's up and running back to normal. They returned it back to me w/ BETA BIOS v0903, figured it'd be a final like v0802. I'd just go back to v0602 since uit was the most reliable for my set.

---

i think most of us have around here. i for one did it as soon as i took the mobo out of the box. took my wife's hair dryer and got to work on it one morning while she was asleep. :rofl: got caught anyway. but i have seen my temps are quite good. i am still tinkering though right now.

on a separate question that you had about the 0907 Bios, i had just recently flashed to that version and have no problems at all with my system. its running pretty rock solid overclocked and all.

Correct me if I am wrong, but this thread seems to be support for the x38 and not the P35 version. Can anyone point me to a thread dedicated to the P35 support here or somewhere else? I have one coming in to replace my Gigabyte P35-DS3R. I went with the Blitz Formula due to price that I got it at, voltage adjustments and the plethora of features compared to my Gigabyte. Any suggestions concerning the setup would be helpful. I have read various posts and have some ideas, but I have some specific questions that I would like to get answered.

1 - Since I already have my OS installed with raid and I am using a ICH9R chipset already do I need to do anything special to get the new MB to recognize the raid?

2 - Any gotcha's I need to be aware of when first setting this board up?

Thank you in advance for any help on this,

Utnorris

Tbh, 99% of the info in here applies to the Blitz as well. I owned both side by side and any tweaks I could apply to the Maximus also worked on the Blitz.

Just don't performa the Maximus mods on the Blitz!!!!!

Thanks for the quick response. Any idea about the raid question?

Utnorris

Quote:

---

Originally Posted by Nuckin_Futs

I always refference the reported , effective voltages as reported by CMOS Power Management I wish many would follow this as it does get comfusing.

So YES, reported 2.24v by just about by PC Probe II and Everest. It may require a CMOS setting of 2.12v.

---

What is your Northbridge chipset voltage set to in the bios?

Quote:

---

Originally Posted by Utnorris

Thanks for the quick response. Any idea about the raid question?

Utnorris

---

Not really sure of RAID, if I'm honest. A few of the other chaps here are far more versed on the ins and outs of RAID and should be able to help you?

Guys I just bought a maximus my e3110 does 9x450 np but the chip in my P5K-E would do 8x512fsb any suggestions on voltage etc in the bios to get my maximus up to 500 fsb. The P5k-E only needed 1.36v to get it there on the core. I'm sure the maximus can match it any suggestion on settings?

Quote:

---

Originally Posted by Utnorris

1 - Since I already have my OS installed with raid and I am using a ICH9R chipset already do I need to do anything special to get the new MB to recognize the raid?

---

You need to enable RAID in the bios, get into the RAID ROM, setup your array to your liking, head back to the boards BIOS if you have additional drives to set it as the boot drive (if intended).

For OS install use the traditional F6 pressing step.

Install the Intel RAID manager and set your RAID volume to enable "write back cache".

If you want you can also cut the array into pieces, which'll also increase performance...

For more info, check this thread:
http://www.xtremesystems.org/forums/...d.php?t=166867

Hey guys, I've spent hours reading this post, tons of great info but can't seem to find what I need. Does anyone have an e8400 running at 4.0 with 0907 bios? If so, please post your settings.

Thanks!

Why do you all suggest to people to use 333 strap?
266 is working just fine....only with the 4:5 it has a few issues but usually some other function is a reason like dram static or Tbooster..

Using moderate needs lower nb voltage.
Try using moderate and the problems may dissapear with det ram
even with your previous setting of pciexpress frequency and other

I have extreme problem:
Only ALL 3 DRAM led are ON, and nothing else (fans are working fine). There is no beep, no picture (I've try to change ram, moved ram to different slots,... even without ram) ANY IDEAS WELCOME:confused: :confused:

Quote:

---

Originally Posted by wreckwriter

Hey guys, I've spent hours reading this post, tons of great info but can't seem to find what I need. Does anyone have an e8400 running at 4.0 with 0907 bios? If so, please post your settings.

---

Do a search in this thread for Zucker2k and Grnfinger in this thread. They've both posted their E8400 BIOS settings a number of times, IIRC. If you're still having problems, it might be easier for you to post your settings... and especially your system specs!!!

This board pwns the E8400!

Quote:

---

Originally Posted by Utnorris

Correct me if I am wrong, but this thread seems to be support for the x38 and not the P35 version. Can anyone point me to a thread dedicated to the P35 support here or somewhere else? I have one coming in to replace my Gigabyte P35-DS3R. I went with the Blitz Formula due to price that I got it at, voltage adjustments and the plethora of features compared to my Gigabyte. Any suggestions concerning the setup would be helpful. I have read various posts and have some ideas, but I have some specific questions that I would like to get answered.

1 - Since I already have my OS installed with raid and I am using a ICH9R chipset already do I need to do anything special to get the new MB to recognize the raid?

2 - Any gotcha's I need to be aware of when first setting this board up?

Thank you in advance for any help on this,

Utnorris

---

If you're going to the same chipset the RAID might migrate to the new board, but I don't think it'll work on a different chipset. I've done Nvidia 570 to 680i RAID migration and it worked, but never tried the ICH9R. I did however move a RAID from one Maximus to the other and it was fine. I would suggest you back everything up and cross your fingers. It just might work but I'm not sure.

Also, like Wolf2000me said. Set everything in your and bios properly, but you shouldn't need to setup the RAID utility. You could go in ther to see if ti recognizes your array, but obviously you do not want to change the stripe size, format or anything in there or it will overwrite and your RAID will not work. (I'm pretty sure about this but I do not know what "write back cache" does)