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

[jdrom]

please fill out the bios template on the main page.
need some info b4 suggestions can be made
Everything was on Auto for that. It would post once, I'd get into the BIOS, then it would freeze. Then I removed 2x1GB of RAM, got into the BIOS, set the NB voltage to 1.67V (reads as 1.72V on monitoring page). Then it would post fine with 4x1GB of RAM. But when I went to change timings, it would stop posting again, even to just the rated timings of 4-4-4-12-2T @ 2.06V (reads as 2.1V). I believe it hung on USBFINAL and CPUINIT. Depends how long I kept trying.

As I said, that only happens on the MF1004 and RF0219 (haven't tried older RF bioses), works perfectly on MF0907 with all auto settings.

[Eastcoasthandle]

Hi guys can anyone help me??
I have just built my sytem up and everything is ok apart from when i turn everything off and then try to boot up again the next morning. It seems to start up with fans at 100% but then nothing else no beep and no boot up screen. Now i can press the cmos button and then it will boot fine but why is it not booting when its been fully powered down . I can restart from windows fine and can have the system of for 10 mins or so it it boots fine. It just seems to be when its left for a few hours or so??
I am using bios 0907 and think it could be a bios setting unless somebody has had the same problem.
Cheers paul
PS im using the same parts as in my sig

Do you completely turn off all power:
-IE turn off the power strip when you are doing using the computer then turn the power strip back on in the morning?

[Budious]

Hi guys can anyone help me??
I have just built my sytem up and everything is ok apart from when i turn everything off and then try to boot up again the next morning. It seems to start up with fans at 100% but then nothing else no beep and no boot up screen. Now i can press the cmos button and then it will boot fine but why is it not booting when its been fully powered down . I can restart from windows fine and can have the system of for 10 mins or so it it boots fine. It just seems to be when its left for a few hours or so??
I am using bios 0907 and think it could be a bios setting unless somebody has had the same problem.
Cheers paul
PS im using the same parts as in my sig

You just describe the exact same behavior that my Formula SE board displays and I'm still using the old bios 0505. I haven't been able to track it down to a particular bios setting but then again my system runs on UPS and and I don't shutdown often. When I reboot from Windows after an OS update or other, the board boots fine. If the system is powered down, it will no boot afterwards. I have to let it sit overnight and it will usually boot fine the next morning. This board has around 99% uptime since built first week of October and is very stable, just this odd reboot issue that's been my complaint so far.

[w4Rd3n]

You just describe the exact same behavior that my Formula SE board displays and I'm still using the old bios 0505. I haven't been able to track it down to a particular bios setting but then again my system runs on UPS and and I don't shutdown often. When I reboot from Windows after an OS update or other, the board boots fine. If the system is powered down, it will no boot afterwards. I have to let it sit overnight and it will usually boot fine the next morning. This board has around 99% uptime since built first week of October and is very stable, just this odd reboot issue that's been my complaint so far.

just install bios 1004.
bye

[Mekoa]

Hey,

Having a spot of trouble with vcore and overclocking my E8400 on Maximus Formula. Cant seem to get stable at lower vcore than 1.36875 for 425x9. Seen a few people doing 4ghz at less than 1.3! Posted my BIOS settings below for both current and attempted 445x9 settings (in brackets).

Oh, Using BIOS 1004.

Any help or ideas is appreciated! Will post my batch etc later as Im at work. Hopefully its just me being a muppet rather than dodgy CPU. First time in a long time at Intel overclocking also!


Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 9
FSB Frequency : 425 (445 is target)
FSB Strap to North Bridge : Auto (400)
PCI-E Frequency: 105
DRAM Frequency: DDR2-1125(ish) / DDR2-1186
DRAM Command Rate : 2T
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 5
RAS# to RAS# Delay : 15
Row Refresh Cycle Time : Auto
Write Recovery Time : Auto
Read to Precharge Time : Auto

Read to Write Delay (S/D) : Auto
Write to Read Delay (S) : Auto
Write to Read Delay (D) : Auto
Read to Read Delay (S) : Auto
Read to Read Delay (D) : Auto
Write to Write Delay (S) : Auto
Write to Write Delay (D) : Auto
DRAM Static Read Control: Auto (Disabled when testing 445x9)
Ai Clock Twister : Strong
Transaction Booster : Enabled (Disabled, Boost Level 0, dont get perf level option?)

CPU Voltage : 1.36875v (have gone upto 1.4v for 445x9)
CPU PLL Voltage : Auto (1.5V)
North Bridge Voltage : Auto (1.59V)
DRAM Voltage : 1.96V (slightly higher for 445x9, Ballistix so cant go too high)
FSB Termination Voltage : Auto (1.2/1.4V)
South Bridge Voltage : Auto (1.05V)
Loadline Calibration : Enabled
CPU GTL Reference : Auto (0.61)
North Bridge GTL Reference : Auto (0.63)
DDR2 Channel A REF Voltage : DDR2_REF
DDR2 Channel B REF Voltage : DDR2_REF
DDR2 Controller REF Voltage : DDR2_REF
SB 1.5V Voltage : Auto (1.5V)

NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED : Unsure.

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

Advanced CPU Configuration
CPU Ratio Control : Manual
- Ratio CMOS Setting : 9
C1E Suppport : Disabled
CPU TM Function : Enabled
Vanderpool Technology : Enabled
Execute Disable Bit : Enabled
Max CPUID Value Limit : Disabled


USB Configuration
USB Functions: Enabled
Legacy USB Support : Disabled

Q748A402 is the batch number. Unsure of week, cant remember!

[Dostoyevsky77]

Is that ram D9? I had lots of problems till I stopped using Micron in the max formula.

Interesting. I have no problems with D9, AND I'm running 4x1.

Incidentally, if any of you are having problems getting into the ASUS FTP, just delete the ".tw" in the URL. That works for me. Kup, it might be worth updating the link on page 1.

[Leeghoofd]

@MEKOA :

Try these and see if you can get it stable, you can get more out of the ram but these should work fine :


Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 9
FSB Frequency : 450
FSB Strap to North Bridge : Auto (400)
PCI-E Frequency: 101
DRAM Frequency: 900
DRAM Command Rate : 2T
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 5
RAS# to RAS# Delay : 15
Row Refresh Cycle Time : 55
Write Recovery Time : Auto
Read to Precharge Time : Auto

Read to Write Delay (S/D) : Auto
Write to Read Delay (S) : Auto
Write to Read Delay (D) : Auto
Read to Read Delay (S) : Auto
Read to Read Delay (D) : Auto
Write to Write Delay (S) : Auto
Write to Write Delay (D) : Auto
DRAM Static Read Control: Disabled
Ai Clock Twister : AUTO
Transaction Booster : Disabled
Relax level 0

CPU Voltage : 1.4250
CPU PLL Voltage : 1.5V
North Bridge Voltage : 1.45
DRAM Voltage : 1.9
FSB Termination Voltage : Auto (1.2/1.4V)
South Bridge Voltage : Auto (1.05V)
Loadline Calibration : Enabled
CPU GTL Reference : Auto (0.61)

Advanced CPU Configuration
CPU Ratio Control : Manual
- Ratio CMOS Setting : 9
C1E Suppport : Disabled
CPU TM Function : Enabled
Vanderpool Technology : Enabled
Execute Disable Bit : Enabled
Max CPUID Value Limit : Disabled


These settings should give ya a stable environment to start off with and to gain more you need to tweak some more... but try these for starters

[me3850]

Interesting. I have no problems with D9, AND I'm running 4x1.

Incidentally, if any of you are having problems getting into the ASUS FTP, just delete the ".tw" in the URL. That works for me. Kup, it might be worth updating the link on page 1.

it's good news for me you use D9GMH Crucial Ballistix PC2-8500 same at OCZ REAPER PC2-8500 :) i have problem with D9GKX the ram was broken after 2 weeks without overclock (cell shock pc9200 1150 5-5-5-18 2.3) i use him at 1133 5-4-4-12 2.3...

you have 2 kit 2x1?

[Mekoa]

@MEKOA :

Try these and see if you can get it stable, you can get more out of the ram but these should work fine :


Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 9
FSB Frequency : 450
FSB Strap to North Bridge : Auto (400)
PCI-E Frequency: 101
DRAM Frequency: 900
DRAM Command Rate : 2T
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 5
RAS# to RAS# Delay : 15
Row Refresh Cycle Time : 55
Write Recovery Time : Auto
Read to Precharge Time : Auto

Read to Write Delay (S/D) : Auto
Write to Read Delay (S) : Auto
Write to Read Delay (D) : Auto
Read to Read Delay (S) : Auto
Read to Read Delay (D) : Auto
Write to Write Delay (S) : Auto
Write to Write Delay (D) : Auto
DRAM Static Read Control: Disabled
Ai Clock Twister : AUTO
Transaction Booster : Disabled
Relax level 0

CPU Voltage : 1.4250
CPU PLL Voltage : 1.5V
North Bridge Voltage : 1.45
DRAM Voltage : 1.9
FSB Termination Voltage : Auto (1.2/1.4V)
South Bridge Voltage : Auto (1.05V)
Loadline Calibration : Enabled
CPU GTL Reference : Auto (0.61)

Advanced CPU Configuration
CPU Ratio Control : Manual
- Ratio CMOS Setting : 9
C1E Suppport : Disabled
CPU TM Function : Enabled
Vanderpool Technology : Enabled
Execute Disable Bit : Enabled
Max CPUID Value Limit : Disabled


These settings should give ya a stable environment to start off with and to gain more you need to tweak some more... but try these for starters

Just tried those settings (Anything with stuff in brackets after I just set to auto) and my PC wouldnt even boot. :shrug: Maybe I shouldnt have set some to Auto?

Joy!

[Leeghoofd]

Mekoa;2882481']Just tried those settings (Anything with stuff in brackets after I just set to auto) and my PC wouldnt even boot. :shrug: Maybe I shouldnt have set some to Auto?

Joy!

Lol set 8 multi once.. works fab here with my E8400 and even the QX... try with 2 dimms... or up Nb voltage to 1.59...

[ninjagordy]

anyone tell me what sort of max fsb there getting on the e8200 and what bios settings they have....im trying to hit the golden 4ghz with the E8200...but im not sure where to go setting it up...i will not be occt'ing it above 1.4vcore (bios)

Cheers :up:

[kup]

Interesting. I have no problems with D9, AND I'm running 4x1.

Incidentally, if any of you are having problems getting into the ASUS FTP, just delete the ".tw" in the URL. That works for me. Kup, it might be worth updating the link on page 1.

Cool, I'll get on it now.

[eSp!s0]

*Update*

XP32-Bit, G.Skill 2x2GB 8500 (GBPK) = 3328MB Windows, E6750 @ TRU120E, Bios 1004, Zotac 8800GTS 512 AMP! 750/1878/1050, Driver 174.74.


450x8=3600, 333Strap, 5:6, 1080Ram PL7:
CPU Feature
Ai Overclock Tuner [Manual]
OC From CPU Level Up [Auto]
CPU Ratio Control [Auto]
Ratio CMOS Setting: [8]

FSB Frequency [450]
FSB Strap to North Bridge [333MHz]
PCIE Frequency [100]

DRAM Settings
DRAM Frequency [1080MHz]
DRAM Command Rate [2T]
DRAM Timing Control [Auto]
5-5-5-15-...-52-...

DRAM Static Read Control [Auto]
Ai Clock Twister [Moderate]
Transaction Booster [Disabled]
Boost Level [0]
Performancelevel 7

CPU Voltage [1.35000]
CPU PLL Voltage [Auto]
North Bridge Voltage [1.39v]
DRAM Voltage [1.96v]
FSB Termination Voltage [1.20v]
South Bridge Voltage [1.050]
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 [Auto]
SB 1.5V Voltage [Auto]

http://www.abload.de/thumb/cachemem84f.png (http://www.abload.de/image.php?img=cachemem84f.png) Read: 9580MB/s Write: 8202MB/s Copy: 9110MB/s Latency: 53.3ns

http://www.abload.de/thumb/superpi1m1004450x8109ou.png (http://www.abload.de/image.php?img=superpi1m1004450x8109ou.png) SuperPi1.5 1M: 14.031s

http://www.abload.de/thumb/3dm061004174.74beta3hgh.png (http://www.abload.de/image.php?img=3dm061004174.74beta3hgh.png) 3DM06: 14378

http://www.abload.de/thumb/am31004g92174.74450x2e3.png (http://www.abload.de/image.php?img=am31004g92174.74450x2e3.png) AM3: 204452

http://www.abload.de/thumb/cssvst1004g92174.744cll.png (http://www.abload.de/image.php?img=cssvst1004g92174.744cll.png) CSS VST: 222.25FPS



515x7=3605, 333Strap, 1:1, 1030Ram PL9:
CPU Feature
Ai Overclock Tuner [Manual]
OC From CPU Level Up [Auto]
CPU Ratio Control [Manual]
Ratio CMOS Setting: [7]

FSB Frequency [515]
FSB Strap to North Bridge [333MHz]
PCIE Frequency [100]

DRAM Settings
DRAM Frequency [1030MHz]
DRAM Command Rate [2T]
DRAM Timing Control [Auto]
5-5-5-15-...-52-...

DRAM Static Read Control [Auto]
Ai Clock Twister [Moderate]
Transaction Booster [Disabled]
Boost Level [1]
Performancelevel 9

CPU Voltage [1.35000]
CPU PLL Voltage [Auto]
North Bridge Voltage [1.39v]
DRAM Voltage [1.96v]
FSB Termination Voltage [1.20v]
South Bridge Voltage [1.050]
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 [Auto]
SB 1.5V Voltage [Auto]

http://www.abload.de/thumb/cachemem2s6t.png (http://www.abload.de/image.php?img=cachemem2s6t.png)Read: 9673MB/s Write: 9318MB/s Copy: 9992MB/s Latency: 52.6ns

http://www.abload.de/thumb/superpi1m1004515x710mri.png (http://www.abload.de/image.php?img=superpi1m1004515x710mri.png) SuperPi1.5 1M: 14.016s

http://www.abload.de/thumb/3dm06174.74beta3605mnsq.png (http://www.abload.de/image.php?img=3dm06174.74beta3605mnsq.png) 3DM06: 14379

http://www.abload.de/thumb/am31004g92174.74515xjzy.png (http://www.abload.de/image.php?img=am31004g92174.74515xjzy.png) AM3: 204951

http://www.abload.de/thumb/cssvst1004g92174.745agc.png (http://www.abload.de/image.php?img=cssvst1004g92174.745agc.png) CSS VST: 224.83FPS

[fordf250]

Interesting. I have no problems with D9, AND I'm running 4x1.

Incidentally, if any of you are having problems getting into the ASUS FTP, just delete the ".tw" in the URL. That works for me. Kup, it might be worth updating the link on page 1.

Best of luck, I got to 540fsbx7 at 1:1 with d9 and it never failed memtest at good overclocked speeds and totaly OCCT stable, it would just randomly reboot and sometimes not boot till I didnt run D9 in it anymore. Now it is the most stable MB I have ever had, 475fsb 24/7.

[Wolf2000me]

I have had strange rebooting issues, very sporadically. This may sound far fetched but I'm fairly certain that it happened because of Speedfan. Perhaps a driver issue, dunno. After I uninstalled it I have never had a single issue since and it's been at least a month now. The reboot issue occurred while speedfan was always active. It happened approximately once a day, likely causing some sort of IO error, disk or memory, no damage. I have only ran the OCCT/Speedfan combo a few weeks. The issue went away when I switched to other stability and monitoring software.
And I also didn't suddenly find the right stable setting. I'm running a config now that had known the issue.

[Eastcoasthandle]

I believe I figured out what was causing my cold boot Det-Dram problems (when I had no problem the day before). It's north bridge voltage @ 1.43V. For whatever reason, when you cold boot the maximus formula the voltage on the north bridge doesn't appear to be enough to properly recognize my PC8500 ram (micron based) at 1066MHz. Causing a Det-Dram error to appear. I tested this theory by rebooting into the bios and setting the VMCH to auto. BAM!!!!!!! instant Det-Dram on reboot. I turned it off for another cold boot try and no go. I put in my PC6400 ram and as always it boots up just fine. I check the voltage on VMCH and it was 1.324V. I upped the VMCH to 1.55V (Everest reads 1.600V) and see if that helps. Temps for the NB at idle are 34C (using a fan on northbridge helps :D ). I will see what the results are tomorrow after a cold boot.

http://i11.photobucket.com/albums/a154/eastcoasthandle/PC8500/everest1.jpg

[Grnfinger]

I ran MB volts at 1.49 for ever, clocks were always stable but I had the odd det ram hang.
Upped NB volts to 1.53 and no more det ram hang no matter what I'm doing.

So I think your theory is correct

[Eastcoasthandle]

It makes sense as I had to run my P5W DH Deluxe at 1.65VMCH or else I would run into wired stability problems. Even though I could never get my PC8500 @ 1066MHz I would run into other problems if I used a lower VMCH with the the P5W DH at the same 3.60GHz OC. Although I had no stability problems with my Max. Formula once I switch ram on cold boot but I did notice some odd delays when clicking on apps and links on the net.

[ir1z]

Hello guys im a noob in this overclocking part.....
a few days back i have manage to flash bios my maximus formula to the rampage formula with help from a friend and currently trying to OC my q6600 GO to 3.6Ghz to no avail....

ive got quite succesive result on manage to get it stable at 3.2 but could not get my system to stable in occt for 3.6

my pc specs:
Q6600 GO @ 3.2 (1.272 vcore)
Crucial Ballistix 2x 2GB kit PC6400 vdimm at everest 2.21
Maximus formula mobo BIOSed to Rampage Formula
pics:
http://img338.imageshack.us/img338/8070/oced32nv4.th.jpg (http://img338.imageshack.us/my.php?image=oced32nv4.jpg)

Have tried up to vcore of 1.4 and still couldnt get the 3.6 to be stable at those same setting in 3.2 just changing multiplier to 9. Anybody can be of assistance plz?

[Maglin]

give it some volts man. 1.4v is nothing. Try going with 1.450v. 1.6v PLL and 1.48v FSBT.

[Nuckin_Futs]

Can anybody experiencing this so-called "OL" det_ram issue confirm if it happened before any beta BIOS like pre v0907? I only got this after 907 and there after. I ran the mobo on several BIOS flashes (always EZ-Flash) and up to beta 903 and never had such ram issues in full auto or trusted OC.

After fresh BIOS flash, clear CMOS and loading defualts, it would not POST (hung at det_ram) unless I at least set RAM frequency and timings to manual 9DDR800 @ 5-5-5-15 for my D9 Micron Tracers). Everything else can be left to Auto and it would load to XP now.

