Non-Overclocking Question

Feb 22, 2000
119
0
0
I just purchased a new CPU/mobo combo, and I have a question.

The CPU is an AMD Athlon XP 2600+ with an ECS L7S7A2 motherboard, and some DDR/400 memory. I don't want to overclock this, but the only way I can get it to be stable seems to be to underclock it...unless something else is wrong

When I put the CPU in, they system defaulted to a frequence of 133, and the BIOS reported that I had a XP2000. It also defaulted the memory frequency to match the CPU.

If I up the CPU frequency to 166 and the memory frequency to 200, the BIOS reports an XP 2600+, but when I perform CPU/memory intensive tasks (like video editing and rendering), the machine freezes. If I reduce everything back down to 133, the computer is stable as heck.

Am I doing something wrong? Could the CPU be bad? Should I leave the memory at the same frequency as the CPU (at 1666)...help...I don't know what to do?

TIA

---

Wheeler Dealer,

Your thread subscriptions are being returned to us with the error message:

Unknown host: <your email address>

These return notices flood our mailbox. For this reason, I have canceled your subscriptions. Please do not subscribe to anymore threads until this problem is corrected.

If you need to update your email address, you will also have to ask us to delete the space from your user name. Please enable PM's, and contact us for assistance.

Thank you,

AnandTech Moderator
 

Shimmishim

Elite Member
Feb 19, 2001
7,504
0
76
is that a normal 2600+ or a mobile 2600+?

and is it a 266 fsb or 333 fsb 2600+ if it isn't a mobile one?
 

Fern

Elite Member
Sep 30, 2003
26,907
174
106
Looks like 2600+ should run at 166/333. Synch your ram at that speed too.

Don't know what mobo you got. First check your manual for setting ram FSB to "auto" (may be called cpu/dram ratio). Prolly in "Soft menu" (if you have that) or "advanced chipset features".
 

3chordcharlie

Diamond Member
Mar 30, 2004
9,859
1
81
Run the memory in synch with the fsb (166/333). If that doesn't fix your problem, back off the memory timings (i.e. set them to larger numbers) and see if that helps.