Very nice mrlobber. I agree so can't really say much more.

TBH I'm messing with AMD's X4 now trying to get its problems sorted because the C2D was boring me quite a bit with SPi inconsistencies. I much prefer to use a C2 lappy or a Dothan given the option.

Also one bit I left out is, I have to uninstall my VGA each time I test now which I do hate quite a bit. Blame ATi drivers for this. I also swapped my PSU because they needed the other with a Seasonic S12II 330W now (hi-pots) and its drops 0.2V on all rails under load, which is bad since the rails are very low to start off (was reading 3.1V on 3.3V rail under load recently).

Times are quicker with higher FSB for me and on ASUS boards (especially P5W DH->very quick in everything). Tried tests at 400, 450 and 470 very early with this, probably the first thing I did. With the Corsair running PL 6/7 made no difference in 32M for me. With the Crucial it makes a good difference. But I can't change PL through the OS and at bootup with the same BIOS settings, randomly, it may choose PL5 or 6 or 7 at different times.

Like I said, you can't really analyze Super Pi accurately because it is so day to day and OS dependent regardless of timings/clocks. One day you try your best and get 14M quickest at x settings and at another, with x+1 settings messing about you get 13m 57s, so you just look at it and stare at the screen knowing you did jack different to get that. Beyond user control or understanding. That leaves me very frustrated.

It's only once you can get this problem fixed that you can start analyzing a tweak, because then the OS effect each time is "controlled/fixed" and not a variable affecting the times.

This is why you see timings of CAS 5-5-5-5-10/5-5-5-5-7/4-4-4-4 PL6/7/8 get close by times. Also, in 32M memory clock seems to make a good amount of difference for me but not in 1M/2M.

I ran the best CDT straight after that day and it drops seconds even further. But I'm not testing it on DS4 anymore, moving to Abit board now. Maybe it'll hit 500 FSB there.

I have to make a general observation: the Corsair XMS2 is running quicker than this Crucial Ballistix at the same settings/timings/OS, even in EVEREST, which puzzles me greatly.

Dinos22: I find 1M very incosistent with a perfectly new OS. Depends on day to day. One day it's uber quick and the next its uber slow at same settings with no other difference from a user perspective. I also find 32M similar, differing on day to day but it's more much consistent and replicatable.

T_M: Something I've explained many times in this thread. 384-384 or 512-512 makes no difference in 4M-32M from my testing posted early so I choose 384-384 because it's better at 1M for me and so I don't have to reboot to change it time and time again.