OC 2500+ w/ Abit NF7-S Rev2.0, HELP?

[cHsasHo]

Hi all, I just bought this NF7-S Rev2.0 board along with the XP2500+ AQXEA 0330 (forgot the rest, but I think it's VPMW or something). Anyways, I was just trying to OC my cpu these days, and the highest FSB that I can get out of it is around 210 ~ 215 x 11 multiplier, which is about 2300 Mhz, but unstable. I've already tried to raise the Vcore to 1.80, and my temperature is around 38 ~ 40 C. It is still unstable for some reason (blue screen errors all da time)
Should I keep raising my Vcore until it becomes stable??
Or is 210 FSB too high for my CPU??
Oh, and I am using the Kingston HyperX PC3500 256MB x2, which is suppose to run at 434 Mhz default....but rite now it's only running at 333Mhz, becoz I set my CPU to default to make it stable so that I can post this message. Also, the MEMORY timing is 7-3-3-2 at 2.6V rite now.
Any suggestions would be great, thx~~

[speedstream5621]

You were doing 2.3GHZ on stock voltage? Hell, even if you have errors...that's damn impressive. Up the vcore in small increments until its stable.

Looks like you have a good chip.

[cHsasHo]

Originally posted by speedstream5621
You were doing 2.3GHZ on stock voltage? Hell, even if you have errors...that's damn impressive. Up the vcore in small increments until its stable.

Looks like you have a good chip.

yeah, I can do 2.3 Ghz on stock voltage, but then it will be unstable (the blue screen error)
but I already tried to raised up my Vcore to 1.8, isn't that enough??
coz the temp is getting about 40 degrees now....I don't want to get it too hot u know~~
so do you suggest me to get my Vcore higher than 1.8??
or should I just increase my Vdimm?? coz it's only 2.6 rite now
but the thing is that I am not too sure if it's the CPU or the RAM that's causing the unstability....so I am not sure which voltage should I increase...

[speedstream5621]

Oh...ok.

Try lowering the multi to 5 and then up the FSB as high as you can go. When you become unstable, add voltage. Once you've found a good FSB, then up the multi. If you experience instability then, its a lack of vcore.

Bear in mind that timings will play a large role in your FSB overclock. Make sure you are running 1:1. Athlons run poorly async.

You should test for stability by running Prime95 and MemTest86 for a few hours.

[cHsasHo]

Originally posted by speedstream5621
Oh...ok.

Try lowering the multi to 5 and then up the FSB as high as you can go. When you become unstable, add voltage. Once you've found a good FSB, then up the multi. If you experience instability then, its a lack of vcore.

Bear in mind that timings will play a large role in your FSB overclock. Make sure you are running 1:1. Athlons run poorly async.

You should test for stability by running Prime95 and MemTest86 for a few hours.

When you talk about Voltage, are you referring to VCore or VDIMM??
and what do you mean by find a good FSB?? is 220 a good FSB to have??
so if Voltage = VCore, then when do I need to increase my VDIMM??

Oh, and should I make my RAM Timing default at first? or can I do 5-2-2-2 at first?
thx~~

[hwmicre]

Is your 40C idle or load? Either way, it's OK, but if it's 40 load that's purty darn good. You definitely have temp headroom.
You may be hitting limits, had to say once you get into the rafified air of the 200+ FSB arena. One thing, though, what's the rev (3 Dig. #) of the mem? I had issues with '012' which were rectified with a RMA to '024' - although MY prob was not getting over 180......

See what u get at 1.85/1.90 Vcore, 2.77 Vdimm.

[speedyaxon]

also...i'm having problems right now too in this area...i've read to make sure fsb spread spectrum and agp spread spectrum are disabled, turn cpu interface off...i would work on the front side bus first, leaving the cpu around 2Ghz to make sure that's not a problem. that way if you have errors, you know it's the fsb/memory and not the cpu. good luck!

[cHsasHo]

Originally posted by hwmicre
Is your 40C idle or load? Either way, it's OK, but if it's 40 load that's purty darn good. You definitely have temp headroom.
You may be hitting limits, had to say once you get into the rafified air of the 200+ FSB arena. One thing, though, what's the rev (3 Dig. #) of the mem? I had issues with '012' which were rectified with a RMA to '024' - although MY prob was not getting over 180......

See what u get at 1.85/1.90 Vcore, 2.77 Vdimm.

Yeah, it is about 35C idle, and 40C load, and I have no idea about what's my MEM Rev. (too lazy to check it)
But I just bought it now long ago....and the default timing that I am using is 7-3-3-2 at 2.6VDimm
by da way, what timing did you use rite now? since you get it up to 215 x 11 FSB now....can you still get it to 5-2-2-2??

[hwmicre]

Originally posted by cHsasHo
by da way, what timing did you use rite now? since you get it up to 215 x 11 FSB now....can you still get it to 5-2-2-2??

I use 2-2-3-7. Nforce can be a bit strange, sometimes looser timings actually providing better BM scores. You gotta try settings.

[GB_Cobber]

Ive been playing around with my A7N8X/XP2200+ for a few weeks now.

Its pretty much like my old athlons. low Vcore ussually results in crash to desktop or reboot while mem failure will give me file errors and sometimes hangs a game.

Im also finding my ram doesnt like high FSB(but its only generic PC3200).
It does 200Mhz fine at 133 or 166 FSB but wont do 200/200 even at 2.8v with any degree of stability.