Re: Should RAM timings have to be set manually?
Rod Speed wrote:
> larry moe 'n curly <larrymoencurly@my-deja.com> wrote
>> My batting average for Kingston ValueRAM is 8 bad PC3200 modules
>> out of 11 or 12 and maybe 30% bad PC2100 modules. The number
>> of errors seemed to correlate with the markings on the chips
>
>> They aint 'bad', the bios just isnt using the appropriate timing etc for them.
>
> > One BIOS was in an Asrock/Asus KT400
> > mobo, the other in an ECS nForce3 mobo.
>
> The technical term for that is 'pathetically inadequate sample'
That's all I can afford. OTOH why did all the Corsair and PNY modules
work fine with those mobos? The only modules that performed as badly
as the Kingstons were Muskin Enhanced (budget) -- all three showed lots
of errors, even when the command timing was set to 2T. Oddly,
Thaiphoon said that those Mushkins were made by Kingston.
> > Thaiphoon reported the same SPD timings for all of these PC3200
> > modules, but all the modules with the completely unmarked chips all
> > failed, most of those with Dxxxxxx chips failed, while almost all the
> > modules with Fxxxxx chips tested fine, and even the failing ones
> > showed only 3-5 errors.
>
> Very unlikely indeed that all the ones that were
> unmarked were deliberately shipped by Kingston BAD.
Why would they ship such chips, especially considering the costs of
warranty replacements?
> Much more likely that the data in the spd is incorrect with SOME chipsets etc. |