It of corsed never OC'd the same after the bad BETA 907 experience so I RMA'd and it is expected any day now.

[ir1z]

sorry if this is repetitive of my post at the turn maximus to rampage but kindly need help about current status to OC my Q6600 GO to 3.6

a few days back i have manage to flash bios my maximus formula to the rampage formula with help from a friend and currently trying to OC my q6600 GO to 3.6Ghz to no avail....

ive got quite succesive result on manage to get it stable at 3.2 but could not get my system to stable in occt for 3.6

my pc specs:
Q6600 GO @ 3.2 (1.272 vcore)
Crucial Ballistix 2x 2GB kit PC6400 vdimm at everest 2.21
Maximus formula mobo BIOSed to Rampage Formula
pics:
http://img338.imageshack.us/img338/8070/oced32nv4.th.jpg (http://img338.imageshack.us/my.php?image=oced32nv4.jpg)

Have tried up to vcore of 1.4 and still couldnt get the 3.6 to be stable at those same setting in 3.2 just changing multiplier to 9. Anybody can be of assistance plz?

This is my bios setup at the extreme tweaker page (while running 3.2Ghz)....

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Setting : 08.0
FSB Frequency : 400
FSB Strap to North Bridge : 400
PCI-E Frequency: 100
DRAM Frequency: DDR2-800
DRAM Command Rate : auto
DRAM Timing Control: Manual
CAS# Latency : 4
RAS# to CAS# Delay : 4
RAS# Precharge : 4
RAS# ActivateTime : 12
RAS# to RAS# Delay : auto
Row Refresh Cycle Time : auto
Write Recovery Time : auto
Read to Precharge Time : auto

Read to Write Delay (S/D) : auto
Write to Read Delay (S) : auto
Write to Read Delay (D) : auto
Read to Read Delay (S) : auto
Read to Read Delay (D) : auto
Write to Write Delay (S) : auto
Write to Write Delay (D) : auto
DRAM Static Read Control: enabled
Ai Clock Twister : Moderate
Transaction Booster : Manual
Common Performance Level : 07
CPU Voltage : 1.2875
CPU PLL Voltage : 1.50
North Bridge Voltage : 1.33
DRAM Voltage : 2.12
FSB Termination Voltage : 1.20
South Bridge Voltage : 1.050
Loadline Calibration : enabled
CPU GTL Reference : .67x
North Bridge GTL Reference : .67x
DDR2 Channel A REF Voltage : auto
DDR2 Channel B REF Voltage : auto
DDR2 Controller REF Voltage : auto
SB 1.5V Voltage : 1.6

NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED :

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

when ocing to 3.6 i changed Vcore to 1.4-1.425 and multiplier to 9. But to no avail. I just couldnt get it stable at OCCT

[ir1z]

This is my bios setup at the extreme tweaker page (while running 3.2Ghz)....

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Setting : 08.0
FSB Frequency : 400
FSB Strap to North Bridge : 400
PCI-E Frequency: 100
DRAM Frequency: DDR2-800
DRAM Command Rate : auto
DRAM Timing Control: Manual
CAS# Latency : 4
RAS# to CAS# Delay : 4
RAS# Precharge : 4
RAS# ActivateTime : 12
RAS# to RAS# Delay : auto
Row Refresh Cycle Time : auto
Write Recovery Time : auto
Read to Precharge Time : auto

Read to Write Delay (S/D) : auto
Write to Read Delay (S) : auto
Write to Read Delay (D) : auto
Read to Read Delay (S) : auto
Read to Read Delay (D) : auto
Write to Write Delay (S) : auto
Write to Write Delay (D) : auto
DRAM Static Read Control: enabled
Ai Clock Twister : Moderate
Transaction Booster : Manual
Common Performance Level : 07
CPU Voltage : 1.2875
CPU PLL Voltage : 1.50
North Bridge Voltage : 1.33
DRAM Voltage : 2.12
FSB Termination Voltage : 1.20
South Bridge Voltage : 1.050
Loadline Calibration : enabled
CPU GTL Reference : .67x
North Bridge GTL Reference : .67x
DDR2 Channel A REF Voltage : auto
DDR2 Channel B REF Voltage : auto
DDR2 Controller REF Voltage : auto
SB 1.5V Voltage : 1.6

NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED :

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

any suggestion where i should i bump up to get a stable readin for a 3.6Ghz OC???

[ir1z]

give it some volts man. 1.4v is nothing. Try going with 1.450v. 1.6v PLL and 1.48v FSBT.

i tried what u suggested and got my pc restarted after 3 minutes throught running the OCCT test.....

[Nuckin_Futs]

Well, I'll try to stear this back to a MAXIMUS FORMULA. Could just create a new MAXIMUS RAMPAGE Hacking tread and advanced RAM sub timings tread.

See edits in BOLD below to give a try. But 1st and foremost What BIOS are you on? I'd stick with final BIOS for now untill you run into something that must be BETA tested. For me v0602 was the best for my E6750 but v0802 is OK too except for limited useability of manual FSB strapping and RAM frequency selections. All the beta BIOS to 907 I tested with E6750 have gotten worse as they go, with litle exception being v0903. But only really scoring in benchmark points, not so much real world stability.


sorry if this is repetitive of my post at the turn maximus to rampage but kindly need help about current status to OC my Q6600 GO to 3.6

my pc specs:
Q6600 GO @ 3.2 (1.272 vcore)
Crucial Ballistix 2x 2GB kit PC6400 vdimm at everest 2.21
Maximus formula mobo BIOSed to Rampage Formula
pics:
http://img338.imageshack.us/img338/8070/oced32nv4.th.jpg (http://img338.imageshack.us/my.php?image=oced32nv4.jpg)

Have tried up to vcore of 1.4 and still couldnt get the 3.6 to be stable at those same setting in 3.2 just changing multiplier to 9. Anybody can be of assistance plz?

This is my bios setup at the extreme tweaker page (while running 3.2Ghz)....

EDIT: [CMOS setting], = Hardware Monitor Reported
remember that this mobo overvolts so make sure to sepperate SET from REPORTED voltages
Extreme Tweaker
Ai Overclock Tuner : [Manual]
OC From CPU Level Up : [AUTO]
CPU Ratio Setting : [09.0]
FSB Frequency : [400]
FSB Strap to North Bridge : [Auto]
PCI-E Frequency: [100]
DRAM Frequency: [Auto]
DRAM Command Rate : [2T]
DRAM Timing Control: Manual
CAS# Latency : [4]
RAS# to CAS# Delay : [4]
RAS# Precharge : [4]
RAS# ActivateTime : [12]
RAS# to RAS# Delay : [auto]
Row Refresh Cycle Time : [auto]
Write Recovery Time : [auto]
Read to Precharge Time : [auto]

Read to Write Delay (S/D) : [auto]
Write to Read Delay (S) : [auto]
Write to Read Delay (D) : [auto]
Read to Read Delay (S) : [auto]
Read to Read Delay (D) : [auto]
Write to Write Delay (S) : [auto]
Write to Write Delay (D) : [auto]
DRAM Static Read Control: [enabled ]
Ai Clock Twister : [Moderate] try LIGHT for more stability &/ or higher FSB
Transaction Booster : [Disable]
Relax Level : [0] up as needed if unstable for testing
CPU Voltage : [1.45xx] = 1.41v (for starters) may need more, hopefully not
CPU PLL Voltage : [1.52] = 1.632 quads on higher FSB may need up to =1.712v (reported)
North Bridge Voltage : [1.47] = 1.504n may need more for some quads, =1.55v (reported) is OK
DRAM Voltage : [2.12] = 2.2v
FSB Termination Voltage : [1.44] = 1.504v
South Bridge Voltage : [1.075] = 1.104v also good to 500FSB
Loadline Calibration : [enabled]
CPU GTL Reference : [.63x] 67x if new BIOS made it available
North Bridge GTL Reference : [.67x]
DDR2 Channel A REF Voltage : [auto]
DDR2 Channel B REF Voltage : [auto]
DDR2 Controller REF Voltage : [auto] - 1.152v
SB 1.5V Voltage : [1.55] more then enough up to 500FSB easy

NB LED Selection : [NB Volt]
SB LED Selection : [SB Volt ]
CPU LED Selection : [CPU VOlt]
Voltiminder LED : []

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

when ocing to 3.6 i changed Vcore to 1.4-1.425 and multiplier to 9. But to no avail. I just couldnt get it stable at OCCT

You can simply aim for 450x8 with pretty much everything the same as long as in 1:1. If changing to divider later, you may need to up NB closer to 1.6v (reported) Your Crucial's should handle 950MHz @ 4-4-4-12 @ 2.22v (set as 2.14).

Keep me posted or PM for more info or help.

[ir1z]

im currently using a modded bios which have been changed to a rampage formula bios ver 0219.....

[Grnfinger]

im currently using a modded bios which have been changed to a rampage formula bios ver 0219.....

then you should be posting in the other thread not here

[Grnfinger]

This is my bios setup at the extreme tweaker page (while running 3.2Ghz)....

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Setting : 08.0
FSB Frequency : 450
FSB Strap to North Bridge : 400
PCI-E Frequency: 100
DRAM Frequency: DDR2-900
DRAM Command Rate : auto
DRAM Timing Control: Manual
CAS# Latency : 4
RAS# to CAS# Delay : 4
RAS# Precharge : 4
RAS# ActivateTime : 12
RAS# to RAS# Delay : auto
Row Refresh Cycle Time : auto
Write Recovery Time : auto
Read to Precharge Time : auto

Read to Write Delay (S/D) : auto
Write to Read Delay (S) : auto
Write to Read Delay (D) : auto
Read to Read Delay (S) : auto
Read to Read Delay (D) : auto
Write to Write Delay (S) : auto
Write to Write Delay (D) : auto
DRAM Static Read Control: enabled
Ai Clock Twister : Moderate
Transaction Booster : Manual
Common Performance Level : 07
CPU Voltage : 1.50
CPU PLL Voltage : AUTO
North Bridge Voltage : 1.51
DRAM Voltage : 2.12
FSB Termination Voltage : 1.40
South Bridge Voltage : 1.050
Loadline Calibration : enabled
CPU GTL Reference : .63x
North Bridge GTL Reference : .67x
DDR2 Channel A REF Voltage : DDR2-REF
DDR2 Channel B REF Voltage : DDR2-REF
DDR2 Controller REF Voltage : DDR2-REF
SB 1.5V Voltage : 1.6

NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED :

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

