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

[tiesum]

edit

[xgman]

2.20 on your RAM might be a little too high (The board overvolts).
I would try 2.12 or 2.14

I've been running 4x1gb of ballistix at 2.4v set in bios with fan over the ram. No detram messages. Somehow I think that 4gb may need a bit more voltage set in bios than 2gb does?

[Durkadurka]

Yeah I dont think the high volt would cause DETRAM, but many people have reported killing their Ballistix with high voltage on this MB.

I run 4 sticks at 2.12v set in BIOS for 2.22v measured, and it's stable as far as I can tell.

[icecpu]

Can someone help me get pass 455 fsb stable.
I getting the massage " Display Driver stopped working and has recover" when I plays game . At 455 fsb I has no problem. I want 465 fsb at least but game freeze and getting the display driver message

I had tried everything but same result, maybe I'm missing something? here is my current stable setting


Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 9
FSB Frequency : 455
FSB Strap to North Bridge : 333
PCI-E Frequency: 105
DRAM Frequency: DDR2-1093
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 : 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: Disable
Ai Clock Twister : Auto
Transaction Booster : disabled
Relax level: 1

CPU Voltage : 1.393
CPU PLL Voltage : AUTO
North Bridge Voltage : 1.61
DRAM Voltage : 2.20
FSB Termination Voltage : 1.54
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

[Ric2L]

I am going to guess you arent getting any post beeps either :-) I would test your power supply before you test the mobo.. the motherboard "was" working as intended. changing out from the 4pin to the 8pin wouldnt do anything except give you more reliable and stable voltages to the cpu. If there is a retailer near you I would have them take your powersupply and test it see if you are getting 12v +- maximum of .3 volts outta it. if its showing like 11.6v or under I would replace it.

Also I know these situations are very rare and I almost never use one but I always ask.. you didnt shock your board did you ? ESD does still kill computer parts nowadays .. its hard to do but "can" happen.

If you bought your board from a local retailer I would just take it with you and test your psu and if your psu tests fine then exchange the board. if you bought it online I would test the PSU before RMAing to asus or wherever you bought it from.

Hope this helps some. Not posting anything can be a series of things from bad ram to a bad harddrive.

When trouble shooting always make sure you have 1 stick of ram in and you dont have anything else connected to the motherboard besides your vid card and CPU. Then swap out sticks of ram till you post if you dont post you know its not your ram and its either the CPU board or PSU... and if you are like most of us computer geeks you have a el cheapo celeron that works laying around that you can pop in. then you can determine if the CPU is dead or not.
Now you ahve narrowed it down to teh board or PSU. So then you have a little powersupply tester on hand to check your voltages. Or if you have a voltmeter you can use one of those too just need to check the power and ground. You get my drift I wont write anymore of a book for ya :-)


Also take out the cmos battery for 30minutes to an hour.

I hooked up another power supply that I had lying around (only 300w) to the 12v mobo connector to see if it would light up the led's for cpu. comp came on all fans spun up but no cpu led. however the comp did not try to restart itself over & over like before, so I unhooked the 12v cable from 300w ps restarted, had the same thing, all fans would come on and stay on until I manually shut it down. Then I hooked the the 12v cable from my 610w that was still in the case back up & computer started right up!!! all leds were lit and green even the one for the cpu. So I hooked the monitor & keyboard back up to see if windows would run & it came up with no problems!!! restarted again, went into bios, set ram timings & voltages, set boot sequence to boot from dvdrom saved settings, put memtest86+ cd in, restarted, memtes started to run, got to 26% on test 3 with 0 errors, & it hung there for 10 mins. had no keyboard functions or anything, so I removed cd, hit reset, comp came back up got into windows decided to try memtest again, shut comp down & when I restarted, nothing???, same as before no cpu led, comp just kept trying to restart hung on CPU INIT!!!!!!

Think its time to RMA???

when I was in bios went to hardware monitor & it showed 11.98v @ the 12v connector?

