-------------------------------1074067257
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In a message dated 1/14/2004 12:52:22 AM US Mountain Standard Time,
kevin_brown@qwest.net writes:
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+.
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)
-------------------------------1074067257
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
In a message dated 1/14/2004 12:52:22 AM US Mountain Standard Time, kev=
in_brown@qwest.net writes:
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 a=
lready). 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=20=
CPU (K7S5A and Palomino 2000+.
I suspect it tries to determine timings by itself, and uses the 133MHz=20=
time with 165, but has no idea how to handle 166. DDR333 didn't exist=20=
when I bought the memory
I know some boards were "We certify it as three slots usable with PC210=
0, but only two with 2700." (ECS K7S6A)
-------------------------------1074067257--