Quote:
Originally Posted by Roger_D25
I put this link here.
http://www.xtremesystems.org/forums/...2&postcount=22
My own
http://www.xtremesystems.org/forums/...1&postcount=23
It explains alot.
I prefer "the cold method" than the "warm" one.
Printable View
Quote:
Originally Posted by Roger_D25
I put this link here.
http://www.xtremesystems.org/forums/...2&postcount=22
My own
http://www.xtremesystems.org/forums/...1&postcount=23
It explains alot.
I prefer "the cold method" than the "warm" one.
Will these boards do 500fsb easily??? My MIIF is having trouble doing so...
With Duals easily. With Quads possible if you know what you are doing and have good cooling.Quote:
Originally Posted by 529th
It will void your warranty. My excuse for taking everything from the board is bad thermal paste and bad connection with the components. Than hope that they will except that if you need to RMA the board.Quote:
Originally Posted by Roger_D25
Are they having trouble like the MIIF board? Or would you say it's possible as it's possible on the Gigabyte UD3 boards?Quote:
Originally Posted by A-Grey
I let Zucker2k answer that. He is the one that can tell you that.Quote:
Originally Posted by 529th
I see you were running Prime95 & UT 2004 at the same time on a quad core. What was your FSB? 558?Quote:
Originally Posted by A-Grey
It'll void warranty I believe.Quote:
Originally Posted by Roger_D25
All you need to remove it is a sharp wood chisel and a hammer. Lightly tap the chisel around the glue to break the bond and the heat pipe should come off. Getting it off the southbridge sink is easy. The chisel is more needed for the NB sink, so you dont damage the sink when removing the stubborn bastard of a heat pipe :D
Thanks for all the replies in regards to the removal of SB/NB heatpipe, doesn't that sound that hard at all. I assumed the heatpipe was soldered onto the heatsinks not glued, in this case I'm glad its not soldered! Thanks A-Grey for your thoughts about the warranty, they probably take it on a case by case basis. I'll report back if/when I try removing my heatpipe and if I see any temp changes. I was also thinking about removing the ROG logo on the SB, it looks like removing that might help a bit with temps (but the difference might be negligable)?
neo rtr - Thanks for posting those links, very interesting! I wish I read that back when I first got my board because the first thing I did was completely remove the heatpipe assembly to replace the thermal paste and make sure everything was seated properly. Just like you noticed my stock thermal paste was rock solid and made very poor contact with the heatsinks so I'm glad it was the first thing I did. I think its a good practice to do this with pretty much any new motherboard (although some seem to be better than others).
I received some information today from my contacts at ASUS. They will verify the problems internally that we found with BIOS 0802.
Yes, I think they do that. A lot depends why you have to RMA the board. When it's because you broke something on the board trying to remove the heatsinks you'll definitely void your warranty.Quote:
Originally Posted by Roger_D25
Removing the ROG logo on the SB might help a bit if you've got good air flow in your case. The plastic cover keeps the air flow from the heatsink. I don't expect huge temperature difference but every degree lower is a gain.
GregGun got his board last week. He told me that it didnt have thermal paste on the SB and NB.Quote:
Originally Posted by A-Grey
Instead it had the same thermal pad as the moffsets.
If we can confirm that as well with another modo will be great.
So i would think that, ASUS knows, what people are doing (removing the heatsink) and took a step to the right direction making it easy for both them selfs and the users.
I completely forgot there was a logo on there! That was the first piece of garbage I removed when I got my board. All it does is trap heat. Nonsense I tell you.Quote:
Originally Posted by Roger_D25
Quote:
Originally Posted by neo_rtr
Thats true. The new rampage i bought, which is made at august, has under nb and sb just a fine thermal pad just like under the mosfets. So removing the heatsink was a piece of cake.
It's easier for them to. The heatsinks are going to make better contact with the thermal pads. It's a win win situation.Quote:
Originally Posted by greg.m
Zucker2k can you tell me what core you have trouble with. Sometimes I've got trouble passing Prime95 Small FFT's. Core #2 fails sometimes in Small FFT's.
I wonder if that is because of the voltage fluctuations from the vtt or if there is something wrong again with the CPU GTL's.
If voltage is fluctuating you need to isolate the problem. Make sure the PSU is able to handle the load at that voltage. Could be the VR on your board is failing too. I'm pretty sure mine isn't nearly as competent now as it used to be. If core is failing also raise the PL + 1 and see if that helps.
You think one core failing at high overclock is an issue! HAH! I'm getting a headache trying to find stable DRAM timing values on this DFI board heh. Playing with CLK/DQ drive strength at the moment because I'm getting instabilities few hours in. Also playing with DRAM DLL skew models, apparently DFI don't have the models for DDR2 listed anywhere so i'm playing guess who!
I already have trouble getting it back stable at FSB 465 with this BIOS. The 12V never goes under 11.98V on full system load.Quote:
Originally Posted by mikeyakame
Heya all.
First post but long time lurker.
I'm having a problem which I'm draging from my Maximus Formula MB and now it is present on Rampage too. I have 3 HDs (2xSeagate 320 in RAID0 + 500GB WD) and Pioneer DVR-216 SATA DVD Burner all connected to ICH9R. Seagates are on ports 0 and 1, WD is on 2, Pioneer is on 5. Vista x64 installs fine but after some time raid fails or WD is missing from drive list. I can make it fail almost instantly after clean install if I watch few movies from DVD. So I narowed it down to SATA DVD. I've used old IDE Pioneer DVD on JMicron and could not replicate the error.
Since the first time I've encountered this problem I've changed all components including MB, DVD, and few BIOS versions. Only same component are those two Seagate disks. Are they a problem? Will changing them with differend brand/model HDs solve it? Or is RAID+nonRAID+DVD on ICH9R mission impossible?
Well...here are my bios settings with which i can pass 5 passes with half memory stressed succesfully and that with my new(replaced) QX9650 and the new Rampage board:
Ai Overclock Tuner : [Manual]
CPU Ratio Setting : [8]
FSB Strap to North Bridge : [AUTO]
FSB Frequency : [475]
PCI-E Frequency: [105]
DRAM Frequency: [DDR2-1141]
DRAM Command Rate : [2N]
Dram CLK Skew on Channel A : [AUtO]
Dram CLK Skew on Channel B : [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]
Ai Transaction Booster : [Manual]
Common Performance Level : [08]
CPU Voltage : [1.43]
CPU PLL Voltage : [1.50v]
North Bridge Voltage : [1.51v]
DRAM Voltage : [2.12]
FSB Termination Voltage : [1.44v] 1.36v real
South Bridge Voltage : [AUTO]
SB 1.5v Voltage : [AUTO]
Loadline Calibration : [Disabled]
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]
NB LED Selection : [NB Volt]
SB LED Selection : [SB Volt]
CPU LED Selection : [CPU Volt]
Voltiminder LED : [Up to you]
CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled
CPU Clock Skew : [200]
NB Clock Skew : [100]
During the burn test my vcore was exactly@ 1.32
Before, i had fsb@1.42, cpu nb skew and cpu nb gtl were untouched and i couldnt pass the burn test. Now i will try to fine tune everything and see which the lower volts i can run 475fsb @ 3800mhz.
Rampage Formula BIOS 802, Intel Q9550 C1 @ 4.01Ghz, Mushkin Ascent 4x2Gb XP2-8500 (996619) cooled with a ZEROThrem FZ120 in a Antec P180 case. I didn`t had much time to stress it to the limit. I hope I have some time for some IntelBurnTest tomorrow.
Idle - 43 grade
Fulload (Prime95) - 65-68grade
CPU-Z ValidationCode:ASUS Rampage Formula BIOS 0802 Template
*Extreme Tweaker*
Ai Overclock Tuner [Manual]
CPU Ratio Setting [08.5]
FSB Strap to North Bridge [333Mhz]
FSB Frequency [470]
PCIE Frequency [100]
DRAM Frequency [DDR2-941MHz]
DRAM Command Rate [2N]
DRAM CMD Skew on Channal A [Greyed Out]
DRAM CMD Skew on Channal B [Greyed Out]
DRAM CLK Skew on Channal A [Advance 300ps]
DRAM CLK Skew on Channal B [Advance 300ps]
DRAM Timing Control [Manual]
1st Information
CAS# Latency [5]
RAS# to CAS# Delay [5]
RAS# PRE Time [5]
RAS# ACT Time [15]
RAS# to RAS# Delay [3]
REF Cycle Time [50]
WRITE Recovery Time [6]
READ to PRE Time [3]
2nd Information
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 Dealy (D) [6]
3rd Information
WRITE to PRE Delay [14]
READ to PRE Delay [5]
PRE to PRE Delay [1]
ALL PRE to ACT Delay [6]
ALL PRE to REF Delay [6]
DRAM Static Read Control [Enabled]
Ai Clock Twister [Light]
Ai Transation Booster [Manual]
Common Performance Booster [8]
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 CHA PH6 [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]
Pull-In of CHB PH6 [Disabled]
CPU Voltage [1.3000] real 1.288
CPU PLL Voltage [1.50] real 1.552
North Bridge Voltage [1.33] real 1.2
DRAM Voltage [2.00] real 2.0
FSB Termination Voltage [1.30] real 1.32
South Bridge Voltage [1.05] real 1.056
SB 1,5V Voltage [1.50] real 1.502
Loadline Calibration [Enabled]
CPU GTL Voltage Reference [0.63x]
NB GTL Voltage Reference [0.67x]
DRAM Controller Voltage REF [AUTO]
DRAM Channel A Voltage REF [AUTO]
DRAM Channel B Voltage REF [AUTO]
CPU LED Selection [CPU Voltage]
NB LED Selection [North Bridge Voltage]
SB LED Selection [South Bridge Voltage]
Voltiminder LED [Enabled]
CPU Spread Spectrum [Disabled]
PCIE Spred Spectrum [Disabled]
CPU Clock Skew [Delay 100ps]
NB Clock Skew [Normal]
*Advanced settings*
CPU Ratio Setting [08.5]
C1E Support [Disabled]
CPU TM Function [AUTO]
Vanderpool Technology [Enabled]
Execute Disable Bit [Enabled]
Max CPUID Value Limit [Disabled]
Intel(R) SpeedStep (TM) Tech. [Disabled]
No mate, it's FSB 465MHz with the memory at 1117MHz like it says in my sig.Quote:
Originally Posted by 529th
I think I am as tweaked as I can get with this mobo and cpu with 8GB of RAM. I have it stable with the settings in my sig and I have the memory set to PL 7. I took out one of the X2 video cards and it didn't make any difference. I am satisfied with this oc on a quad running 8GB.
Are you the same person who posted this settings on the ASUS Rampage Formula forum?Quote:
Originally Posted by xr1140
If you are the same person, well I think that I did buy garbage.
Quote:
Originally Posted by A-Grey
yes, I am the same. Thank you, i know you and mikeyakame deserve some credit for this bios release. :up:
How did you get it stable with such a low voltage with 8 giga and LLC enabled?Quote:
Originally Posted by xr1140
Are you sure that it's 1.2V real for NB Voltage? Seems like a huge difference from 1.33V in the BIOS to 1.2V real.
NB voltage is usualy undervolting for 0.01-0.03V, and FSB VTT is usualy undervolting for 0.08-0.09V, so that voltages are bit wierd unless you have compleatly special mobo made specialy for you :)Quote:
North Bridge Voltage [1.33] real 1.2
FSB Termination Voltage [1.30] real 1.32
Who has tested latest bios 0802 and how it works?
Read last 2 or 3 pages of thread and you have your answer. ;)Quote:
Originally Posted by OverDozeD
I finally figured it out what is going on with this BIOS.
The problem is the DRAM Clock Fine Delays. They can change after a reboot. What probably happens is that if you advance with 300ps and get a DRAM Fine Delay of 0T after a reboot something gets messed up and instead of advancing 300ps the DRAM Clock Fine Delays get delayed 300ps resulting in 14T.
This explains why Prime95 fails sometimes after a reboot.
Something else that I found is that it is necessary to have tREF in the BIOS that is calculated according to Intel specs.
With a closer tREF used that I should use for my memory speed I can run Prime95 + UT2004 almost an hour before I run into a General Protection Fault.
What I did is make some screen shots and send them to my contact at ASUS. I hope they can figure out what is going wrong.
DO you mean Intel or Jedec specs?Quote:
Originally Posted by A-Grey
Jedec is tREF = REFI[ns] / CK[ns].
Intel just sets register space according to JEDEC timing specs.
I've found that with tREF = 4171T for 1066mhz on my DFI board that it doesn't leak memory over time like the RF did. Well once I adjusted CLK and DQ drive strength it seems better. My memory use is idling about 10% lower than it was in Windows 7 with the RF.
By the way FELIX amended Memset with auto tREF timing value according to frequency and it works great! I don't know if its public yet, but if you want a copy let me know and i'll email you it ;)
Oh also the broken DRAM clock fine delay timings are the same since god knows what bios heh. That is the exact same problem I was complaining about to you a while back :D It changes on its own with no reason what so ever I have to keep advancing skew between resets. Thats the reason I asked Asus if they could have a read out of current skews in bios so we can tell when they are broken so we can adjust them heh. It's one thing being broken if they can't fix it, at least if we have a read out in bios we can know when to fix it without nuking our system or stability.
After i had installed my new cpu and mobo i noticed that for the first time vista could read the real cpu speed(at least for a while) with the rampage.
But... after a blue screen i had everything went back to the old days - wrong cpu speed is displayed again. Vista read only the
multiplier again while it counts fsb @ 333(default) always. Do you have any idea why does that happen?
Is it this mobos issue or windows fault?
I mean Jedec. And yes I would love to have a copy with auto tREF. I'll try it to see if it works better with tREF timing value according to the frequency of my memoryQuote:
Originally Posted by mikeyakame
I know you complained about the DRAM Clock Fine Delays but I used normal since BIOS 0408 and never had a problem with it until now with BIOS 0802. Normal doesn't work anymore for me because it's set at 6 and not at 3 that it was before. I can't even get it back to 3. I have to use 2 or 4.:shrug:
Now that I have to use a different value than Normal I see it to that they change sometimes after a reboot. If I use Advance 300ps and I get 0T and after a reboot the BIOS delays them with 300ps and I get 14T.:confused:
Well I think I don't have to explain what happens after a while with the stability.:shakes:
It goes to hell :DQuote:
Originally Posted by A-Grey
AI Clock Twister is at fault. That's as much as I know.
AI Clock Twister controls:
Channel A Cross Clocking Skews (fine clock delay/fine control delay/fine command delay)
Channel B Cross Clocking Skews (fine clock delay/fine control delay/fine command delay)
Channel A/B Common Clock Skews (common clock address strobe delay)
EDIT:
Side note get my Rampage back today. It's been tested for 4 hours by Asus and appears to be problem free. Lets hope this is the case. Might put it back in this weekend or whenever I get around to it!
Nice, did they fix something on your board?Quote:
Originally Posted by mikeyakame
It looks like the only way to have the DRAM Clock Fine Delays at the same value every system start or reboot is to use Auto for DRAM CLK Skew in BIOS 0802.
It s*cks but there is nothing we can do about it till ASUS fixes this in a new BIOS.:down:
Edit:
Correction they aren't always the same at auto but the difference isn't that big.
Fixed up the cpu contacts. Resoldered something around the clear rtc switch area of CMOS, some thing wasnt making good contact. They gave me a full cover southbridge heat sink too which I didn't know where to buy from. I'll attach pic shortly.Quote:
Originally Posted by A-Grey
http://au.asus.com/999/images/products/2594/2594_l.jpg
Same as that SB heatsink basically.
One hour Prime95+UT2004 stable with closer tREF value for my memory speed.
There is no doubt anymore that tREF should be set in the BIOS according to the memory speed.
In the second screen shot you can see UT2004 failed with the famous "General protection fault" while Prime95 is still running fine without errors.
This BIOS is excellent to see the importance of tREF and system stability if you know that with the same settings and tREF at default 3120T in the BIOS I can only run 10 to 15 minutes before I run in to a general protection fault.
How do you calculate the right tREF for a determined memory speed? Mine is currently at 590mhz - what would be the right tREF?Quote:
Originally Posted by A-Grey
Currently testing my system at 1:1, already reached 590, but still not optimized. My goal is 600 but I donīt know if my OCZ FLEX II 9200 will reach it or if the Rampage will allow it.
+1Quote:
Originally Posted by A-Grey
Is it generally available? If not, can someone please point me to a copy?
Not sure if it is working 100% yet. A-Grey reported it isn't. Hard to tell for me anymore. Current DFI board I'm using has tREF self tracking, so it sets it correctly for DDR2 speed.Quote:
Originally Posted by coo-coo-clocker
Formula for tREF is.
REF[T] = REFI[ns] / CK[ns]
where
REFI[ns] = Refresh Interval from SPD in nanoseconds, all performance dimms are 7.8us
7.8us * 1000ns = 7800ns
REFI[ns] = 7800
CK[ns] = Clock period in nanoseconds, 1000 divided by ddr2 io frequency, which is half the double data rate.
For 1066mhz
1000 / 533 = 1.86667ns
therefore
REF[T] = 7800 / 1.86667 = 4171T
Thats pretty much self explanatory ;)
The 802 Beta BIOS seems to mess up my overclocking .... badly
I can't go back to 701 as Asus update tells me to use DOS and I don't have it
Am I missing something ? with 701 I did 3.66 for my Q6600 with 1.525 and memory at 1100 2.12v with PL07 , now , it is not stable at all :(
What are the best configuration for Q6600 ? or how can I go back to 701 from Windows ?
You can't period. Only way to go back to older bios is through ms dos flashing tool AFUDOS and you have to boot from MSDOS floppy/flash drive to do that.Quote:
Originally Posted by minaelromany
You cant just dial in same settings when bios options are added. Clear CMOS, set CPU Clock Skew to 100 or 200ps. NB Clock Skew normal, and make setting adjustments. Bios to bios changes occur and you can't expect stable settings from one to the next to be the same. It doesn't work like that. Sometimes you are lucky, other times when major changes happen you arent.
Thank you very much for the replyQuote:
Originally Posted by mikeyakame
Can you tell me the settings you have for overclocking your CPU ?
I mean the exact settings and I can start from it and tweak them
I feel like a whole new experience of the Rampage is happening all over again and it was painfull at first but when everything was settled , I was very happy :)
just find out that this is kinda general asus bug, its also there on my brothers p5k pro...Quote:
Originally Posted by mikeyakame
[QUOTE=mikeyakame;3663860]You can't period. Only way to go back to older bios is through ms dos flashing tool AFUDOS and you have to boot from MSDOS floppy/flash drive to do that.
I used the Asus update tool to downgrade the bios.Just open it up and choose options in the drop down menu.Then click next, put a check mark in BIOS downgradable.Click next again.Now choose update bios from a file and click next.Then it will work.
With ASUS EZ Flash II that you can find in the BIOS under Tools you can always flash back to earlier BIOS versions. It's the most easiest way to flash your board safely. Do a Clear CMOS before you flash your board. The BIOS will give you a warning that it didn't find any settings after you did a Clear CMOS. Just hit F1 and enter BIOS setup to flash your board. After you flashed the board do a Clear CMOS again and don't load any overclock profiles that you stored from a previous BIOS. Loading overclock profiles from previous BIOSes screws up the settings. Put everything back manually.Quote:
Originally Posted by minaelromany
No, it's MemSet version 4.0 and auto tREF isn't available.:(Quote:
Originally Posted by coo-coo-clocker
Here is something interesting with the new rampage(shipped with bios 0401) and QX9650.
Now with LLC enabled i dont get blue screens under idle anymore!
Before, with the old mobo(shipped with bios 0219) whatever i was doing i couldnt fix that problem.
After that i have come to the conclusion that the first rampage was the problem and i think that it has to do with the mfrdate. The old one was one of the very first made rampages and i think that thatswhy it had some faults.
I know that A-Grey has the same problem and ithink that its a good reason to rma that mobo. Its something unexcusable, a new top mobo for which someone pays a lot to has such a problem:down:
Here is a scrnsht with my system @ idle for more than 8 hours without having any problem at all!:
Hi guys!
I am currently running a RF motherboard with a Q6600 @ 3.6Ghz.
It is stable at 450x8 1.41v.
The problem comes when I try to overclock my RAM. I own 2 kits of 2x1Gb G.Skill PC8500 with D9GMH inside. I bought them together, so pairing is not my problem. Also, I did tests with one kit each time, and I was able to run DDR2-1250 with 2.34v primestable.
When I plug all sticks in, I cant go ahead 1128mhz (No matter how much vDimm). I have been playing with skews, vNB, and PL, but nothing helps.
I wanted to reach 1200mhz. Where can I start playing? Any sugestion?
RGDS and thx!
NOTE: Sorry for my poor english, I'm Spanish
Is this with BIOS 0802 that you are using LLC?Quote:
Originally Posted by greg.m
I didn't try it with LLC enabled anymore since BIOS 0601. I don't really care that it doesn't work. For what I know it did work flawless with my Pentium D 840@4.2GHz on my board.
I should give it a try again with BIOS 0802. It seems that a lot of you guys are doing very well with LLC enabled and BIOS 0802. If that works now for me, well than ASUS did at least fix something that I've been asking for a long time. If it doesn't work it must be something else that makes my system crash with it enabled.
I hope they fix the DRAM Clock Skews in an other BIOS release and finally add tREF and perhaps do something about the CPU GTL Voltage Reference.
No its with 0701. I went back to see how it would work with the new machines. But really give it a look because it might me a mobo fault from the beginning. Im telling you that because ive seen a lot - construction - differencies between the old and the new.Quote:
Originally Posted by A-Grey
The changes that i have made to my system are new rampage and new qx9650 - i had the same before - thats all. Os is the same i had, vista 64. With my old rampage and qx9650 and with 0701 i had exactly the same problem as you.
By the way what about cpu gtl ref?
hi guys
im planning to get myself this board
does it fit xigmatek Achilles S1284C cpu cooler?
and another thing i couldnt find on the net is
is this board compatible with the "fusion block" found on maximus extreme?
sorry for my poor english ;)
Whats the motherboard revision ID? Screenshot the chipset ID tab in CPU-Z.Quote:
Originally Posted by greg.m
It's more than just a BSOD with the CPU idling. Don't know what is wrong with LLC on my board and like I said I don't really care if it works or not. I'm not going to RMA the board for that.Quote:
Originally Posted by greg.m
For the CPU GTL Voltage Reference, smaller increments and independent control and also smaller increments for FSB Termination Voltage.
Edit:
And of course keep out the General from messing with my system.:D
Vtt smaller increments would be much much appreciated. I've got 0.002 or 0.005v increments on this DFI board. It's magic.Quote:
Originally Posted by A-Grey
And when the vtt fluctuates with 0.02 volt and poor GTL settings there isn't much fun anymore.:shakes:Quote:
Originally Posted by mikeyakame
Neh its like beating yourself over the head with a rock for a headache, at first the headache goes away, then after a while the pain from the rock just makes the whole exercise pointless :)Quote:
Originally Posted by A-Grey
Quote:
Originally Posted by mikeyakame
I can take - later - some photos direct from the motherboard.
Here is a scrnsht:
You can read the revision on the board it's just under RAMPAGE FORMULA.Quote:
Originally Posted by greg.m
Mine is revision 1.0G, PCB made in CHINA.
You can see where it's made in the top left corner of the board.
Here comes some real stufffffQuote:
Originally Posted by A-Grey
Since you did ask it I will tell you.:DQuote:
Originally Posted by greg.m
I'm running into an old BIOS bug again with BIOS 0802. It's impossible to get it stable at FSB 466MHz with this BIOS. I'm using 1.34V in the BIOS (1.23v-1.25v real) for FSB Termination Voltage an CPU GTL 0.63X and NB GTL 0.67X. Like that it fails in Prime95 Large FFT's, no matter what NB or memory voltage I use. The only solution is one step higher FSB Termination Voltage 1.36V in the BIOS (1.25v-1.26v real). Problem fixed.:confused:
The problem is fixed for the Large FFT's but now I have problems with Small FFT's. The step higher FSB Termination Voltage seems to be to high for the CPU GTL Voltage Reference. Using the CPU GTL 0.62X doens't work it makes it complete unstable.
So, what can I do? :shrug:
Well... nothing, just hope that ASUS finally decide to implement independent CPU GTL Voltage Reference settings in the BIOS with usable multipliers.;)
Guys
i jes tested out this board
but my NB & SB are sky high...around 60'C ish on stock E8400 idle
and it would jump to 70'c ish if i push my proc to 4.0ghz (445x9)
at first i thot it was due to the contact point
but when i touched the chipset heatsink with my fingers
damn they were HOT~ ***almost burned my fingertips hot***
so that rules out the contact surface issue
any suggestion guys?
Lower your nb voltage, dont use Auto settings to start with. And get some damn air flow around your northbridge.Quote:
Originally Posted by dro
I was going to suggest the same thing but assumed the NB/SB voltage must have been checked after seeing high temps? With that said make sure to go into your BIOS and manually set the CPU PLL/NB/SB/VTT/and 1.5v SB. The "Auto" settings as mikeyakame mentioned already doesn't always "choose" the correct voltage for a given setting.
will try that out ;)
i have yet to put a fan on the chipset
but i did turn my table fan to blow directly to the system
hahaha
anyhow...being a new user to this 75 page thread
i know that its tough to remove the chipset heatsink from the NB
but will the thermal paste loosen up if i heat it up by stressing the chipset?
Quote:
Originally Posted by xr1140
Once I get my NB back under water, I'm going to have to try this new bios. Those NB voltages are too good to be true!?!? Is is because of the NB skew? or is that just your board being nice? :shrug:
Don't know mine came off extremely easily!Quote:
Originally Posted by dro
If you wriggle it around it should come off quite easily, if you need to apply a little bit of leverage under the outer lip of the heat sink with a "non-magnetic" flat head screwdriver, using the PCIE 16x slot and a bit of foam on top of it for leverage point.
will be working on it this coming weekend mikeyakame
thanks for the tip :)
i was thinking off replacing the whole board's cooling with thermalright heatsink
anybody tried it before?
do you guys think its worth it?
im still finding my way around the AMI bios
i have been playing around with phoenix bios on dfi too much lately :P
guys
my my pcprobe suddenly gives me this error :down:
it happened twice..
crazy readings **check out the Vdimm there*** :shrug:
Hi guys, long time ago that i checked this thread.
What brings me to a question, is it worth trying to get my OC higher with a newer bios or is it not worth the effort?
yeah it does it don't worry too much. Use everest readings. They don't show same ridiculous spikes that never happened :)Quote:
Originally Posted by dro
PC Probe has always done that. No idea why.
If you need to ask it probably isn't :)Quote:
Originally Posted by Earzz
Me personally I just like playing with new bios' heh.
It is worthing mate, i had problem with temps on NB, my mobo require quite a lot of voltage on NB for 450 fsb and the temps was quite high, if you want to be stable you need to chill the NB.Quote:
Originally Posted by dro
http://www.myrmidoni.com/_stuff_/sistem/sistem1.jpg
http://www.myrmidoni.com/_stuff_/sistem/sistem2.jpg
http://www.myrmidoni.com/_stuff_/sistem/sistem3.jpg
http://www.myrmidoni.com/_stuff_/sistem/sistem4.jpg
http://www.myrmidoni.com/_stuff_/sistem/sistem5.jpg
http://www.myrmidoni.com/_stuff_/sistem/sistem6.jpg
http://www.myrmidoni.com/_stuff_/sistem/sistem7.jpg
http://www.myrmidoni.com/_stuff_/sistem/sistem8.jpg
Somebody explain me something about this new 0802 bios, so basically if till now with old versions of bios i wasnt able to get a lower voltage on NB on high fsb probably with this new version using the values wroted under ill manage maybe to get lower voltage on NB?
CPU GTL Voltage Reference [0.63x]
NB GTL Voltage Reference [0.67x]
CPU Clock Skew [Delay 100ps]
NB Clock Skew [Normal]
You require less voltage supply to do the task within spec, its when its out of spec you compensate with higher supply.Quote:
Originally Posted by DaLiu
I received an answer on that question from ASUS. It isn't possible to change the vtt increments. It's probably like I thought hardware limitation.Quote:
Originally Posted by mikeyakame
hi there lads, im not an actual RF owner, but i do have its bios modded to my P5E :D bios is RF0410. ok, so straight to the point... i was just wondering how i could set tREF values in bios instead of having to set them with MemSet 3.4 in windows. any clues? i thought that extreme tweaker was the right setting to do the trick, but the other day i proved myself wrong... the strange thing is that when i had my SuperTalent (cheap ass) memory, i allways had tREF at 16383T while on "Stronger" extreme tweaker setting.. but now, with my g.skill set i find that i would only get 3120T when in OS. "strange" :( i thought, "but hey, dont give up!" and so i ended up here...
hope this helps:
Code:Extreme Tweaker
Ai Overclock Tuner : Manual
OC From CPU Level Up : AUTO
CPU Ratio Control : Manual
- Ratio CMOS Setting : 7
FSB Frequency : 458
FSB Strap to North Bridge : 333
PCI-E Frequency: 105
DRAM Frequency: DDR2-1100
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 : 50
Write Recovery Time : Auto
Read to Precharge Time : Auto
Read to Write Delay (S/D) : 9
Write to Read Delay (S) : 4
Write to Read Delay (D) : 6
Read to Read Delay (S) : 4
Read to Read Delay (D) : 6
Write to Write Delay (S) : 5
Write to Write Delay (D) : 7
Write to Pre Delay: 14
Read to Pre Delay: 5
Pre to Pre Delay: 1
All Pre to Act Delay 6
All Pre to Ref Delay: 6
DRAM Static Read Control: Enabled
Ai Clock Twister : Stronger
Transaction Booster : Manual
Common Performance Lvl: 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.375000
CPU PLL Voltage : 1.5
North Bridge Voltage : 1.51
DRAM Voltage : 2.0
FSB Termination Voltage : 1.36
South Bridge Voltage : 1.10
Loadline Calibration : Disabled
CPU GTL Reference : 0.67
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.55
CPU Spread Spectrum : Disabled
PCIE Spread Spectrum : Disabled
Advanced CPU Configuration
CPU Ratio Control : Manual
- Ratio CMOS Setting : 7
C1E Suppport : Disabled
CPU TM Function : Disabled
Vanderpool Technology : Disabled
Execute Disable Bit : Disabled
Max CPUID Value Limit : Disabled
many thanks in advance for any piece of advice anybody can provide :)
Hello,
I would like to know which is the best memory for my rampage. I have compatibility problems with my Mushkin Extreme pc2-8500 and I want to be sure the new one will work perfect.
I can buy for example the following memorys.
- 2x2GB Corsair Dominator pc2-8500 with airflow
- 2x2GB GSkill 8800 Pi
- 2x2GB GSkill 8500 Pi
- 2x2GB GSkill 8500 Pk
- 2x2GB OCZ Reaper pc2-8500
Thanks for your help
Sidious - I've used a few different kits of GSkill (both 2 x 1GB and 2 x 2GB) and they have all worked perfectly. My current RAM is significantly better than any other 4GB kits I've used, however out of the kits you posted above I'd go for either the 8800Pi or 8500Pi. Those kits are very inexpensive and clock very well, plus GSKill's warranty is stellar (since you live in Spain however I'm not sure how the warranty service would be)? After the GSkill kits I'd suggest the Corsair 8500's, that kit is very compatible and should work with no problems in your board. Last but not least would be the OCZ, its a great kit but out of the 4 your posted it would be my last choice. You probably know this already but make sure your motherboard is flashed with one of the newest BIOS versions (either 0701 or 0802). Good luck and keep us posted on what you get and how it works.
Well I'm finally running Prime95/3D stable at 450FSB x 9.0x which until 0802 was impossible for me to accomplish! After methodically going through many different setting combination's it turned out that "CPU Clock Skew" and "NB Clock Skew" made all the difference (A-Gray made this point a few pages back and I should have taken the advice, it would have saved me many hours of testing)! Although things are running stable I'm using far more voltage than is needed I think when compared to many of your results at similar settings. I'm hoping that I'll be able to lower my voltages with better tweaking, especially since I'm still running my GTL's at [Auto]? I will post my current settings later today (once I figure out how to post my settings like vodka3dg did above, using the scrollable table). In any case I'm very happy to finally be running stable at 450FSB x 9.0x, for a while I thought this was going to be impossible!
the dominators for sure. I use 8GB of them, and I can bring em all the way to 1250 with 2.00v 5-5-5-15. I have never had a problem with the 2x2GB 8500 stuff.Quote:
Originally Posted by Sidious
It depends on what revision you get. Some overclock very good others just don't.Quote:
Originally Posted by ChaosMinionX
I'm using the OCZ Reapers HPC PC2-8500 and they overclock good up to 1120MHz on this board with SPD Timings. They don't need 2.1V to run that fast on the ASUS Rampage Formula.
The G.Skill memory will do better on this board.:up:
It isn't possible to change tREF in the BIOS. You have to use MemSet for that. I hope Felix add auto tREF for the ASUS Rampage Formula X48 Chipset.Quote:
Originally Posted by vodka3dg
Mikeyakame already gave him some code to make it easier for him.:up:
ASUS should definitely add it to the BIOS that it sets tREF timing for the memory speed you are using.
Let's see what they have to say about it. They are going to run some tests to find out what should be done to fix the issues with BIOS 0802.
Thats always a start. Now if they'd only take a leaf out of DFIs book and display the current PS skew values it'd be awesome.Quote:
Originally Posted by A-Grey
DIMM1 Clock Fine Delay 5T
DIMM2 Clock Fine Delay 7T
DIMM3 Clock Fine Delay 5T
DIMM4 Clock Fine Delay 6T
They are my values at 415mhz fsb, cross clocking/common clock aggressive (aka strong) , I'm using a2/b2 for ram so dimm 2/4 which the values of clock fine delay are pretty much how I set them in bios.
Fine Clock Delay Adjust = 30PS (number of degrees times this adjust gives you final ps skew)
Dimm2 Clock Fine Delay = 22 degrees (660ps)
Dimm2 Control Fine Delay = 26 degrees (780ps)
Dimm4 Clock Fine Delay = 19 degrees (570ps)
Dimm4 Control Fine Delay = 22 degrees (660ps)
Dimm4(B2) is advanced 90ps from Dimm2(A2), the base values were around 740ps on clock fine delay for both a2/b2 which I've found using DLL Skew Model 1 for these sticks is the right model to use for delays. Also reducing DRAM CK (clock) and DQ (data) Drive Strength from CK=6, DQ=8 to CK=5, DQ=6 has magically fixed the random memory errors I was getting here and there when using higher drive strengths.
You know the nicest thing though.
Im using 8x415FSB at the moment, and Speedstep/C1E are both enabled and working as should, VID Special Add is amazing. 105.5% VID (1.2875v VID) which gives me 1.34v load, and 1.355v or so idle with Vdroop Compensation enabled. DFI's implementation is nowhere near as aggressive as Asus LLC, still has small droop but its consistent, 0.01-0.02v droop is worst I've seen so far.
Speedstep gives me 6x415 = 2.45ghz, C1E drops Vcc down to 1.22v during speed step. It's stable as could be too with them both enabled. I've never cared much for power saving features mostly because Asus boards never have them working once overclocked, but after experiencing working powersaving when overclocked on this DFI board I don't think I'll be content with broken Asus power saving features anymore!
I never understood why this isn't possible on ASUS boards. Isn't this something that the EPU chip supposed to do, saving energy?Quote:
Originally Posted by mikeyakame
Perhaps they think that if you start overclocking you don't really care much about saving energy and it's easier for them to leave it like it is now.
I just got my Rampage Formula and everything is running fine except I have to drivers that are not loaded in the device manager. I searched a little and still came up with nothing. It is looking for the SM Bus Controller which is my chipset, correct? I have tried loading drivers from website but nothing changes. I am using all SATA drives. Everything is working that I know of. I have two 500gb Maxtors in Raid 0.
Returning to the same question. I did try the 3.7ghz with similar results:shrug:
Iam thinking now if i need to run a hight CPU PLL to achive my goal for 3.8Ghz (9x425 or similar)
What is the general experience how far can i go on a 65nm Quad?
this is what i use today
http://img23.imageshack.us/img23/7607/pict0059qz3.jpg
New ASUS Rampage Formula Bios 0803.
Edit:
Nothing visually changed in the BIOS. Testing for stability now.
ASUS way of fixing a General protection fault.:D
I'm runnin @3.8 with my Q6600.. First thing i would do is drop the multi to 8, and set the CPU/NB GTL's to .67... If you need it, i can post my bios settings, i'm also runnin 8gb of mem to, so it may be a bit different with your setup...Quote:
Originally Posted by neo_rtr
new bois for rampageformula 803
ftp://ftp.asus.com.tw/pub/ASUS/mb/so...rmula-0803.zip
http://img515.imageshack.us/img515/605/capture88ys3.png
Hi, the picture above is 8x450 : 3.6GhzQuote:
Originally Posted by screwtech02
my CPU GTL is 0.63x
NB GTL is 0.67x This is the 65nm QX6700 iam having
Is your suggestion to change 8x475 : 3.8ghz?
Any pressing reason or improvement to flash from 802 to 803?
The General protection fault seems to fixed in BIOS 0803. I'm using DRAM CLK Skew Advance 300 ps or DRAM Clock Fine Delay 0T for both channels.
With DRAM CLK on Auto I get a result like the screen shot that I posted that my system will be shutdown.
I post a new one when I'm satisfied with the amount of time it's been running stable.
Uhmm... the general is back after 55 minutes running. I'll try now with changing tREF.
I realize somebody already asked but does anyone know exactly what changes have been made in BIOS version 0803? You mentioned above A-Gray that the "General Protection Fault" seems to be fixed but do you know of any other changes? Until reading your post above I had never even heard of this "General Protection Fault" issue (probably because I haven't tried the combination of settings which causes this fault to happen)?
mikeyakame - As I was reading your post above (#1882) I got confused becausee I thought you were talking about the Rampage Formula and wondering why I didn't have any of those BIOS settings! What DFI board are you currently using, just curious? My last board was a DFI UT X48-T3R which was a great board, unfortunately I wasn't capable of getting it stable where I wanted to be so I picked up my current Rampage.
PS: I just searched both online and here in the thread for the voltage read points on this motherboard with no luck? Does anyone know where the actual voltage read points are on the Rampage Formula so I can use my DMM to read actual idle/load voltages (at least for CPU, PLL, VTT, NB, and SB)? I've tried a handful of different spots but its very hard to verify that I'm reading the correct actual voltage? Thanks for any help on this guys, if I can find them I'll do my best to test and record all the voltages and post them here (it might help everyone out)!
Suggestion is to set your cpu gtl to 0.67x for whatever your fsb is, because you have a 65nm cpu. Then you can try to raise a little your fsb and see what happens.Quote:
Originally Posted by neo_rtr
No, it should be CPU GTL 0.65X for 65nm CPU. That's what Anandtech says to use for 65nm and that is what mikeyakame is using for his Q6600.Quote:
Originally Posted by greg.m
BIOS history:Quote:
Originally Posted by Roger_D25
[ 0803 ]
----------------------
Improve compatibility with some Raid card
You won't run in to a General protection fault when you don't stress your full system. The BIOS didn't fix that but the DRAM Clock Fine Delays seems to stay on the same value now. Although it's still early to say that it is really fixed. Time will tell if it is.
Using LT X48-T2R with most recent bios. Board is pretty much same as you had except DDR2, and different cooling. It's definitely not as simple to clock as the RF! I found a few hours yesterday to spare for overclocking this thing, and I've managed to get 8x420FSB PL8 1120mhz DDR2 stable. Amazingly I've got it stable with only 1.312v Vtt (65nm quad) and 1.33v Vnb real.Quote:
Originally Posted by Roger_D25
Latency is around 59.5ns or so memory bandwidth around 8700mb read, 8200mb write, 8500mb copy. Still haven't quite worked out what DRAM Delay Skew values I need for PL7 to be fully stable. I'm using cross clocking cha/chb aggressive and ch1ch2 common clock more aggressive at the moment.
Still got slight run away clocks but I've reduced the run away to safe buffer now. DRAM CLK and Data Drive Strength helped a lot here.
Nothing.. bump up the volts CPU PLL etc 3.8ghz big nothing.. i give up. also updated to 0803 bios.
EDIT
With my current settings 8x450
CPU GTL 0.65X for 65nm CPU Fails Prime within Secs
CPU GTL 0.63X for 65nm CPU PrimeStable
You have to change the FSB Termination Voltage when you change the CPU GTL. And maybe you need to change the NB GTL to. Look where it fails in Small or Large FFT's.Quote:
Originally Posted by neo_rtr
Thanks A-Gray and mikeyakame for helping out with my questions, its greatly appreciated! By the way A-Gray how does Prime failing in SmallFFT's or LargeFFT's help determine what the problem may be or determine what CPU/NB GTL settings you should use?
Small FFT uses L1/L2 cache for calculations so its more likely to be CPU GTL Ref.Quote:
Originally Posted by Roger_D25
Large FFT uses DRAM so it crosses cross clocking boundaries of MCH/DRAM so it could be more likely DRAM Clock Skews or NB GTL Ref.