Associate
- Joined
- 24 May 2003
- Posts
- 1,429
- Location
- UK
My mate has a motherboard that has 2 memory slots and he has 512Mb of RAM installed on the one memory module.
This leaves the other slot free but when he puts in the other 256Mb memory module, the motherboard fails to recognise it.
He originally had 256Mb of RAM but found Windows XP ran a bit too slow so he bought another 512Mb and was hoping to use the both taking his RAM up to 768Mb.
He is now running 512Mb in his PC and he asked me the other day if I knew why the second memory module isn't recognised?
I haven't got a clue so I was wondering, out of curiosity, if anyone knew why?
I guess that it is because the memory modules are different sizes?
It is the memory slot closest to the CPU socket that is recognised.
They are also different brands as he mentioned that the 512Mb stick is manufactured by Kingston and the 256Mb stick is a generic make.
Would either of these 2 facts matter I wonder?
This leaves the other slot free but when he puts in the other 256Mb memory module, the motherboard fails to recognise it.
He originally had 256Mb of RAM but found Windows XP ran a bit too slow so he bought another 512Mb and was hoping to use the both taking his RAM up to 768Mb.
He is now running 512Mb in his PC and he asked me the other day if I knew why the second memory module isn't recognised?
I haven't got a clue so I was wondering, out of curiosity, if anyone knew why?
I guess that it is because the memory modules are different sizes?
It is the memory slot closest to the CPU socket that is recognised.
They are also different brands as he mentioned that the 512Mb stick is manufactured by Kingston and the 256Mb stick is a generic make.
Would either of these 2 facts matter I wonder?
