Good/Bad Memory

[Leslie_h]

We are using Kingston memory in our Compaq machines. We have recently brough all pcs up to between 32 & 64 mb ram. After about 2 months we start seeing lockups. We had been told that it could be due to bad memory modules so we have replaced memory in some pcs. My question is how do we know for certain is really is bad memory and not something else? Could it be because we aren't using Compaq memory? Is Kingston noted for bad memory?

[Ygor]

One more reason people build their own pcs...
Ram is ram, until you get into cas 2 specs.
There are several companies which make ram chips and a lot more that assemble them onto the little printed circuit boards that go in the ram slots.
Many pc manufacturers are specifying their own ram cartridges in order to keep un-informed customers coming back. It's possible that some have their own ram slots that won't take any cartridges but their own, but I don't know that for sure.
As long as it's not overclocked, the ram you have should not be a problem.
If this is a Compaq 5200, try this link: http://www.sysopt.com/forum/Forum2/HTML/002956.html

[This message has been edited by Ygor (edited 10-20-1999).]

[digital_rat]

make sure you cpu fan is ablowin""

[DLazlo]

What series Compaq are you using? If it's 5200, see my post Com. or Microsft. A few of these problems show up on 4700 thru 5300 series, however most of the data I have so far is on 50-53. You could try Presario user forum on Compaq's site, although be prepared for their e-formletter: At the C prompt-. I'm not sure they like me, having trouble loging on there lately. Is it me or the defective cheapware I'm starting to think they were shoving out when the PC market was hot & Dell was coming up on their heels. Gotta keep them profits up boys! As soon as I can I will try to post some usable bandaides for some of these till they can be resolved. Unfortunatly, some of them appear to keep coming back to haunt you. The kingston shouldn't be your problem if they meet the right specs. Luck, CL

[Axel]

It's possible the RAM is bad, but it's much more likely that something loaded on the boxes in the way of software caused a problem. Also, any chance you might be running short of hard drive space? How long has it been since you've ran scandisk on the systems? (programs/accessories/system tools/scandisk) Also, defrag might help, or possibly make things worse. Back up the hard drives to tape before running defrag if you've never run defrag.
Lastly, clean out the following files:
c:\windows\temp
c:\windows\tmp
c:\tmp
c:\temp
and the history files for IE, or the cache files under netscape.
If you have a swap file size problem - i.e. running out, that should help. Also remember to use start/shutdown when turning the system off - otherwise, you dump temp files on your hard drive which will eventually make you crash.
Most likely, however, it was something you loaded in the way of software.