Article View: mn.general
Article #614Re: Parity check error-What is it? HELP PLEASE!
From: Ken Bell
Date: Thu, 26 May 1994 00:28
Date: Thu, 26 May 1994 00:28
38 lines
2804 bytes
2804 bytes
In article <kozu0003.769894089@gold>, John T Kozubik <kozu0003@gold.tc.umn.edu> wrote: >Why is this happening? How can I prevent it? what should I do when it >does this? A parity error simply means that the contents of some memory location did not correspond to a "legal" value for your system. Parity checking is a simple but useful means for detecting otherwise "silent" errors that could nonetheless corrupt your data. Since your "Summary" line suggests that your PC was not doing this before, I'd say there are two likely reasons for it. (1) Sometimes the contacts between chips and their sockets "loosen up"; try reseating your memory chips, carefully (don't bend the pins -- this is very easy to do by mistake, and a real pain to correct -- if you break a pin, you'll have to replace the chip). That might correct the problem. (2) You might have a bad memory chip/module. If so, once you locate it, you can replace it. If your "parity error" message contains a numeric string (could be a combination of digits 0-9 and letters a-f, since it's frequently expressed in hexadecimal), this is identifying the memory location of the error. Depending on your PC and configuration, this should point you to the offending chip. Otherwise, there's the tried and true method of swapping two chips at a time until the location moves. Then you know it's one of the two, and you can swap each of this, in turn, with another chip to determine which one it is. Clearly, if you have the necessary info for your system, using the address is the preferred method. You might get more response to this question if you posted it in a more suitable newsgroup, like maybe comp.sys.ibm.pc.hardware.misc. -- Ken Bell (kenbell@panix.com -or- syklb@nasagiss.giss.nasa.gov)
Technical Details
Message-ID:
<2s0qfk$ebq@panix.com>Path:
arc1-ca.pugleaf.net!bga.com!cs.utexas.edu!usc!nic-nac.CSU.net!charnel.ecst.csuchico.edu!yeshua.marcam.com!zip.eecs.umich.edu!panix!not-for-mailReferences:
<kozu0003.769894089@gold>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 106ed4,202ea9728c5e1ce0 X-Google-Attributes: gid106ed4,public X-Google-Thread: f765b,202ea9728c5e1ce0 X-Google-Attributes: gidf765b,public X-Google-Thread: 10a12a,202ea9728c5e1ce0 X-Google-Attributes: gid10a12a,public X-Google-Thread: 1073ca,202ea9728c5e1ce0 X-Google-Attributes: gid1073ca,public X-Google-Thread: 103916,202ea9728c5e1ce0 X-Google-Attributes: gid103916,public X-Google-ArrivalTime: 1994-05-25 17:28:56 PST Path: arc1-ca.pugleaf.net!bga.com!cs.utexas.edu!usc!nic-nac.CSU.net!charnel.ecst.csuchico.edu!yeshua.marcam.com!zip.eecs.umich.edu!panix!not-for-mail From: kenbell@panix.com (Ken Bell) Newsgroups: mn.general,co.general,ca.general,ny.general,tx.general Subject: Re: Parity check error-What is it? HELP PLEASE! Date: 25 May 1994 20:28:36 -0400 Organization: PANIX Public Access Internet and Unix, NYC Lines: 38 Message-ID: <2s0qfk$ebq@panix.com> References: <kozu0003.769894089@gold> NNTP-Posting-Host: panix.com