So I'm setting up a home-hosted server on a kinda old desktop I had around. The thing is that I was going to run it with 1 GB of RAM but I found another piece of 1 GB laying around. I connected both to the motherboard but the pc did not boot. Their speeds are the same (DDR2 533Mhz) and the strangest thing is that if I connect only one of them, they both work and the pc boots, but not together. What could this be?
Thanks.
It's nothing I've had to deal with myself but I think using mismatching ram can cause some issues if the timings and or voltages don't match.
I think it would be helpful if you'd post everything it says on the labels on the ram sticks so we can get the part numbers and thereby complete specs. Don't omitt anything and be descriptive. Or better yet take pictures, use good lighting when you take the picture and make sure the camera focuses well so we can read it.
[QUOTE=chipset;35555832]It's nothing I've had to deal with myself but I think using mismatching ram can cause some issues if the timings and or voltages don't match.
I think it would be helpful if you'd post everything it says on the labels on the ram sticks so we can get the part numbers and thereby complete specs. Don't omitt anything and be descriptive. Or better yet take pictures, use good lighting when you take the picture and make sure the camera focuses well so we can read it.[/QUOTE]
There we go. [url]http://www.box.com/s/44117eea02ad1f0d4af6[/url]
Specwise they are identical, what motherboard do you have? Full model number and or part number would be appreciated. If you're not sure there are usually stickers on it somewhere with the partnumber.
[QUOTE=chipset;35565780]Specwise they are identical, what motherboard do you have? Full model number and or part number would be appreciated. If you're not sure there are usually stickers on it somewhere with the partnumber.[/QUOTE]
No, they aren't. The only things identical between them is that they're both DDR2 sticks and they both run at 533 MHz. The CAS latencies and other timings are completely different, which is likely the source of the problem. Those two RAM sticks are never going to work together.
[QUOTE=bohb;35567313]No, they aren't. The only things identical between them is that they're both DDR2 sticks and they both run at 533 MHz. The CAS latencies and other timings are completely different, which is likely the source of the problem. Those two RAM sticks are never going to work together.[/QUOTE]
What? I googled the model numbers, they're both CL4
[editline]14th April 2012[/editline]
[url]http://www.newegg.com/Product/Product.aspx?Item=N82E16820218202[/url]
[url]http://www.valueram.com/datasheets/kvr533d2n4_1g.pdf[/url]
There are far more variables in memory timing than just CAS.
tCK (CAS), tRC, tRFC, tRAS
Also the fact that the TwinMOS is PC2-4300 instead of PC2-4200 means that it is either rounding or using non-standard timings that aren't official JEDEC standards.
[QUOTE=bohb;35574545]There are far more variables in memory timing than just CAS.
tCK (CAS), tRC, tRFC, tRAS
Also the fact that the TwinMOS is PC2-4300 instead of PC2-4200 means that it is either rounding or using non-standard timings that aren't official JEDEC standards.[/QUOTE]
You said the cas latencies where different, I pointed out they wheren't. Anyway I didn't find any other timing info on the twinmos ram. Nice catch on the 4300 though, didn't notice that.
[QUOTE=chipset;35565780]Specwise they are identical, what motherboard do you have? Full model number and or part number would be appreciated. If you're not sure there are usually stickers on it somewhere with the partnumber.[/QUOTE]
The motherboard is a Gigabyte GA-EP31-DS3L.
I might not have explained very well what I mean with not booting. I mean the motherboard screen shows but stays there forever.
I discovered my CD/DVD Drive was fried. I installed a new one I had around and it boots instantly now. Maybe it was not the RAM that was making it freeze on boot screen. I'm still going to try starting it with both pieces of RAM now that I fixed that issue.
Sorry, you need to Log In to post a reply to this thread.