View Single Post
  #2   Spotlight this post!  
Unread 02-12-2005, 01:11
Mike AA's Avatar
Mike AA Mike AA is offline
Programmer and Mentor
AKA: Mike Aalderink
FRC #3458 (Code Blue)
Team Role: Programmer
 
Join Date: Jan 2003
Rookie Year: 1999
Location: Holland, Mi
Posts: 698
Mike AA is a splendid one to beholdMike AA is a splendid one to beholdMike AA is a splendid one to beholdMike AA is a splendid one to beholdMike AA is a splendid one to beholdMike AA is a splendid one to beholdMike AA is a splendid one to beholdMike AA is a splendid one to behold
Send a message via MSN to Mike AA
Re: Older computer memory trouble

Quote:
Originally Posted by sanddrag
I have a system that I think is a Celeron 700. It was a nicely functioning machine. It has two memory slots. Here's where the story begins. The computer is just full of dust beyond belief so I blow and vacuum it out. Them, I take out the single stick of 128mb PC133 memory out of it (the other slot is empty) for use in another system. I then install a stick of 32mb PC66 memory into each of the two slots. I power on the system, I get no beep, no video, and a strong burning smell. I quickly disconnect the power and remove the RAM and see that one pin in one of the RAM slots is burned/melted and so is the corresponding pin on the stick of memory.

What did I do wrong? Are you not supposed to use PC66 memory in a PC133 system? Did the dust get in there and short something? Was there a jumper I should have moved but didn't?

I'm afraid to put the original PC133 128mb stick back in there for fear of damaging it.
did the computer work before you swapped out the PC133? if you put the other dimm in, the one without the burned pin, does it work? Where did you acquire the older dimms? Usually its OK to use a slower speed and not have a problem with it, I have used numerous different sizes and brands and never had issues, other than possibly slightly slower access. Did you literally vacuum the insides? Did you use your household vacuum or a shop vac or a computer vacuum? This can often damage components beyond repair from static. It is possible that the PC66 was damaged in the first place or might have been loose.

-Mike