Tref values

[Mardok]

133 MHz 7.8us = in bios = 4128

[mad mikee]

Just trying out my table, tried 2336 (see my table above, = 299.5 FSB @ 7.8) and running memtest on 300x9 2.5-3-3-6 @ 2.65 Vdimm (will pass test 5 no problem, (runs and checks again in 'da lab' ) looks like test 8 also ) Would never have gotten that value from anywhere else. And since the CPU fan is temp controlled on the test bench, get audible indication of what stresses teh CPU more. (This seems to not stress it as much when you 'get it right'. ) Also if you can a slightly less FSB value seems to work better than a value that is higher than the target FSB..

All the exponents cancel out after all is said and done so just take a TREF value (cycles) and divide by the 'offical' refresh rates (15.6, 7.8, etc) which is how I got my table. Seems like 7.8 is a good value so far . That is how I got teh table above. It is also helping me to get 250x11 @ 3.27vdimm(PITA since there is nothing in the table between 236 and 263 FSB so its a crap shoot), will find out if all this helps vcore also later today.

Oh well, back to testing!

P.S. Read up on the GSkill 3200 thread, Agent-JC gave me the other part of the equation for fiddling w/ drive strengths.

@WSP: use space a column marker, or grab it and dump it into a .txt doc and tab it out (sorry no table software on this machine) make improve your settings

[WeStSiDePLaYa]

anybody got any more info on how to set my tref accordingly? i would think this would be highly researched as it can have a HUGE impact on bandwidth.

[The Mofo]

Im sure someone in the programming/coding forum can come up with a simple GUI proggie to convert the values. Try posting in there.