RAM running a little slow after my overclock

[BigCoolJesus]

Info on last page

 

[DarkKnight69]

superpi usually crashed for me under instablility,

Prime95 is good, if you are really unstable you will crash in 1-2 minutes...If you do not crash that fast let it run 6-12 hours, if it still doesnt crash, you are good to go!

 

[DarkKnight69]

superpi usually crashed for me under instablility,

Prime95 is good, if you are really unstable you will crash in 1-2 minutes...If you do not crash that fast let it run 6-12 hours, if it still doesnt crash, you are good to go!

 

[BigCoolJesus]

well i just did a SuperPI 8m calculation in 7mins 30 seconds, so does that mean im still stable? (only at 2,5GHZ right now)


i might try Prime95, but i never liked it that much

 

[theMan]

prime95 is the way to go. you should slowly increase your overclock, and run it for 5 minutes every time you increase. as soon as it fails in those 5 minutes, decrease your overclock by 5%. then run it for like 12hrs. it should pass. then increase it a bit more and run it for 12hrs. see how high it can go before it cant do 12hrs. it probably wont get much above that 5% drop.

 

[BigCoolJesus]

well, is it worth it to get Prime95?

it seemed a lot harder to use then what i expected when i tried it a year ago

 

[BigCoolJesus]

well i hit the wall

anything over 2.6GHz cuases windows to either freeze up, or my BIOS to boot in safe mode


now onto the RAM



one question, if i set the RAM at 166MHz, but the CPU clock is running at 240, that means the RAM is actually operating at 406MHz, right (ie, DDR400 basically)?

 

[BigCoolJesus]

OK, heres the final result

the CPU Ratio (FSB) is at 237MHz
Multiplier is at 11x
Vcore is at 1.55
Vdim is at 2.7
RAM frequency is at 166MHz (the system would boot if it got any higher then 205, so i have to use the divider)

this gives me exactly 2.6GHz, with a RAM speed of 403MHz (right?)


how is that for a 3500+Venice?



another question, when the system wont boot, or it freezes due to to high of a CPU frequency, is that just because the Vcore is to low? (ie, if i raise the Vcore more, will i get any more speed out of the CPU)?

 

[Shimmishim]

yes you can raise the vcore and it should let you boot if it can run that speed even unstably.

if i were you though, i'd still run prime95...

superpi is good for testing mem and for initial testing but that's about it...

 

[BigCoolJesus]

yea, im gonna run Prime95 while im gona tonight (about 4 hours)
I just ran a quick Memtest86 (1 cycle) and passed with no errors, will run for more tomorrow


so everything is looking good so far, temps are at 33C idle (XP-90C)
Im a little dissapointed in the RAM though, had some good hopes for it (OCZ ValueSelect, heard good things from it though)


anywho, once again, if im running the RAM at 166MHz, with a CPU FSB of 237, that means the RAM is actually running at 203MHz right?



Also, is it worth raising the Vcore more to get some more out of the CPU, or for stability and heat sakes, should i just stop at 2.6GHz?

 

[Shimmishim]

for memtest you need to loop test #5 for hours and hours.... i loop test #5 for at least 6 hours before i can call it somewhat stable...

as for prime, you need to do a minimum of 6 hours.... i've had an error pop up at 5 hours 35 minutes before....

 

[BigCoolJesus]

i made it 2 hours on prime before i got an error


says there was a hardware failure, etc



so does this mean i should back down the CPU speed (maybe to 230, instead of 237)?

 

[BigCoolJesus]

below

 

[BigCoolJesus]

Right now, these are my current settings

CPU Ratio (FSB) - 234MHz
CPU Multiplier - 11x
RAM frequency - 166MHz
HTT - Auto
Vcore - 1.58
Vdim - 2.7

This gives me 2.57GHz on the CPU



My first question is, with a FSB speed of 234, and a RAM speed of 166MHz, this equates to an actual RAM speed of 400MHz (DDR400), right???




Ok, now the reason im frustrated is i dont know why im getting SuperPI errors.

Earlier in the day when i tested SuperPI with the DDR at 100MHZ and the CPU running at 2.7GHz (11x multiplier, FSB at 247) i was able to do 16M in 15 minutes without any errors.

But now that its running at more stable settings (RAM is exactly DDR400, CPU is running at 2.57GHz, less then what it was doing before) im getting errors speratically on SuperPI
I can go up to 1m, but anything over that and i get rounding errors, or other things of that nature.

