Does memory slot matter? 600m

Hi,
I just bought a new motherboard for a 600m to fix a network problem. I
swapped in my old memory, which seemed to be working in my old laptop
(I'd run a memory diagnostic which it passed)...

I have two modules 512 Mb DDR 266 CL2.5 and 256 Mb DDR 333 and
CL2.5...
These both worked for years in my old machine.

I put them in the new mobo and got a memory error (could only
recognize the 256)... I swapped them around and it seems to be
working fine once I swapped the slots (256 Mb module in slot B).

Should this matter, or is it just luck that it is currently working.

I've got a 7 days no DOA on the mobo, and I'd like to know if I should
return it.

thanks,
mike

I am not 100% certain what is going on here, but a good rule of thumb when
deasling with memory modules of different sizes is to put the higher capacity
one(s) in the first memory socket(s), e.g. DIMM A or DIMM 0... Ben Myers

On Tue, 8 Jul 2008 21:11:23 -0700 (PDT), mooseo <> wrote:

>Hi,
>I just bought a new motherboard for a 600m to fix a network problem. I
>swapped in my old memory, which seemed to be working in my old laptop
>(I'd run a memory diagnostic which it passed)...
>
>I have two modules 512 Mb DDR 266 CL2.5 and 256 Mb DDR 333 and
>CL2.5...
>These both worked for years in my old machine.
>
>I put them in the new mobo and got a memory error (could only
>recognize the 256)... I swapped them around and it seems to be
>working fine once I swapped the slots (256 Mb module in slot B).
>
>Should this matter, or is it just luck that it is currently working.
>
>I've got a 7 days no DOA on the mobo, and I'd like to know if I should
>return it.
>
>thanks,
>mike

"mooseo" <> wrote in message
news:e8d15959-28b9-4e6b-b863-...
> Hi,
> I just bought a new motherboard for a 600m to fix a network problem. I
> swapped in my old memory, which seemed to be working in my old laptop
> (I'd run a memory diagnostic which it passed)...
>
> I have two modules 512 Mb DDR 266 CL2.5 and 256 Mb DDR 333 and
> CL2.5...
> These both worked for years in my old machine.
>
> I put them in the new mobo and got a memory error (could only
> recognize the 256)... I swapped them around and it seems to be
> working fine once I swapped the slots (256 Mb module in slot B).
>
> Should this matter, or is it just luck that it is currently working.
>
> I've got a 7 days no DOA on the mobo, and I'd like to know if I should
> return it.
>
> thanks,
> mike


From what you've described to me, I think you have a bad board - perhaps
even damaged DIMM pins/sockets.

I'd return it.

Stew

"S.Lewis" <> wrote in message
news46dk.20433$...
>
> "mooseo" <> wrote in message
> news:e8d15959-28b9-4e6b-b863-...
>> Hi,
>> I just bought a new motherboard for a 600m to fix a network problem. I
>> swapped in my old memory, which seemed to be working in my old laptop
>> (I'd run a memory diagnostic which it passed)...
>>
>> I have two modules 512 Mb DDR 266 CL2.5 and 256 Mb DDR 333 and
>> CL2.5...
>> These both worked for years in my old machine.
>>
>> I put them in the new mobo and got a memory error (could only
>> recognize the 256)... I swapped them around and it seems to be
>> working fine once I swapped the slots (256 Mb module in slot B).
>>
>> Should this matter, or is it just luck that it is currently working.
>>
>> I've got a 7 days no DOA on the mobo, and I'd like to know if I should
>> return it.
>>
>> thanks,
>> mike
>
>
> From what you've described to me, I think you have a bad board - perhaps
> even damaged DIMM pins/sockets.
>
> I'd return it.
>
> Stew
>Nope nothing wrong with the board from what you say, the golden rule is to
>always reseat memory if you get errors or not recognised. However if you
>swap them back around and get the same error then it is possbile it might
>be a fault on the board but I doubt it. Of course the memory will only run
>at the slowest speed of the slower module. You should always use module of
>the same speed.

"Fixer" <> wrote in message
news:93adk.122130$2...
>


<snip>

Fixer,

You're absolutely correct. I should've read the OP's post more closely when
he stated that moving the modules corrected the issue.

Mea culpa.


Stew