I'm stumped, think maybe something is shorting the board, but I've unhooked everything & tried them 1 at a time, same prob over & over.

any more ideas??

I keep you posted as to progress, if I get any further.

Rick

[xgman]

Yeah I dont think the high volt would cause DETRAM, but many people have reported killing their Ballistix with high voltage on this MB.

I run 4 sticks at 2.12v set in BIOS for 2.22v measured, and it's stable as far as I can tell.

Has anyone actually done a multimeter vdimm test on this board to see if the board is really overvolting ram as reported in bios?

[Robin77]

I would remove and re seat them with after market cooling. The heat pipe leading to the SB actually makes your SB chip run hotter than it would due to the extra heat the NB is send down the pipe. I don't even have anything on my SB since I removed the stock and it lowered the temps 8 deg not being connected to the NB.

Also my NB ran 52-55 stock and I couldn't clock the CPU past 3.2 since I couldn't run stable voltage, now that I water cool my NB is runs an idle 29 and loaded 44 roughly.

EDIT: if my NB ran idle at 66 I would have RMA'd it

Why? You'd only get to hear that this temps within the official max loaded temp of 92 C (for proof just search Intel thermal design spec from X38: http://download.intel.com/design/chi.../31761201.pdf).

[0ut0fstep]

So im looking at everyone's cpu-z CPU voltage to the board setting they have....

Why am I getting such a wide spread difference. for ex: when I have cpu voltage set to 1.36 I get 1.32 in cpu-z when I have it set to 1.5 I get 1.44 its always a difference of .06.... I know I can compensate for it but is anyone else having the same issue?

[[timko]]

So im looking at everyone's cpu-z CPU voltage to the board setting they have....

Why am I getting such a wide spread difference. for ex: when I have cpu voltage set to 1.36 I get 1.32 in cpu-z when I have it set to 1.5 I get 1.44 its always a difference of .06.... I know I can compensate for it but is anyone else having the same issue?

On mine if I have "Loadline calibration" enabled the difference between BIOS setting and CPU loaded CPUz reading is about 0.01v. Disable and "Loadline calibration" and the difference is just under 0.1v!

[Grnfinger]

Hi Guys,

I'm running my E8400 at 4050 MHz now and it's almost stable. The problem is that about one in five times the system hangs at DET RAM. When it does boot to windows there is no problem and it's orthos and OCCT-stable for 12 hours. Can u guys help me with the last bit of tweaking? I'm running this now:

Ai 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 : 333
PCI-E Frequency: 100
DRAM Frequency: DDR2-1081
DRAM Command Rate : 2T
DRAM Timing Control: Auto
CAS# Latency :
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: Disabled
Ai Clock Twister : Auto
Transaction Booster : Disabled
Relax Lvl: 1

CPU Voltage : 1.375
CPU PLL Voltage : 1.50
North Bridge Voltage : 1.55
DRAM Voltage : 2.20
FSB Termination Voltage : 1.22
South Bridge Voltage : 1.05
Loadline Calibration : Enabled
CPU GTL Reference : 0.63
North Bridge GTL Reference : 0.67
DDR2 Channel A REF Voltage : Auto
DDR2 Channel B REF Voltage : Auto
DDR2 Controller REF Voltage : Auto
SB 1.5V Voltage : 1.50

NB LED Selection : FSBT Volt
SB LED Selection : SB 1.5 Volt
CPU LED Selection : PLL VOlt
Voltiminder LED : Enabled

CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled

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

I had the random det ram hang alot, once I set my ram sub timming it went away, I would try that for starts.
Also your FSBT is kinda low, try 1.40, and you have alot of volts going into your NB for only 2GB of ram is ther a reason for that?
I would think 1.49 for NB should be ok if it will run stable

Can someone help me get pass 455 fsb stable.
I getting the massage " Display Driver stopped working and has recover" when I plays game . At 455 fsb I has no problem. I want 465 fsb at least but game freeze and getting the display driver message

I had tried everything but same result, maybe I'm missing something?

