OC'ing help on Q6600 & Striker Extreme

Page 2 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
You may want to investigate what tweaks must be made to BIOS for SLI. I'm totally blind to any experience in that arena. Look at the i4Memory website, because "EVA2000" has posts there for an SLI configuration with the Striker. Obviously, they contain the BIOS settings for about ten different over-clock configurations. Just remember that they use earlier BIOS revisions that had the discrepancies per voltages.
 

coolamasta

Member
Jan 8, 2008
57
0
0
OK I am on 1301 and now running @ 3GHz!!

I have set the following in the Bios:

PCI-E clocks to 100Mhz
The last item fr PCI-E bus to 200Mhz
QDR FSB to 1334
MEM DDR to 667
Vcore to 1.31875
All spread spectrums to disabled
Thermal control to disabled
Enhanced C1 to disabled
Mem voltage to 2.0v
1.2v_HT to 1.3v
NB core to 1.3v
CPU_VTT to 1.3v
SB to auto

And im currently in Vista and been running Prime 95 for last 20 mins, CPU is @ 39 degrees, Mobo is at 41 degrees :)

How accurate is Asus PC Probe II by the way? Its saying:

Vcore is @ 1.28v
1.2VHT is @ 1.36 (and keeps setting off PC Probe alarm, is this ok?)
NB core is @ 1.34v
SB core is @ 1.52v
CPU VVT is @ 1.36 (sets of PC Probe alarm every now and then when it hits 1.38v)
Mem is @ 2.03v

What do you think I should do next? Im going to shut it down and go to bed in about 20 mins but will leave Prime95 running for a couple of hours tomorrow

Thanks again for all yer help with this matey :D
 

coolamasta

Member
Jan 8, 2008
57
0
0
Also just thinking because I have the G0 could I lower the Vcore anymore do you think or is it trial and error to find that one out? haha

Oh and should I try running it with the NB, CPU VTT and and 1.2VHT back on Auto?
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
The conventional wisdom is to run all voltages at lowest stable settings.

But unless I'm coming close to a "recommended maximum" voltage limit, I'm inclined to kick something up a notch once I've found a stable setting.

However, the G0 is more elastic for clock-speed at lower voltages. The indications at these forums are such that the G0 and B3 steppings for the Q6600 seem to coincide in voltage requirements at 3.0 Ghz, but once you've found a setting that is stable for a couple hours, you might want to edge the VCORE down a notch at a time, reboot, re-test, and see if it fails. Once I find a voltage that fails, I may kick it up two notches, but no more.

Some people have found lower VCORE settings that work at this over-clock for 3.0 Ghz. 1.31875V is the lowest setting -- shown in BIOS and Everest at 1.31V (idle) -- that I've used for the B3. I'm guessing, since I've had it at 1.300V running stable for as much as an hour with the B3, yours might work at that setting.

But patience is the rule. Whatever setting you tune to, I'd advise seeing if it will run 6 hours or more with no errors under PRIME95. This may get frustrating if it fails after 4 or 5 hours, because you would need to tweak the voltage a notch again and then re-run the test. Even so, it's a good chance that if it runs 4 or 5 hours before failing, kicking it up a notch will be sufficient -- although I might give it two notches if the voltage is low enough and I don't want to re-test.

On the VTT, 1.2V_HT and NB voltages, you might try "Auto" on these -- I'd say knock them down one at a time if you've set them to 1.30+V. But if you look at the BIOS monitor with the settings on Auto, you'll see that they're all in the upper end above 1.25V. At least, i'm assuming no quirks with your motherboard different than mine.

Once you start trimming the VDIMM voltage to see how low it will go, you may find a point where it will run for a couple hours and fail, and you may want to at least try and kick up 1.2V_HT (and even possibly the NB core) by 0.05V.

Generally the BIOS monitor is a good indicator of where to start testing voltages and OC settings. If at stock settings the monitor shows a certain value, you might want to set something to that value and fix it. Later, test these things individually -- if they don't help while raising FSB, set them back to where they were. It pays to keep a Windows Notepad log of what you're doing so you don't get lost.

Once you have stable settings at 3.0 Ghz, you might want to see how you can trim the memory latencies before they fail, and then judge whether there is wiggle-room with the memory voltage to make the settings stable.

