What's the current state of the world?

>> If it crashes when running with an FSB of 166, then the memory might not be
>> able
>> to handle it. I know crucial is good (I have it here), but it can fail (as I
>> have had to replace some already). You might want to double check the sticks

> That's why I use 165. :) It also happened at 133, and at 133 with a
> different mobo and CPU, and at 100 with the same different mobo and CPU (K7S5A and
> Palomino 2000+.

if the same behavior is showing up in different machines and the only thing the
same is the RAM, then you most likely have bad memory. Also, since it isn't
certified by Crucial to do DDR333, then you might need to buy newer memory that
can take those voltages and clock rates.

> I suspect it tries to determine timings by itself, and uses the 133MHz time
> with 165, but has no idea how to handle 166. DDR333 didn't exist when I bought
> the memory
>
> I know some boards were "We certify it as three slots usable with PC2100, but
> only two with 2700." (ECS K7S6A)
>