F
Fish Taco Joe Schmuckatelli
Gentlemen all:
I have a customer's system here in the shop, with the P4T533-C board (bios 1008)
and a 3.0GHz chip sitting on top of it. Recently, he's been reporting blue
screens in his Win2K install, and through trial and error, discovered that when
he slowed the cpu clock/FSB down from 133 to 100, the system stabilized.
Initially, the system had a pair of 256MB Samsung 1066Rambus sticks, to which
was later added a pair of 512MB Samsung 1066Rambus, totalling 1.5 GB. Memtest
is still showing intermittent memory errors when run for extended periods of
time.
Having found the processor to be at fault in the past, I dropped it into a
different model board with some newer DDR memory, and it ran for about 24 hours
without incident. So, that doesn't appear to be the culprit. Next step was to
put the chip back on the old board and put on a pair of 800Rambus sticks I
brought in from home... no errors.
The question, then, would seem to be this: is the memory itself (two different
batches, dated a year apart) at fault, does this board not like this flavor of
memory, or is it having trouble running *any* memory at 1066? Sadly, as I lack
another brand of 1066 memory, or another Rambus-equipped board, I do not have
the ability to test further.
Is there anything else I can try?
I have a customer's system here in the shop, with the P4T533-C board (bios 1008)
and a 3.0GHz chip sitting on top of it. Recently, he's been reporting blue
screens in his Win2K install, and through trial and error, discovered that when
he slowed the cpu clock/FSB down from 133 to 100, the system stabilized.
Initially, the system had a pair of 256MB Samsung 1066Rambus sticks, to which
was later added a pair of 512MB Samsung 1066Rambus, totalling 1.5 GB. Memtest
is still showing intermittent memory errors when run for extended periods of
time.
Having found the processor to be at fault in the past, I dropped it into a
different model board with some newer DDR memory, and it ran for about 24 hours
without incident. So, that doesn't appear to be the culprit. Next step was to
put the chip back on the old board and put on a pair of 800Rambus sticks I
brought in from home... no errors.
The question, then, would seem to be this: is the memory itself (two different
batches, dated a year apart) at fault, does this board not like this flavor of
memory, or is it having trouble running *any* memory at 1066? Sadly, as I lack
another brand of 1066 memory, or another Rambus-equipped board, I do not have
the ability to test further.
Is there anything else I can try?