Article View: mn.general
Article #615Re: Parity check error-What is it? HELP PLEASE!
From: steve skierka
Date: Thu, 26 May 1994 17:37
Date: Thu, 26 May 1994 17:37
36 lines
3293 bytes
3293 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 check is simply a means of detecting errors in data transmission. Commonly, the bits contained in a byte (which can represent a data item such as a numerically coded ASCII character or a simple number), in memory, on disk, over a network, etc, are counted. Then it is determined whether this count is odd or even. From this an extra bit (the parity bit) is then added to the byte indicating whether the bit count is odd or even (1 or 0) . Upon reception, the bits in the byte are then recounted, the count is then determined to be odd or even, and this result is then compared with the transmitted parity bit. An error would indicate that the parity did not match and that the data received is flawed. While this is not a full-proof method of error detection, it works a large majority of time and is among the simplest methods. As to your problem, I expect this error being reported is only related to your PC and not to a modem, etc. It is very likely that you have a bad memory chip somewhere which is causing the parity check error while data is being trans- ferred in memory. Usually a code will accompany such an error and can often point you to the set of memory chips (SIMM board for example), where the error was detected. I suggest you determine from either a tech manual or from a technical support outlet which memory board is the culprit and replace it. Another method is to swap out successive memory boards with a known good memory board and see which board when removed, takes away this problem. One other possibility is that there may be bad electrical contacts between the system boards and the computer. All that may be necessary to fix this problem is to simply remove all the boards (not just memory, taking care to handle them only by the edges to avoid finger prints and/or static discharges), clean the copper contacts (an eraser does a good job), then carefully reinsert all the boards, making sure of good electrical contact. I hope you find this useful.
Technical Details
Message-ID:
<CqF7n2.1CEB@yuma.ACNS.ColoState.EDU>Path:
arc1-ca.pugleaf.net!bga.com!cs.utexas.edu!usc!howland.reston.ans.net!usenet.ins.cwru.edu!att-in!csn!yuma!skierkaReferences:
<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: 1073ca,202ea9728c5e1ce0 X-Google-Attributes: gid1073ca,public X-Google-Thread: 103916,202ea9728c5e1ce0 X-Google-Attributes: gid103916,public X-Google-Thread: f765b,202ea9728c5e1ce0 X-Google-Attributes: gidf765b,public X-Google-Thread: 10a12a,202ea9728c5e1ce0 X-Google-Attributes: gid10a12a,public X-Google-ArrivalTime: 1994-05-26 11:17:58 PST Newsgroups: mn.general,co.general,ca.general,ny.general,tx.general Path: arc1-ca.pugleaf.net!bga.com!cs.utexas.edu!usc!howland.reston.ans.net!usenet.ins.cwru.edu!att-in!csn!yuma!skierka From: skierka@CS.ColoState.EDU (steve skierka) Subject: Re: Parity check error-What is it? HELP PLEASE! Sender: news@yuma.ACNS.ColoState.EDU (News Account) Message-ID: <CqF7n2.1CEB@yuma.ACNS.ColoState.EDU> Date: Thu, 26 May 1994 17:37:50 GMT References: <kozu0003.769894089@gold> Nntp-Posting-Host: beethoven.cs.colostate.edu Organization: Colorado State University -- Computer Science Department Lines: 37