With the Crucial Tracer DDR2-800's, a review here at Anandtech shows them working at DDR-667 (3.0 GHz 1:1) with timings 3,3,3,8. I verified that the voltage required was somewhere around 2.125 to 2.150V with a 2T command rate. If you tighten the command rate to 1T, you may want to kick up the voltage again, but I advise against running these at 2.2V. [See if your board shows a 0.035V upward bias in monitored over "set" voltage]. You could also run a 1T command rate by loosening the timings, say, to 4,3,4,9, and either the same or lower voltage.

I'm willing to bet that high-end Crucial Ballistix or Tracer DDR2-1000+ modules will meet the benchmark tests for Tracer DDR2-800's. Later, as I already said, you might want to try a 4:5 CPU-to-RAM divider and loosen the timings to the spec. For instance, 2.88 Ghz with 1280 FSB and exactly 800 Mhz for memory is 4:5 (320:400). Right now, something I never tried before, I'm using the 3.0 Ghz CPU setting with FSB @ 1,336 and DDR @ 835. the timings are set to 4,4,4,10, 1T after trying 4,3,4,9,1T ("no cigar" -- fails too soon). At the 1280 2.88Ghz setting and DDR = 800, I think the 4,3,4,9,1T is stable -- and at under 2.100V -- I think about 2.050V, actually.

At 3.15 Ghz, I can run these Tracers in 4:5 at 1,400 FSB and 875 DDR -- last time I checked, it was stable with timings 4,4,4,10,1T with voltage at 2.125V. I think, though, that it requires a slight adjustment to the 1.2V_HT voltage to about 1.35V. Need to check my notes.

If you have Everest Ultimate, you can use the memory Benchmark under "Tools" to check the memory "read", "write", and "Copy" bandwidths. At some of these settings at 3.15 Ghz, my "read" bandwidth score is about 9,750 MB/s. You'll get about the same thing running DDR= 700 and 1:1, but you'll push the voltage higher. Everyone agrees that SiSoft Sandra provides a better measure using "buffered" memory benchmark tests, but for comparison, Everest's benchtest is no-frills, easy to run, easy to read, and easy to compare.

Eventually, you may either want to try going above 3.2 Ghz with the G0 Q6600 -- either at 1:1 or 4:5. With 4:5, you'll start tapping into the frequency-spec headroom that the high-end modules offer, but you'll still have to loosen the timings, as CPU-Z shows with the latency settings for 800 Mhz vs 1,000 Mhz operation. And if you go up the ladder using 1:1, you would certainly loosen the timings to -- say -- 4,3,4,9 and/or 2T so that you can manage to keep from pushing the voltage too far.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
PS Screw ASUS Probe. Don't rely on it. If you do use it for anything, you'll need to adjust the alarm tolerances for your voltage and other settings . . .
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
Don't have time to go back through other posts to see what you've said, but use a CoreTemp version or Beta that works with VISTA, or use Everest Ultimate to measure your core temperatures. Your mobo temp at load is higher than mine, but several people here might be able to tell you why (Search the "Cases and Cooling" forum for "Motherboard Ducting.")
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
We sure cleared up that mess about Striker BIOS revisions, didn't we? This has been fun.
 

coolamasta

Member
Jan 8, 2008
57
0
0
Hi mate, I had a fiddle with the voltages last night - I turned the CPU core down 2 notches to 1.30v and the 1.2_VHT, NB and CPU_VVT down to 1.25v

It booted up but after 5 or so minutes in Windows it locked up, rebooted and it did the same thing...

I put CPU core back upto 1.31875v but left the rest on 1.25v and everything seemed fine, ran Prime95 for 5 hours and it didn't bat an eye lid and CPU seemed to be a bit cooler than the other day :D

On the weekend I will have a play with memory settings and try run them at what you put above - (3,3,3,8. I verified that the voltage required was somewhere around 2.125 to 2.150V with a 2T command rate)

Will report back!

But yeah it has been interesting messing with the bios on the board and prooves that the new bios is a pile of crap, well certainly for 1066fsb chips, maybe its different for the 1333 chips?!
 

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
I'm getting excited, UPS is dropping off my replacement DS3L board, which I need in another computer so I can free up my Striker Extreme system for a re-model.

