RAM HELP PLEASE =[

vmacman

Member
Apr 15, 2005
68
0
0
I've been trying to install this stick of 512 corsair. It worked yesterday, but my brother needed it for a couple minutes so he took it out. I tried to put it back, pushed it in, latched it. Tried it 10 times, but my system only reads it as 512. I should have 1gig. I removed one of my hardrive, not my important one though. Mayb thats the problem? help please
 

Matthias99

Diamond Member
Oct 7, 2003
8,808
0
0
Are you sure it's in the right slot? Some motherboards will only work with two DIMMs if they are in specific slots.

Does the removed/replaced DIMM work by itself (or in another system)? If not, it could have gotten fried.
 

vmacman

Member
Apr 15, 2005
68
0
0
Yes, I put it in the exact spot i put it in yesterday. I doubt it's fried though, since it is pretty new
 
Oct 1, 2005
338
0
0
Usually, the the comp won't boot (and Go beeping like crazy) if you insert into the wrong DIMMs. Still, check that, (Check your mobo manual, its different for every mobo, most of time it makes little sense the strange rules they put.

Of course, easy thing is to just take out your other stick and this questionable one into one of the slots... and if you don't POST or start beeping like crazy you know the stick is probably dead... (Or you stuck it in the wrong slot?)
 

forumposter32

Banned
May 23, 2005
643
0
0
How about try to push with the right hand or left hand then the right, then left...
It should go in all the way (if that's the problem anyway).
 

Lalakai

Golden Member
Nov 30, 1999
1,634
0
76
most common problem is seating, but you're fairly sure that you were able to seat them. If your system has 4 slots, try different slots. as was noted earlier, make sure you're using correct slots. If all this has been done, and still a problem, try 'em in another system. If they still don't work, then high probability one of them is fried. Remote chance you could have developed problem with memory slot on mb, but that is very rare, and trying the modules in another system should also identify that possibility. 90% of time when i run into that problem, it's due to the modules not being fully seated.

good luck