:eek:error @ 71%
give atry @ 1.61nbv and see:confused:..........
Printable View
:eek:error @ 71%
give atry @ 1.61nbv and see:confused:..........
greg.m why you are not using memtest86+? And did you try to adjust tREF?
Maybe it's your ram man.Quote:
Originally Posted by greg.m
My ram requires 2.4v to work stable at 600mhz, I wouldn't be surprised if your ram would want more power.
Yeap, until you run 2.1 vdimm and fail, you don't have much of an argument. Besides,other factors like high fsb and improper NBV and timings could also be factors. Give a little higher cpu volts too, just to eliminate the possibility of that being an issue.
Ive already done that with success and with using much lower nb,ram volts like A-Grey. Thats the prob...Quote:
Originally Posted by kuebk
I highly doubt that PL <= 7 is reachable above 600mhz on ram without much volting MCH/RAM.Quote:
Originally Posted by Zucker2k
You can't compare volts, some sticks require less - some more. I would start with 2.3v on ram.Quote:
Originally Posted by greg.m
I've been running MemTest86+ V2.11 without problems with DRAM Voltage 1.90V and NB Voltage 1.41V.Quote:
Originally Posted by Zucker2k
I'm going to try it Windows with MemTest to see if it's really the memory that fails.
Why should I use DRAM Voltage 2.10V and 1.55-1.60V to run at FSB 465MHz if I can have FSB 450MHz with DRAM Voltage 1.80V and NB Voltage 1.33V?
This doesn't make sense.:confused:
just to say that with 0902 bios and same settings as before i fail in 2-3 Prime pass.
I took it up +1 on CPU, PLL,NB,FSB (x63 and x65) and i fail almost all the time.
qx6700 and 8x450, 333 strap 1018 mem.
I shoudn't try that with these sticks without active cooling.Quote:
Originally Posted by kuebk
Yes it does, after some point the amount of volts is disproportionate to the amount of mhz you can earn.Quote:
Originally Posted by A-Grey
Do you know about which mem are we talking about?Quote:
Originally Posted by kuebk
If not here it is: G.SKILL F2-9600CL5D-4GBPI. There is also a thread here in xs.
This mem have done crazy things. And there are other mobos with which it works like a charm..
Anyway i wouldnt have problem to raise vram beyond 2.1(rated) but how far can i go. Wahts the vlimit before.....:eek:?
Edit: i updated my sig with right comps
Do you agree if I say that CPU Clock Skew Delay 200ps and NB Clock Skew Delay 100ps are the settings that we should use but that it can't stay stable with these settings?Quote:
Originally Posted by greg.m
I think that with some small adjustments in the BIOS on the CPU and NB Clock Skew it would be possible to keep it stable.
It has nothing to do with tRD, Ai Clock Twister moderate, DRAM Static Read Enabled or DRAM CLK Skew on Channel A/B.
I tried everything and nothing helps to keep it stable. From the moment you go above DDR 1200MHz it isn't possible anymore to keep it stable.
You can try 1600MHz with 2.6V and dry ice like the guy on that thread that you are saying.:DQuote:
Originally Posted by greg.m
Quote:
Originally Posted by A-Grey
Except the first test iv done all the others is with cpuskew100 and nbskewnormal
and all these : tRD, Ai Clock Twister moderate, DRAM Static Read Enabled or DRAM CLK Skew on Channel A/B set to auto or as it was.
But ill be back with my exact bios settings. Right now im testing with 1.61nbv.....
With 1.61nbv error came much earlier @ 18% .........f@kc
Yes I know, but don't forget that every stick is different. As I said some are better some are worst. Maybe quad is the problem - its used to put much stress to the fsb.Quote:
Originally Posted by greg.m
You didn't understand me. What I'm saying is that if you would use CPU Clock Skew Delay 200ps and NB Clock Skew Delay 100ps it could have been stable without having to force it. But with this BIOS it isn't and that's why I think that corrections should be done in the BIOS to make it stable with CPU Clock Skew Delay 100ps and NB Clock Skew Delay 100ps.Quote:
Originally Posted by greg.m
The think that both A-Grey and Fritz the germ have almost the same prob with running that mem above 1200 stable, points either to the mobo or to the mem. But i think its the rampage that limits mems performance. Enough for today, time to play crysis and relax:rofl:Quote:
Originally Posted by kuebk
I totally agree that asus should do some corrections/fixes because its unacceptable to stop caring for a "top" mobo after a year. They made a new bios which supports "new cpus"(who cares but if so which ones), but i havent seen since a long time ago a new bios which "supports new ram" or "improve ram compatibility" or "improve ram performance" or whatsoever:down:.Quote:
Originally Posted by A-Grey
Oh... and don't forget Roger_D25. He is also running with this fine memory on his ASUS Rampage Formula board. He is also saving on his electricity bill like I do and is running at 8 X 450MHz and DDR 1200MHz with tRD 6.:DQuote:
Originally Posted by greg.m
Why are we having so much trouble with DDR speeds above 1200MHz on our ASUS rampage Formula board that OFFICIALLY has no DDR 1200MHz limitation.:shrug:
That's something that I just found out.:up:
Visit the ASUS rampage Formula forum and add your thoughts to the ASUS Rampage Formula BIOS 0902 thread.Quote:
Originally Posted by greg.m
Thank you for your help sorting things out. We didn't get any wiser but we know enough now.;)
Okay those of you having problems with DDR2 1200 try this: Move rams into white slots, set cpu skew to delay 100 (I agree finer adjustments eg. 50ps would do wonders), set nb skew to normal. Set your ram to max volts (2x2GB skills don't suffer from over-voltage even up tp 2.80v) ie. 2.100v - make sure this is actual. Set NB to 1.4.5 - 1.5 (for FSB 450). Advnace both DRAM CLCK SKEW Channels A/B to 300. Set Ai Clock Twister to moderate.
I would test this myself, but I no longer own this board. Please give me some feedback; I'm more interested in MCI Memtest (Windows) than Memtest 86+ under DOS mode. Thanks.
ASUS Rampage Formula BIOS 0902 UPDATED:)Quote:
Originally Posted by A-Grey
para fsb strap 266 que lvl perfomance usan ?
Not possible. ASUS already optimized the DRAM CLK Skew on Channel A/B for running these sticks without problems on the ASUS Rampage Formula. They have fix this issue in BIOS 0902.Quote:
Originally Posted by Zucker2k
Changing the DRAM CLK Skew on Channel A/B isn't going to work. The DRAM Clock Fine Delays are on 11-9-11-9 and that's where they should be.
I'm going to run MemTest in Windows XP with the maximum available free memory. This means that I have to use two copies of MemTest with both half the free memory.
This is a copy of my post at the ASUS Rampage Formula forum.
Just like I expected. Running 2 copies of MemTest to use all free memory available in Windows gave ZERO errors.
What does that tell me?
There are no Memory problems with BIOS 0902. I've been running MemTest86+ V2.11 Test 5 for more than an hour and it didn't find any errors on the Memory.
To see that there are no problems with the Memory in our OS I have been running 2 copies of MemTest for Windows to use all free memory available to test.
Most users prefer to use MemTest for Windows because it's more stress full and is going to pick up errors much quicker than MemTest86+ V2.11 because it stresses the NB more.
To look if DDR 1239MHz, DRAM Static Read Control Enabled, Ai Clock Twister Moderate and tRD 6 are a problem, I did the test with MemTest.
Here's is a screenshot of my result. No errors after 100%. Some users are going to say that 100% isn't enough. I tell you I can run MemTest86+ V2.11 or MemTest for Windows all day long and it will pick up ZERO errors.
http://i431.photobucket.com/albums/q...D6-MemTest.jpg
How come that Linx already fails after the second pass as you can see in this screenshot?
http://i431.photobucket.com/albums/q...D6-LinxFai.jpg
The answer is very simple. It isn't the Memory that makes Linx fail it's something else.
If it isn't the Memory it must be the CPU.
Well it isn't the CPU that makes Linx fail because my CPU can be perfectly stable at 3.72GHz.
What can be wrong that it randomly fails in Linx or Prime95 after some time?
The answer is more easy than I expected. It's been there for quiet some time but we didn't look at it. Let's have a look at my settings for 8 X 465MHz and DDR 1117MHz with tRD7.
What are the differences between these settings and the ones I've been using for DDR 1239MHz?
A different Strap, faster Memory speed, tRD 6 and CPU Clock Skew Delay 200ps.
MemTest86+ V2.11 and MemTest for Windows already showed us that there is no problem with the Memory so we can rule out the different strap, faster Memory speed and tRD 6.
These settings seem to be bullet proof.
When all these settings seem to be bullet proof there is only one that remains and that is the CPU Clock Skew Delay 200ps.
Brilliant! Here's our problem. The difference between the CPU Clock Skew Delay and The NB Clock Skew Delay is making these random failures.
As I don't know the exact amount of delayed time I can only speculate what the problem is. It could be that the CPU Clock Skew is to far or to short delayed. It can be that the difference between the CPU and NB Clock Skew delay is to short or to large.
Anyway if what I'm thinking is true the random failures can be removed with some adjustments on the CPU and NB Clock Skew.
It's possible that we need smaller delay times of 50ps like we have on the DRAM CLK Skew on Channel A/B.
There's only one doubt to be removed; supercool your cpu/nb and see if you still fail linx, then you'd be able to tell if it's heat/voltage or a timing issue. Linx will stress your (total) system more than MCI memtest ever could. As you can see from the ss you provided, your cpu isn't working as hard. With linx all your components are operating at full power, even the integrity of your power supply comes into play.
Yes I know that MemTest isn't stressing the CPU to hard. It's just to know that the memory is really stable in our OS. The problems starts when you stress the CPU really hard. That makes me think that the delay between the CPU and the NB isn't good. With the 100ps delay difference it could be to much or to little.Quote:
Originally Posted by Zucker2k
Without a delay between the CPU and the NB it isn't possible to run with DDR 1239MHz. You will end up with a system crash. With a delay of only 100ps on the CPU and normal on the NB we have the same problem that it's to much or to little when we are using DDR 1239MHz.
It is also possible that it isn't the delay difference that creates instabilitys but that the time of the CPU and NB Clock Skew delays is to late or to early for DDR 1239MHz.
This is something that ASUS should try out to see what's happening when they do some corrections on the CPU and NB clock Skew. This is the only thing that I can think of that makes it fail.
Am facing a strange problem after upgrading to BIOS 0902.Once an OC fails, one of the Hard Disks(a WD 500gb one, which is just a dump disk) disappears and the CMOS Date/Time gets reset with the OC settings also getting cleared.I have to manually disconnect and reconnect the SATA cable to have the HDD detected again.
Did you do a Clear CMOS after flashing your board?Quote:
Originally Posted by RedBull1985
In regards to the flash process guys, how do you usually do it? I don't know if this is correct or not but this is what I've been doing,
1. Go into BIOS and set everything to default after clearing the CMOS (so that there are no stability issues while flashing).
2. With new BIOS on thumb drive I enter the flash utility via BIOS.
3. Load new BIOS file and allow computer to restart.
4. After the computer starts I let it go through the bootup process and manually shut it down before Windows starts to load.
5. After the computer shuts down I pull the power plug and hit the power button a few times.
6. I manually clear CMOS.
7. Reboot computer, go into BIOS, load default settings, and reboot.
8. Only now do I go back into BIOS and manually change to the settings I want.
Granted everyone does their own thing when it comes to flashing the BIOS but does my process seem alright to you guys? Have I missed any important steps or taken steps I shouldn't have? Thanks very much for the help!
No, it's good.Quote:
Originally Posted by Roger_D25
I don't do a Clear CMOS before the flash I only load setup defaults.
After flashing the board I enter BIOS setup and load setup defaults again.
I let it post and shutdown my computer with the power switch on my PSU to do a Clear CMOS.
I enter BIOS Setup again and put al my settings back.
I never load old OverClock Profiles from the previous BIOS.
Great, thanks for posting how you do it A-Grey! I forgot to add it but I also never load old "Overclock" profiles from a previous BIOS even though some say it works just fine (its a good way to have problems in my opinion)!
A-Grey your errorfree memtest is @ 1240mhz or 1117? If its @ 1240 is that with settings you gave me?
It's with DDR 1239MHz and with the settings I posted for you. I can probably lower the NB Voltage a bit and still stay stable. I should try it again with 1.37 or 1.39V but it isn't really important because it isn't the Memory or the NB that creates the random instabilities.Quote:
Originally Posted by greg.m
yep indeed.Loaded Setup defaults, rebooted to Windows, shut down and hit the CMOS reset button in the mobo, reboot and then flashed.Quote:
Originally Posted by A-Grey
But whats most strange abt the problem now is that its the same HDD that gets undetected each time the CMOS gets reset.All the other HDDs are fine and when i clear CMOS, it gets detected again and works perfect until the next hang when the HDD again disappears and CMOS settings get cleared.
I even tried changing the SATA cable, the power connector to the HDD but to no avail.If its int he 4th SATA port, it gives
"4th SATA HDD error
Press F1 to resume" message in POST.If its int he 3rd SATA port, message becomes
"3rd SATA HDD error
Press F1 to resume"
Sometimes, there will be a " CMOS Date/Time not set" message along with the above one too...
Am absolutely frustrated with this error.Any help wud be highly appreciated.
PS: Checked the HDD with HDTune thoroughly for any sorta errors and it just is as good as day 1 when it is getting detected.
nob question, in Prime Small FTT i have BSOD due to the 4th core is left behind about 1-2 cycles.
Any pointers? pls
It's like talking to a brick wall :)Quote:
Originally Posted by Zucker2k
Linpack calculation errors like in his pic are more than likely CPU GTL1/2 or NB GTL related, I've told him this too. Since CPU GTL1/2 can't be adjusted seperate of CPU GTL0/3, he is screwed basically so he needs to back off settings till its stable.
CPU GTL1/2 wants to be high, CPU GTL0/3 wants to be low, you can't dial both in low and expect stability, only other alternative is raising Vtt and balancing it out.
I can replicate those type of Linpack errors on my DFI board simply by changing GTLs by as little as 0.0008v sometimes, and this means one of two things. First most likely my Vtt needs some minor adjustment, or second I've found where the max or min threshold for logic receiver GTL sampling lies.
You can't test GTLs with a tight PL as well, need to be done with at least PL-2 lower than aimed. That way takes strain off MCH, and if Vnb was too low it won't trash your results. CPU multi should be dropped as well by 1 or 2x. To give a frequency that'll work on VID for testing.
A-Grey, your Vtt is too low to use 0.63x CPU0/1/2/3. I use the following at 425fsb on my Q9550, 3.61ghz, PL7.
Vcc = 1.21v, Vtt = 1.19v, Vnb = 1.39v, CPU GTL1/2 = 101 (~0.6665x), CPU GTL0/3 = 87 (~0.648x), NB GTL = 81 (~0.662x). On top of these i use MCH Vref1-3 and MCH Slew Rate Offset which are MCH registers for compensating insufficient circuit resistance. Basically they give additional resistor impedance adjustment within a limited range, for circuit level slew rate/voltage crossing point correction, when at higher FSB both voltage noise and clock jitter/shifting/skewing gradually get worse and require compensation at logic receiver to bring them back within limits.
Try to flash it again but this time only load setup defaults before and after you flashed the board. After you flashed the board and loaded setup defaults, let it post and shutdown your computer with disconnecting the power from the PSU with the power switch or removing the power cable. Do a Clear CMOS with the power still disconnected. Don't load old OverClock Profiles.Quote:
Originally Posted by RedBull1985
If want to do a Clear CMOS before flashing the board you still have to load setup defaults before flashing it.
Here: http://www.anandtech.com/cpuchipsets...oc.aspx?i=3184 you can read about core throttling.Quote:
Originally Posted by neo_rtr
Great Thanks for that.Quote:
Originally Posted by kuebk
Just flashed back to 803. SO HAPPY. Works like a charm! testing already but no sign of any problems what to ever..
That's why I use FSB 465MHz. The CPU and NB GTL Voltage reference and the FSB Termination Voltage are exactly the same as the one I used before with my 8 X 465MHz DDR 1117MHz and tRD 7 setup that was 100% stable.Quote:
Originally Posted by mikeyakame
I tried different CPU and NB GTL Voltage Reference settings and different FSB Termination Voltage. This isn't the problem it only gets worse and I fail Prime95 immediatly.
With the settings I posted I can run hours stable in Prime95 or fail it in a few minutes. I can run a few passes stable in Linx or already fail the second pass like in that screenshot.
There are 4 guys among us that are running with this memory and nobody can run it stable with DDR speeds higher than 1200MHz.
If there is one brick wall you can talk to it's the one called ASUS.:D
That's exacly what I meant before, quads with high clock + mem with high clock + low performance level probably will no go.Quote:
Originally Posted by mikeyakame
Definitely mate.Quote:
Originally Posted by kuebk
On my previous RF i ran a Q6600 G0. It walled at 481mhz FSB, I ran that every day...but I only ran on 7x multi so 3.36ghz, PL7, and 1158mhz ddr freq. Board threw fits if i tried 8x and 481. It didn't like it period.
I have an E8400 from a rather poor batch (3.6GHz @ 1.22v yet anything higher like 3.8GHz or 4GHz requires huge doses of voltage) and am still using bios 308. Is there any risk from using bios 308 since it maxes out tREF? System is stable but I'm convinced that a tREF of 16383 on DDR2 800 is somehow going to cause problems for me in the future. Will my stubborn C0 E8400 failbatch benefit from flashing to the newer bios versions?
You can always adjust tREF using MemSet, and imo upgrading to 803 is a good option.Quote:
Originally Posted by Armored_Kech1
There is one among us with a C2D and he has the same problem.;)Quote:
Originally Posted by kuebk
Ooh... If this is the problem ASUS would have told me that.
I tell you ASUS is trying to fix this problem but doesn't really know how to. BIOS 0902 should have been released a few weeks ago but they didn't because the problem isn't fixed. They only released it because of the fan mail that they received lately.:D
With 2x2 or 2x1?Quote:
Originally Posted by A-Grey
With the G.SKILL F2-9600CL5D-4GBPI of course.:confused:Quote:
Originally Posted by kuebk
Il run some tests and ill be back... asta la vista...:D
Yoh guys,
I am the one with the C2D having the same problems. I am not able to run my system (prime or LinX) stable using a higher freq, than 1,200 Mhz memory speed.
So I tried to talk to the ASUS brick wall in this way:
I have some serious problems running my memory more than 1,200 MHz.
The board is running excellent with 9 X 450MHz, memory speed at 1199MHz and tRD 6. Every time I try to increase the speed and I run my Memory above DDR 1,200 Mhz, the board starts randomly failing. No matter what I do. No setting in the BIOS that I've got available can help me to stabilize the board.
For example:
I tried to run it at 9 X 465MHz, memory at DDR 1239MHz and tRD 6.
The memory is MemTest86+ V2.11 stable at DDR 1239MHz tRD 6 and my CPU is
stable at 4.185 GHz. I know that because I tested my CPU at that speed with a different strap and my memory running at DDR 1117MHz and tRD 7.
With the memory at DDR 1239MHz I can run Prime95 Blend Mode but it will randomly fail. This can be in small FFT's or in Large FFT's. It can be stable for a few hours or it can fail in a few minutes.
I can run IntelBurnTest or Linx for a few passes stable before it randomly starts failing.
I tried DDR 1239MHz and tRD 7 with no Phase Pull-Ins enabled but I still can't get it 100% stable.
It's strange that I've got to delay DRAM CLK Skew on Channel B with 50ps while Channel A is on Normal with the Memory running at 1199MHz and tRD 6 to be able to run IntelBurnTest or Linx for a few passes stable.
I don't have to delay Channel B with 50ps when I'm using tRD7.
Many friends of mine are having these random stability
problems too when they are trying to run the memory faster than DDR 1200MHz and I am (or better we are) blaming the BIOS for those random failures. Because of the fact that the Intel X48 Chipset is designed to run at DDR 1600MHz.
Is there a memory limitation on this board of 1200MHz or is that just coincidence?
I find this very strange because in the QVL I can find X 1 Giga Corsair 1250MHz 5-5-5-15 that seems to be compatible with the ASUS Rampage Formula.
ASUS replied and feeds me some sweet talking bulls***:
"Thank you for contacting ASUS Customer Service.
My name is Lyn and it's my pleasure to help you with your problem.
We cannot assure you can run the RAMs over its rated frequency(1200MHz).
There is no such limitation for the memory frequency on this motherboard. But to overclock, you need to try it yourself.
In fact, even DDR2 1200 is O.C. speed. The motherboard supports 4 x DIMM, Max. 8 GB, DDR2 1200*/1066/800/667 ECC,Non-ECC,Un-buffered Memory.
Welcome to refer Troubleshooting & FAQ for ASUS products in ASUS website:
http://support.asus.com/troubleshoot...Language=en-us
http://support.asus.com/faq/faq.aspx?SLanguage=en-us
If having any problems, please don't hesitate to let me know. Let's discuss this
issue together.
Thank you for using ASUS products and enjoying ASUS services!
Lyn"
I will reply in a harder way. But what do you guys think about that? Isnīt it a shame to react like that?:eek:
They dont give a frak. They will use the "we dont support overclocking" excuse ANYTIME they can, especially to get out of fixing any type of issues.... Most, if not all MB manufacturers are the same way.... Its pretty weak to "advertise" the board as being able to support 1 thing, only for the end user to find that is doesnt.... Go figure.....
At least they give you the chance to talk about it.:DQuote:
Originally Posted by Fritz_the_germ
There's plenty of useful information to throw at them.;)
We could ask them to show us some screen shots running 4 X 1 Giga Corsair 1250MHz 5-5-5-15 Memory on the rampage Formula. This memory is in the QVL.;)Quote:
Originally Posted by screwtech02
Don't ask me how they know that it's possible to run that stable without OverClocking.:D
Since this is a new BIOS that we're using I'm going to try it at 8 X 465MHz with DDR 1117MHz and tRD 7. I'll run some Linx tests to see if I can get it stable with this BIOS.
If I can get it stable with these settings we'll never get it stable with DDR 1293MHz and tRD 6.;)
Wasn't that obvious much earlier?Quote:
Originally Posted by A-Grey
I get errors already on the 2nd pass.Quote:
Originally Posted by A-Grey
Weird
Reboot the PC run Linx and BSOD as soon as i press the test button to start
No, it wasn't because nobody could have known that the problem is the CPU and NB Clock Skew.Quote:
Originally Posted by kuebk
I did my job today to finish my testings with this BIOS. You can find everything on this page: http://vip.asus.com/forum/view.aspx?...Formula&page=2
Shame on ASUS.:shakes:
Are you still using BIOS 0902?Quote:
Originally Posted by neo_rtr
If so move back to BIOS 0803. You'll never get a 100% stable system with BIOS 0902.
Iam on 0803. This is the weird part.Quote:
Originally Posted by A-Grey
Following some more tests last night i have issues, BSOD with Small FTT now, on the same settings that i have been running this M/B since few months back.
I am going to buy a Mac! :rofl:
Maybe one of your memory sticks is bad. Run some memory tests to be sure.Quote:
Originally Posted by neo_rtr
So, A-Grey , is 0803 better according to u?
Yes it's better. We don't need the DRAM CLK Skew on Channel B fix. We can't run anything 100% stable with BIOS 0902.Quote:
Originally Posted by RedBull1985
With BIOS 0803 we can at least run our system stable with the OverClock that we are using.
I had a lot of fun with BIOS 0902 but I flashed it back to BIOS 0803.:D
BIOS 0902 tastes for more. If ASUS decides to fix the problem with BIOS 0902 we might have the BIOS that we all want on our ASUS Rampage Formula.
Running Linx at 8 X 465MHz, 2 X 2 Giga DDR 1117MHz and tRD 7 with only 1.35V for the NB. Sure would like to see that running 100% stable.:up:
Do you mean your ocz or gskills?Quote:
Originally Posted by A-Grey
With my G.SKILL Memory. I sold my OCZ Memory.Quote:
Originally Posted by greg.m
Did you pass MemTest at DDR 1239MHz with your G.SKILL Memory in BIOS 0902?
Well here i am with some new tests. I tried 490x8 because i didnt want to press cpu a lot with - biossets - 1.49nbv, 1,44vtt, 2.04ramv@1225pl7. While Primeing95small and after i had done 1and a half cycle, the system just freezed. I suppose that it has something to do with nbv and/or fsbv or even ramv. Any ideas?
BTW, any voltsuggestions for running 500:explode2:fsb?
No:mad: and with exactly your settings i got memtest error @ only 5% of first cycle, so i gave up and now im trying with higher fsb to gain some performance. But i started from zero with the bios settings.Quote:
Originally Posted by A-Grey
Ill go back to 0803 and test again.
I'm almost sure that the problem is either to tight PL or to low vDDR.Quote:
Originally Posted by greg.m
Whatever I'm trying in BIOS 0902 I'm always with the wrong CPU and NB Clock Skew.Quote:
Originally Posted by greg.m
With CPU Clock Skew Delay 100ps and NB Clock Skew Delay 100ps I did better in Linx with dropping the NB Voltage. My best score was at 1.35V. I could do 9 passes. I lowered it to 1.33V and It fails after the first pass.:confused:
Strange that with lowering the NB voltage Linx runs longer stable but it can be stranger.
With CPU Clock Skew Normal and NB Clock Skew Normal I did better with raising the NB Voltage. My best score was exactly 9 passes again with 1.43V.
I raised it to 1.45V and I fail Linx in the first pass again.:confused:
Maybe we need to buy one of those new CPU's to run with this BIOS.:D
Ive already ordered 2 more RAMPAGE and 3 of those NEW CPUS which bios 0902 supports:rofl::ROTF:
Do it Do it Do it...:yepp:Quote:
Originally Posted by greg.m
Stop.
Guys , dont put ides on his head. He is spending god know how much on this PC...
His cash, he can do whatever he wants with it - no point in disputing about this.Quote:
Originally Posted by neo_rtr
HELP IM ADDICTED:help::rofl:Quote:
Originally Posted by neo_rtr
i run a double instance on the mem test, pass 110% and no errors!Quote:
Originally Posted by A-Grey
put default settings and initital results with linkx where stable but had to stop the test at that point.
Het got a 1500W PCU only to blow it on the 2nd reboot.Quote:
Originally Posted by kuebk
I will start a shop and sell him computer parts!:ROTF:
Any voltsuggestions for running 500fsb?
Something to start with?
You naughty boy:cord::rofl: the first thing ill buy is your QX6700 - its a little piece of ....(guess the word):rofl::rofl:Quote:
Originally Posted by neo_rtr
Solution:
Right answer is.... art:rofl:
Will be hard to hit 500fsb with quad, imo vMCH > 1.45, vCPU and VTT stricly depends on your CPU.Quote:
Originally Posted by greg.m
If you overclock your memory run MemTest86+ V2.11 and try to get it stable before you move to your OS. Than you can try MemTest for Windows.Quote:
Originally Posted by neo_rtr
When you know that your memory is stable run 10-15 minutes Prime95 Small FFT's and 10-15 minutes Prime95 Large FFT's. When you can run that stable you can start with Linx.
I always try to run 25 passes of Linx before I try to run Prime95 for 6 hours.
500fsb depends on your CPU. If you are getting lockups you are either walling the CPU or your gtls/skews are the problem.Quote:
Originally Posted by greg.m
I've had a Q6600 boot to windows at 510mhz FSB on this board, but only with 2 cores. It dropped the other 2.
I'm so done with this board, puttin my MFII back in, I cannot get this setup to run 4.0/1199 stable for the life of me, unless i overvolt to high-heaven... MFII will at least have seperate core gtl adjustments, and a bettter power regulation.....
I think 500 FSB is a no-go for thi9s mobo + Quad....even 500x6 is throwing in errors and lockups with stress testing.Tried each and every combination of voltages,taking NB from 1.43 to 1.73 - to no avail.So, I am happy sitting here at 495 x 8.5 and trying to find stability with the 0902 BIOS and reducing voltages bit by bit.
Read this... http://www.xtremesystems.org/forums/...197802&page=40Quote:
Originally Posted by RedBull1985
Don't skip page 41, the most important screenshots are on there. I used more volts than I should have because the dude challenged me and I was just out to prove him wrong and move on to other things. At least if nothing else, this shows it is more than doable. I've done it with Q6600, Q9550, and Q9650; all with 8GBs to boot.
With DDR 1199MHz and BIOS 0803 I don't think you will get it stable. We need the DRAM CLK Skew on Channel B fix for that. This BIOS can't run stable with high DDR speeds.Quote:
Originally Posted by screwtech02
Try BIOS 0902 that has that fix. Maybe you've got more luck with that BIOS than I do.
Correct My memory is running 100% stable at 1081Mhz , I tested that by running the windows MEMTEST, and i also run two instances of the program at the same time..with no errors.Quote:
Originally Posted by A-Grey
The fix to what?Quote:
Originally Posted by A-Grey
To run your Memory at high frequenty.;)Quote:
Originally Posted by kuebk
With BIOS 0803 you've got the problem that with your Memory running at high frequency you have to start delaying Channel B. A delay of 50ps on Channel B can partially correct that problem but the Memory will still make some errors there is still a small sync problem between Channel A and B.
Without the delay on Channel B it isn't possible to have your Memory running at that higher speed with this BIOS.
With a faster CPU speed you will see that problem much earlier. That's why we can run our Quads at 3.6GHz and DDR 1199MHz with tRD 6 without problems but if you run your CPU at 4.05GHz with a 9 multiplier you won't get it stable anymore with DDR 1199MHz.
BIOS 0902 corrects that problem and there is no sync problem anymore between Channels A and B.
With fixing that problem they created an other problem.
This is what I think happens in BIOS 0902. With fixing the sync problem between Channels A and B they moved the problem to the NB and created a problem between the CPU and the NB. This is probably the reason why I'm always with the wrong CPU and NB Skew.
Advancing the Skew a little bit in the BIOS for the NB might fix that problem.
But hey... I'm not a engineer and I don't know all the technical sh*t and this can be totally wrong.:shrug:
Try to run Prime95 Small FFT's to adjust your CPU Voltage and your FSB termination Voltage and Prime95 Large FFT's for your NB Voltage.Quote:
Originally Posted by neo_rtr
When you've got that stable for 10-15 minutes you can run Linx to tweak your GTL's in combination with the FSB Termination Voltage and adjusting the CPU Voltage.
When you can run 25 passes stable in Linx you can go to Prime95 again and run Blend Mode to see what needs to be done to keep it stable for a long time.
When you still fail Large FFT's it is your NB or FSB Termination Voltage.
Quote:
Originally Posted by A-Grey
Thats for the feedback. Will put down some time on this.
How am i supposed to use the ASUS EZFlash Utility ? I wanna flash back to 0803 and it seems to be the only option.Shud i make my USB bootable or something?
^^ ah sorted it myself.Now back on 0803
I've got a mail today from one of the ASUS engineers. He wants to know what the problem is with BIOS 0902.
"Problem with BIOS 0902:confused:... I don't know we're all using BIOS 0803":D
To make a long story short. I told him that it's impossible to run stable with that BIOS.:yepp:
That I already informed ASUS about the problems and that they shouldn't release it as a Final BIOS but that nobody seems to care and have no time to reply to me.:yepp:
That we've been asking for god knows how long time to do something about the BIOS on the ASUS rampage Formula.:yepp:
And of course that we aren't so happy with the current situation.:yepp:
So, I'm hoping that the ASUS Engineer is going to take this serious and that they actually going to do something about this.:yepp:
Asus engineers need some real overclockers who can bring out the worst in their bioses, so they can catch them in time and fix them before release to the public. Key word: hardcore overclockers!
It's like I said before. They run some benchmarks and they are happy if they can finish them before the problems start.:DQuote:
Originally Posted by Zucker2k
It's easy to say that you don't support OverClocking. When you don't want to support OverClocking you shouldn't sell boards who can do it.;)
You are right. For every board they should have someone that is capable to find the problems in their BIOSes. There are guys enough who can do it. They just have to ask it and those guys would be happy to do that.
BIOS 0902 was only a few days available on their FTP before they moved it to the Official download page. That's to early because most problems can only be found after a lot of hours stress testing.
oc E8600
585x 8,5 5ghz divisor 1:1 1170mhz perfomance 8
556x9 5ghz divisor 1:1 1112mhz perfomance 8
600x 8 4,8ghz divisor 1:1 1200mhz 3dmark03 perfomance 8
570 x 8.5 4.8ghz divisor 1:1 1140mhz 3dmark03 perfomance 8
515x9.5 4,9ghz divisor 6:5 delay300 advance 300 perfomance 7
533x9 4.8ghz divisor 6:5 DELAY300 advance 300 memos marco perfomance 7
24/7 E8600
450x10 4.5ghz divisor 3:4 1200mhz 1.36vcore advance 300 advace 300 perfomance 6
563x8 4,5ghz divisor 1:1 1130mhz 1.36vcore perfomance 8
500x9 4,5ghz divisor 6:5 1200mhz 1.36vcore delay 300 advance 300 perfomance 7
474x9.5 4,5ghz divisor 6:5 1140 mhz delay300 advance 300 perfomance 7
573x7 4ghz divisor 1:1 1150MHZ 1.18VCORE advance 300 advance 300 perfomance 8
helpme xtreme systems
Of better to villain divisor: 3:5 2:3 8:5 4:5 5:6 3:4 1:1
200fsb strap is imposible up 360fsb is anormal stable
266 fsb strap 8:5 4:5 up 370fsb and 480fsb ? But it he does not remain stable Alone achievement superpi2m
333fsb strap 5:6 is stable in 4.4ghz since in 4.5ghz is unstable For superpi alone achievement to 4.8ghz not import multiplicador
help to calibrate plizz
lvl perfomance and dram skll chanel a y b
eyes Everything oc those that I gave I lack for doing since not manage mas time
eyes mi oc stabl is 4.4ghz multi 9x fsb strap 333 divisor 5:6
record superpi 2m 23seg 4.82ghz fsb strap 333 divisor 5:6 multi 9.5
3dmak 03 4.5ghz 1.31vcore multi 10 fsb strap 400 divisor 3:4 98mil puntos
Mind if I add to your keyword :DQuote:
Originally Posted by Zucker2k
"Competent" Hardcore Overclockers.
They are rare and few inbetween.
Lol. How about dedicated, competent, hardcore overclockers? I woldn't mind overclocking systems for a career. :rofl:Quote:
Originally Posted by mikeyakame
Hell neither would i :D As long as whomever wants me to do it, supplies me with a logic analyzer and the Intel Data Analyzing/PC Logging Software to go with it!Quote:
Originally Posted by Zucker2k
Without the proper hardware to confirm problems, overclocking blind is kinda pinning the tail on the donkey! Just hope that donkey doesn't turn out to be somebodies mother! :D
Dont know what is going on. On a previous good and stable system after the move to 0902 then back to 0803 with the same settings iam having probs to get it stable.Quote:
Originally Posted by neo_rtr
Iam going up and down volts all over the place with no luck.
i will start taking down the OC to 3.4ghz now to see what happends
Reflash your board with 0803.Quote:
Originally Posted by neo_rtr
Remove your power cable from your PSU or disable it with the power switch if you have one. Do a Clear CMOS before you flash it.
Start your system and enter BIOS Setup to load Setup Defaults and save it.
Enter BIOS Setup again and flash your board again with BIOS 0803.
After flashing your board power it down remove the power cable again from the PSU or disable the power switch and do a Clear CMOS again.
Start your system and enter BIOS Setup again to load Setup Defaults and save it.
Now you can put all your settings back.