[comp.sys.ibm.pc] Memory chips killed by heat?

cl34316@uxa.cso.uiuc.edu (07/03/90)

Lately my Packard Bell AT compatible with a Seagate 40MB drive has been
giving me a "memory parity error" within 1-10 minutes of turning it on.
I was wondering if this could be caused by heat, as I have no air conditioning
and it's around 85 degrees in here on a normal day. I don't want to pay for
chip testing and such if this is the problem, because I can easily install
an air conditioner (I'm starting to bake a little myself).  Thanks in
advance.
						---C.J.

silver@xrtll.uucp (Hi Ho Silver) (07/03/90)

In article <46500135@uxa.cso.uiuc.edu> cl34316@uxa.cso.uiuc.edu writes:
$Lately my Packard Bell AT compatible with a Seagate 40MB drive has been
$giving me a "memory parity error" within 1-10 minutes of turning it on.
$I was wondering if this could be caused by heat, as I have no air conditioning
$and it's around 85 degrees in here on a normal day. I don't want to pay for

   It's possible, but that kind of temperature shouldn't kill chips.  What-
ever the cause is, you can find out which chip (assuming it's just one chip)
is causing the problems by buying one of whatever kind you have and using it
to replace, one at a time, your memory chips.  This could be a pain, though,
if your board uses 36 chips :-)  And of course, you can't do it if it uses
SIMMs.

   There may be software available which will help you find out which bank
of chips is causing the problem; try looking around local BBSs.
-- 
   /Nikebo \ Nikebo says "Nikebo knows how to post.  Just do it."\silver@xrtll/
  /---------\_____________________________________________________\----------/
 /yunexus!xrtll!silver (L, not 1)\ Hi Ho Silver \   just silver for short   /
/Silver:  Ever Searching for SNTF \  Life sucks. \  someone buy me a BEER! /

jca@pnet01.cts.com (John C. Archambeau) (07/04/90)

cl34316@uxa.cso.uiuc.edu writes:
>Lately my Packard Bell AT compatible with a Seagate 40MB drive has been
>giving me a "memory parity error" within 1-10 minutes of turning it on.
>I was wondering if this could be caused by heat, as I have no air conditioning
>and it's around 85 degrees in here on a normal day. I don't want to pay for
>chip testing and such if this is the problem, because I can easily install
>an air conditioner (I'm starting to bake a little myself).  Thanks in
>advance.

Anything electronic can be killed by heat.  Why do you think the rooms that
mainframes are housed in are usually kept at 55 to 65 degrees F?

Because of the weather conditions in southern CA and me not having air
conditioning, I down my computer during the day if I'm not around and using
it.  An air conditioner would be a wise investment.
 
     // JCA

 /*
 **--------------------------------------------------------------------------*
 ** Flames  : /dev/null                     | Small memory model only for
 ** ARPANET : crash!pnet01!jca@nosc.mil     | Unix?  Get the (*bleep*) out
 ** INTERNET: jca@pnet01.cts.com            | of here!
 ** UUCP    : {nosc ucsd hplabs!hd-sdd}!crash!pnet01!jca
 **--------------------------------------------------------------------------*
 */

labach@herald.usask.ca (Terry Labach) (07/09/90)

In article <46500135@uxa.cso.uiuc.edu> cl34316@uxa.cso.uiuc.edu writes:

>Lately my Packard Bell AT compatible with a Seagate 40MB drive has been
>giving me a "memory parity error" within 1-10 minutes of turning it on.
>I was wondering if this could be caused by heat, as I have no air conditioning
>and it's around 85 degrees in here on a normal day. 

Probably...I once administered a student lab that had been jerry-rigged in
a south facing classroom.  Once summer hit, the temperature got up to
35 C in the room.  Starting at about 29 C, machines would start
failing and _nothing_ would run past 33 C.  Not all the machines would
give parity errors, though.  Many would just lock and would not
respond to anything.  Once I had convinced the administration to put in
air conditioning, the temperature plummeted to a high of 25 and I had
_no_ further problems with the hardware. (the students on the other
hand... :-) )

Don't take my word for it, you should still check out any other
possibilities that could cause this...

"...if you are not able to adapt yourself, if || T. Labach, Computing Services
you are not inclined to crawl in the mud on   || University of Saskatchewan
your belly, you are not a revolutionary but a || BITNET:labach@sask
chatterbox..." - V. I. Lenin (1918)           || Internet:labach@sask.usask.ca