Thanks to this thread I am really excited about the prospects of doing a fresh install, updating the BIOS, etc. Am even going to lap my CPU and vapoLS head to see if I can squeak an extra multiplier out of the overclock.

If the OP doesn't object, I'll post my results/updates in this thread too.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
If HE doesn't OBJECT?!!! I'D be VERRRRY INTERESTED in finding out how this goes for you!!

This thread has been a kick-in-the-***. Damn, I'm going to rate it myself and give it 5 *s.

What's more, I don't know if either of you have watched this forum since last June and had drift of the nasty remarks about Striker Extreme. We know there are some limits.

But . . . get this . . .

I STILL believe that 1:1 ratio for CPU/RAM is best, but I can OC my RAM at lower voltages with 4:5. What's more, the bandwidth benchies are on top of the best I get at 1:1 -- unless I want to push the VCORE higher and the processor above 3.2 Ghz.

Given what I just said, and the general observation that "performance is in the eye of the beholder," I'm 60th-place for a "difficult" track-layout in TrackMania United in the whole US, and about 3rd or 4th place in another track-layout for all California. AFTER switching over to the 4:5 settings!!

Sure -- you get "better" playing games, but the 4:5 settings have given me a virtual heart-attack going 200 virtual-miles-per-hour.

I LIKE it this way!!
 

coolamasta

Member
Jan 8, 2008
57
0
0
haha yeah thats coooool :D

Idontcare - feel free to post you findings in here mate, its all good info, I will be playing with mine more when I get the time and info is good to share, BonzaiDuck has helped me greatly and for that I thank him :)

Will post back what I find on the weekend after I've played with memory settings.

Oh what is TrackMania then?
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
It's a virtual Formula Racing game. I think you can play it on-line with players all over the world, all running under their individual national flags. There's a set of "Stadium" tracks that alternate between dirt and pavement; "Island" -- where you race something that looks like a hybrid Corvette-Porsche on pavement tracks; "Desert" -- with old clunkers with high centers of gravity on old, two-lane roads in the SW USA; "Bay" -- with SUV's racing the same sort of tracks in "Island."

I read a review about it, and the reviewer said "It's too hard." Frankly, I think it's a bit idiotic, but I still "get off" playing it.

I appreciated your experiments with the 1.2V_HT, NB and CPU_VTT voltages -- very informative. I'd started with "Auto" settings, but bumped these up by trial and error striving for 3.2 Ghz (and not much problem there, either.) I think I left them set at 1.30V, at lower settings, though, and as I said, wanted to "fix" the voltages.

Here's something I discovered. Running 4:5, 3.0 GHz and the memory @ DDR2-835 (437.5 memory-bus), I wanted to keep the voltage at 2.125V or lower. I still have to test {4,3,4,9} latencies some more, but it's "do-able." Even so, the difference between failure after 2 hours or so @ 4,4,4,10,1T, and rock-solid operation -- seems to be bumping up the 1.2V_HT to 1.35V.

If I remember correctly, you're using DDR2-1066 Crucials? Be careful, but it just may be possible to run those with tCL (CAS) = 3 at 800 Mhz. I don't know for sure what voltage it would require, and I'd be careful with the Crucials above 2.15V.

I can't get the DDR2-800s to run at less than 4,3,4,9,1T at their rated spec.

You could either try pushing your processor to the limit to get to 400 Mhz in 1:1, or run the 4:5 memory divider with the processor at 2.88 Ghz -- FSB 1,280 . . . DDR2=800.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
NOTES:

tRAS >= tCL + tRCD + 2

tRC >= tRP + tRAS

example:

If tCL = 4, tRCD = 4, then tRAS can be = 10 -- thus 4,4,4,10 {tCL, tRCD, tRP, tRAS}

If tRCD = 3, then tRAS can drop to 9.

If tRP = 4 and tRAS = 10, then drop tRC to 14. If tRP = 4 and tRAS = 9, then drop tRC to 13.

tRCD reduced means greater bandwidth improvement than tCL reduced.

tRAS by itself doesn't improve bandwidth if tightened, but tRC reduced provides several hundred MB/s improvement in bandwidth.

