Thanks for the help getting over 280HTT, now some help on a RAM speed issue please

[Sparky]

Got it fixed now, see my last post at the bottom for my final results :)

-----------------------

Thanks to the suggestions on how to get over the 280MHz HTT barrier :) Now I have another problem. :rolleyes:

First off I am currently running orthos at 315x9 = 2.84GHz with 1.36V vcore, with 320HTT orthos failed within seconds on core 0, upping vcore helped it last a minute or two before failing so I dropped back to what I'm at now and so far so good.

Now here is the problem: My RAM is on the 100 divider, so my RAM speed is only at 157MHz. I'd like to get it back up to 200MHz where it belongs, and it can go up to about 210 I know with no problem. Now the 133 divider would put it back up there, but when I select it the system won't even POST.

Here is a pic of my current RAM settings from CPU-Z:

http://i58.photobucket.com/albums/g270/SparkyJJO/slowram.jpg

I have tried raising the max asynch latency a little more (currently at 10), loosening the timings from 2.5-3-3-6 1T to 3-3-3-6 1T and 3-4-4-7 1T and no go. Any ideas on how to get this stuff back up to speed or am I just stuck at 157MHz? If I am stuck which would be better, 280x9 = 2.52GHz on the CPU with RAM at full speed or my current 315x9 = 2.84GHz with ram slowed by 40MHz?

Thanks for your time guys, I greatly appreciate it! XS is the best :toast:

[markr]

Use A64Info and try the 120 divider from windows.

http://avala.yubc.net/~lukija/A64Info-beta.exe

[shadow_419]

You could try running at 2t and see if that allows you to use a smaller divider.

[Sparky]

I failed Orthos after a little more than 2 hours on core 0. No errors, just warnings but it told me to go to the readme file (which doesn't exist?) And then a few minutes later my computer just SHUT OFF. As if I pulled the plug. Pushed the power switch and it came right back on :confused:

Any ideas?

[cantankerous]

usually a system shutdown is due to a psu not being able to keep up to the load or due to temps being too high and it shuts off as a safety measure but you said you now have good temps after popping the IHS right?

[Sparky]

usually a system shutdown is due to a psu not being able to keep up to the load or due to temps being too high and it shuts off as a safety measure but you said you now have good temps after popping the IHS right?
Yeah temps are only a couple degrees warmer than they were on my single core 3700+ and I've seen where people have had their CPUs running warmer than mine without shutdowns.

I did try changing my X1900XT from one PCIe cable to the other and it didn't change anything.

Well so far Orthos has been running for 4 hours straight and no shutdowns... Maybe the shutdowns were due to instability?

[cantankerous]

who knows, just keep an eye on it over the next few days and see how it does. 4 hours is a good start but keeping it going. Let us know what you come up with as a final overclock and at what ACTUAL voltage, not a bios readout as it will always be lower than actual.

If it shuts down again I would suspect your psu.

[Sparky]

Current speed 2.8GHz @ 1.325V bios, 1.36 actual.

http://valid.x86-secret.com/show_oc?id=137373

But a strange thing just happened. Orthos was running fine for 15 hours and 38 minutes and I tried to load up CPU-Z to validate and it just froze up :confused: Rebooted, tried again, worked fine. Temps aren't super high, little bit warm I suppose (50 for core #0, 53 for core #1) under full load.

Any idea why CPU-Z would crash my system? :confused:

[cantankerous]

sounds similar to me. I can orthos or do anything stress related with my cpu at 2.82ghz however last week editing my resume in word locked up my system. Rebooted and everything was fine. Ran orthos just about every day after that for hours on end without issue. Never locked up again since either.

Don't you just hate when stuff like that happens? Trying to track down the problem is near impossible if it doesn't repeat itself. After awhile you have to get the same point I did where you stop worrying about how high/stable you can get and just enjoy your system. If it works the way you want it to for what you do with it then just enjoy it.

say, what video card are you running? Run some 3dMark 05/06 and let me know what you come up with. I want to compare it to my scores since our cpus are nearly identical.

ALSO, you managed to get higher than 2.8 or are you going to stay there?

[Sparky]

I got to 2.9GHz with only a very slight voltage bump but then heat became my enemy. So I dropped back to 2.8GHz at stock voltage and it seems to be liking it there (aside from that random lockup). I'm happy there, my old 3700+ was at 2.86GHz so only 60MHz slower than it but then double the cores is cool with me.

Once I go water though, I expect to go higher. I can tell this chip can go higher if I could cool it better :)

BTW I have a X1900XT

[tictac]

the trc ... can you lossen it a bit... maybe 15clocks

[Sparky]

15? OK I'll try that. I did try loosening it to 10 and it didn't do anything, but I wasn't sure how far to go with it and being fairly clueless about all this ram timing stuff I didn't want to mess with too much before consulting the pros here :)

[cantankerous]

I got to 2.9GHz with only a very slight voltage bump but then heat became my enemy. So I dropped back to 2.8GHz at stock voltage and it seems to be liking it there (aside from that random lockup). I'm happy there, my old 3700+ was at 2.86GHz so only 60MHz slower than it but then double the cores is cool with me.

Once I go water though, I expect to go higher. I can tell this chip can go higher if I could cool it better :)

BTW I have a X1900XT

what temps were you getting at 2.9ghz that you felt you were too high and what temps are you getting now at 2.8ghz? Not core temp readings please but say everest, systool, smart guardian etc. Thanks.

[Sparky]

what temps were you getting at 2.9ghz that you felt you were too high and what temps are you getting now at 2.8ghz? Not core temp readings please but say everest, systool, smart guardian etc. Thanks.
PC Probe/everest would was about 50 C and coretemp was getting up to 57 or so. I didn't like it so I backed down. I'm happy at 2.8GHz for now though :) But come water and I'll go higher :D

[Sparky]

I FINALLY got around to adjusting the RAM timings. I loosened the TRC to 15, TRFC from 10 to 12, and the TRWT from 4 to 5. Any tighter and it wouldn't POST. But now my RAM is back at 200MHz where it belongs. It doesn't OC well at all unfortunately, oh well. The main timings I still have set at stock 2.5-3-3-6 with the 1T command rate.

My final CPU speed is 2.81GHz (9x312) stock volts with max load temps of 47-48 C according to PC Probe, 53 C in coretemp (hottest core). And no more random shutdowns for over a week! Whatever the glitch was I think worked itself out :)

CPU-Z validation (http://valid.x86-secret.com/show_oc?id=139895)