any suggestion where i should i bump up to get a stable readin for a 3.6Ghz OC???

Make the suggested changes and see how it goes, if you have a poor chip that scales bad you may need more than 1.50 volts for 3.6GHz

[JackeShan]

Should I enable DRAM Static Read Control or disable it? I have always had it on enabled without a problem.

[Eastcoasthandle]

I believe I figured out what was causing my cold boot Det-Dram problems (when I had no problem the day before). It's north bridge voltage @ 1.43V. For whatever reason, when you cold boot the maximus formula the voltage on the north bridge doesn't appear to be enough to properly recognize my PC8500 ram (micron based) at 1066MHz. Causing a Det-Dram error to appear. I tested this theory by rebooting into the bios and setting the VMCH to auto. BAM!!!!!!! instant Det-Dram on reboot. I turned it off for another cold boot try and no go. I put in my PC6400 ram and as always it boots up just fine. I check the voltage on VMCH and it was 1.324V. I upped the VMCH to 1.55V (Everest reads 1.600V) and see if that helps. Temps for the NB at idle are 34C (using a fan on northbridge helps :D ). I will see what the results are tomorrow after a cold boot.

http://i11.photobucket.com/albums/a154/eastcoasthandle/PC8500/everest1.jpg



Morning #1

After a 8 hours I am happy to report that the computer does in fact properly cold boot with my PC8500 ram at 1066MHz. It appears that having the north bridge voltage at 1.55V instead of 1.43V is working so far.


Side note:
Enabling DRAM Static Read Control increases the memory controller performance level; disabling it decreases it. If you disable it you may experience lower performance from your ram. If it's stable with it enabled keep it there unless you are experiencing other non critical OS, program or gaming problems like stuttering, hitching, pausing, programs closing do to errors, etc.

[Notechis]

Can somebody tell me one thing because I'm clueless.
I recently put 4x1 GB of ram (planing to move on 64bit win) and bios shows that I have only 3328MB. I know that 32bit win doesn't show above that but shouldn't bios show 4GB? :confused:
Thanks in advance

[kup]

New sudden instability with this board...again. I tried a higher overclock, it wasn't stable so I backed down again. Now the old 110% stable (literally over a month 100% load 24/7 Folding Dual SMP Clients) is as flakey as :banana::banana::banana::banana:...

I can't wait until I have the money for a DFI board and to get away from this Asus POS. :(

[itznfb]

Mekoa;2882481']Just tried those settings (Anything with stuff in brackets after I just set to auto) and my PC wouldnt even boot. :shrug: Maybe I shouldnt have set some to Auto?

Joy!

i've tested 6 E8400's on my MaxForSE and each one i was able to just pop it in and set the FSB to 450x9 vcore 1.3, ram 1:1 at 900 and run 100% stable in windows.

i can't get past 450fsb though. other mobo's i can go way higher.

===================================

on a separate note: how the effing sh do you get the thermal crap off the back of the stock blocks? i've tried everything, nothing dissolves that crap. what is it? cement?

[wilson]

well i got another coolermaster 850w psu and i got the same results... I then put a 300w cheap psu in and it worked no fans at 100% with no post it just booted up straight away. Its funny as the psu worked fine on the p35 and 680i chipsets but not the x38 and x48. I guess its time to get a good psu and not a £136 piece of c++p....

[Dostoyevsky77]

Not sure if any of you have read this, but check out this AnandTech article about tRD and command level (CL). I'm currently running CL7 in the 333 strap at 6:5 and 1.49 vNB, but it turns out the same is possible at CL6.