The default tRC value for these Crucials is somewhere between 20 and 31.
 

coolamasta

Member
Jan 8, 2008
57
0
0
Arrrgghhhhhhhhh it keeps crashing :(

Ive not done a single thing to it, last coupe days ive been playing games, watchin Divx's, surfing etc etc, must of have it running for like 4-5 hours a day perfecty fine but today I was sat chilling watching a film and windows locked up, i done a reboot, locked up again about 10 mins after getting into windows EVERY time!!

I had a quick play with voltages, bumped the 1.2v_HT, NB & CPU_VTT up to 1.3v which made no difference as it still locked up so put them back to 1.25v...

Its been running now for about half hour with the memory on 2.1v instead of 2.0 and its not crashed yet *touchs wood* but the mem seems to be getting quite warn, IE its almost too hot to touch!! Not sure what the hell is going on though?! :(
 

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
Originally posted by: coolamasta
Arrrgghhhhhhhhh it keeps crashing :(

Ive not done a single thing to it, last coupe days ive been playing games, watchin Divx's, surfing etc etc, must of have it running for like 4-5 hours a day perfecty fine but today I was sat chilling watching a film and windows locked up, i done a reboot, locked up again about 10 mins after getting into windows EVERY time!!

I had a quick play with voltages, bumped the 1.2v_HT, NB & CPU_VTT up to 1.3v which made no difference as it still locked up so put them back to 1.25v...

Its been running now for about half hour with the memory on 2.1v instead of 2.0 and its not crashed yet *touchs wood* but the mem seems to be getting quite warn, IE its almost too hot to touch!! Not sure what the hell is going on though?! :(

This was the same kind of "overclock loss creep" that happened to me during the the first 3 months or so of owning the board (or having it own me as it were...).

On my B3 quad I eventually walked the FSB overclock back down to stock and just relied solely on overclocking the CPU via higher multipliers as it was an unlocked chip (QX6700).

Today though I took the system down and started my overhaul. Started with lapping the IHS down to copper (finished with 1000 grit, pictures to come later) and the condenser head on my Vapochill LS (what a pain in the ass to lap this thing!).

I upgraded the BIOS to 1305 (just to see if it would be as bad for me as it was for you) and nearly immediately re-found my old friend the FSB wall with this shietty B3 quad. These things HATE FSB.

I seem stable at 1333 FSB (4x333) though which is a first, can't go any higher though and make it into windows (4x367 for example, dies just posting).

Your mileage will no doubt vary as these early B3's are pretty finicky for FSB.

Anywho, here's my current BIOS settings and readings. Will leave it running small FFT overnight and see if this is stable. Thanks for the Eva2000 link up above, that lead me to the voltage settings that ultimately gave me this (currently) stable 1333 FSB.

4.00GHz (12x333)
Vcore Voltage: 1.550V Bios set -> 1.50V Bios Read -> 1.440V idle -> 1.408V Blend -> 1.376V smallFFT
Memory Voltage: 1.8v
1.2v HT Voltage: 1.3v
NB Core Voltage: 1.4v
SB Core Voltage: 1.55v
CPU VTT Voltage: 1.4v

FSB - Memory Clock Mode: Linked
FSB - Memory Ratio: Sync Mode
FSB (QDR), Mhz: 1333 (means 333FSB)
MEM (DDR), Mhz: 667 (means 333mhz speeds)

Memory timings are loose ATM:
CL: 5
tRCD: 5
tRP: 5
tRAS: 13
TRC: 19
CR: 2T

Temps
-45C idle -> -35.6C CPU Loaded (Vapochill)
470W idle -> 660W Loaded (system w/LCD at wall)
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
Several things.

I'm not sure how voltage deviations from "set" VARY between motherboards, but I have two of them and I think they are consistent.

For IdontCare, go back to BIOS version 1301 and see what happens.

Here are my settings for two stable OC settings at 3.0 Ghz under either version 1301 or the unavailable 1303 (emphasis: either one):

1:1 CPU : RAM
VCORE = 1.31875 to 1.32500V
FSB = 1,334
DDR = 667
VDIMM [Crucial Tracers or Ballistix] = 2.150V
1.2VHT = 1.30V
NBCore = 1.35V
SB = Auto
CPU_VTT = 1.35V
Timings: 3,3,3,8,1T, tRC = 11

4:5 CPU : RAM
VCORE = same
FSB = 1,336
DDR = 835
VDIMM = 2.125V
1.2VHT, NB, VTT = 1.35V
SB = Auto
Timings 4,4,4,10,1T, tRC = 14

I think coolamasta is a tad too low on the RAM voltage.

With the Ballistix DDR2-1000's, I was able to run up to FSB = 1,424 and DDR = 712 with VCORE @ 1.41875 to 1.412500V

This goes to 3.2 Ghz with 1:1.

The VDIMM memory voltage, however, and at that setting, should be somewhere between 2.175 and 2.2 depending on the timings. I don't recommend 2.2. 2.175 comes "awfully close." As I said, there's a bias (with BIOS 1301 and higher) of -0.035V to the "set" value compared to the BIOS monitor. IF BIOS monitor is "accurate," then 2.175 is really 2.21V

For the 3.2 setting at 1:1, the HT, VTT and NB probably need to be set to 1.40, 1.45 and 1.45V respectively. The timings were variously set to 3,3,3,8,{1T or 2T}, and 3,4,4,8 (which might allow a drop in voltage by one notch). You could drop the voltage again or probably get it down to 2.125 with 4,3,4,9 -- and certainly with a 2T command-rate, I think.

3.15 Ghz probably still requires VCORE = 1.41875V, and a 4:5 ratio puts the RAM DDR at 875. There, I think I was able to keep the RAM voltage down to 2.125V, and 2.15 would probably resolve any instability. I also think the timings were 4,4,4,10,{1T or 2T}, tRC=14.
The HT, VTT and NB voltages were 1.30, 1.35 and 1.35 respectively.

I haven't experienced any instability on these settings, except in the process of achieving them. However, there is at least one other variable factor in my configuration versus coolamasta's and probably IdonCare's -- the power-supply. All I can say is that I'm using a Seasonic M12 750W.

And especially one more thing. My motherboard ducting has assured that the NB chipset, even at 100% load under PRIME95 -- never, never exceeds 43C degrees at a room ambient of 70 to 75F. The ducting provides the same cooling to the entire copper "heatpipe necklace" and the components it cools.

The only time I had instability at the higher settings arose when I added a 1GB (2x512) kit of Crucials to the mix for a total of 3GB. It proved stable under PRIME95 for several hours, but eventually I ran into trouble with it.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
Oops. One more item.

Idontcare is using a QX6700. I think our experience in this forum is fairly consensual in that it appears the binning of these CPUs results in some . . . . average, statistical trend or indication of low-end processors being more "over-clock-able," and higher-end processors being less "over-clock-able," although the unlocked multiplier feature throws a new twist into the equation.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
Incidentally, Idontcare -- looking at your timings -- yes -- they are loose, but the tRC setting is almost as low as it can go for those settings. I've taken a risk to set it so that:

tRC = tRP + tRAS

My earlier explorations of tweaking the bank-cycle-time gave it an extra clock cycle, such as your settings show.

Also, I was stunned at your choice of a voltage setting -- yes, I know that's what the EVA2000 forum post shows with early BIOS revision. But also, we discovered that the discrepancy between set and monitored voltage values seems to have resurfaced with BIOS 1305. It is especially revealing to see your load voltages under the different tests.

So if load voltage is the most relevant, significant criterion for stress on the processor, and small FFT test shows 1.376V, your processor is probably at no more risk than mine at my highest over-clock settings. That is, for mine, 1.42V under BIOS 1301 gives 1.41 to 1.42 in the monitored value, and I think my "drooped" Vcore under load is about what yours is for small FFTs.

If the QX6700 has stock multiplier (bus-to-core ratio?) of 10, 4Ghz versus 2.66 is nothing to sneeze at. Gee Whiz!!
 

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
Well BonzaiDuck I already know my particular applications are predominately CPU limited (they peg utilization at 100% on all 4 cores) so juicing lower latency on the memory is something I want to do mostly because I want my money's worth and not necessarily because I expect to see a return for the effort. Hence loose timings for now until I find a stable CPU/FSB overclock combo.

For example I am pretty sure I could drop the CR from 2T to 1T and see a healthy boost. I hope so anyway. Should get to that part of the optimization later today if all goes well.

Just an update on the 4GHz (12x333) stats up above, Speedstep got me somehow and the multiplier was running 10x at load despite my setting it to 12x. (yes this is an unlocked chip) I caught it by running super-pi and realized the scores were a tad to slow for a 4GHz chip.

Turned off speedstep, C1E, etc and am now running 4GHz per CPUz and per super-pi times. Took more cowbell, er Vcore, though...am running 1.6V Bios set which comes out to 1.488V idle in windows. I am not too worried about this Vcore as I am running -35C temps. However it still isn't stable so I may be hitting Bios 1301 soon.
 

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
Am checking out 1401 BIOS at the moment. Nothing special for me.

By the way, if you want 1303 it can still be downloaded directly from ASUS ftp server.

Direct link to 1303 bios download

General link to Asus FTP server

I will probably checkout 1303 after my current round of tests, am not having any luck finding stable settings for 12x333 on my B3.
 

coolamasta

Member
Jan 8, 2008
57
0
0
Right then, been playing with memory and fsb settings and found that running the crutials @ 1067mhz with the cpu @ 1334 5:4 it wasn't stable in memtext86 after about 20 mins but I was on 2.150v for mem...

Decided to try your settings:
4:5 CPU : RAM
VCORE = same
FSB = 1,336
DDR = 835
VDIMM = 2.125V
1.2VHT, NB, VTT = 1.35V
SB = Auto
Timings 4,4,4,10,1T, tRC = 14

and after a quick hour mem test and 2 hours or so on prime95 all seems fine.

what is better for memory latency and bandwidth? 667mhz (1:1) or 835mhz (4:5)

will see how this goes for the next few days and report back

Oh and although I set the memory to 4,4,4,10,1T, tRC = 14 in the bios they show as 4.5.5.16.1T tRC 20 in CPU-Z, whys that?

Thanks for your help again mate, you are a legend with this board :D
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
Originally posted by: coolamasta
Right then, been playing with memory and fsb settings and found that running the crutials @ 1067mhz with the cpu @ 1334 5:4 it wasn't stable in memtext86 after about 20 mins but I was on 2.150v for mem...

Decided to try your settings:
4:5 CPU : RAM
VCORE = same
FSB = 1,336
DDR = 835
VDIMM = 2.125V
1.2VHT, NB, VTT = 1.35V
SB = Auto
Timings 4,4,4,10,1T, tRC = 14

and after a quick hour mem test and 2 hours or so on prime95 all seems fine.

what is better for memory latency and bandwidth? 667mhz (1:1) or 835mhz (4:5)

will see how this goes for the next few days and report back

Oh and although I set the memory to 4,4,4,10,1T, tRC = 14 in the bios they show as 4.5.5.16.1T tRC 20 in CPU-Z, whys that?

Thanks for your help again mate, you are a legend with this board :D

I'm flattered.

The CPU-Z data comes from the eeprom SPD / EPP area of the memory. It shows the guaranteed latency settings at those respective speeds -- IF you are accessing the tab window "SPD". If you are accessing the "memory" window, then something is really screwy there. My CPU-Z shows the "set" latencies just as I set them.

This is most strange, considering that you used my settings to get at least 2 hours stable. I usually test a setting configuration for between 6 and 13 hours. 2 hours indicates to me that if it doesn't last for half a day, you're pretty close to it, and it's "achievable."

Latency requirements mean looser settings as you increase the FSB. So at 667, you are likely to find settings with CAS=3 to be good. There would then be a range over which those settings continue to be stable as FSB increases, and the increase in FSB would require an increase in VDIMM or memory voltage to maintain the tight latencies. Conversely, as you increase the FSB (we're talking about 1:1), you can also loosen the latency settings, quite possibly making it tenable to decrease voltage a tad.

A review article that got me started with the Crucials -- so that I didn't have to experiment blindly -- suggested that settings of 3,4,4,10 were good through around 775 Mhz (DDR); 4,3,4,9 was supposed to be good between 775 and something like 840.

Now that I look at the Anandtech review on Crucial memory, the other reviewer may have had it wrong about 3,4,4,10, but he was probing memory speeds in the 740 to 775 range, and didn't mention lower settings -- as i recollect (and I could be wrong). It was a German review, and my fluency in German is limited -- Ich spreche kleine Deutsch, und viele Jahre seitdem meinem Tage auf Universitat.

but the article had tables of latency results at different CPU : RAM ratios and FSB speeds.

The best Everest memory benchmark "read" result I got at between DDR 710 and DDR 712 was below 9,700 -- more like 9,650 if I remember -- with a 1:1 ratio.

With 4:5 and DDR 835, I get about 9,500. But with FSB = 1,400, 4:5 with DDR 875, 2.15 to 2.175V, the bench result is 9,750. I think that's with the processor at 3.15 Ghz.

While I can get it rock-stable -- now to think of it, my notes show this:

3.15 Ghz
350 Mhz CPU_FSB
1,400 FSB; 875 Mhz DDR (RAM 437.5 = 5 * (350/4)) || CPU:FSB_ratio = 4:5
VDIMM = 2.125V
VCORE = 1.40625V
1.2V_HT= 1.35V
NB_Core = 1.35V
CPU_VTT(FSB)= 1.35V
SB_Core= 1.55V

So the voltage requirement may only be 2.125V.

Now . . . . . the CPU Power-User Magazine reviews of DDR3 modules when put through their paces are blown away in Everest benchmark comparisons with these settings.

Also -- I think I'd bump up the VCORE as shown above to 1.41875V. The "Droop" under load will bring it back to between 1.36 and 1.38V. I know for sure that the higher setting was stable for many hours. Here's the remainder of my notes on those settings:

Timings: 4,4,4,10,1T,tRC = 14
Certified, 8 hrs sFFT; 6 hrs LFFT; 5 hrs Blend @ VCore=1.40625V and 9 hrs Blend at VCore = 1.41875V

Despite the way I phrased my "Certified, . . . . " line, I believe I manually terminated every one of those tests to show 4 x {0 errors, 0 warnings}

Also, many thanks to Idontcare for providing the ftp link to BIOS version 1303. But again -- why does it not appear on the BIOS download page with the other versions 1301 and 1305?

I thoroughly enjoy the Chinese, and taught Chinese graduate students for ten years. Halcyon days. But there is a stereotypical trait -- often described by the word "inscrutable." I cannot figure out why they've obscured the 1303 version, whether this is a random inconsistency, or some . . . . deliberate choice. For now, I'll stick with version 1301. When I upgrade to an E6850 or a 1,333FSB Penryn, I'll flash the BIOS again with v.1305.
 

BonzaiDuck

Lifer
Jun 30, 2004
16,705
2,081
126
I've noticed some anomalies and problems with SpeedStep at certain settings. the troubles I had with the 3GB = 2 x 1GB + 2 x 512MB of memory arose when I had SpeedStep "enabled."

Definitely -- I will tell you this: SpeedStep doesn't seem to work properly at lower mutlipliers below the stock value, because at idle, it resets the multiplier to 6. I have no idea what happens when you increase the multiplier with an unlocked processor and enable SpeedStep.

I've also heard you're better off to enable C1E, but I want to experiment with it cautiously.

 

Idontcare

Elite Member
Oct 10, 1999
21,110
64
91
Well gentlemen I'm out. After 3 days of literally spending every waking hour trying to get this system running the striker extreme mobo has died. It was an exasperating death too.

Spent sooo much time fighting phantom stability issues, and it just seemed like for every hour that passed I lost more and more.

Mobo simply won't post now. Nothing I do will revive it. Even changed CPU, simply attempting to post with nothing more than PSU plugged into board and a CPU. LCD screen just hands on "CPU INIT".

I know what probably did it too. Those damn VRM solder pins that stick out so fricken far are notorious for shorting out on backplates. I got two of the looking and nice and crispy black right now.

And so ends a year long hate/hate relationship with my Striker Extreme. Now I have to figure out what mobo will replace it. I am thinking not Asus.

Good luck gents, don't let my negativity deter you from enjoying your Striker boards, I am sure your experiences are 100% unlike mine.