xp pro problems...

[01041003]

hi all.
recently, i replaced my mobo so i upgraded from win xp home to xp pro.
i reformatted, then did a clean install of xp pro corp. i upgraded the board because i bought a Athlon xp 2600+ (333mhz version)processor and my old board topped out at 133mhz fsb, new board tops at 200mhz.

whenever i run the processor at 166fsb (the correct setting) i get alot of bsod's with various errors...(0x8e, 0x4e<--i get this one alot!, 0x50) and so i dropped the fsb back down to 133mhz and it seems to run more stable...i think i've still gotten a bsod at this settting too, but im not positive...

anyways, have you guys heard of anything like this?? my ram is pretty new, so i dont think its that, but i havent had a chance to run memtest yet, sooooo...

my specs:
Windows XP PRO CE
Biostar M7NCD (NForce 2 chipset)<-- dont laugh! lol...
Athlon XP 2600+ (running at 1.54mhz)
160 GB Seagate Barracuda hdd
PNY GeForce 4 mx440 64mb DDR
768MB DDR (pc2700)

[bailey]

[QUOTE=01041003]hi all.
recently, i replaced my mobo so i upgraded from win xp home to xp pro.
i reformatted, then did a clean install of xp pro corp.

this is a red flag fro me.

usally that error is from bad memeroy, but then you could also have a bad copy of xp pro corp.

[Statica]

Which XP 2600+ are you using? The barton (stock settings) runs at 1917Mhz w/ 512K cache @ 166Mhz x 11.5 clock multiplier; the t-bred XP 2600+ runs at 2083mzh w/ 256K cache @ 166Mhz x 12.5 clock multiplier.
However, all things being equal (you did have a stable system with the old RAM), I would suspect the issue to be w/ your motherboard (the nforce2 hasnt been the most stable one out there) or your CPU itself. To me the worrisome issue wouldnt be that your system is crashing frequently at 166Mhz, it would be that your system is still crashing when you underclock it at 133Mhz.
However, I would also urge you to check out the common suspects like heat and run the memtest to rule out memory errors.

[01041003]

ok, thanks for the help guys....

from pcwizard2004:

Monitoring Chip : Winbond W83627HF
CPU Core : 1.63 V
VCore1 : 1.49 V
+3.3V Voltage : 3.15 V
+5V Voltage : 4.97 V
+12V Voltage : 11.67 V
Chassis Fan : 5294 rpm
Processor Fan : 64285 rpm
Processor Temperature : 37.5 °C
Mainboard Temperature : 209 °C
Power/Aux Temperature : 25.5 °C
Hard Disk Temperature #1 : 40°C

MAINBOARD TEMP. 209!?!?!?
yeah right...*** is going on here???
ok, besides the mb temp, everything looks ok to me.
cpu dropped 1 deg. while i was typing this!

anyways...my 2600+ is a barton core

also, i ran windiag (approx. same thing as memtest, right?) and it found 27 errors out of 54 complete passes, all while running the WMATS test. these errors occurred so late in the testing that im assuming they occurred in the second mem. module?
so i've pulled that one(thankgod it was the 256!) and im just using the 512mb right now. if im not assuming correctly, please lemme know!

so far though, i've gotten no errors of any kind. im hoping it was just a faulty module
so i wont have to replace the mobo AGAIN. though i think i paid less for the board than i did for the 512mb ram! haha, good 'ole Biostar!

***UPDATE***

as of 6:15pm pst:
well, like i said, i removed the 256mb module and since then i have had no probs whatsoever... soooo, i guess that was the problem and i'd like to thank you both for responding, if i get some errors later, i'll be sure to post them here!

also, i would like to thank PCMECH.com, a great resource for UBERNOOBS like me!!!