Overclocking an AMD XP 2500+ CPU

[AN O'Nymous]

Just a moment ago, I tried overclocking my AMD XP 2500+ Barton CPU to
3200+ by changing the FSB from (166x11) to (200x11). I didn't change
anything else.

I have DDR400 RAM and the BIOS settings is on optimal, which means it
auto-adjusts the RAM to DDR333 for (166x11) and DDR400 for (200x11).

After doing so, I was not able to get into Windows. The error I got was
a blue screen, saying that Windows had shut down the PC to prevent
damage to my hardware. The non-generic portions of the error message
seemed to be:
"page_fault_in_nonpaged_area" &

Technical info:
***STOP: 0x00000050 (0xFFFFFFFF, 0x00000001, 0x00000000, 0x00000000)

Any ideas what the problem might be?

Thanks.

 

[old jon]

Just a moment ago, I tried overclocking my AMD XP 2500+ Barton CPU to
3200+ by changing the FSB from (166x11) to (200x11). I didn't change
anything else.

I have DDR400 RAM and the BIOS settings is on optimal, which means it
auto-adjusts the RAM to DDR333 for (166x11) and DDR400 for (200x11).

After doing so, I was not able to get into Windows. The error I got was
a blue screen, saying that Windows had shut down the PC to prevent
damage to my hardware. The non-generic portions of the error message
seemed to be:
"page_fault_in_nonpaged_area" &

Technical info:
***STOP: 0x00000050 (0xFFFFFFFF, 0x00000001, 0x00000000, 0x00000000)

Any ideas what the problem might be?

Thanks.

Remove your BIOS battery to reset the BIOS and stop trying to be so greedy.

 

[Sleepy]

Just a moment ago, I tried overclocking my AMD XP 2500+ Barton CPU to
3200+ by changing the FSB from (166x11) to (200x11). I didn't change
anything else.

I have DDR400 RAM and the BIOS settings is on optimal, which means it
auto-adjusts the RAM to DDR333 for (166x11) and DDR400 for (200x11).

After doing so, I was not able to get into Windows. The error I got was
a blue screen, saying that Windows had shut down the PC to prevent
damage to my hardware. The non-generic portions of the error message
seemed to be:
"page_fault_in_nonpaged_area" &

Technical info:
***STOP: 0x00000050 (0xFFFFFFFF, 0x00000001, 0x00000000, 0x00000000)

Any ideas what the problem might be?

Thanks.

Make sure you have your RAM timings as conservative as possible and how much
did you increase the core voltage ? You dont mention that or what
motherboard you are using. My brother has tried the same overclock on a Abit
NF7 v2.0 board and his XP2500 wouldnt go higher than 190 though his isnt a
mobile - its the mobile XP2500 that everyone overclocks so easily.

 

[AN O'Nymous]

My motherboard is an Abit NF7 motherboard, just like your brother's.

I didn't touch the core voltage, just the CPU FSB. Do you know of any
overclocking guides specific to our mobo-CPU combination?

Thanks.

 

[kony]

Just a moment ago, I tried overclocking my AMD XP 2500+ Barton CPU to
3200+ by changing the FSB from (166x11) to (200x11). I didn't change
anything else.

Why?

Why would you just randomly increase the FSB? Consider it a
rule that higher speed requires higher core voltage. IF
your particular CPU didn't need a voltage increase for the
higher speed, what that really means is that it didn't need
the core voltage it was already set to at it's stock speed
and it could've been running far cooler all along.

So, don't raise FSB without raising core voltage. IF you
later find the core voltage can be lowered back down some,
GREAT, but that's AFTER you get the box up and running
stabily first.

I have DDR400 RAM and the BIOS settings is on optimal, which means it
auto-adjusts the RAM to DDR333 for (166x11) and DDR400 for (200x11).

Don't set it to auto.
Set it to 100% of FSB, synchronous mode... that's how it
should've been running all along regardless of whether it's
overclocked. I assume you have PC3200 memory.

Even if it's PC3200 memory, it might be defaulting to 2.5V
and needs raised to 2.7V or so... you really need to Google
for some overclocking tutorials first, before sacrificing
stability... because there's a point where you might get the
system running but it wouldn't be stable and could crash or
even worse, corrupt OS files then it'll keep crashing even
after the hardware is stable. Above all, do NOT defrag the
hard drive until it's been tested stable long-term. Even
best to make a backup of data on hard drive before
proceeding.

After doing so, I was not able to get into Windows. The error I got was
a blue screen, saying that Windows had shut down the PC to prevent
damage to my hardware. The non-generic portions of the error message
seemed to be:
"page_fault_in_nonpaged_area" &

Technical info:
***STOP: 0x00000050 (0xFFFFFFFF, 0x00000001, 0x00000000, 0x00000000)

Any ideas what the problem might be?

CPU voltage too low, memory instable, CPU overheating, or
power supply insufficient... probably in that order, the CPU
voltage is definitely the first to suspect.