Stuck at 210mhz...

[Ritalin]

Hey people, my ram will be rock stable at 210mhz and pass memtest without a single error. But at 215 prime will crash after maybe 30 minutes. And at 220 it wont even go into windows. All this is using 2-3-3-6-8 timings at 2.85v.
What can i do? Relax timings? SPD gives me 2.5-4-4-8... what should i do?
Ritalin

[stan03]

yea relax the timings. or change the divider

[Grandpa Dan]

With pc3200 I don't think even relaxing the timings will give any more than about 3-5mhz more if that. If everything is that solid at those #'s. I would switch to the 5:4 divider and really start pushing the fsb up. See if you can get back to your mem @ 200, That would a great oc with a 2.8c.

Your sys will perform better with a little slower fsb and tighter timings.

[Ritalin]

yeah but is it even worth it? how much better will the results be if i higher the fsb at 262 or 263 at 5:4 to get 210mhz at the ram in comparison to keeping it all at 210 at 1:1?
EDIT: well that was easy, no boot to windows at 250mhz 5:4 with 2-3-3-6. What now? I think i was told that could be due to nb cooling unsuficient, not sure.
Ritalin

[stan03]

up the vcore, slacken timings a little more maybe. try upping the vcore first.
yes the faster cpu is better than the 210 1:1.

if that ram is bh5 you should be able to get much higher than 210, cna you give it more than 2.8 volts?

[Speed_Mechanic2]

He's using GeIL memory, so it would be of GeIL's WLCSP design.

[Grandpa Dan]

Originally posted by Ritalin
yeah but is it even worth it? how much better will the results be if i higher the fsb at 262 or 263 at 5:4 to get 210mhz at the ram in comparison to keeping it all at 210 at 1:1?
EDIT: well that was easy, no boot to windows at 250mhz 5:4 with 2-3-3-6. What now? I think i was told that could be due to nb cooling unsuficient, not sure.
Ritalin

Can't say for sure(performance increase) on the oc till you bench it. I had probs at 250 even also. Try like 248, 251. Whats the vcore at? To get stable I had to take mine off auto and now it's set @ 1.5875.

If your not pushing any extra voltage to the Cpu the NB temp shouldn't be a prob.

[Ritalin]

The voltage is at 1.6 now... Ill try relaxing the timings I guess. Should i put the timings higher than 1.600?

[Grandpa Dan]

Originally posted by Ritalin
The voltage is at 1.6 now... Ill try relaxing the timings I guess. Should i put the timings higher than 1.600?

No, you may actually want to lower it a bit. Too high can be as problematic as to low. I didn't have to move my vcore from default(auto) until my fsb got over 290. What's your ram voltage @? and for some reason upping your agp voltage to 1.6 or 1.7 helps stability alot. What about your other settings? mam,turbo, dram burst. disabled all onboard devices not being used?

Crap, I'm not stupid just slow! @ 220 fsb what's your cpu running at? I just realized it's a 2.8 not a 2.6. Try clockgen it's made by the same people as cpuid. It got me to break the 300 barrier.

[Ritalin]

clockgen?
i disabled the onboard sound... what else can i disable?
ill put agp at 1.7v.
should i put the cpu voltage @ auto?
turbo mode is on either auto or disabled. mam... wow i never knew what that was...
dram burst is on 8.
What can i do?
Ritalin

[Grandpa Dan]

I would put the vcore @ 1.575. mam=memory acceleration mode, it's on the page w/ the timings. lock the agp/pci @ 66/33. try 2.75v. to the ram. Stay w/ the 320 setting for the ram. You can disable (if not in use) lan, 1394 controller, parallel ports. Set your ram timing manually to man. spec.

Clockgen is a free windows based overclocking utility. The guys @ ocaddiction referred it to me when i got stuck @ 299. Basically I was told to get my oc as high as possible via bios, then use clockgen.

[Ritalin]

ok i use the lan for sure, 1394 is the firewire? i dont use that and the parallel... not that i know of. I have everything on usb. so i can disable those two? what about mam and turbo? what should i do with those?

[Ritalin]

oh and also, isnt the higher the better for ram voltage? i can go up to 2.85v. Ill try at 2.75. For vcore 1.575. ill try that too.

[Grandpa Dan]

I run my ram @ 2.85. The danger point is like 3.2v on ram, which requires a volt mod. Correct on the firewire. Tough call on turbo & mam. start w/ both off. Then when your getting no errors you can try them enabled. I've tried them both ways a the gain is marginal at best when enabled. Try dram burst @ 4 to start, again the increase @ 8 is marginal. Have you gotten it to do anything? Try fsb a little under 250 to start(240ish). It seems like if you make a lot of changes at once the bios likes to hiccup those first couple restarts. Don't worry about memtest too much yet. just see if it will post.

Sorry about the delay was busy(Halo).

[Ritalin]

np ill try that soon

[Grandpa Dan]

What time is it there?

[Ritalin]

1:53 pm

[Grandpa Dan]

3:53 a.m. here...so pour the coal to that badboy and lets see what it does!!

[Ritalin]

oh ok do you have icq/msn/aim or something like that?

[Grandpa Dan]

Have what? Is that your only sys.? Thats gotta suck trying to troubleshoot if it goes down. All the other systems in my house are just a shared folder for me.

[Ritalin]

i have a laptop but there's nothing on it yet

[Ven0m]

afaik Golden Dragons don't like tight timings. I'd try maybe 2.5-3-3-8, it should go higher freqency.

[Ritalin]

it said, and ran/runs great at 2-3-3-6 at stock and 210, but it screws up after that.