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

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.

Thanks!

---

4.0GHz is walk in the park.
Post your bios settings and we can see what needs to be adjusted

Quote:

---

Originally Posted by Spyrus

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

---

Thanks for the tips. I will try that and see if that helps to bring my Q6600 config up to 475*8 with 5/6 divider using the same current NB Volt or lower.

Reverting to older bios didn't work and cooling my NB with the Antec spot cool didn't work. (Although it dropped my temps by 6 degrees C.) I can't flash my bios to the Rampage bios because my USB stick refuses to become bootable. I also tried the settings that you guys said would get rid of the det dram. error but it still did not work. Any other ways to get rid of the det dram. error above 440 fsb?

Hello! I've been following this thread (and a few others) since this past weekend. I've just been waiting (for 4 days!) for the ability to post... :)

My issues are incredibly odd with the board. It sounds like Nuckin_Futs and Eastcoasthandle are in similar situations...

Basically I have all kinds of rididculous boot issues if i touch anything in manual mode in the BIOS. I've even (after clearing the cmos) gone into the bios, changed nothing, save/exit'd and it just powers off. Turning the PSU off until the board LEDs clear, and then back on again will often get it to boot.

Quote:

---

Originally Posted by Eastcoasthandle

Your post isn't to clear for me but I'll try to answer (both 907 and 1004 yield the same results):
-When I first got my MF it would not boot with my PC8500 ram. I just so happen to put in my PC6400 ram and it worked. I later installed my PC8500 ram and it worked but that was only after I installed the PC600 ram. My northbridge voltage was left at auto. I had my PC8500 at 2.02Volts in the bios (Everest reads 2.128V). At this point everything was working fine. I had no problems whatsoever but, I realized that my norhtbridge voltage was reading higher then I liked at 1.64V. So I decided to manually set it to 1.43V.
-All was well for a few days. I never counted the number of days. Then one morning it would no longer cold boot (plugging in the power cord to a wall socket for example) with det-dram hangs. I switched back to PC6400 and had no problem. PC8500 ram would only work only after I re-installed PC6400 ram 1st. To make a long story short, as long as I didn't unplug the power cord from the wall socket I could warm boot with PC8500 ram just fine. If I removed all power from the PC and left it alone for at least 5-8 hours I would get a det-dram hang with PC8500 ram. The only fix was to up the voltage on the NB to 1.55V which has worked for 3 consecutive days in a row with no power, cold boot-up. This cold boot was after a complete power shut off from the wall socket for more then 5+ hours (IE the power strip was turned off).

---

I've tried a variety of BIOS versions to no avail.

I recently tried a full cmos clear after re-flashing 1004 (removed memory, cmos battery, left overnight, etc). After putting the pieces back together my system seemed to have no issues until after a few hours and it was right back to the odd boot issues.

I too discovered that jamming the on-board power button a number of times after a failed post would sometimes get it to boot-up.

Sometimes if I remove or unplug some components/fans from the motherboard I can also get it to boot up. Once I've successfully booted and successfully gotten some OC settings applied. I can plug everything back in with no boot issues (so long as I leave the PSU switch on the whole time).

I've gotten my QX9650 up to 4 ghz with (10*400 and 12*333) and stable. I'd still love to tweak some things but having to deal with clearing my cmos and redoing the settings again and again is driving me insane (I can't just save my settings to a profile as I often have to incrementally adjust the settings or it seems to freak out and not boot).

However, the problems all come back again the moment I turn off the power switch on the PSU. Once it loses that it's the same issues aaall over again.

I'm trying eastcoast's suggestion of pumping the NB voltage up to see if that gets me anywhere, but it's not looking good.

Any help or suggestions would be greatly appreciated. I've been banging away on this thing since last Friday.

All I can say is that I'm using a E8400 so I don't have to go as high on the NB voltage. Plus, I am using fans on both north and south bridge heatsinks. If you are using a quad and over clocking higher then 400 (were I am comfortable with) one suggsstion is that you may need to go higher then 1.55V (for example 1.59Vor 1.60V depending on your FSB) on the northbridge with proper cooling. It's really all trial and error if the MB is actually working properly. Can both of your guy post your current Extreme Tweaker settings (IE: What setting you tried that didnt' seem to work)?

