HELP! Technical glitch with RAM

[Perry Mason]

OK, techies...

I know there are many of you out there with much more technical knowledge than I...

A couple of days ago I increased my RAM from 256 to 512. At first, my computer responded extremely well... a day or so later it started to hang, stop at will, restart at will... I am losing time on my live clock, etc.

Any ideas for a fix?

I run Windows 98SE, dual 30 gig hard drives, run FreeRAM all the time...

Perry

 

[Gentle Ben]

A friend had a similar problem, the computer works fine with either stick alone, combined it would hang & freeze, I recently put together a low end machine for another friend just starting out, added the stick from friend1 to the computer, same situation, the memory isint defective, just seems to be incompatable for some reason.

The clock issue sounds like a mb battery issue perhaps

 

[lonecoxxman]

This probably won't help you, but on a previous computer I added 256 RAM to an already existing 128. I couldn't see any improvement in performance. I suspect that what I should have done is to take out these two sticks and replace with one having the very large RAM I desired.

 

[WoodPeckr]

Adding memory can be tricky. You probably just have a compatibility problem. A few years back I added some ram and was told if there is a compatibility problem, it will surface fast. I had problems, PC ran funny and had to take that memory back. Just make sure you can bring it back or exchange it for another type ram. I went from 64 to 128 and saw only a little improvement back then but when I went to my system max of 384 ram, WOW, it was like getting a new PC, everything ran much faster and better and that was on Win 98.

XP seems to run better with at least 512 ram and even better if you double that to 1024.

You never have enough ram memory.

 

[Peeping Tom]

If it worked for an initial period, remove and reseat both sticks. Improperly seated ram will do exactly as described

 

[Perry Mason]

Thanks guys...

I ran the test, asn, and because I left the computer on the test while I went out, it mde several passes. No errors.

Normally I would tear out my hair trying to figure this one out logically... but it ain't worth it. It proves what may be a new rule for IT: If something can go wrong, it will. Sometimes, it just takes a little longer.

I think I will just trade the chip for another...

Unless someone has a logical solution...

Thanks for the suggestion Peeping Tom. You posted just before I finished typing this. I will try your suggestion...

Perry

 

[Perry Mason]

Weird shit!!!???

I decided to wait until the next time the computer screwed up before opening the case and fooling around with the RAM chip...

Guess what? Since I ran the memory tests, it's working like a charm???!!!

Thank you, gentlemen....

Perry

 

[canucklehead]

I had a PC at a cleints that their in house tech updated and did the samething. I had to run memtest for it to set. I know on a mac if you change the RAM and then reset the open firmware it resets your firmware password because it sees itself as having the hardware reset. I also the set of scripts memtest runs are unix/DOS commands for checking the hardware in reseeds it virtually.
That could have been what was needed.

 

[Perry Mason]

Canucklehead...

You mean this shit is not weird?

Perry

 

[canucklehead]

Not really i have seen it with Linux Unix and macs as well as PCs ...sometimes you just need to reseed the RAM....