Printable View
OK, i have 2gb of corsair xms2 RAM in my system that is running with 313.2mhz and latency timings of 5-5-5-15, but then it says w\ cpu-z that it will run at 266mhz with timings of 4-4-4-12...
would my system run better with the memory running slower with faster latency rates or as it is now....?? any help would be appreciated.
i dont really want answer B:"your ram sucks.... buy better ram" lol thanks anyhow though.
Try to lower the timings one by one manually and see if it works or is stable. If it's good, stick with it. Otherwise you really have no choice but to use 5-5-5-15.
For DDR, timings was a major factor. However it's not that important for DDR2. The improvement from tigher timings will be offset by the loss in clock speed.
The high frequency will result in better performance if your FSB can handle it. In your case it would take 5 cycles from the request to the first bit, but you are doing 313,000,000 cycles a second, in the second it would take 4 cycles but you are only doing 266,000,000 a second. So if the rest of your system can handle it the faster frequency will be better.
Ok, i've returned to this thread. I was reading a little about timings earlier today and pulled up the specs for my memory and they are :
* Each module pair is tested together in an Intel-based motherboard at 667MHz
* Tested and packaged in pairs
o Packaged together immediately following system test
* Tested at JEDEC-standard latency settings (4-4-4-12) at 1.9V
* SPD programmed at JEDEC standard 4-4-4-12 values
Is there a reason why mine are not running at 667MHz ? Is there something that i have to tweak in order to get this speed? I will have to wait until tonight to pull up cpu-z on my computer and see if the setting is still the same w\ vista installed.:confused:
It's not running at 667? What is it then?
when i last had my system running it was jumping between 200 and 330 or so. or is the 667 going to be represented as 333 x2 for ddr?
Yes. Always divide the number by half.
*feels like a nub*
mk... i was worried that it wasn't performing at the right speed. thanks :)