geronimo said:
It has a XP 3000 CPU, and two Corsair XMS 512 mb ddr 3200 (400 Mhz)
SDRAM (operating single channel). Initially it was set for "optimal"
(slowest). I think it said CPU speed was 1050 Mhz. I changed to custom
(I think it ws called). I bumped the FSB to 220 (more or less) and
bumped up mulitiplier to 12.5 (the highest you can select).
Now when it boots, it STILL says the CPU speed is 1050 Mhz and the RAM
speed is 100 MHz. I thought the CPU speed was supposed to be 12.5x 220
which is 2750 Mhz. Whats up with that? Shouldn't I be able to get a
lot more than 1/3 of the rated max CPU speed? I have experienced a
couple of blue-screens in the two days since doing this, so perhaps
it is at the max. The core voltage is set to 1.75, BTW. THe CPU has
a hefty Volcano 9 on it. What max performance should I be able to get
out of it?
Clocking a processor, should be done like "sneaking up on it". You make
changes in small steps, then observe the results and work from there.
Selecting a ridiculous overclock level will result in the board
crashing in the BIOS. Asus has an overclocking recovery feature,
which will return the settings to safe defaults, so you can enter
the BIOS and make more adjustments. When you see the low frequency
values, that is what has happened. The board crashed, and has
recovered automatically for you. (My board has failed to recover
from an overclock only once, forcing me to clear the CMOS. So the
automatic recovery feature seems to work pretty good.)
There are two Barton 3000+ processors.
You have the 200MHz one (the top one here).
Barton 2100MHz (3000+) OPGA 200 512 10.5x 1.65V 85oC 53.7W
Barton 2167MHz (3000+) OPGA 166 512 13x 1.65V 85oC 58.4W
If the clock after the crash recovery is 100, and the multiplier is
the 10.5 default, then the observed value of 1050MHz is correct.
You need to move the clock from the crash recovery value of
100MHz, up to 200MHz in small steps. You can start by trying 133MHz,
and see if it survives that. Check that the core voltage setting
is in the correct range (1.65V setting, 1.69V or so measured).
When idle, the motherboard will overvolt by a tiny bit, which is
normal for Asus boards, and is part of their interpretation of
the correct load line.
When you are finished, you should be at 200 x 10.5 . That would give
the correct nominal value of 2100MHz. And it should say 2100MHz
in the BIOS.
Changing the multiplier in the BIOS works, if you have an old
processor. Processors after a certain production date are locked.
Mobile processors (I have one in my A7N8X-E) also allow the
multiplier to be set in the BIOS. If you change the multiplier
value, and are still seeing the effects of the 10.5x nominal
multiplier, that should be a hint to you that the processor is
locked.
In terms of other potential issues, be aware that Nforce2 is
picky about the RAM. I had problems with the first RAM I
had in the board, and after a lot of testing, it turned out
the RAM had a bad location. After I put a couple sticks of
Ballistix PC3200 CAS2 in the board, it was rock solid. And
remains that way to this day. Using "good RAM" compensates
for the barely adequate performance of the I/O pads on the
Nforce2 Northbridge.
If you are having trouble with your RAM, go into the BIOS
and set the memory to "Manual". The speed settings
offered should be percentage values. A value of "100%" is
the same as operating synchronous with the FSB. If you
select a value of "83%", that is usually enough to bring
stability. If you still experience crashes, try cranking
the RAM down to 83%. If you want to run at 100%, that
may take some "good RAM".
And be careful with that memory setting. Do *not* use 50%
or 200%. There have been failures after doing that. So don't
go near the extremes. Like the CPU clock, try small
deviations from 100% and see how it goes.
Paul