Comp crashes as 166FSB

Wow, 2 computers that I can't figure out what's wrong with then in as many days. I'm really losing my touch. Ok, this computer crashes whenever I set the FSB to 166. It will run for maybe 5-15 minutes and then either blue screen, or just crash to desktop. In either case, all it gives is a generic 'Windows doesn't know what happened' error. Setting the FSB to 100 or 133 it runs fine all day long. The mobo is a MSI K7N2 Delta-L, processor is Athlon XP 2700+ and both are rated to support 166. Heck, even the memory is 166 (333, whatever). Any ideas?

Oh, and no, it's not overheating. Checked that already.

Hrm. I'm starting to lean toward the mobo being the problem. I'm getting some sound and video problems as well. Sound onboard and is garbled in some applications (IE, WMP) but fine in others (Windows sounds, games). Not the speakers or cables or anything, as this has happened on two diffrent setups. Video is acting weird, not creating artifacts or the screen flickering, but flickering in places. Hard to describe anyway. Again, two diffrent setups and geting the same result even using my personal video card. The only thing in this comper I haven't swaped out and verified are the processor and mobo. I'm gonna drop a diffrent processor in there to see what happens.

Update your BIOS lately? PSU w? What's the voltage for the CPU? How many e's are there in this sentence?

Take note that there is a version of the 2700+ that uses a 133 fsb, it just depends on the core.  The early versions of the chip used 133 while they uped it to 166 later.  So it could be that you have an earlier revision of the chip.

>>4
BIOS is up to date and PSU is 450W. More than enough. 6.
>>5
The site I got it from _says_ its the 166 version. I have no real way of knowing though. And I'm never buying from ikonpc.com again.

And an aditional update, I took the processor and put it in my personal computer, same result with the garbled sound and video.  I don't even run with onboard sound, I have a Live! card and getting the same result. The only thing I changed was the processor so at least I know my culpret. Oh, and this was at a bus of 100 to be safe.

try running memtest86. it sounds like some of your components can handle running at 166 mhz, and memory is always the first place to look.