DDR400 DIMM has DDR333 chip on it

gudodayn

Distinguished
Feb 15, 2006
236
0
18,680
Check http://photos.yahoo.com/pwl42 then check Micron Technology.

Please tell me if this is not a DDR333 chip on a DDR400 DIMM.

A lot fo manufacturers use DDR333 modules for their DDR400s, they pretty much just lower the Cas Latency to 2.5 or 3 and make it run at DDR400.

But if yours is not running properly, RMA it.
Maybe even show them a screen shot of Memtest or something showing that it's faulty!!!!

I have ran into some modules similiar to yours (or situation) and is usually fixed by manually configuring the voltage on them....change it to 2.7V instead of leaving it on default 2.6V.

Of course if you are not happy with the DDR333 numbers on there, and technically, standard DDR400 meant to run on 2.6V so if it isnt / can't, you can still RMA it!!!
 

gudodayn

Distinguished
Feb 15, 2006
236
0
18,680
Could you name a few of those manufacturers?

I'd like to check that out.

I have a Micron and Kingston on hand like yours (both fixed by turning up the voltage to 2.7V instead of leaving it on default)

I've also seen PQI and Adata modules that have similiar situations but both work fine at 2.6V so according to specifications, they are DDR400 complaint!!

The DDR333 and DDR400 is nothing but a number they laser cut on there during sorting thats all
 

phil42

Distinguished
Jul 24, 2006
14
0
18,510
If it were a faulty socket it would have to be something that shows up with a 1G DIMM but not a 512M DIMM.
 

ivoryjohn

Distinguished
Sep 20, 2001
174
0
18,680
Some slots don't accept 1gb modules. (especially laptops)

Some BIOS don't support 1gb modules.

You may have checked this, in which case consider these comments as being on behalf of the readership that might not be aware.
 

PCKid777

Distinguished
Aug 1, 2005
669
0
18,990
Uhm... I don't believe I understand your answer. My own experience dictates that the RAM is not always at fault. I once had 2 out of 3 working RAM modules, but I couldn't get the 2 working modules to work. I had to individually test each RAM socket until I found the faulty one. You may have to spend some time with Memtest86 and a working module before you can rule out a defective socket.

EDIT: for grammer