This is my 4.3GHz setting its 15hours prime stable, maybe it will help you.

Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 9
FSB Frequency : 478
FSB Strap to North Bridge : 333
PCI-E Frequency: 110
DRAM Frequency: DDR2-1147
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 : 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
DRAM Static Read Control: Disabled
Ai Clock Twister : Strong
Transaction Booster : Disabled
RELAX LEVEL:0

CPU Voltage : 1.38
CPU PLL Voltage : AUTO
North Bridge Voltage : 1.49
DRAM Voltage : 2.16
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 : DDR2
DDR2 Channel B REF Voltage : DDR2
DDR2 Controller REF Voltage : DDR2-REFF
SB 1.5V Voltage : 1.5

[cuke2u]

Hi, 1004 http://rapidshare.com/files/97294391...-1004.rom.html anyone care to risk it and give it a try?
Chris

[Grnfinger]

I'm game

[xgman]

I hope it fixes the problem with the 9650's and 1001-1003 bioses.

[Grnfinger]

So far it seems that 1004 is a MAJOR improvement for Wolfdales.
It booted right up with my 907 settings with no iisues unlike 1003, gone is the slow sluggish feel of 1003.
Row Refresh Cycle Time is changed abit I no longer have a 42 option.
Ram is liking this bios alot.



Going to run a few benches and give it a run on Fall of Liberty ans see how it performs.

[iadstudio]

So far it seems that 1004 is a MAJOR improvement for Wolfdales.

1004? Where did you find that?

Edit:

[xgman]

So far it seems that 1004 is a MAJOR improvement for Wolfdales.
It booted right up with my 907 settings with no iisues unlike 1003, gone is the slow sluggish feel of 1003.
Row Refresh Cycle Time is changed abit I no longer have a 42 option.
Ram is liking this bios alot.


Going to run a few benches and give it a run on Fall of Liberty ans see how it performs.

Sounds good, I'll try it tonight.

[xgman]

1004? Where did you find that?

uh, look 4 posts up from yours . . . .

[theonlybabyface]

So far it seems that 1004 is a MAJOR improvement for Wolfdales.
It booted right up with my 907 settings with no iisues unlike 1003, gone is the slow sluggish feel of 1003.
Row Refresh Cycle Time is changed abit I no longer have a 42 option.
Ram is liking this bios alot.

Interesting. What Row Refresh Cycle Time's are available and can you select them in single increments?

[Grnfinger]

So far I am very pleased with this new bios
A big thanks to cuke2u

Interesting. What Row Refresh Cycle Time's are available and can you select them in single increments?

There is auto/20/25/30/35/40/45/50/55/60/65/70/80/85/105/132

[theonlybabyface]

Thanks...so same as 1003. Too bad as being able to select in single increments would be just perfect.

[eSp!s0]

no bugs or problems found?

[Grnfinger]

no bugs or problems found?

So far its 100%, trying to find something I dont like and I cant.
going to test dividers in a few mins when 3dmark is done

[Darkstormz]

ne1 got a SLIC version of this 1004 bios ?

[eSp!s0]

So far its 100%, trying to find something I dont like and I cant.
going to test dividers in a few mins when 3dmark is done

Yes, do that

Just flashed bios and 2x2GB Redlines are running the 1000Mh now because of TRFC (set to 55), TRFC was the big problem of the board/ram.

[ericab]

flashed the 1004 bios an hour ago, and now am back to 907.

1004 didnt work at all for me.
after the successful flash, i rebooted, and reloaded my saved profile. all the options were skewed; so i went through every menu, and set it back to where they should be. saved it, rebooted, and everytime, no matter what, the lcd poster said, CMOS error. went back into bios finally, and loaded setup defaults, rebooted, and still cmos error. i could tell the bios had updated properly, because i had the extra tRFC options........

.......bottom line: 1004 doesnt work for me.

1003 did buuutttttt....

still stickin' with 907 for a while :/

cmon asus! give us some love.