Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!caen!uflorida!unf7!shite
From: shite@unf7.UUCP (Stephen Hite)
Newsgroups: comp.sys.ibm.pc.hardware
Subject: Re: Parity Error.  What do I do?
Summary: Parity errors
Message-ID: <328@unf7.UUCP>
Date: 2 Dec 90 15:22:55 GMT
References: <73334@iuvax.cs.indiana.edu> <56470002@hpcupt1.cup.hp.com>
Organization: Univ. of N. Florida, Jacksonville
Lines: 20

In article <56470002@hpcupt1.cup.hp.com>, swh@hpcupt1.cup.hp.com (Steve Harrold) writes:
> >>> Memory parity interrupt at
> >>> 0BC6:006D
> >>> type (S)hut NMI (R)eboot, other keys to continue
> >>> 
> few months) issues this message.  The work-around is to power off/on and 
> it goes away.  Perhaps this is truly an intermittent hardware problem, 
> but I think, in my case, it is software related.
> 

   This sounds like a good idea. It happened to be also.  In my case, it
was pretty obvious what the problem was.  I took out 4 of the 8 meg I had
installed in my 386 PC and when I put it back in, some of the chips were
not as well seated as I had thought.  I reseated the chips and my problem
has vanished.

-----------------------------
Steve Hite
...gatech!uflorida!unf7!shite
shite@sinkhole.unf.edu