• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

A8N32 FSB speed - what's yours ...?

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.
Agis said:
Revision 1.01,i don't know what is it mean.

Thanks.

Agis


Means you have the same revision board as mine, which is a good thing :D These particular revisons tend to clock better and higher ( so i'm told, lol).
 
Nebulous said:
Means you have the same revision board as mine, which is a good thing :D These particular revisons tend to clock better and higher ( so i'm told, lol).
Indeed, they seem to clock MUCH higher on the FSB, which is critical if you're running one of the super-cheap Opty 165s!

You just can't beat $93 (and sometimes less) for a 3+ GHz, 2 Mb L2, dual-core CPU ... :D
 
Nebulous said:
I was using Corsair XMS4400 and I had no trouble getting 300+ from them. I got this OCZ ram and it will not run pass the 250.

my first stick of 1gb ocz went to 271, i stuck this new second 1gb stick and my comp is unstable at stock speeds, WTH, it wont boot past 2.15
fails at 5 seconds under blend, and 7 seconds with large fft's
is it because 2 sticks wont run 1T?
 
I've run all my dual-channel kits in 1T mode. The Corsair TwinX 3500LL (stock 2-3-2-6-1T @ ~220) went up to 265 MHz or so (didn't test higher) with 3-3-2-6-1T timings. From what I've read you almost have to run 2T if you have four sticks but I have no experience with that.



Hmmm, you bought a second stick?? Are they a matched pair (same timings and chips)??? That may be the problem. And even with the exact same sticks if they weren't sold as a pair you may have issues ...
 
Last edited:
QuietIce said:
Might be able to run 2T since it's the same timings and model ...
well this is weird, i switched to 2T, ran a blend and it failed at 8 seconds like it always has, then decided to try again, clicked reset then go, and its been 20 minutes no problem, not much stability-wise but its seemed to have fixed the problem
 
Back