ARTICLE (http://www.anandtech.com/mb/showdoc.aspx?i=3208&p=4)

This really unlocks the potential of this rampage hack.

[ericab]

ir1z;

try disabling load-line calibration.

[kup]

I'm having to retest my overclock with the 0219 bios. After trying a faster overclock it proved to be unstable so I backed down to my 110% stable settings...apparently they're unstable too now! :(

[Dostoyevsky77]

I'm having to retest my overclock with the 0219 bios. After trying a faster overclock it proved to be unstable so I backed down to my 110% stable settings...apparently they're unstable too now! :(

Sounds like something might be dying. Did you recently spill coffee onto your northbridge or something?

[kup]

Nope. The problem is an odd one. The FSB is stable if the CPU is clocked lower, and the CPU is stable if the FSB is clocked lower and the multi increased to compensate, but both together and it starts to randomly reboot again.

It just baffles me. I'm testing the FSB again, and then I'll do the CPU once more...

[Grnfinger]

Not sure if any of you have read this, but check out this AnandTech article about tRD and command level (CL). I'm currently running CL7 in the 333 strap at 6:5 and 1.49 vNB, but it turns out the same is possible at CL6.

ARTICLE (http://www.anandtech.com/mb/showdoc.aspx?i=3208&p=4)

This really unlocks the potential of this rampage hack.

Just read the artical, have you made any adjustments?
If you have, did you do any b4 and after tests to compare the differences if any?

[Grnfinger]

I'm having to retest my overclock with the 0219 bios. After trying a faster overclock it proved to be unstable so I backed down to my 110% stable settings...apparently they're unstable too now! :(

mc2k just got his real Rampage yesterday, it shipped with 215.
Maybe 219 has a bug, once he is around I'll grab 215 and post it here or I'll have him do it. You can test it and see if the issue is still there?

[Dostoyevsky77]

Just read the artical, have you made any adjustments?
If you have, did you do any b4 and after tests to compare the differences if any?

Yes, I made adjustments. Everything tighter than tRD 7 at sigged results in DET RAM for me, even 450FSB which they say will work with 1.6 vNB. I haven't pulled any DIMMs, though. I'm still 4x1. Maybe this weekend I'll mess around with that.

It was a really good article, and it really helped me understand what's going on, though. Now it makes perfect sense that running tRD of 8 with all the phases pulled-in resulted in the same bandwidth.

[p2501]

I've been trying around with Rampage BIOS and I think it's quite okay. The only error I've encountered is that the BIOS shows me pull ins for 10 cores at my current FSB. On a single q6600, nice eh? :)

Anyway, I think the q6600 I bought is a volt pig. First some volts and temps loaded with FAH (CPU PLL is set to Auto, I hope that helps getting the box stable):
http://bandwidth.se/imgs/101/227/everest.jpg

Near 8hrs OCCT RAM (stopped that myself, I'm guessing it would have done just fine..):
http://bandwidth.se/imgs/101/227/over7hrsocctram.jpg

And some 17hrs p95:
http://bandwidth.se/imgs/101/227/primescreen.jpg

Now I'll just wait a few days to see if it's craps out on me again. To gain only 100 Mhz over these values, be it on 8x or 9x the chip needs over 1.5 vcore. Amazing, huh? :shrug:

Stupid thing is that it doesn't like more FSBT, in fact it either destabilises it or has no effect whatsoever. If I'm going water later this year I think I'll beat the chip with some more of this sweet vcore. :devil:

[Dostoyevsky77]

I've been trying around with Rampage BIOS and I think it's quite okay. The only error I've encountered is that the BIOS shows me pull ins for 10 cores at my current FSB. On a single q6600, nice eh? :) (SNIP!)


I recommend reading the article I linked on the previous page. It will explain where the number of pull-ins is dependent upon which NB strap you're in. It looks like you're 6:5 in 333 (like I am). The 333 strap has 5 pull-ins per channel, or ten total. This can be easily verified by changing the strap in BIOS (no need to save or restart).

Thanks for sharing your screenies! What is your desktop background? It looks cool.

[Grnfinger]

Yes, I made adjustments. Everything tighter than tRD 7 at sigged results in DET RAM for me, even 450FSB which they say will work with 1.6 vNB. I haven't pulled any DIMMs, though. I'm still 4x1. Maybe this weekend I'll mess around with that.

It was a really good article, and it really helped me understand what's going on, though. Now it makes perfect sense that running tRD of 8 with all the phases pulled-in resulted in the same bandwidth.

I have set PL7 and disabled pull-ins, I find it give a slight increase in bandwidth, I hae also tried 6 and cant get the :banana::banana::banana::banana::banana: to boot.
Adjusting timings and strap now to get a bootable pl6 and see if its worth the headache.
I have Rampage bios 215 , going to test it tonight aswell

[p2501]

I recommend reading the article I linked on the previous page. It will explain where the number of pull-ins is dependent upon which NB strap you're in. It looks like you're 6:5 in 333 (like I am). The 333 strap has 5 pull-ins per channel, or ten total. This can be easily verified by changing the strap in BIOS (no need to save or restart).

Thanks for sharing your screenies! What is your desktop background? It looks cool.

Heh, thank you, I bookmarked that link for further reading tomorrow. Too sleepy now for reading it.

And for that wallpaper, it's from AnimePaper.com (http://www.animepaper.net/gallery/wallpapers/Jigoku-Shoujo/item74907/), a very nice community, you'll have to register and earn (be it own wallpapers or comments or whatever) your wallpapers through active participation though.. :up:

[kup]

Nope. The problem is an odd one. The FSB is stable if the CPU is clocked lower, and the CPU is stable if the FSB is clocked lower and the multi increased to compensate, but both together and it starts to randomly reboot again.

It just baffles me. I'm testing the FSB again, and then I'll do the CPU once more...


mc2k just got his real Rampage yesterday, it shipped with 215.
Maybe 219 has a bug, once he is around I'll grab 215 and post it here or I'll have him do it. You can test it and see if the issue is still there?

CPU seems stable again. The vCore seems lower now too. 1.456v for 3.715GHz 100% Load. Used to need 1.475v...?!

It might be the FSB flaking out on me.

[Edro Davis]

Not sure if any of you have read this, but check out this AnandTech article about tRD and command level (CL). I'm currently running CL7 in the 333 strap at 6:5 and 1.49 vNB, but it turns out the same is possible at CL6.

ARTICLE (http://www.anandtech.com/mb/showdoc.aspx?i=3208&p=4)

This really unlocks the potential of this rampage hack.


Here is another excellent article regarding tRD and other things that I wish I could understand better.
http://www.anandtech.com/cpuchipsets/intel/showdoc.aspx?i=3184&p=8

edro

[Grnfinger]

CPU seems stable again. The vCore seems lower now too. 1.456v for 3.715GHz 100% Load. Used to need 1.475v...?!

It might be the FSB flaking out on me.

That seems promising, I do find that the board needs more NB volts now to avoid the det ram hang. A few others have reported the same.
Have yet to try and lower my current vCore, was happy I could push an extra 100MHz on my overclock

[ericab]

hook us up with 215!

[Nuckin_Futs]

Can somebody tell me one thing because I'm clueless.
I recently put 4x1 GB of ram (planing to move on 64bit win) and bios shows that I have only 3328MB. I know that 32bit win doesn't show above that but shouldn't bios show 4GB? :confused:
Thanks in advance

This is normal since XP x64 9not Server) is using some of the rules of XP x86. You can either use BIOS remap and fix boot file to use 4028 RAM. Keep in mind now Hibernate S4 will not function anymore just because the rule writen into Windows wether you have 4G of hdd space or not. I diasble Memory Remap and let XP x64 use 3.5+ and it works fine. Since most are looking only at number scores, Just so you know, I got slightly less points in Everest when forcing to uise 4Gbs opposed to 3.5 Using OCZ Platinum in 2x2gb as DDR1000 @ 5-5-5-15.

Anybbody also removing the X38 NB chipset IHS as well to improve contact with aftermarket coolers or just stock water block?

[Webster]

Just finished flashing 0219 to my Maximus "Rampage". Very very nice find Stilt, thanks for such a great and simple guide. My only question is the purpose of the .bat files I flashed at the end. Sorry if this question has been asked already.

Also, on with the 0215!

[ericab]

Just finished flashing 0219 to my Maximus "Rampage". Very very nice find Stilt, thanks for such a great and simple guide. My only question is the purpose of the .bat files I flashed at the end. Sorry if this question has been asked already.

Also, on with the 0215!

webster webster, WEBSTER!!!.....


.bat's are NO LONGER NEEDED; however i wont yell any longer at you since there are many pages in this thread, and not everyone has the time or patience to read it all... the alternate and BETTER (Best) method (enabled by ZenEffect, and many others amazing google skillZ) allows for DIRECT bios flashing, without loaders, or scripts (as well as reversion to the MF bios). its called AFUDOS "engineering version." the best we have found is 2.36 ES. I have uploaded it to usenet, where you can DL it, or the link is provided on page 15 or 16 or so of this thread..

btw your avatar is freaky

[ZenEffect]

someone share 215 already :p:

[golfjam]

btw your avatar is freaky

LOL:rofl:

[Webster]

webster webster, WEBSTER!!!.....


.bat's are NO LONGER NEEDED; however i wont yell any longer at you since there are many pages in this thread, and not everyone has the time or patience to read it all... the alternate and BETTER (Best) method (enabled by ZenEffect, and many others amazing google skillZ) allows for DIRECT bios flashing, without loaders, or scripts (as well as reversion to the MF bios). its called AFUDOS "engineering version." the best we have found is 2.36 ES. I have uploaded it to usenet, where you can DL it, or the link is provided on page 15 or 16 or so of this thread..

btw your avatar is freaky

:( I knew this had already been addressed. I did use 2.36ES because the link on page 1 was down, and google brought up the 2.36ES Rapidshare on an earlier page. I suppose the .bats didn't hurt anything as I booted into Vista normally. Anyways, I just so happen to like my avatar:p: . Much thanks for the speedy and helpful response.

[loften]

i need to remove my stock cooler and re seat it in a bad way. the temps are way up there. at 1.48 nb volts it was getting to 65+. i will be getting water soon. i put the little fan over it for now and it is about 10 degrees lower. i was able to get it tested for 5 hours at 450x8 on the 333 strap with my 4x1 crucial pc8500 at 1080..then i played ut for 4 hours.. using close to esp!so top settings. oh yeah i am on bios 907

[ChaosMinionX]

Wheres 0215 already!

[ninjagordy]

well troops!,

i fired the e8200 in my p5k-e rig and oc'd it to 4ghz and it was benchable in windows at 1.4vcore, but i dropped back to 3.8ghx and 1.385 for safety....

this is on air....

i take it the p5k is able to do higher fsb easier than the maximus formulas

cheers

Gordy! :shrug:

[Mekoa]

itznfb;2885089']i've tested 6 E8400's on my MaxForSE and each one i was able to just pop it in and set the FSB to 450x9 vcore 1.3, ram 1:1 at 900 and run 100% stable in windows.

i can't get past 450fsb though. other mobo's i can go way higher.

Im just using a normal Maximus Formula. Either I have a bad chip or motherboard is playing funny buggers?

Any idea if you tested a Q748A402?

Ill test it like that tonight, everything to auto except those settings.

Edit: Stable at 425x9 @ 1.35V. Tested that on Monday night. Could probably drop vcore as well.

[Nuckin_Futs]

This mobo is very capable of higher FSB then most play with. I use 500 as a normal everyday and this was on air w/ 1.504v on NB. Now that I'm moving it to water, I expect to hit over 525 w/ a 1.6v NB. Most peepz are limiting themselves by insisting on the higher multi's so of corse you run out of CPU before you can get the FSB.

I found that only a E6300/E6400 can really take this over 525FSB. The quads are more FSB limited so doing so on this mobo with limited PLL and GTL-Ref tweaks makes it more work then for those on a DFI X38. But still, 480FSB isn't that out of reach on the MAXIMUS if you liten up on the performance RAM and sub timings a bit. Thats where most cut themselves shot I noticed.

I had the P5K Deluxe when new and it did no better then the MAXIMUS now on BIOS v0602 for my same E6750, But then this CPU is limited around 525FSB anywayz,

[Grnfinger]

Sorry for the delay, did not test this yet.
This is off the Rampage Mobo Disk, according to mc2k its bios 215 altho its not been confirmed.

Rampage Bios 215 (http://rapidshare.com/files/104254502/rampage_bios_mc2k.rar.html)

[TouGe]

Wow, I guess it pays to stay up all night and into the weee hours of the morning. Thank you.....

[Eastcoasthandle]

Morning #1

After a 8 hours I am happy to report that the computer does in fact properly cold boot with my PC8500 ram at 1066MHz. It appears that having the north bridge voltage at 1.55V instead of 1.43V is working so far.


Side note:
Enabling DRAM Static Read Control increases the memory controller performance level; disabling it decreases it. If you disable it you may experience lower performance from your ram. If it's stable with it enabled keep it there unless you are experiencing other non critical OS, program or gaming problems like stuttering, hitching, pausing, programs closing do to errors, etc.

Morning #2

After more then 8 hours I am happy to report again my computer does in fact properly cold boot with my PC8500 ram at 1066MHz. This means no electricity for at all for more then 8 hours. It appears that having the north bridge voltage at 1.55V instead of 1.43V is in fact working. It still double boots from a cold boot using my Corsair PC8500 ram. However, if I hit the reset button or restart XP it will reboot once (IE like normal).

[Sources]

Hey gang, after flashing to the Rampage bios I was able to lower the volts on my Q6600 G0 to only 1.36v to reach 3.6Ghz. I think I can actually go even lower but I got tired last night, hehe. Gonna try lower volts for stability tonight again.
Also noticed I only need to run 2.08v on my RAM to get 1066mhz.

Great bios so far imo.

[TouGe]

The file you posted is 0207, not 0215.

[devilhood]

If you manage to bag a 1.2125v VID Quad G0, you'll be able to drop your VCore to 1.32v even with the stock MF BIOS. That's what I'm running mine at currently.
Not sure if using the Rampage BIOS means you'll be able to take it lower than 1.32v though; I'd try it but I'm not willing to take the risk and/or void my warranty.

[zlojack]

Much difference between 0215 and 0219?

[BigGaroupa]

If you manage to bag a 1.2125v VID Quad G0, you'll be able to drop your VCore to 1.32v even with the stock MF BIOS. That's what I'm running mine at currently.
Not sure if using the Rampage BIOS means you'll be able to take it lower than 1.32v though; I'd try it but I'm not willing to take the risk and/or void my warranty.

What program do I use to check my VID?

I noticed I'm having problems with my Q6600 G0 chip, it won't stay stable at 3.6GHz unless I'm running 1.5v through it...

[Dostoyevsky77]

Much difference between 0215 and 0219?

I doubt it. Some people are having problems with 0219, and it was never officially released. Since the Rampage is shipping with 0215, it's the closest thing to an official revision since the (very) dated 0207 on the FTP.

They need to get on that FTP and at least post the release revision!

I have a guy HERE (http://forums.nvidia.com/index.php?showtopic=63774&st=0&p=355425&#entry355425) who just got a Rampage and will hopefully check his disk too to see what he got... but it looks like they flashed with a different revision than what's on the disk. Is that normal?

[Sources]

What program do I use to check my VID?

I noticed I'm having problems with my Q6600 G0 chip, it won't stay stable at 3.6GHz unless I'm running 1.5v through it...

CPUID

[Leeghoofd]

Most use Coretemp to read out VID's

http://www.alcpu.com/CoreTemp/

[Brama]

but it looks like they flashed with a different revision than what's on the disk. Is that normal?

Very normal! :)

The DVDRom is made one time normally, at the start of the production.
MB is flashed normally with latest stable BIOS available at final testing time.

[Newms118]

Ok smart guys, i have a very VERY strange problem that happened last night. i believe its RAM related because it happened after i changed my 2 Gb Crucial Ballistix Tracer 1066 DDR2 (double sided so not the revision) from 800 Mhz to 1066.

the problem started when i did the above change because the RAM is rated for that speed and i wanted to run it that level. I can notice the comp is more speedy at that speed then at 800, however its just slight. RAM is at 2.13V actual too. Windows boots up fine and reading websites and what not and i decide to make sure the system is stable at this speed, just to be sure. I load up Prime95, start blend test and my Q6600 on begins running 2 cores, the other two report an error "cannot initialise small fft, error code 1005." So i turn off the test and restart it, same thing, but different cores are working and different ones are turned off. I try again and only one core runs. I looked on the web and found that this occurred before on Orthos, so i loaded that up, ran blend, and same thing, same error, AND the motherboard starting BEEPING every 5-7 seconds, along with the LCD poster saying "RESERVED" Note that the beeping is a different tone than the initial beeps you get during start up, if that has any significance. I cant find anything on what the hell RESERVED means, and after i changed the RAM speed back to 800 i was able to run the blend tests fine with no beeping or RESERVED message

Keep in mind that i can run both small fft and large fft in prime95 just find, just not the blend. I can even run Memtest and prime95 small or large fft and let it go for 8+ hours with no errors. so what the HELL is this? im debating calling ASUS tech support because the error seems so unique.

I have my board on 0907 bios, with these settings:
Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 8
FSB Frequency : 400
FSB Strap to North Bridge : auto
PCI-E Frequency: 100
DRAM Frequency: DDR2- 800
DRAM Command Rate : auto
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 15
RAS# to RAS# Delay : auto
Row Refresh Cycle Time : auto
Write Recovery Time : auto
Read to Precharge Time : auto

Read to Write Delay (S/D) : auto
Write to Read Delay (S) : auto
Write to Read Delay (D) : auto
Read to Read Delay (S) : auto
Read to Read Delay (D) : auto
Write to Write Delay (S) : auto
Write to Write Delay (D) : auto
DRAM Static Read Control: auto
Ai Clock Twister : auto
Transaction Booster : auto

CPU Voltage : set = 1.36 actual = 1.35
CPU PLL Voltage : auto, actual = 1.6
North Bridge Voltage : set = 1.49 actual = 1.48
DRAM Voltage : set = 2.08 actual 2.128
FSB Termination Voltage : 1.424
South Bridge Voltage : 1.056
Loadline Calibration : enabled
CPU GTL Reference : 1.072
North Bridge GTL Reference : auto
DDR2 Channel A REF Voltage : auto
DDR2 Channel B REF Voltage : auto
DDR2 Controller REF Voltage : auto
SB 1.5V Voltage : 1.504

NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED :

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

Advanced CPU Configuration
CPU Ratio Control : Manual
- Ratio CMOS Setting :
C1E Suppport : Disabled
CPU TM Function : Disabled
Vanderpool Technology : Disabled
Execute Disable Bit : Disabled
Max CPUID Value Limit : Disabled


USB Configuration
USB Functions: Enabled
Legacy USB Support : Disabled

i sincerely hope my board isnt screwed, but its been running fine minus the supreme commander crash during a certain skirmish level, but i believe thats more a SC/VISTA/Driver/Patch problem or something. Any suggestions would be much appreciated

[Sources]

Im guessing you are gonna have to up your voltage. It says the RAM requires 2.2v to run at 1066 but all sticks are different and it may require you to up your NB and CPU volts a bit if they are drawing more power to RAM. So if its randomly picking cores to use for Prime then its not getting enough juice to run all 4 ?

Give it a try


Ok smart guys, i have a very VERY strange problem that happened last night. i believe its RAM related because it happened after i changed my 2 Gb Crucial Ballistix Tracer 1066 DDR2 (double sided so not the revision) from 800 Mhz to 1066.

the problem started when i did the above change because the RAM is rated for that speed and i wanted to run it that level. I can notice the comp is more speedy at that speed then at 800, however its just slight. RAM is at 2.13V actual too. Windows boots up fine and reading websites and what not and i decide to make sure the system is stable at this speed, just to be sure. I load up Prime95, start blend test and my Q6600 on begins running 2 cores, the other two report an error "cannot initialise small fft, error code 1005." So i turn off the test and restart it, same thing, but different cores are working and different ones are turned off. I try again and only one core runs. I looked on the web and found that this occurred before on Orthos, so i loaded that up, ran blend, and same thing, same error, AND the motherboard starting BEEPING every 5-7 seconds, along with the LCD poster saying "RESERVED" Note that the beeping is a different tone than the initial beeps you get during start up, if that has any significance. I cant find anything on what the hell RESERVED means, and after i changed the RAM speed back to 800 i was able to run the blend tests fine with no beeping or RESERVED message

Keep in mind that i can run both small fft and large fft in prime95 just find, just not the blend. I can even run Memtest and prime95 small or large fft and let it go for 8+ hours with no errors. so what the HELL is this? im debating calling ASUS tech support because the error seems so unique.

I have my board on 0907 bios, with these settings:
Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 8
FSB Frequency : 400
FSB Strap to North Bridge : auto
PCI-E Frequency: 100
DRAM Frequency: DDR2- 800
DRAM Command Rate : auto
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 15
RAS# to RAS# Delay : auto
Row Refresh Cycle Time : auto
Write Recovery Time : auto
Read to Precharge Time : auto

Read to Write Delay (S/D) : auto
Write to Read Delay (S) : auto
Write to Read Delay (D) : auto
Read to Read Delay (S) : auto
Read to Read Delay (D) : auto
Write to Write Delay (S) : auto
Write to Write Delay (D) : auto
DRAM Static Read Control: auto
Ai Clock Twister : auto
Transaction Booster : auto

CPU Voltage : set = 1.36 actual = 1.35
CPU PLL Voltage : auto, actual = 1.6
North Bridge Voltage : set = 1.49 actual = 1.48
DRAM Voltage : set = 2.08 actual 2.128
FSB Termination Voltage : 1.424
South Bridge Voltage : 1.056
Loadline Calibration : enabled
CPU GTL Reference : 1.072
North Bridge GTL Reference : auto
DDR2 Channel A REF Voltage : auto
DDR2 Channel B REF Voltage : auto
DDR2 Controller REF Voltage : auto
SB 1.5V Voltage : 1.504

NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED :

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

Advanced CPU Configuration
CPU Ratio Control : Manual
- Ratio CMOS Setting :
C1E Suppport : Disabled
CPU TM Function : Disabled
Vanderpool Technology : Disabled
Execute Disable Bit : Disabled
Max CPUID Value Limit : Disabled


USB Configuration
USB Functions: Enabled
Legacy USB Support : Disabled

i sincerely hope my board isnt screwed, but its been running fine minus the supreme commander crash during a certain skirmish level, but i believe thats more a SC/VISTA/Driver/Patch problem or something. Any suggestions would be much appreciated

[dc2]

what would yield better results

425 x 9

or


465 x 8

[Sources]

roughly the same but the 465x8 would allow for a higher FSB.

[Newms118]

Im guessing you are gonna have to up your voltage. It says the RAM requires 2.2v to run at 1066 but all sticks are different and it may require you to up your NB and CPU volts a bit if they are drawing more power to RAM. So if its randomly picking cores to use for Prime then its not getting enough juice to run all 4 ?

Give it a try

ill try increasing the volts, but i thought the volts for vcore and NB were already high for just 3.2 Ghz, i dont remember my VID but i remember it being low, ill come post it after i see again tonight, i mean what arent my vcore and NB volts for that low of an overclock? anyone recommend me calling asus to see what that beeping and "reserved" message meant?

[ante_ante]

Sorry for the delay, did not test this yet.
This is off the Rampage Mobo Disk, according to mc2k its bios 215 altho its not been confirmed.

Rampage Bios 215 (http://rapidshare.com/files/104254502/rampage_bios_mc2k.rar.html)

Does bios 0215 work good ??

[cajer]

Everytime I boot up I get the det. dram. error when I boot up above 440 fsb. I know it's not my memory that limiting me because I can get to 5-5-5-12 @ 1200 2.2v. Also it's not my proc because i can get my proc to 3.8 ghz on other mobos. Could you help me? This is my setting-

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting :8
FSB Frequency : 445
FSB Strap to North Bridge : 333
PCI-E Frequency: 110
DRAM Frequency: DDR2- 891
DRAM Command Rate : 2t
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 5
RAS# to RAS# Delay : 12
Row Refresh Cycle Time : Auto
Write Recovery Time : Auto
Read to Precharge Time : Auto

Read to Write Delay (S/D) : Auto
Write to Read Delay (S) : Auto
Write to Read Delay (D) : Auto
Read to Read Delay (S) : Auto
Read to Read Delay (D) : Auto
Write to Write Delay (S) : Auto
Write to Write Delay (D) : Auto
DRAM Static Read Control: Enabled
Ai Clock Twister : Strong
Transaction Booster : Enabled
Relax: 0

CPU Voltage : 1.3
CPU PLL Voltage : 1.7
North Bridge Voltage : 1.61
DRAM Voltage : 2.22
FSB Termination Voltage : 1.52
South Bridge Voltage : Enabled
Loadline Calibration : 0.63x
CPU GTL Reference : Auto
North Bridge GTL Reference : Auto
DDR2 Channel A REF Voltage : Auto
DDR2 Channel B REF Voltage : Auto
DDR2 Controller REF Voltage : Auto
SB 1.5V Voltage : 1.6

NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED : enabled

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

[kup]

From what I can tell my problem was the vDroop pencil mod coming undone... oops! :P

[cajer]

Whenever I try to format my usb drive to be bootable it fails. Any hints on how to make it work?

[grimpy]

cajer,try disabling transaction booster and set relax to 1.

[heanwi]

Anyone else had problems with the soundcard (SupremeFX)? Worked perfectly, but after I reinstalled my system in a new case it wont work. The "logo" lights up and the system identifies the card, but I can't hear anything. Any suggestions?

[cajer]

I disable the transaction booster and set relax to 1, but I still get the det dram error and it does not boot.

[Sources]

Can someone post their settings with the Rampage bios mod with a Q6600 o/c'd more than 3.6ghz plz.

[Dostoyevsky77]

Does anyone know of issues or problems running an 9800GX2 on this board?

[ericab]

how are you trying to format it ?
you need to use the hp format tool; not the one built into windows.

[cajer]

I am using the hp format tool it gets 4/5 of the way done. Then it says "Failed to make the device DOS-bootable".

[cajer]

No problems with the 9800GX2 so far for me.

[devilhood]

What program do I use to check my VID?

I noticed I'm having problems with my Q6600 G0 chip, it won't stay stable at 3.6GHz unless I'm running 1.5v through it...

Personally, I use CoreTemp.

You must have a really high VID then, 1.5v is too excessive, your CPU wont last long under that kind of pressure.

[Sources]

What program do I use to check my VID?

I noticed I'm having problems with my Q6600 G0 chip, it won't stay stable at 3.6GHz unless I'm running 1.5v through it...

Might not be your CPU voltage that is lacking, try double checking you other settings. PPL, NB etc...

Remember this board has TONS of settings that can affect your whole stability and OC.

[Edro Davis]

The file you posted is 0207, not 0215.

There is no indication of what version BIOS ROM file is on the ASUS supplied DVD for the Formula Rampage that I just received. The DVD is rev.362.01 and also has "M1307" written on it. But even in the file which lists the files on the DVD (including itself), it does NOT list the FORMULA.ROM file and thus does not indicate its version.

If someone wants me to upload my FORMULA.ROM file from the Rampage Formula Motherboard DVD, I'd be glad to do it..

edro

[ericab]

try this:

right click on the usb drive, and format it (ie, erase all data)

once done, extract the files from this zip:

http://rapidshare.com/files/104380422/win98bootfiles--DOS.zip.html

voila.

[ericab]

There is no indication of what version BIOS ROM file is on the ASUS supplied DVD for the Formula Rampage that I just received. The DVD is rev.362.01 and also has "M1307" written on it. But even in the file which lists the files on the DVD (including itself), it does NOT list the FORMULA.ROM file and thus does not indicate its version.

If someone wants me to upload my FORMULA.ROM file from the Rampage Formula Motherboard DVD, I'd be glad to do it..

edro

yeah, upload it and ill check what version you have.

[Eastcoasthandle]

Everytime I boot up I get the det. dram. error when I boot up above 440 fsb. I know it's not my memory that limiting me because I can get to 5-5-5-12 @ 1200 2.2v. Also it's not my proc because i can get my proc to 3.8 ghz on other mobos. Could you help me? This is my setting-

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting :8
FSB Frequency : 445
FSB Strap to North Bridge : 333
PCI-E Frequency: 110 100
DRAM Frequency: DDR2- 891 1066
DRAM Command Rate : 2t
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 5
RAS# to RAS# Delay : 12
Row Refresh Cycle Time : Auto
Write Recovery Time : Auto
Read to Precharge Time : Auto

Read to Write Delay (S/D) : Auto
Write to Read Delay (S) : Auto
Write to Read Delay (D) : Auto
Read to Read Delay (S) : Auto
Read to Read Delay (D) : Auto
Write to Write Delay (S) : Auto
Write to Write Delay (D) : Auto
DRAM Static Read Control: Enabled Auto
Ai Clock Twister : Strong Auto
Transaction Booster : Enabled Disabled
Relax: 0 keep at 0

CPU Voltage : 1.3
CPU PLL Voltage : 1.7
North Bridge Voltage : 1.61 1.55V
DRAM Voltage : 2.22 2.10 unless your ram voltage specifically calls for 2.30
FSB Termination Voltage : 1.52 reduce accordingly, suggestion 1.40
South Bridge Voltage : Enabled
Loadline Calibration : 0.63x
CPU GTL Reference : Auto
North Bridge GTL Reference : Auto
DDR2 Channel A REF Voltage : Auto
DDR2 Channel B REF Voltage : Auto
DDR2 Controller REF Voltage : Auto
SB 1.5V Voltage : 1.6

NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED : enabled

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

Try that and see what happens. Also, please actively cool your Northbridge chipset if you haven't already. You will need to put a fan on the Northbridge.

[cajer]

Still does not work. :( Do you think I could boot from a cd and put he mod on that?

[ericab]

Still does not work. :( Do you think I could boot from a cd and put he mod on that?

yes, of course.

im assuming you dont have a floppy ?

[cajer]

Try that and see what happens.

I tried those settings but I still get det dram. error.

[Eastcoasthandle]

I tried those settings but I still get det dram. error.

ok try 1.61 then. Go into your bios tab over to Power, then Hardware Monitor and post your heat and voltage. In particular your northbridge voltage. It maybe higher then normal. We will see.

[Grnfinger]

To bad its not 215, altho the board is supposed to be shipped with it.
I'll see if he will make a copy from the mobo itself.

[Grnfinger]

I tried those settings but I still get det dram. error.

try trans booster disabled level1

[TheOriginalTB]

A small update from me again. I swapped the E6600 with an E8400 - this board actually rocks now! My ram has never been faster, and has never been clocked so high (544MHz), perfoamnce level 8 with all pullins enabled. CPU clocked at 4.1GHz (1.311v), FSB VTT 1.23V, NB 1.47V, SB 1,1V

Everest bench with my 24/7 settings: 9461MB/s read, 9479MB/s write and 9016MB/s copy. Latency is 52.9ns.

But I have an issue with 1:1 dividers, they just don't boot with FSB above 398MHz :/

[Grnfinger]

8400's play very nice with this bios
I gained an extra 100MHz with little voltage increase
Bandwidth is very very good

What ram are you running?

[ericab]

hey Grn?

what everest voltage are you putting through your ram for 1175 ?

are you version 2.1 or 2.2 ?

[Grnfinger]

2.2 volts and my ram is ver 1.2

I can post my bios setup if you like

[jurc_podgurc]

Hi

Anyone else here has strange sound coming from maximus formula at load (occt, super pi)? it sound like old 56k modem connecting, only quieter, but gets louder when oc memory to 1080MHz 2.1V (from 900MHz 1.9V). i think that sound is coming from somewhere near NB. Otherwise mb is stable (few hours of occt and prime95).
Thanks in advance for any info or help.

[sofarfrome]

Most peepz are limiting themselves by insisting on the higher multi's so of corse you run out of CPU before you can get the FSB.

Then most peepz don't know they can drop the multi and take full advantage of the higher FSB.

[loften]

Hi

Anyone else here has strange sound coming from maximus formula at load (occt, super pi)? it sound like old 56k modem connecting, only quieter, but gets louder when oc memory to 1080MHz 2.1V (from 900MHz 1.9V). i think that sound is coming from somewhere near NB. Otherwise mb is stable (few hours of occt and prime95).
Thanks in advance for any info or help.
does it go away for a second when you scroll your mouse wheel?

[TouGe]

Hi

Anyone else here has strange sound coming from maximus formula at load (occt, super pi)? it sound like old 56k modem connecting, only quieter, but gets louder when oc memory to 1080MHz 2.1V (from 900MHz 1.9V). i think that sound is coming from somewhere near NB. Otherwise mb is stable (few hours of occt and prime95).
Thanks in advance for any info or help.

Yeah, I used to get that ever once in a while when I am running Prime95 Small FFTs. I believe the sound is comming from the Mosfets. After I dropped my CPU GTL to 0.63x/NB GTL to 0.65V and CPU PLL to 1.50V (1.616V) I haven't heard anything.

On a side note, that sound you speak of plagued many people who owned Nvidia 680i reference boards but it was much louder from what I understand.

[Edro Davis]

yeah, upload it and ill check what version you have.

Here it is: Formula.ROM (http://www.rodatus.net/openfiles/Formula.ROM)

[ericab]

Here it is: Formula.ROM (http://www.rodatus.net/openfiles/Formula.ROM)

the version you posted is : 207

[Edro Davis]

the version you posted is : 207

Is it possible to extract BIOS ROM instructions from the MB as someone else suggested?

It seems very odd to me that ASUS would be shipping the boards with 0215, shipping the DVDs with 0207, and putting 0217 on their website.

I wonder why? What is their "official" word on 0215? :shrug:

Thanks for checking the version for me. :up:

[ericab]

Is it possible to extract BIOS ROM instructions from the MB as someone else suggested?

It seems very odd to me that ASUS would be shipping the boards with 0215, shipping the DVDs with 0207, and putting 0217 on their website.

I wonder why? What is their "official" word on 0215? :shrug:

Thanks for checking the version for me. :up:

i believe Grnfinger is working on 215, with a friend.

as for shipping different bios versions on cd/mb/web etc... someone here stated it pretty well... the cds are burned with the latest version available at the time; and as the r&d / manufacturing of the boards finalizes, the most recent version is flashed to them. it sucks, but never install drivers with included cd/dvds; their always outdated. google is your friend :yepp:

[Nuckin_Futs]

Morning #2

After more then 8 hours I am happy to report again my computer does in fact properly cold boot with my PC8500 ram at 1066MHz. This means no electricity for at all for more then 8 hours. It appears that having the north bridge voltage at 1.55V instead of 1.43V is in fact working. It still double boots from a cold boot using my Corsair PC8500 ram. However, if I hit the reset button or restart XP it will reboot once (IE like normal).

To make clear. Are you saying you could not cold boot in full auto dufaults or sujt your RAM when set to 1066 period? 1.55v is rather for 1066 and especially if on mild FSB of under 475. I can Run Ballistics at 1200MHz on a NB of only 1.504v in 5:6 divider at 500x8. However, S3 (Stand By/Sleep) is not 100% stable unless I up NB to 1.54v and FSBT to 1.504v.


So are you MAXIMUS owners now not able to boot w/ defaults after a BIOS flash or just because sinne BETA BIOS v0903? Isa this gonna be the norm from now on?

[jurc_podgurc]

does it go away for a second when you scroll your mouse wheel?
no, it doesn't


Yeah, I used to get that ever once in a while when I am running Prime95 Small FFTs. I believe the sound is comming from the Mosfets. After I dropped my CPU GTL to 0.63x/NB GTL to 0.65V and CPU PLL to 1.50V (1.616V) I haven't heard anything.
already have the same voltages set in bios

i left pc running orthos overnight (~5 hours) without problems, temps are fine. the sound doesn't disturb me (fans are louder and seagates when reading too), board is stable, without det ram problems if nb 1.45V or more, should i keep or rma the board? does this sound mean it will die on me soon? motherboard is only few days old and this strange sound is present from day one.

thanks

[Grnfinger]

Will have the bios Friday
mc2k is busy with school and has not installed the board yet.
Personally I would have been all over that board like a fat chick on chocolate but....

[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.

[Eastcoasthandle]

To make clear. Are you saying you could not cold boot in full auto dufaults or sujt your RAM when set to 1066 period? 1.55v is rather for 1066 and especially if on mild FSB of under 475. I can Run Ballistics at 1200MHz on a NB of only 1.504v in 5:6 divider at 500x8. However, S3 (Stand By/Sleep) is not 100% stable unless I up NB to 1.54v and FSBT to 1.504v.


So are you MAXIMUS owners now not able to boot w/ defaults after a BIOS flash or just because sinne BETA BIOS v0903? Isa this gonna be the norm from now on?
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).

[TheOriginalTB]

What ram are you running?

OCZ FlexXLC 6400 CAS3. There is still some room left in them, at 2.38V they can run 575MHz CAS 5-5-5-18, but itunes will crash :/

24/7 setting is as stated above.

[newls1]

Will have the bios Friday
mc2k is busy with school and has not installed the board yet.
Personally I would have been all over that board like a fat chick on chocolate but....

LMAO:p:

[GoldiClocks]

Just got my Asus Rampage Formula yesterday (no maximus -> rampage conversion.)
It had BIOS version 0219 ready. Voltages seem to be bit strange (Dram voltage set 2.1 in bios, reads 2.192 in bios; cpu voltage set 1.38125, reads 1.360 in bios ?).
Can anyone comment those voltage readings?

[wilson]

Ok now even with a new psu i get the same problem and i was confused as my cheap 300w psu powered it up fine. So on a close look i found that the cheap psu only had the 4 pin cpu cable and not the 8 pin ? well after pulling the 8 pin out and swapping it with the 4 all seems to be well but is this ok for my quad :shrug: It sure is strange that my maximus formula has cold boot problems then my rampage had the same problem then with two new psu`s still the same problem but now with only the 4 pin in its fine..

[Eastcoasthandle]

Ok now even with a new psu i get the same problem and i was confused as my cheap 300w psu powered it up fine. So on a close look i found that the cheap psu only had the 4 pin cpu cable and not the 8 pin ? well after pulling the 8 pin out and swapping it with the 4 all seems to be well but is this ok for my quad :shrug: It sure is strange that my maximus formula has cold boot problems then my rampage had the same problem then with two new psu`s still the same problem but now with only the 4 pin in its fine..

If (and only if) you have a fan connected to the power fan connector (upper left corner of the board page 2-33 of MB manual) remove it and see if it will boot up.

[cajer]

ok try 1.61 then. Go into your bios tab over to Power, then Hardware Monitor and post your heat and voltage. In particular your northbridge voltage. It maybe higher then normal. We will see.


Now with these new settings I can post and boot but it freezes in the windows load screen. Also idleing my NB is at 48 degrees C. Voltage wise it is at 1.65 in the Hardware Monitor. Also how would I mount a fan on my NB if I am running my system in a case?

[Brama]

Just got my Asus Rampage Formula yesterday (no maximus -> rampage conversion.)
It had BIOS version 0219 ready. Voltages seem to be bit strange (Dram voltage set 2.1 in bios, reads 2.192 in bios; cpu voltage set 1.38125, reads 1.360 in bios ?).
Can anyone comment those voltage readings?

My P5E converted to Rampage does the same.
Actually, to have 2.1 V BIOS sensor reading, I have to set 2.02 V.
Cpu voltage is normal because if you don't enable LLC, the BIOS apply a minus offset to the preset voltage, following Intel best practice in designing a VRM for core2 processors.

[Eastcoasthandle]

Now with these new settings I can post and boot but it freezes in the windows load screen. Also idleing my NB is at 48 degrees C. Voltage wise it is at 1.65 in the Hardware Monitor. Also how would I mount a fan on my NB if I am running my system in a case?

Yup, just what I thought, your NB is to hot for idle temps IMO. OK, now I'm willing to guess that if you figure out a way to cool your north and south bridge chipsets you should be in the clear for stability. Right now your problem appears to be heat related regarding the northbridge chip. Get yourself 2, 40mm fans (http://www.sidewindercomputers.com/sunon40x20mm.html) and 4 1 1/2" wood screws and you should be good to go. For now, I would lower your dram frequency to 800 then lower your NB voltage between 1.45V to 1.50V and you should be ok in the meantime.

Side note:
Did you ever remove that thermal cement before you installed the MB to your PC? If you look at my post here (http://www.xtremesystems.org/forums/showpost.php?p=2602760&postcount=4) you will see that the HS doesn't always make full contact with the chipset.

[GoldiClocks]

My P5E converted to Rampage does the same.
Actually, to have 2.1 V BIOS sensor reading, I have to set 2.02 V.
Cpu voltage is normal because if you don't enable LLC, the BIOS apply a minus offset to the preset voltage, following Intel best practice in designing a VRM for core2 processors.

Loadline Calibration was turned on when I looked at the voltages though :(

[eSp!s0]

Not stable till now, 533FSB is hard to reach but I am close:
533x6:
http://www.abload.de/thumb/cachemembios1004533x5vc.png (http://www.abload.de/image.php?img=cachemembios1004533x5vc.png)
525x7:
http://www.abload.de/thumb/cachemembios1004525x8mh.png (http://www.abload.de/image.php?img=cachemembios1004525x8mh.png)

[Durkadurka]

Has anyone had problems installing soundcards on this board?
I've tried with both the Supreme FX II in the top black slot, and with a Creative X-Fi Platinum in the lower white PCI slot.
None of the drivers work, and I get a "No Audio output device is installed" message.
This is under Vista Ultimate 64-bit SP1 RTM.

Could this have anything to do with SB voltages or PCIe Frequency? (Currently running 1.5v SB and 110 MHz PCIe Frequency)

[Dostoyevsky77]

I want to run multiple displays on two Nvidia graphics cards. Just to be clear, I'm NOT talking about SLI.

Does anyone see a problem with that? Does anyone have specific experience with multiple display adapters for multiple displays? I want to run an 9800GX2 (which only runs one display) and a 320MB 8800GTS for my secondary display.



Has anyone had problems installing soundcards on this board?
I've tried with both the Supreme FX II in the top black slot, and with a Creative X-Fi Platinum (SNIP!)

I run an X-Fi Platinum on the top slot (to make room for my HR-03+, sigged pics) with no problems whatsoever. I run Vista Ultimate x64. The only time I did have a problem was when I tried the drivers from the included disc. There is only one appropriate storage contained for the drivers disc: the rubbish bin. Your vSB is very high. I run a little over 1.1 with no problems... unless you're talking about vSB 1.5v, which I also have at 1.5 (and I also run PCI-E at 110). I don't think these things should have an effect, though.

***UNRELATED EDIT: New Maximuses at NewEgg! Maybe we're not going to be left out with the laundry!

[Dostoyevsky77]

Loadline Calibration was turned on when I looked at the voltages though :(

The vDRAM is a normal overvolt. A lot of ASUS boards do that, and the Maximusi were no exception, so it surprises me not in the least that Rampages would do the same. Just be aware of it and undervolt where necessary.

Your CPU undervolt seems odd. I have no comment regarding it besides that.

[zlojack]

We should compare the X48 Rampage results vs. the X38 Rampage results to really see the benefit of the X48 NB.

[Grnfinger]

Just got my Asus Rampage Formula yesterday (no maximus -> rampage conversion.)
It had BIOS version 0219 ready. Voltages seem to be bit strange (Dram voltage set 2.1 in bios, reads 2.192 in bios; cpu voltage set 1.38125, reads 1.360 in bios ?).
Can anyone comment those voltage readings?

I get the exact same over voltss on the ram and same under volt on the cpu.
I have load line enabled but it still does it
Just make the adjustment in bios

[Mindfield]

Loadline Calibration was turned on when I looked at the voltages though :(


Loadline calibration helps with vdroop (the drop while under load) and not the vdrop which is the undervolt I've seen on every board I've owned. I have mine set 1.30v in bios and get 1.28v real. I also have the vdroop pencil mod and the voltage doesn't budge under load.

Loadline calibration never seemed to do anything for me so I left it off. Pencil mod works much better.

btw this is with P5E -> Rampage

[Grnfinger]

I want to run multiple displays on two Nvidia graphics cards. Just to be clear, I'm NOT talking about SLI.

Does anyone see a problem with that? Does anyone have specific experience with multiple display adapters for multiple displays? I want to run an 9800GX2 (which only runs one display) and a 320MB 8800GTS for my secondary display.




I run an X-Fi Platinum on the top slot (to make room for my HR-03+, sigged pics) with no problems whatsoever. I run Vista Ultimate x64. The only time I did have a problem was when I tried the drivers from the included disc. There is only one appropriate storage contained for the drivers disc: the rubbish bin. Your vSB is very high. I run a little over 1.1 with no problems... unless you're talking about vSB 1.5v, which I also have at 1.5 (and I also run PCI-E at 110). I don't think these things should have an effect, though.

***UNRELATED EDIT: New Maximuses at NewEgg! Maybe we're not going to be left out with the laundry!

I do think you need to run different cards ie 1 nvidia and 1 ati or else there will be a driver conflict and only 1 nvidia card will be enabled. I could be wrong but I think it wont work with 2 nvidia cards installed.


Has anyone had problems installing soundcards on this board?
I've tried with both the Supreme FX II in the top black slot, and with a Creative X-Fi Platinum in the lower white PCI slot.
None of the drivers work, and I get a "No Audio output device is installed" message.
This is under Vista Ultimate 64-bit SP1 RTM.

Could this have anything to do with SB voltages or PCIe Frequency? (Currently running 1.5v SB and 110 MHz PCIe Frequency)

I run a X-FI ExtremeGamer in the top slot., Vista 32 and SP1 and have had no issues. I installed the drivers from the cd and then do updates from creative site.
my PCIE is set 110, google the issue and see if others have had the same problem and see how it was resolved

[cajer]

Get yourself 2, 40mm fans (http://www.sidewindercomputers.com/sunon40x20mm.html) and 4 1 1/2" wood screws and you should be good to go. For now, I would lower your dram frequency to 800 then lower your NB voltage between 1.45V to 1.50V and you should be ok in the meantime.


Side note:
Did you ever remove that thermal cement before you installed the MB to your PC? If you look at my post here (http://www.xtremesystems.org/forums/showpost.php?p=2602760&postcount=4) you will see that the HS doesn't always make full contact with the chipset.

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?

[GoldiClocks]

ok, thanks for all the replies guys, guess I won't be RMA'ing my board yet.. :p:

I'll give it more work tomorrow, completely new to c2d overclocking so it will take some time to get results.

[Eastcoasthandle]

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?

I think you are on your own on that one based on your setup, case, etc.

[brewer265]

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?

you could try one of these fans from antec to cool your nb.
http://www.antec.com/us/productDetails.php?ProdID=75018#

[Eastcoasthandle]

you could try one of these fans from antec to cool your nb.
http://www.antec.com/us/productDetails.php?ProdID=75018#

Hey, that's a good idea.

Look here (http://www.overclockersclub.com/reviews/spotcool/)

[TouGe]

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?

Look at the bottom of my sig for the model of SB sink that I use. There are two types of Enzo coolers for the SB, the one I have listed comes with a fan and the GX2 clears it just fine.

[Jodiuh]

Does anyone know iof the bios setting for ACPI 2.0 should be enabled or disabled?

For my Vista x64 Ultimate acpi 2.0:

off = no sleep
on = sleep

What about some of those legacy options for USB?

[Nuckin_Futs]

So you guys experiencing this DET_RAM issue on cold boot, are you also getting this upon loading of system defaults? And also, are we talking since new on an ASUS final BIOS of v0802 and below?

I got mine on BETA v0903 and I can boot form reset of CMOS on cold boot out of the box w/ my Crucial Ballistix Tracers PC28500 2x1g on al BIOS to v0903. Never was an issue till I dabbled with BETA v0907 and then on. I RMD'd and the new one is fine again.

I'm just asking cause this is not normal and 2 of mine never did that w/ same RAM or even my OCZ. These RAMS just load as DDR800 and vdimm is already 2.0 since the mobo overcolts. My NB was only 1.35v on out of the bos cold boot for the first time. I did so in 2nd slots so cannot confirm 1st slots today on this mobo but my 1st one was fine either way.


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?
Are you willing to remove the stock NB + SB assy.? This is the best method but then you need to find air or water cooling to fit in there where ned it.

2nd is to just remove the "ROG" badge off the SB and fix 10x30 fan to take the load off the NB since it is fed upwards. Another idea, would be to shroud the whole length of the aluminum himps with NB inside and fan from front to back. Just make sure air is drwan from front lower cool area and exhaulsted to somewhere away from GPU. If anything shield the heat from that GPU as it isnt helping the already limited NB block.

Just some ideas!

[Dostoyevsky77]

I do think you need to run different cards ie 1 nvidia and 1 ati or else there will be a driver conflict and only 1 nvidia card will be enabled. I could be wrong but I think it wont work with 2 nvidia cards installed.

I'm hoping that can be resolved in device manager by "updating" the driver on the other device.

Anyway, I think I'm going to do this thing (pending wife's approval). I'm nervous but excited: I can't wait to see the improvement.

I'll let you all know how it goes, but it probably won't be until next weekend.

Here is my sweetie:
http://www.newegg.com/Product/Product.aspx?Item=N82E16814130344

[cajer]

So you guys experiencing this DET_RAM issue on cold boot, are you also getting this upon loading of system defaults? And also, are we talking since new on an ASUS final BIOS of v0802 and below?

I got mine on BETA v0903 and I can boot form reset of CMOS on cold boot out of the box w/ my Crucial Ballistix Tracers PC28500 2x1g on al BIOS to v0903. Never was an issue till I dabbled with BETA v0907 and then on. I RMD'd and the new one is fine again.

I'm just asking cause this is not normal and 2 of mine never did that w/ same RAM or even my OCZ. These RAMS just load as DDR800 and vdimm is already 2.0 since the mobo overcolts. My NB was only 1.35v on out of the bos cold boot for the first time. I did so in 2nd slots so cannot confirm 1st slots today on this mobo but my 1st one was fine either way.


So... are you saying that if I revert to an older bios or do the maxiumus rampage mod everything will clear up? Also I don't think that I can go water or buy some better cooling for my whole mobo because I am short on money. :( So I will just get hte Antec spot cool and point that thing towards my NB.

[Eastcoasthandle]

Is the older bios compatible with your CPU (X3350). I would be very careful with older Bioses.

[cajer]

Is the older bios compatible with your CPU (X3350). I would be very careful with older Bioses.

I will go check.

[Nuckin_Futs]

So... are you saying that if I revert to an older bios or do the maxiumus rampage mod everything will clear up? Also I don't think that I can go water or buy some better cooling for my whole mobo because I am short on money. :( So I will just get hte Antec spot cool and point that thing towards my NB.

NO, reverting did not help me once I did go v0907, and from what I understand on RAMPAGE BIOS, this will void your warrenty (correct me if it has changed). But nevertheless, you're only opening the door for more problems if using a BIOS written for another mobo. So if doing so, do so at your own RISK.

I had to RMA mine to get back to normal after the bad v0907. I know others have used it and claim no issues, so again, as with any beta BIOS, nothing is guarentied. Either mine was an isolated case or nobody wants to report it.

As for the cooling, totally understood, thats why I gave the idea of modding with things around the house, some plastic and cut and shape a duct for the NB and put small 40x25mm fan either to case rear exhaulst or on front end. Abit used this method on their early OATES system to cool mosfets and it did fine on air. I still have the 1st IC7-MAX 3 and changed the mosfets blocks to copper.

[Eastcoasthandle]

NO, reverting did not help me once I did go v0907, and from what I understand on RAMPAGE BIOS, this will void your warrenty (correct me if it has changed). But nevertheless, you're only opening the door for more problems if using a BIOS written for another mobo. So if doing so, do so at your own RISK.

I had to RMA mine to get back to normal after the bad v0907. I know others have used it and claim no issues, so again, as with any beta BIOS, nothing is guarentied. Either mine was an isolated case or nobody wants to report it.

As for the cooling, totally understood, thats why I gave the idea of modding with things around the house, some plastic and cut and shape a duct for the NB and put small 40x25mm fan either to case rear exhaulst or on front end. Abit used this method on their early OATES system to cool mosfets and it did fine on air. I still have the 1st IC7-MAX 3 and changed the mosfets blocks to copper.

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?

[Nuckin_Futs]

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.

[cajer]

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.

[Nuckin_Futs]

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.

[ZenEffect]

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/attachment.php?attachmentid=74089&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

[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

[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 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

[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.

[Nuckin_Futs]

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!

[cajer]

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.

[Nuckin_Futs]

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.

[kup]

@ 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:

[cyrixMII300]

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.


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.

[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

[kup]

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!!!!!

[Utnorris]

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

Utnorris

[Eastcoasthandle]

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?

[kup]

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?

[trt740]

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?

[Wolf2000me]

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/showthread.php?t=166867

[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!

[giorgos th.]

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..

[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

[M-XXXX]

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:

[Dostoyevsky77]

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!

[iadstudio]

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)

[Grnfinger]

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

[XtremeTiramisu]

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.

[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?

[jwfitt]

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.


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.

[Eastcoasthandle]

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)?

[Wolf2000me]

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.

[jwfitt]

... 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...

[Nuckin_Futs]

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).


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)


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.

[Nuckin_Futs]

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.

[trt740]

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.

[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.

[Nuckin_Futs]

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!

[loften]

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.

[iadstudio]

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:

[jwfitt]

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.

[jwfitt]

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.

[Utnorris]

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

[Eastcoasthandle]

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?

[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.

[Nuckin_Futs]

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.


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.


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.

[jwfitt]

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)?

[Dostoyevsky77]

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/ee93/Dostoyevsky77/Capture-21.jpg

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

[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?

[Dostoyevsky77]

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.

[loften]

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

[jwfitt]

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


It's a single rail I believe with a split 4/8 pin connection. The 1200W one is indeed a double 12v rail.

850W:
http://www.newegg.com/Product/Product.aspx?Item=N82E16817153043

1200W:
http://www.newegg.com/Product/Product.aspx?Item=N82E16817153054

[Skyguy]

I'm having a very weird issue with my Formula..........maybe someone can help??

Am running 2 Raptors in RAID0 with Vista on my Maximus Formula SE, and also have a single 500gb drive with Vista as well in case my RAID takes a dump.

In BIOS I set SATA Configuration to RAID, everything runs great........can boot into Windows on the Raptors and the single drive no problems at all. However, I'm planning on selling my Raptors, so I disconnected them, went into BIOS and turned off RAID in SATA Configuration and also converted them back to single drives in the RAID Utility Manager. Then I rebooted..........but it won't recognize my single drive AT ALL.

I cannot get the drive to be recognized without a RAID setup. As soon as I plug the Raptors back in (and a frickin format and OS install too) and set BIOS SATA Configuration back to RAID, everything is fine and I can boot into Windows on the both RAID and single drive no problem. But when I unplug the Raptors, and try a single drive, it won't recognize the drive nor boot.

I've tried setting the SATA Configuration to IDE (Enhanced), IDE (Compatible), even AHCI........none work for a single drive.

Any ideas????

[XtremeTiramisu]

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.

No, FSB470~475+ isn't feasible. I'm preety sure this is due to the FSB wall winthin the Q6600 G0 (FSB/Strap 266 CPU). This mobo isn't too 65nm quad friendly but I'll hope for the better when I get a FSB/Strap 333 45nm Q9450/Q9550, 8.0/8.5x multi and try again.

RF Bios is still in the beta stage, maybe after some revisions to the bios I'll be able to push my FSB further. So far it's an improvment over my previous P35 P5K-Dlx config.

[Zucker2k]

I can do fsb 475 here with a q6600, so its probably your chip.

[jwfitt]

Skyguy, maybe try taking all of the drives out (except the one you want to install the OS on), setting up your BIOS for single drive and formatting and installing?

[Dumo]

RF bios more stable for 3D bench....

PCI-E @ 110, PLL @ 1.6V and vmem @ 2.2V the rest with autos


http://img81.imageshack.us/img81/1692/screenshot338xc6.jpg

[simplyX]

But when I unplug the Raptors, and try a single drive, it won't recognize the drive nor boot.
Any ideas????

Are you saying that the BIOS Main page doesn't list the single drive if not RAID mode? It should. Or are you saying the drive isn't listed in the boot order menu?

If the later, (at least on my P5E WS Pro) there's a second menu where you must specify the single drive as bootable and then it will appear in the boot order menu. Can you check into this? Hope it helps.

[Nuckin_Futs]

Just so you know, if only one HDD connected the Intel ICHxR in RAID or AHCI enabled, you will NOT see any list of drives during POST. This is noraml and has been. BIOS can only see 2 or more HDD's connected to the hub. A single is or will be there, it is just not displayed in POST.

You must however leave the Intel RAID driver installed after you converted your OS to single disc in RAID ready mode. Were you coming from a 0 back to non RAID sinle or from 1?
How did you convert your RAID to single? Windows based or DOS?

But if you cannot boot to XP even as IDE mode off Intel SATA ICHxR, then something else went wrong during conversion.

[Reg Fessenden]

Hi, i have been following this thread for some time but only just had my account validated. First of all many thanks to The Stilt for the mod in the first place. I have been running the RF bios on my MF for around 3 weeks and found it to be much more stable, i have my Q6600 at 3.6Ghz under WCooling. But recently I installed some OCZ ReaperX ( 2 X 2Gig) and have run into stability problems even at stock speeds they are the 800Mhz version but OZC Tony on their forums says that these should still run at 1066Mhz as they are the same chips as the higher speed version. I have the TRef at 55 which is the nearest to the recommended 54 that i can get (I have tried many of the bios settings posted on this thread). This seems the most stable but i still get blue screens occasionally, usually after one hour or so the computer can be running an app or at idle it doesn't seem to make any difference. I will post more info on my settings and system later when i have more time, but was wondering if anyone else was using this ram with their setup and come across similar problems? Anyway just wanted to say hello to everyone, and get my first post out of the way, Best Regards Tony.

[XtremeTiramisu]

I can do fsb 475 here with a q6600, so its probably your chip.

and it's probably also the diff cooling method we use. I'm on high end air and you're on water. But using *9 multi I could push the cpu mhz in the mid 3800s and stable, the system does suffer from instability using *8 multi and FSB470+

Can you post your BIOS settings template at 475FSB*8 multi? and the bios version, thx

Edit: Nevermind, I saw you're using a 45nm 333fsb/strap E8400 dual core cpu in your sig...this anwers my question now. Your CPU is undoubtedly behaves in a completely diff way than my Q6600 G0. First being 45nm architechture, 333fsb/strap and it's a dual core as opposed to my 65nm, 266fsb/strap and quad. Obviously my cpu will run into a fsb wall before yours. 475fsb for a 333fsb/strap cpu is nothing spectacular really if we compare the fsb increase % to a 266fsb/strap cpu at 466fsb for example. So unless a 45nm 333fsb/strap chip can push well over 500fsb and being stable, that would be considered as a great advancement. However, in that case it may be limited by the current available mobo which can handle at such a high fsb and stay stable under hours of stress tests for daily use.

[MrWizard6600]

Sorry guys, I'm sure this has already been asked.. but, 109 pages :S, thats alot of reading :S

Does this board play nice with 4 sticks of identical stuff? how about not identical stuff? I'm running 4 gigs (4X1GB however, 2 dif kits, ones 64mb X 16chips X 2sticks the other is 128mb X 8chips X 2sticks) of Crucial Ballistix 1066 and I'm very dissapointed in my results. Granted, its not it its final config (airflow isn't as good as its going to be), I cant seem to get this thing stable at 1:1 at 500FSB, which I know this ram can do. Running the strap at 400, but I'm really not sure how that works, something to do with an internal NB clock? gotta research that more...

[M-XXXX]

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

[jwfitt]

I mentioned this in an edited earlier post, but as I'm playing with my overclock settings, what are the highest temps I should be around (Cores, NB, SB) under a full Prime95 load?

Thanks!

[Nuckin_Futs]

Sorry guys, I'm sure this has already been asked.. but, 109 pages :S, thats alot of reading :S

Does this board play nice with 4 sticks of identical stuff? how about not identical stuff? I'm running 4 gigs (4X1GB however, 2 dif kits, ones 64mb X 16chips X 2sticks the other is 128mb X 8chips X 2sticks) of Crucial Ballistix 1066 and I'm very dissapointed in my results. Granted, its not it its final config (airflow isn't as good as its going to be), I cant seem to get this thing stable at 1:1 at 500FSB, which I know this ram can do. Running the strap at 400, but I'm really not sure how that works, something to do with an internal NB clock? gotta research that more...
Odd, I have the regular Ballartix and they looked liek 16 chip double sided and so are my TRacers. Anywayz, I can say the regular and Tracers mixed fine and so did the Tracers and OCZ Plats or Corsair Dominators and OCZ Plats. They all did well to 500FSB in 1:1 all 4 but needed more NB to 1.52v and FSBT to 1.488v. Keep the NB as low as can to keep the heat down cause 4 sticks taxes any mobo and especially on OC. But I did get my 4 to DDR1000 @ 4-5-4-13, where 4-4-4-10 was norm for 2. So not bad. Timings will need to be loosened to keep stable as this is stress on MCH, So carefull of too high FSBT too. Try to keep under 1.504v


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
Sounds like RAM issue, but not certain. I'd look for different RAM and test 1 slot at a time. You will need at least 1 to boot. Boot only w/ CPU RAM and VGA, nothing else for starters. Pull PSU pwr & battery + tap PWR button every few seconds for over 1 min.


I mentioned this in an edited earlier post, but as I'm playing with my overclock settings, what are the highest temps I should be around (Cores, NB, SB) under a full Prime95 load?

Thanks!
In over over 6 months of use, I found 55c to be so so for stability for NB but can get iffy up to 60c and so 51c is comfort zone for mine. SB, 36c - 41c is cool but can hit 44c-49c in the summer heat. I'd try to keep the SB under 48c max for SATA RAID stability.

[Griff]

Just got my 1.03 board fitted and plumbed in, hit the power button to bleed the loops up away it goes, hold power button in to stop so i can top up t-lines and now nothing, reset cmos via rear switch, moved ram to various slots and nada, when i go for a power on the little leds on the mobo for the ram, nb & sb all flicker on for a nano second then nothing, Lcd is showing cpu init.. Just removed the battery and off to do a little shpping for a few hours, hope i havent killed it :shrug:

Any suggestions? cpu is an E8400, psu corsair 650 and 2 gig of Tracers, i have also tried both 4 & 8 pin eatx power..

Cheers Griff

[Nuckin_Futs]

Just got my 1.03 board fitted and plumbed in, hit the power button to bleed the loops up away it goes, hold power button in to stop so i can top up t-lines and now nothing, reset cmos via rear switch, moved ram to various slots and nada, when i go for a power on the little leds on the mobo for the ram, nb & sb all flicker on for a nano second then nothing, Lcd is showing cpu init.. Just removed the battery and off to do a little shpping for a few hours, hope i havent killed it :shrug:

Any suggestions? cpu is an E8400, psu corsair 650 and 2 gig of Tracers, i have also tried both 4 & 8 pin eatx power..

Cheers Griff
What BIOS version and BIOS history usage? What CPU? Try some of the remedies I and others mention just a day ago.

[Griff]

What BIOS version and BIOS history usage? What CPU? Try some of the remedies I and others mention just a day ago.

Never got into the bios, it ran for about 10 seconds whilst i was trying to fill the loops then nothing, fault finding with duel external loops is not a lot of fun :shakes: Loops dismantled and its now sat on the bed, have mofset back plates on, they are insulated but its now nagging at me that i may have a short..

[Griff]

Trying to get it to run with a E6600 then update bios for One that agrees with E8400, Reading identical problem on Asus forums, the guy ended up going RMA in the end..

[Grnfinger]

and it's probably also the diff cooling method we use. I'm on high end air and you're on water. But using *9 multi I could push the cpu mhz in the mid 3800s and stable, the system does suffer from instability using *8 multi and FSB470+

Can you post your BIOS settings template at 475FSB*8 multi? and the bios version, thx

Edit: Nevermind, I saw you're using a 45nm 333fsb/strap E8400 dual core cpu in your sig...this anwers my question now. Your CPU is undoubtedly behaves in a completely diff way than my Q6600 G0. First being 45nm architechture, 333fsb/strap and it's a dual core as opposed to my 65nm, 266fsb/strap and quad. Obviously my cpu will run into a fsb wall before yours. 475fsb for a 333fsb/strap cpu is nothing spectacular really if we compare the fsb increase % to a 266fsb/strap cpu at 466fsb for example. So unless a 45nm 333fsb/strap chip can push well over 500fsb and being stable, that would be considered as a great advancement. However, in that case it may be limited by the current available mobo which can handle at such a high fsb and stay stable under hours of stress tests for daily use.

Zucker2k used to do 500fsb on his quad not 45nm chip.

[golfjam]

Does anybody know a "fix" to run at 333 strap? 400 is rock solid but if I change it and run Prime my system will reboot(sometimes after 10 min or 3 hrs) and hang on "DET RAM".

[Grnfinger]

Does anybody know a "fix" to run at 333 strap? 400 is rock solid but if I change it and run Prime my system will reboot(sometimes after 10 min or 3 hrs) and hang on "DET RAM".

adjust your settings, I only use the 333 strap and run my ram rock solid at 1175MHz.

Post your current settings and we can see where adjustments need to be made

[wreckwriter]

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

Thanks much! I'll get them up today.

[Zucker2k]

and it's probably also the diff cooling method we use. I'm on high end air and you're on water. But using *9 multi I could push the cpu mhz in the mid 3800s and stable, the system does suffer from instability using *8 multi and FSB470+

Can you post your BIOS settings template at 475FSB*8 multi? and the bios version, thx

Edit: Nevermind, I saw you're using a 45nm 333fsb/strap E8400 dual core cpu in your sig...this anwers my question now. Your CPU is undoubtedly behaves in a completely diff way than my Q6600 G0. First being 45nm architechture, 333fsb/strap and it's a dual core as opposed to my 65nm, 266fsb/strap and quad. Obviously my cpu will run into a fsb wall before yours. 475fsb for a 333fsb/strap cpu is nothing spectacular really if we compare the fsb increase % to a 266fsb/strap cpu at 466fsb for example. So unless a 45nm 333fsb/strap chip can push well over 500fsb and being stable, that would be considered as a great advancement. However, in that case it may be limited by the current available mobo which can handle at such a high fsb and stay stable under hours of stress tests for daily use.


I can do fsb 475 here with a q6600, so its probably your chip.

I will quote myself again. Anyway, I'm on MF bios 1004; yes, it makes a huge difference for my quad in terms of stability.

[wilson]

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

I had a problem like that on my maximus formula and my rampage formula and the only way to get it to work was to remove everything but the cpu for it to boot. Then i spent hours putting stuff in to see if it was a faulty ram ,g card ,sound card etc. And i found nothing really other that it would just do it at random times. I have rma`d both mobo`s now and am using a DFI mobo with all the same parts and have no cold boot problems at all. I think its just a faulty batch of chips that got out as it happens to some not all and i got both my MF and RF from the same pc shop.

[BigKriss]

Hi, i have been following this thread for some time but only just had my account validated. First of all many thanks to The Stilt for the mod in the first place. I have been running the RF bios on my MF for around 3 weeks and found it to be much more stable, i have my Q6600 at 3.6Ghz under WCooling. But recently I installed some OCZ ReaperX ( 2 X 2Gig) and have run into stability problems even at stock speeds they are the 800Mhz version but OZC Tony on their forums says that these should still run at 1066Mhz as they are the same chips as the higher speed version. I have the TRef at 55 which is the nearest to the recommended 54 that i can get (I have tried many of the bios settings posted on this thread). This seems the most stable but i still get blue screens occasionally, usually after one hour or so the computer can be running an app or at idle it doesn't seem to make any difference. I will post more info on my settings and system later when i have more time, but was wondering if anyone else was using this ram with their setup and come across similar problems? Anyway just wanted to say hello to everyone, and get my first post out of the way, Best Regards Tony.

A big welcome Tony..Seems the chaps are a bit pre occupied to say hello...

[adrenaline7879]

edited*

[Spyrus]

strap 333 is the most easy i have benced fsb 500@600MHz memory

[wreckwriter]

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

OK, here we go:

Asus Maximus Formula, e8400, 4 GB G-Skill PC2 8500 RAM, 8800GTS video, PC Power and Cooling 750 PSU, Gigabyte Aurora 3d case. Running XP Pro SP2. Bios 0907

Cooling is self built. mostly water, MCP655 pump, PA 120.3 rad (mounted on back of case with 3 medium speed Yates pulling), D-Tek Fuzion CPU block (with washer only), DD Ione video block, EK NB-S-Max northbridge block, XSPC 5 1/4 bay reservoir (components are in that order in loop). Fluid is distilled water with a few drops of Petra's nuke, TIM is MX-2 except CPU which is AS-5. All tubing is 1/2" ID, 3/4" OD. South bridge is air cooled with Thermalright HR-05 IFX with Sythe fan, mosfets with Thermalright HR-09 Type 2 sinks, RAM is cooled by a Corsair Dominator.

Bios settings:


Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : AUTO
- Ratio CMOS Setting :
FSB Frequency : 333
FSB Strap to North Bridge : 333
PCI-E Frequency: 100
DRAM Frequency: DDR2- 1066
DRAM Command Rate :
DRAM Timing Control: AUTO
CAS# Latency : 5,5,5,15
RAS# to CAS# Delay :
RAS# Precharge :
RAS# ActivateTime :
RAS# to RAS# Delay :
Row Refresh Cycle Time :
Write Recovery Time :
Read to Precharge Time :

Read to Write Delay (S/D) :
Write to Read Delay (S) :
Write to Read Delay (D) :
Read to Read Delay (S) :
Read to Read Delay (D) :
Write to Write Delay (S) :
Write to Write Delay (D) :
DRAM Static Read Control: AUTO
Ai Clock Twister : AUTO
Transaction Booster : AUTO

CPU Voltage : AUTO
CPU PLL Voltage : AUTO
North Bridge Voltage : AUTO
DRAM Voltage : 2.00
FSB Termination Voltage : AUTO
South Bridge Voltage : AUTO
Loadline Calibration : ENABLED
CPU GTL Reference : AUTO
North Bridge GTL Reference : AUTO
DDR2 Channel A REF Voltage : AUTO
DDR2 Channel B REF Voltage : AUTO
DDR2 Controller REF Voltage : AUTO
SB 1.5V Voltage : AUTO

NB LED Selection : NB Volt
SB LED Selection : SB Volt
CPU LED Selection : CPU VOlt
Voltiminder LED : ENABLED

CPU Spread Spectrum : AUTO
PCIE Spread Spectrum : AUTO

Advanced CPU Configuration
CPU Ratio Control : AUTO
- Ratio CMOS Setting :
C1E Suppport : Disabled
CPU TM Function : ENABLED
Vanderpool Technology : ENABLED
Execute Disable Bit : ENABLED
Max CPUID Value Limit : Disabled


USB Configuration
USB Functions: Enabled
Legacy USB Support : AUTO


Thanks very much for any tips!

[MrWizard6600]

Odd, I have the regular Ballartix and they looked liek 16 chip double sided and so are my TRacers. Anywayz, I can say the regular and Tracers mixed fine and so did the Tracers and OCZ Plats or Corsair Dominators and OCZ Plats. They all did well to 500FSB in 1:1 all 4 but needed more NB to 1.52v and FSBT to 1.488v. Keep the NB as low as can to keep the heat down cause 4 sticks taxes any mobo and especially on OC. But I did get my 4 to DDR1000 @ 4-5-4-13, where 4-4-4-10 was norm for 2. So not bad. Timings will need to be loosened to keep stable as this is stress on MCH, So carefull of too high FSBT too. Try to keep under 1.504v


I got old rev Ballistix and new rev ones. They're tracers too. I'm sure, ones 16X64, double sided and the other is 8X128, single sided.

Tried all the settings you've suggested and more. I'm running stock now, but I donno about 500, at 500 is somewhat stable, but nuts to 500, 503 was the last I tried and at 2hrs of orthos + general use + a screen shot at the end, it BSODd. so 500 might get me on track. But this thing posts up to 570!, I think my little E6300 is a trooper and I wanna get every clock out of it I can!

Funny thing is when I set the FSB:mem speed at anything other then auto, it fails to post. Always.

bah, I'll deal with this when I get it into a proper case :p.

[Grnfinger]

Try this for a start
You might need to adjust a few settings, vcore and NB
lmk

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : AUTO
- Ratio CMOS Setting : 9
FSB Frequency : 445
FSB Strap to North Bridge : 333
PCI-E Frequency: 100
DRAM Frequency: DDR2- 890
DRAM Command Rate : 2T
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 15
RAS# to RAS# Delay : 3
Row Refresh Cycle Time : 50
Write Recovery Time : 6
Read to Precharge Time : 3

Read to Write Delay (S/D) : Auto
Write to Read Delay (S) : Auto
Write to Read Delay (D) : Auto
Read to Read Delay (S) : Auto
Read to Read Delay (D) : Auto
Write to Write Delay (S) : Auto
Write to Write Delay (D) : Auto
DRAM Static Read Control: Disabled
( enabled will give better bandwidth but might create instability in ram)
Ai Clock Twister : Strong
Transaction Booster : Disabled
Relax level: 0


CPU Voltage : 1.35 ( you may need to adjust this)
CPU PLL Voltage : AUTO
North Bridge Voltage : 1.49
DRAM Voltage : 2.00
FSB Termination Voltage : 1.40
South Bridge Voltage : 1.050
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-REFF
SB 1.5V Voltage : 1.5

[Griff]

I read all this with envy, i would be happy if mine just posted, looking on ebay now for some cheep Geil ddr2 to try and get a post, not confident as the other 99 ideas i tried via google all gave nada in return, This board with a 4ghz E8400 and a GX2 would make an ideal gaming rig imho...:shrug:

[wreckwriter]

Try this for a start
You might need to adjust a few settings, vcore and NB
lmk

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : AUTO
- Ratio CMOS Setting : 9
FSB Frequency : 445
FSB Strap to North Bridge : 333
PCI-E Frequency: 100
DRAM Frequency: DDR2- 890
DRAM Command Rate : 2T
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 15
RAS# to RAS# Delay : 3
Row Refresh Cycle Time : 50
Write Recovery Time : 6
Read to Precharge Time : 3

Read to Write Delay (S/D) : Auto
Write to Read Delay (S) : Auto
Write to Read Delay (D) : Auto
Read to Read Delay (S) : Auto
Read to Read Delay (D) : Auto
Write to Write Delay (S) : Auto
Write to Write Delay (D) : Auto
DRAM Static Read Control: Disabled
( enabled will give better bandwidth but might create instability in ram)
Ai Clock Twister : Strong
Transaction Booster : Disabled
Relax level: 0


CPU Voltage : 1.35 ( you may need to adjust this)
CPU PLL Voltage : AUTO
North Bridge Voltage : 1.49
DRAM Voltage : 2.00
FSB Termination Voltage : 1.40
South Bridge Voltage : 1.050
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-REFF
SB 1.5V Voltage : 1.5

Thank you! Will give it a shot.

[MrHydes]

greetings
i have 0907 what bios do you recomend...
really usefull this thread thanks guys :clap:

[Grnfinger]

greetings
i have 0907 what bios do you recomend...
really usefull this thread thanks guys :clap:

bios 1004 is the best so far imho

[wreckwriter]

Thank you! Will give it a shot.

A couple of the settings couldn't be matched, bios version differences I guess. These:
DRAM Frequency- DDR2 890 not available, had to use 891
ROW REFRESH CYCLE TIME- 50 not available, highest was 42

Anyway, no post. Tried CPU voltages of 1.3125. 1.3750, 1.2500, 1.4375. No post on all.

[wreckwriter]

bios 1004 is the best so far imho

Heard some reports of 1004 not saving settings. I assume you haven't had this problem? Can 1004 be reverted to 0907?

[MrHydes]

bios 1004 is the best so far imho

hmm not sure if i should change because have this so stable and i'm so close of scoring 20k in 30Dmark06...

i'm going to wait first the score then i change thanks

by the way what ate the highlights int bios @1004?

[ElEctric_EyE]

BIOS 1004 kicks ass even over the Rampage BIOS. I could get up to 3.77GHz stable (470x8) on 0903. Now up to 3.97GHz (440x9) 400 strap. Rampage BIOS is RAM friendly though, I was able to get the RAM at 1253MHz at the cost of cpu speed, I could only get 3.6GHz stable. I rec BIOS 1004:up:

EDIT: 0907, not 0903.

[Grnfinger]

A couple of the settings couldn't be matched, bios version differences I guess. These:
DRAM Frequency- DDR2 890 not available, had to use 891
ROW REFRESH CYCLE TIME- 50 not available, highest was 42

Anyway, no post. Tried CPU voltages of 1.3125. 1.3750, 1.2500, 1.4375. No post on all.

what does the lcd poster report?
det ram?
and what bios are you running?

[wreckwriter]

what does the lcd poster report?
det ram?
and what bios are you running?

It never changes from "en setup". Bios 0907.

[Nuckin_Futs]

O.K. since this was predominately a RAM sub timing tread for MAXIMUS, maybe some of you can help here or at least give commnt. These are my current settings for tested stable profile but now back on BETA BIOS v0903 and still 480x8 w/ E6750 and Ballistix Tracers as in sig, old batch
NOTE where [] is as set in CMOS and = ___ is as reported

FSB Strap to North Bridge: [Auto] (no manual of anything works, but gives me the spd I need)
PCI-E Frequency: [110]
DRAM Frequency: [DDR2-1153]
DRAM Command Rate: [2T]
DRAM Timing Control: [Manual] (have to use Auto for 1:1 or it wonnt POST)
Primary Info : 5-5-5-15-3-42-6-3
CAS# Latancy: [5]
RAS# to CAS# Delay: [5]
RAS# Precharge: [5]
RAS# Active Time: [15]
RAS# to RAS# Delay: [Auto] = 3
Row Refresh Cycle Time: [Auto] = 42
Write Recovery time: [Auto] = 6
Read to Precharge Time: [Auto] = 3

Secondary Info : 8-3-5-4-6-4-6
Read to Write Delay(S/D): [Auto] = 8
Write to Read Delay(S): [Auto] = 3
Write to Read Delay(D): [Auto] = 5
REad to Read Delay(S): [Auto] = 4
Read to Read Delay(D): [Auto] = 6
Write to write Delay(S): [Auto] = 4
Write to Write delay(D): [Auto] = 6
DRAM Static Read Control: [Enabled]
Ai Clock Twister: [Moderate]
Transaction Booster: [Auto]
RElax Level [N/A]

I'm 1st wanting to know if they are already to tight in the sub settings as used by Auto or if not, what areas to tighten or loosen for stability and smoothness, not scores. I dont mind better performance just so long that it doesnt cost stability.

[Grnfinger]

Heard some reports of 1004 not saving settings. I assume you haven't had this problem? Can 1004 be reverted to 0907?

I have never had an issue with 1004 and it can be reverted using Asus Update or the proper version of AFUDOS




hmm not sure if i should change because have this so stable and i'm so close of scoring 20k in 30Dmark06...

i'm going to wait first the score then i change thanks

by the way what ate the highlights int bios @1004?


1004 offers a higher trfc options so 4GB users will benifit and its very 45nm friendly

[MrHydes]

I have never had an issue with 1004 and it can be reverted using Asus Update or the proper version of AFUDOS
1004 offers a higher trfc options so 4GB users will benifit and its very 45nm friendly

now it's too late 'cause i've dropped a 2Gb module :shrug:

[Grnfinger]

what GPU did you run b4 the 9800GX2?

[Zucker2k]

It never changes from "en setup". Bios 0907.

What fsb are you running at?

vcore?

VNB?

[Grnfinger]

What fsb are you running at?

vcore?

VNB?

He's shooting for 4.0GHz
445x9
NB 1.49
vCore 1.35

[trt740]

Try this for a start
You might need to adjust a few settings, vcore and NB
lmk

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : AUTO
- Ratio CMOS Setting : 9
FSB Frequency : 445
FSB Strap to North Bridge : 333
PCI-E Frequency: 100
DRAM Frequency: DDR2- 890
DRAM Command Rate : 2T
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 15
RAS# to RAS# Delay : 3
Row Refresh Cycle Time : 50
Write Recovery Time : 6
Read to Precharge Time : 3

Read to Write Delay (S/D) : Auto
Write to Read Delay (S) : Auto
Write to Read Delay (D) : Auto
Read to Read Delay (S) : Auto
Read to Read Delay (D) : Auto
Write to Write Delay (S) : Auto
Write to Write Delay (D) : Auto
DRAM Static Read Control: Disabled
( enabled will give better bandwidth but might create instability in ram)
Ai Clock Twister : Strong
Transaction Booster : Disabled
Relax level: 0


CPU Voltage : 1.35 ( you may need to adjust this)
CPU PLL Voltage : AUTO
North Bridge Voltage : 1.49
DRAM Voltage : 2.00
FSB Termination Voltage : 1.40
South Bridge Voltage : 1.050
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-REFF
SB 1.5V Voltage : 1.5

This chip did 4.0ghz in my P5K-e 8x500 so thats why I was asking for your current bios settings Here are my current setting at 4.2ghz

x9 multi
FSB = 468
FSB Strap = 400 Which gives me DDR2 1247
PCI-E = 110
Ram timings= 5 5-5-15
DRAM static read is Disabled
Ai Clock Twister is Strong
Trans Booster is Enabled
Boost Level is 0

NB (Set at) 1.57
Ram V's (Set at) 2.12
LLC = Enabled
DDR2 Controller Ref = DDR2 Ref




a friend gave me these and they are good for 9x463 I just wanted to get a 500 FSB was wondering if your setting could help.


I just tried you setting and they work for 4.0ghz np.

[Grnfinger]

This is running a E8400

from memory I think it was.....

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 9
FSB Frequency : 500
FSB Strap to North Bridge : 333
PCI-E Frequency: 110
DRAM Frequency: DDR2-1200
DRAM Command Rate : 2T
DRAM Timing Control: Manual
CAS# Latency : 5
RAS# to CAS# Delay : 5
RAS# Precharge : 5
RAS# ActivateTime : 18
RAS# to RAS# Delay : 3
Row Refresh Cycle Time : 45
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
DRAM Static Read Control: Disabled
Ai Clock Twister : moderate
Transaction Booster : Disabled
Relax level: 0

CPU Voltage : 1.475
CPU PLL Voltage : AUTO
North Bridge Voltage : 1.53
DRAM Voltage : 2.12
FSB Termination Voltage : 1.40
South Bridge Voltage : 1.050
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-REFF
SB 1.5V Voltage : 1.5


hope it helps

[Eastcoasthandle]

If you are using g. skill ram this is a good beginners guide
here (http://www.gskill.us/166.pdf)

[MrHydes]

someone can tell me what temps you have in NB, SB, FSB