Path: utzoo!attcan!uunet!aplcen!samsung!cs.utexas.edu!rutgers!news-server.csri.toronto.edu!helios.physics.utoronto.ca!ists!yunexus!xrtll!silver
From: silver@xrtll.uucp (Hi Ho Silver)
Newsgroups: comp.sys.ibm.pc
Subject: Re: Memory chips killed by heat?
Message-ID: <1990Jul3.114124.2414@xrtll.uucp>
Date: 3 Jul 90 11:41:24 GMT
References: <46500135@uxa.cso.uiuc.edu>
Reply-To: silver@xrtll.UUCP (Hi Ho Silver)
Organization: Not around here, pal!
Lines: 20

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! /