Bizarre problem w/ Biostar M7NCD/Athlon XP2500

[kcasvitt]

I've been having an odd problem with my system. I will describe the problem, then list my components and settings. If i set my FSB to correct (default, 166mhz) settings, my system is unstable and crashes. For stability i use 133 mhz, but this underclocks my athlon xp 2500+ to 1900+. my system:
Case: Antec SLK1600
Power Supply: Antec TrueBlue 480w
Motherboard: Biostar M7NCD (max fsb 200mhz)
CPU: Athlon XP 2500+
Graphics: Asus V9999gt (geforce 6800gt 128mb)
Memory: Generic PC3200 (1gb)
CD: Generic DVD 16x
Floppy

All settings are default (except the underclocked FSB), the cpu is cooled by a copper heatsink/fan, the case is well ventilated and clean, with 2 case fans.

I am looking for the source of the problem. Any ideas? Any similar experiences?

 

[o1die]

If your cpu is a barton 2500, then 166 is the correct setting. I haven't heard of any regular xp's marked at 2500 running at 133 fsb. I would suspect your memory is causing the instability. Run memtest. It's a free download.

 

[kcasvitt]

thanks for the idea. i'll check my mem. Just to be clear, my problem is that my computer crashes at default FSB settings. I must underclock to 133 mhz for stability.

 

[endyen]

Yup, sonds like cheep memory all right. You could try raising the voltage. It may work okay at 2.7 volts, and if you increase the timings to 3,3,3, 8, it might also help.
Another problem could be your psu. If you download MBM5, you can use that to keep an eye on your voltage rails, and temps.

 

[kcasvitt]

I got some memory heatsinks, and readjusted the fans in my case, so the memory now runs cool to the touch. I also ran memtest, which reported zero errors. It appears the memory is okay. Biostar support gave me a flash update, which didn't help at all. Any other ideas? I'm thinking it may just be a lame mobo, but i want to rule out any other possibilities before dropping the cash for a new one. My next step is to reinstall windows and see if that helps.

 

[tweebel]

Sorry for asking, but did you run memtest at 166MHz FSB?

 

[pat]

Do this board has a sqaure 4 pins power connector? Is it plugged?

-Always put the blame on you first, then on the hardware !!!

 

[kcasvitt]

No, i ran memtest at 133mhz FSB. The system is very unstable and crashes at 166mhz. Also, the motherboard does not have a 4pin connector.

 

[kcasvitt]

bump

 

[Crashman]

That's the point of running memtest86 at 166MHz bus, in order to see if the thing that's crashing it is a memory error. We're not speaking of the "other" program by the same name that runs in windows, we're talking about the program that runs in DOS mode from a bootable floppy or CD.

<font color=blue>Only a place as big as the internet could be home to a hero as big as Crashman!</font color=blue>
<font color=red>Only a place as big as the internet could be home to an ego as large as Crashman's!</font color=red>

 

[endyen]

Just for the sake of it, pull the hsf, make sure it was in the right way round, and use some AS5.

 

[kcasvitt]

I've tried it with the case open, no change, everything runs cool to the touch. I've ruled out a heat problem, and also a memory problem (i have two sticks of 512mb pc3200, both check out fine, and neither fixes the problem if used alone). Interestingly, i just picked up this month's MaximumPC, where a user posted almost the same question in Ask the Doctor. MPC claimed that problems of this kind are most often caused by remarked processors. My proc is OEM, from an internet site. So my hunch is that that's my problem. I RMAd the cpu today for a replacement, which should fix the problem. if not, it has to be the motherboard.

 

[kcasvitt]

I recieved my new proc today. I installed it and there are no more problems! I'm very happy now. Thanks to everyone who offered advice.