|
Adding some pc2700 ram to computer, now wont boot.
|
|
|
redhatman
Member
|
26. August 2005 @ 14:09 |
Link to this message
|
|
Hey, I have a friend that just bought some 512mb pc2700 ram to put in his dell. He asked dell to make sure what type and what his motherboard can hold, and all is good. What it does, is it will turn on, but not even show the dell sign, or any sign of video. It then reboots, and still shows no video, but just stays there without rebooting again. He would appreciated any help. Thanks
-Pat (redhatman)
|
|
Advertisement
|
|
|
|
|
webhedreg
Suspended permanently
|
26. August 2005 @ 14:38 |
Link to this message
|
|
Are you adding to or replacing what was already installed in the PC.
If you list the MB product code and RAM ID I'll check the compatibility for you. I would not trust anything any of the Dell support people quote as they usually have no idea beyond the basics.
|
|
jonni3
Suspended due to non-functional email address
|
26. August 2005 @ 14:52 |
Link to this message
|
|
Have you tried clearing the cmos/bios & then restarting the p.c ......
|
|
ddp
Moderator
|
26. August 2005 @ 16:06 |
Link to this message
|
|
try the new ram individually to see if have a bad 1 or not.
|
|
redhatman
Member
|
26. August 2005 @ 19:25 |
Link to this message
|
|
hey webhedreg, i told my friend that, and this is the info he gave me. Tell me if it is the right info or not:
"dimension 2400
elixer n2ds25680bt-6k
159z0afy
033
i dont no wich on you are talking about
sorry so i gave them to you all and i dont know what you mean MB
producut code means"
|
|
ddp
Moderator
|
26. August 2005 @ 19:54 |
Link to this message
|
|
the make & model# of the motherboard.
|
|
webhedreg
Suspended permanently
|
27. August 2005 @ 01:21 |
Link to this message
|
|
The MB was the motherboard product code, which is printed somewhere on the motherboard. From what I can see the 2400 is made to take Celeron CPUs and runs at 533FSB. The memory you have is Nanya Elixier 2700 which should be fine for the machine you are using it in. The Dims quoted are 256MB not 512, so I presume you have got 2 of them to take it up to 512MB. Would repeat what ddp said, try them individually and see what happens. It could well be that the new memory is dead. Where was it purchased from and did he use anti-static to fit it, if not it could be fried.
|
|
Daggy-G
Member
|
27. August 2005 @ 03:40 |
Link to this message
|
|
Im with jonni on this 1 ... Have you tried clearing the cmos/bios & then restarting the p.c
This is because diff rams use diff cas latencys ...
so if old ram was 3t & new ram is 2t then the bios is still configured for the old ram (thus wont shit turn on)
Do what jonni said (u need to unplug pc move the cmos reset jumper from pins 2&3 to pins 1&2 wait 1 min & then put the jbitch back on pins 2&3.
This will reset bios to factory default which is usually set to auto detect everything (cpu,ram,all that shit)
try & tell us what happens
|
|
jamesmont
Newbie
|
27. August 2005 @ 17:41 |
Link to this message
|
|
Hey Daggy-G i tried that it didn't work so what else can i do?
|
|
jonni3
Suspended due to non-functional email address
|
28. August 2005 @ 05:32 |
Link to this message
|
|
So have you tried what DDP sugested " one stick at a time " . Will it boot with just the new 512 stick in place of the original 256 , if it does then add the 256 to the other slot & se what happens ...
|
|
webhedreg
Suspended permanently
|
28. August 2005 @ 06:28 |
Link to this message
|
|
redhatman hasn't got a 512MB stick as suggested, he has only got 256MB as indicated in part number provided.
|
|
jonni3
Suspended due to non-functional email address
|
28. August 2005 @ 07:46 |
Link to this message
|
|
Right so he has 2 x 256 pc2700 ? , 1 original & 1 aftermarket or was the part number from the 256 stick already in the p.c or the other stick his friend purchased .....
|
|
Advertisement
|
|
|
|
webhedreg
Suspended permanently
|
28. August 2005 @ 08:01 |
Link to this message
|
|
Could do with bit more info really, as I'm not exactly sure what hardware he has as the part numbers don't match the description of the new memory.
|
