Should I try to get all RAM timings low as poss?

keogh

keogh

keogh

Soldato
Joined
22 Jun 2004
Posts
2,756
Location
Bangkok, Thailand (formally London)
Howdy,

I've been fiddling with my timings for my ram (sig) and I want to know, should I be trying to get ALL my timings as low as possible?

The reason I ask is, just know I set my timings back to default (well I thought I did), but instead of setting my Tras to 12, I set it to 4. My PC booted fine and orthos ran for a bit without stopping? I stopped it myself cos I wanted to try sumin else out.

But a Tras of 4 is far too low to work right? I mean that should have not allowed me to boot right? I mean from 12 to 4 is a HUGE jump?

ta

Steve M
 
Intel loves clocks, AMD loves low-latency.

If you're sacrificing clocks for lower latency times then I wouldn't bother. If you think you can tighten your timings a bit without losing clock speed then go ahead. It won't make that much odds on current Intel systems though.
 
Well im running my CPU:RAM ratio in Sync mode, anything else and I seem to get random boot failures. As I have my CPU at 3.4ghz at the moment, and ratio in SYNC my PC6400 is running at 755mhz. I cant change my CPU mulit down to get closer to the stock 800mhz, so I thought id fiddle with the timings seeing I cannot get the clock higher.

If I could get my clock speed closer to 800mhz Id be happy, but I cannot without either 1. Uping my FSB effectively uping my CPU clock to 3.5/3.6 at which point I need to up my vcore too much and my temps get to 59c/60c or 2. Changing my multi which I cannot do?

I got my CAS to 3 from 4, but Super Pi seems to take 1 second longer? Thought the CAS would have sped things up?
 
BEn_2600+ said:
Run memtest to make sure its stable and not getting any errors:)

http://www.memtest.org/
Click to expand...

yeah i got my memtest floppy in waiting to run, but i wanted to get into windows and run a quick large fft to see if it works. then once i get to a point im happy then i will run memtest.

Takes a while to run all 8 tests, so I didnt want to do that on every change :)
 
BEn_2600+ said:
Yeah i know what yu mean it is a bit tedius waiting 30mins ish between clocks :(
Click to expand...

Sure is.

Ok I have it to the lowest timings I can get before I get no booting, Im at 3-4-3-10 755mhz and I get 2 seconds quicker on Super Pi than at the stock of 4-4-4-12.

Im now running memtest and will leave it for all 8 tests and see if I get errors. If not I will then run orthos all night again, and I think I can then safely say I am at the peak of my clock of 3.4ghz and 3-4-3-10 2T.

Wish I could get 3.5ghz at least from my 6600, but I have to go to 1.525v+ vcore to get that, and I start hitting 59c/60c then. You reckon thats too hot?
 
You should be fine upto 60C what are you using to monitor temps? Some people are comfortable upto 65C+ But personally i would only go to 60C or <65 Max, just goto what your comfortable, its your chip at the end of the day :)
 
BEn_2600+ said:
You should be fine upto 60C what are you using to monitor temps? Some people are comfortable upto 65C+ But personally i would only go to 60C or <65 Max, just goto what your comfortable, its your chip at the end of the day :)
Click to expand...

Im using Core Temp, I always use that... seeing as TAT doesnt work on my PC.

Im so use to my X2 that where not happy 60c above that I have used that rule for my C2D. I would love to get 3.5ghz, but to get that stable I reckon I will be at least 61c/62c on full load... and thats just too much.

Although I do have QFan enabled to keep my Artic 7 silent... its a bit too noisy at full pelt. I reckon with it on full I might get a max of 59c... but tbh Id rahter have the silence and 3.4ghz!

I gotta see if 3.4ghz is ok yet though, orthos run for 16hrs no probs, but I set it to 3.4ghz before and orthos ran for 19hrs. But I was getting random boot failures and BSODs in games, so I went back to 3ghz.

I've made many other changes in the BIOS from the last time though, including running linked : sync opposed to unlinked CPU:RAM... I'm quite sure it was that causing it, as the ratio it was doing was crazy and I dont think the P5N likes it tbh.

Ill see how it goes... might even get a Tuniq Tower one day, they are suppose to be cool!
 
Anyone notice weird things happen on orthos when you set to priority 6? it run really slow, then crashed (but my PC didnt). So I rebooted and set my RAM to stock and tried again, didnt crash this time but run really slow and was odd.

Set it to priority 8 and it runs fine? Prob just me, but that seems odd?
 
BEn_2600+ said:
probally an orthos error with it being beta still :)
Click to expand...

could be right. Im out of SYNC mode now and gone for 3:2 and my RAM is at 1008mhz, ive been going thru the timings gradually, and i think (empashis the word think) im ok at 5-4-4-12 2T @ 1008mhz which is cool. 4-4-4-12 causes BSODs so the CAS will stay at 5.

Suer Pi is now 3 seconds faster, and I am running orthos for a few seconds now to see if it errors early. Then I will run memtest, then back to orthos for many hours... if all goes well I am done! My overclocking will be finished and no more reboot, reboot, reboot and more reboot :)
 
You must log in or register to reply here.
Back
Top Bottom