Quote:

---

Originally Posted by iadstudio

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)

---

Volume write-back cache greatly increases performance, certainly in benching. Run a HD tach bench enabled and disabled, you'll be pleasantly surprised.
It's not a bios option of course, you'll find it in the Matrix Storage Console.

I'd never recommend installing an OS on one chipset and later replace it on a different chipset. I've seen it work a few times but never without any hiccups. It's not a good idea at all, imho. I wouldn't give a eurocent for the OS' stability and it also adds a new stability variable when overclocking.

For just swapping out data it's a piece of cake when using the same RAID controller. Don't rebuild it, just plug it in and see if it gets detected correctly.
Then it's generally good practice to go back to the system bios and check out the boot order, among other things.

Utnorris...
If you do want to go down the OS swapping road, see if it boots. If it does then the first thing I'd do is install the chipset drivers for X38 after the swap.

Uninstall most of your drivers when you're still on the P35 board but make sure the storage driver is still live.

Quote:

---

Originally Posted by Eastcoasthandle

... Can both of your guy post your current Extreme Tweaker settings (IE: What setting you tried that didnt' seem to work)?

---

I can set absolutely nothing in the BIOS after a fresh CMOS clear, and it will exhibit this behavior. Which is - Enter bios after cmos clear, save/exit - Computer turns off (LCD still reads EN SETUP). Computer will not power back on except when I turn off the PSU - wait for MB LEDs to clear - turn PSU back on. Computer will turn on and I can even save out a few setting adjustments in the BIOS.

That aside... I finally got to my breaking point and took apart my file server so I can try its PSU out, which is a:

Thermaltake W0131RU ATX12V / EPS12V 850W Power Supply

So far it seems like the issues of turning the PSU off and not being able to boot up with OC settings afterwards are gone. It will try to power on, turn back off again, then a second later power back up. The POST screen shows the correct settings I had enabled for OCing, but I'll get an error message after it goes through the entire POST (hard drive/raid read-outs and all).

"ERROR! The CPU core to bus ratio or VID configuration has failed!
Please enter BIOS setup to re-config it.

F1 for setup
F2 for defaults"

Interestingly enough, if I just hit the reset switch on my computer it reboots and I load up windows just fine w/o ever having to go back into the BIOS...

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?

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

---

YES, moving an Intel RAID will migrate easily from P35 to X38/X48, even an older !975x on ICH8R will go (only needing chipset INF update). Just configure as in other mobo and you're good to go> INF appears to be fine but you can update with driver from this mobo CD.

I'd say stick to the final BIOS for now untill you find they dont cut it then take the chance on BETA. Notice the many issues in this tread and other to BETA BIOD mainly 907 and above. Start w/ CPU section in full auto till you get RAID and drivers up to date, before any OC'n. I found v0602 to be the best for mine, but newer CPU's may have other needs. In v0802, For most BIOS vers. keeping FSB strap and RAM frequency to Auto is most stable for 1:1 (some will let you move RAM spd for certain dividers other then 1:1).

Quote:

---

Originally Posted by Eastcoasthandle

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

---

NB= 1.504v for up to 500FSB w/ dual in 1:1, in 5:6 (5:6 needs a tad more of each PLL FSBT and GTL_Ref)

Quote:

---

Originally Posted by cajer

Reverting to older bios didn't work and cooling my NB with the Antec spot cool didn't work. (Although it dropped my temps by 6 degrees C.) I can't flash my bios to the Rampage bios because my USB stick refuses to become bootable. I also tried the settings that you guys said would get rid of the det dram. error but it still did not work. Any other ways to get rid of the det dram. error above 440 fsb?

---

I figured it wouldn't , v0907 corrupted mine too so no matter what I did from then on didnt help. Maybe you 'll have better luck.

To make sure card reader is bootable, leave all USB and floppy Emulate options to AUTO, or it wont see a lot of flash drives. NOTE, it doesnt have to be thumb drive, make use of most popular USB mass storages divices you may alread own. iPod, PSP, and most MP3 Media players. Just make sure to follow the file & floder naming rules for FAT_32 DOS, all caps, no spaces. It can even be from full sized HDD as long as it meetsa those rules (FAT_32, single partition).

Also check on ASUS forum to make sure the RAMPAGE hack is not gonna' void your warrenty and you can revert back without them knowing, cause w/ all this hacking, an RMA is not unrealistic nowdays.

Quote:

---

Originally Posted by jwfitt

I can set absolutely nothing in the BIOS after a fresh CMOS clear, and it will exhibit this behavior. Which is - Enter bios after cmos clear, save/exit - Computer turns off (LCD still reads EN SETUP). Computer will not power back on except when I turn off the PSU - wait for MB LEDs to clear - turn PSU back on. Computer will turn on and I can even save out a few setting adjustments in the BIOS.

That aside... I finally got to my breaking point and took apart my file server so I can try its PSU out, which is a:

Thermaltake W0131RU ATX12V / EPS12V 850W Power Supply

So far it seems like the issues of turning the PSU off and not being able to boot up with OC settings afterwards are gone. It will try to power on, turn back off again, then a second later power back up. The POST screen shows the correct settings I had enabled for OCing, but I'll get an error message after it goes through the entire POST (hard drive/raid read-outs and all).

"ERROR! The CPU core to bus ratio or VID configuration has failed!
Please enter BIOS setup to re-config it.

F1 for setup
F2 for defaults"

Interestingly enough, if I just hit the reset switch on my computer it reboots and I load up windows just fine w/o ever having to go back into the BIOS...

---

I'm curious, cause I got simular, but isor was this after a trial on BETA v0907? Or if you F2, will it boot to OS as defualt? Mine did. But yet if I F1'd to change so much as anything (excluding RAM timings and Freuency), it would always hang at the DET_RAM, requiring hard reset to get teh F1 or F2 option again.

So I could get past if I at least set RAN to manual timings and frequency for my RAM. For initial test, I used DDR800 @ 5-5-5-15 for the RAM in sig with 2.0vdimm (as overvolted by CMOS from BIOS 1.8 setting).

So does this work for you too? I knwo it's not normal but just curious.

I know a lot of peepz say they used v0907 and had no "quoted" issues, so maybe it's isolated to a few, or just mine. I also see a lot of peepz claiming the DET_RAM has to do with NB or VDIMM , but not for mine. It happened with stock rated DDR800. And for me, It only happened after V0907 test and moving back to v0802.

Quote:

---

Originally Posted by Grnfinger

Both Maximus threads are muddy now, part2 was for INFORMATION only, not chatting and bench scores ect. Instead ppl chose to double post.
To bad cause alot of information is burried now and I dont blame Kup for not updating the main page

---

What are your bios setting bro I would like to see if my chip can match yours.

i wonder about some setting in the bios.. restore on ac poweer loss.. could this settings effect the boot problems people are having.. i don't have that boot problem but i think i have a tweaky nb problem with 4x1 pc8500 at 1080 and no water yet my temps at 1.51 (1.55 actuall) volts with fan blowing on it get up to 53-54 loaded way less then before i put on the fan but i still have a couple random crashes only when heavy gaming on certain servers with more eye candy than most. i also get a few random hard drive/data loss errors where my raid has to rebuild.

Real quick, so all of us can compare notes! Is there anybody here who never flashed to BETA v907 but has these DET_ hang issues now? and or has also moveed to a BETA BIOS after v0907 and now experienced them?

Please take a moment to share so it can help others.

Thanx!

i can't help.. i went from 401 to 903 and then 907. i never had the boot problem. i must have been lucky. so lucky to get a board with a different problem (hot nb) that hasn't gone away with any of the bios changes i tried. my memory tests out the only thing for me to do is remove the stock nb heat sink and reseat or add water to cool it down. which kind of sucks that i have to take my whole computer apart then dismantle the heat sink and void the warranty so it can run the way it should have right out of the box.

Quote:

---

Originally Posted by Wolf2000me

Volume write-back cache greatly increases performance, certainly in benching. Run a HD tach bench enabled and disabled, you'll be pleasantly surprised.
It's not a bios option of course, you'll find it in the Matrix Storage Console.

I'd never recommend installing an OS on one chipset and later replace it on a different chipset. I've seen it work a few times but never without any hiccups. It's not a good idea at all, imho. I wouldn't give a eurocent for the OS' stability and it also adds a new stability variable when overclocking.

For just swapping out data it's a piece of cake when using the same RAID controller. Don't rebuild it, just plug it in and see if it gets detected correctly.
Then it's generally good practice to go back to the system bios and check out the boot order, among other things.

Utnorris...
If you do want to go down the OS swapping road, see if it boots. If it does then the first thing I'd do is install the chipset drivers for X38 after the swap.

Uninstall most of your drivers when you're still on the P35 board but make sure the storage driver is still live.

---

write-back cache enabled bumped me up 25 MB's in most of my HDD bench's. Thanks :up:

Quote:

---

Originally Posted by Nuckin_Futs

I'm curious, cause I got simular, but isor was this after a trial on BETA v0907? Or if you F2, will it boot to OS as defualt? Mine did. But yet if I F1'd to change so much as anything (excluding RAM timings and Freuency), it would always hang at the DET_RAM, requiring hard reset to get teh F1 or F2 option again.

So I could get past if I at least set RAN to manual timings and frequency for my RAM. For initial test, I used DDR800 @ 5-5-5-15 for the RAM in sig with 2.0vdimm (as overvolted by CMOS from BIOS 1.8 setting).

So does this work for you too? I knwo it's not normal but just curious.

I know a lot of peepz say they used v0907 and had no "quoted" issues, so maybe it's isolated to a few, or just mine. I also see a lot of peepz claiming the DET_RAM has to do with NB or VDIMM , but not for mine. It happened with stock rated DDR800. And for me, It only happened after V0907 test and moving back to v0802.

---

I'm pretty sure we've been chatting over on extremeoverclocking.com too, but let me reiterate for the benefit of everyone else as well.

I did receive the F1/F2 for defaults option after clearing the cmos to try to get the machine running again. Unfortunately, using F2 for defaults did nothing for me as my vista install was on a raid config. Going into the BIOS and save/exit'ing (w//o even changing a thing) would cause the computer to turn off completely. However, if i turned off the PSU until the MB LEDs cleared, and turned it back on I could then start up the machine and the settings I applied would be there.

From that point on the machine would be VERY finnicky. Like if at any time I went into Manual OC mode, and even left everything at defaults, and the power from the PSU was ever lost or manually turned off to the point where the board LEDs cleared, turning it back on wouldn't happen without another CMOS clear.

Sometimes, if i tapped the on-board power button a bunch of times after it tried to start up it would give it a 2nd go and load up fine - even with a lot of OC settings enabled.

I tried pumping my NB all the way up to 1.71ish and still these "cold boot" issues would happen.

I recently (as I mentioned in an earlier post) stuck the PSU from server into this box...same exact PSU basically except this one is 850W vs the newer 1200W PSU I was using.

So far all seems to be functional now.

The strange thing is the machine would run completely fine at stock and OC settings ONCE it got booted. It's like it wasn't getting enough juice at power-on...

Gonna keep testing my rig with the 850W PSU now... I'll keep you updated.

Quote:

---

Originally Posted by loften

i wonder about some setting in the bios.. restore on ac poweer loss.. could this settings effect the boot problems people are having.. i don't have that boot problem but i think i have a tweaky nb problem with 4x1 pc8500 at 1080 and no water yet my temps at 1.51 (1.55 actuall) volts with fan blowing on it get up to 53-54 loaded way less then before i put on the fan but i still have a couple random crashes only when heavy gaming on certain servers with more eye candy than most. i also get a few random hard drive/data loss errors where my raid has to rebuild.

---

I did not have a chance to try this out, but I'm working well on an older (almost identical but smaller W) 850W PSU.

Thermaltake W0131RU ATX12V / EPS12V 850W Power Supply

The one I was using before (1200W) is still in my sig.

Hey, thanks for all the responses everyone. I didn't think it would be an issue since I am going from one P35 with ICH9R to another P35 with ICH9R chipset. I had just read a few posts where people were having problems with raid on the Blitz Formula P35 and I wanted to be ready for it. Now I just need to get the board here and finish my custom case and drain my W/C system so I can set it up on the new board. I am friggin stoked about this board, I am hoping I can run 4Ghz (450x9) with the added voltage settings. My Gigabyte goes from 1.6 to 1.8 with no in between and with vdroop I just can't get it stable at 4Ghz and I am betting it just needs a little more juice. Anyway, I will try some of the settings listed in the forums to see if they work for me.

One other question and I haven't done much research, but is there a SLI driver for P35 boards floating around? Just curious since this board comes set up to run 2 cards (although they are for CF) and I would love to add a 2nd 9600GT card to the system.

Again, thank you everyone for all the replies,

Utnorris

Quote:

---

Originally Posted by XtremeTiramisu

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

---

Has anyone tried this yet?

that is kind of interesting about the psu thing.. hmmmm.. i don't know anything about the boot problems. i have never experienced them.. maybe people with multi 12v rail psu's are having problems on this board.. mine is a single rail x3 1k. it works good.. i just have a different problem.

Quote:

---

Originally Posted by Utnorris

One other question and I haven't done much research, but is there a SLI driver for P35 boards floating around? Just curious since this board comes set up to run 2 cards (although they are for CF) and I would love to add a 2nd 9600GT card to the system.

Again, thank you everyone for all the replies,

Utnorris

---

I would guess so and more so for Linux custom users, but would guess it is not gonna be all the great since it will have to be an older exploited hacked firmware just like we did back on the !975X w/ nVidia 6800 Ultras. I did it and was hardly worth anything except to say I did it cause nVidia made it so hard for us not to. But yes, it is in essence truelly compatable, but nVidia will continue to do its best to keep it from us, the SLI support on Intel chipsets, as long as they have ties with AMD and AMD now has interest with ATI so it's a big investment deal. My thoughts of it at least.

Quote:

---

Originally Posted by Eastcoasthandle

Has anyone tried this yet?

---

I did all that last month, and found I only needed at minimum to chamge the Frequency and manual timings so I can reset to get back in CMOS to set RAID. Like I said the min. of corse I set the rest of my profile as desired, but auto voltages had nothing to do w/ my issue.

Quote:

---

Originally Posted by loften

that is kind of interesting about the psu thing.. hmmmm.. i don't know anything about the boot problems. i have never experienced them.. maybe people with multi 12v rail psu's are having problems on this board.. mine is a single rail x3 1k. it works good.. i just have a different problem.

---

I used each a SilverStone quad rail and OCZ dual,, same thing, only the quad had less stability issues afterward.

Well, I've been putting this thing through the ringer. The smaller 850w PSU seems to be just fine with this board, and the larger 1200W PSU is doing just fine in my server...

What a week... :mad:

Anyhow, onto the fun part with tweaking my OC settings, gonna work on getting a Prime-stable 4 ghz config going. I'll post up my bios specs later tonight or tomorrow I hope!

EDIT:
What are some Max temps I should keep in mind for my cores and my NB (when under full prime loads)?

Sorry about this: but it is the first time I've ever been able to bench at 1GB/s on all R/W/C...

http://i228.photobucket.com/albums/e...Capture-21.jpg

Basically, tRD 7 all pull-ins disabled, and 5-4-4-12-2, tRFC 25 and the rest AUTO.

I have a P5E and I'm looking to flash it to the Rampage's bios. I went through the thread and it looks like a just have to follow the directions on the first page. But before I do will that do it properly and do I have to do anything else?

Quote:

---

Originally Posted by xBanzai89

I have a P5E and I'm looking to flash it to the Rampage's bios. I went through the thread and it looks like a just have to follow the directions on the first page. But before I do will that do it properly and do I have to do anything else?

---

Just make sure you flash to 0219. You can flash to 0207 and then UPGRADE to 0219, but it's a PITA.

just wondering is your 850 a single 12v rail psu?