Any idea why?
Could the Vcore be to high/low?
Vdim to high/low?

 

[NINaudio]

It's a ram error. You were running it at a lower speed before and had no errors. I would try raising your ram voltage a bit and see if that helps. What kind of ram is it?

 

[BigCoolJesus]

Originally posted by: NINaudio
It's a ram error. You were running it at a lower speed before and had no errors. I would try raising your ram voltage a bit and see if that helps. What kind of ram is it?

Its OCZ ValueSelect
Its stock voltage is 2.7, so should i try 3.0?



EDIT***

I (think) i have found the problem.

I set the timing for the RAM to 1T (instead of 2T) and that seems to be the problem, as everything was running at stock speeds and i was still getting SuperPI errors, but once i set it back to 2T it was fine.

I guess ill try the overclock again.


Also, what Vdim should i use if my RAM is defualting to 2.7?

 

[BigCoolJesus]

OK, I GOT IT TO WORK.

YAY


how stupid was i


after all this, it was a timing problem
I set the RAM to run at 1T, but the stock is 2T.

I went back, put it back on 2T and now everything is running great.

SuperPI runs without errors on a 2.57GHz overclock

Multipler - 11x
FSB - 234MHz
RAM - 166MHz
VDimm - 2.8
Vcore - 1.58

yay


one last thing, my RAM is running at DDR400 since the FSB and RAM speed equal 400, right?

 

[GuitarDaddy]

How many sticks? What are your timings?

If your only using two sticks it should run 1T, 2T puts a pretty big hit on performance. 1T with looser timings would be much better.

And don't go from 2.7 to 3.0:roll: try 2.75 then 2.8 then 2.85, I wouldn't go over 2.9

 

[BigCoolJesus]

2 sticks of 1GB
i think timings are 3-4-4-8

Seriously, 1T was the problem, as im now at 2.6GHz (260 x 10, RAM at 133MHz, so its running at 393MHz, which ill accpet) and SuperPI is running fine.

Im keeping the VDimm at auto, since the RAM is running under stock speed (393MHz instead of 400MHz)


Also the VDimm seemed to cuase some problems, because if i have it at anything other then Auto (or 2.7, which is stock) i get major artifacts (and lock-ups) in Aquamark.

 

[BigCoolJesus]

One last question


If the FSB (HTT) is set at 260, and the RAM is set to run at 133MHz, does this mean that its actually running at 393MHZ (260+133)??

is this to slow?

 

[Avalon]

Originally posted by: GuitarDaddy
How many sticks? What are your timings?

If your only using two sticks it should run 1T, 2T puts a pretty big hit on performance. 1T with looser timings would be much better.

And don't go from 2.7 to 3.0:roll: try 2.75 then 2.8 then 2.85, I wouldn't go over 2.9

2T won't do squat to performance by itself. It will cause a 1-5% performance hit at the most.

 

[BigCoolJesus]

well i just got done running Memtest86 for 6 hours.

0 errors, all passes

now onto Prime95 to ensure this baby is stable

 

[Furen]

2T command rate is slightly worse than CAS 3 instead of 2 (like -2.9% average as opposed to like -2.5%). The command rate also lowers your mem bandwidth by quite a bit, so some tasks (like winrar) will take bigger hits.

 

[BigCoolJesus]

yea, but theres nothing i can do about it so i dont mind

Just ran Prime95, 0 errors, and everything is working good (highest temp i got was 42C)


if im running my FSB at 260, and my RAM is set to 133MHz, whats the actual frequency my RAM is at?
(393 right?)

 

[Leper Messiah]

Originally posted by: BigCoolJesus
yea, but theres nothing i can do about it so i dont mind

Just ran Prime95, 0 errors, and everything is working good (highest temp i got was 42C)


if im running my FSB at 260, and my RAM is set to 133MHz, whats the actual frequency my RAM is at?
(393 right?)

I made a thread somewhere about a month ago about A64 RAM speed, but I shall reiterate, yet again (mods...a sticky would be nice. This is like the 5th time I've said this this month...)

R= C([M/D]) where R is ram, C is CPU speed, M is CPU multiplier, and D is your RAM divider expressed as decimal number. So, for you we get R= 2600([10/.66]) which simplefies to R=2600/15.151 which is like 172MHz or so...