Path: utzoo!attcan!uunet!aplcen!uakari.primate.wisc.edu!uflorida!mailrus!cs.utexas.edu!usc!brutus.cs.uiuc.edu!psuvax1!psuvm!cunyvm!uupsi!rodan!amichiel
From: amichiel@rodan.acs.syr.edu (Allen J Michielsen)
Newsgroups: comp.sys.ibm.pc
Subject: Re: 201 Memory Fault Code question
Keywords: legend howto
Message-ID: <2001@rodan.acs.syr.edu>
Date: 6 Feb 90 19:14:49 GMT
References: <536@smcnet.UUCP> <25c86ca0:4498.1comp.sys.ibm.pc;1@vpnet.UUCP>
Reply-To: amichiel@rodan.acs.syr.edu (Allen J Michielsen)
Organization: Syracuse University, Syracuse, NY
Lines: 16

In article <25c86ca0:4498.1comp.sys.ibm.pc;1@vpnet.UUCP> akcs.amparsonjr@vpnet.UUCP (Anthony M. Parson, Jr.) writes:
>I've seen ads for software that purport to be able to tell you the exact
>chip that is defective.

In the 201 error, is the row number of the first defective chip.
This number is usually / always correct.  However, the rest of the
info, or any software perports to being able to identify the defective
chip further is best guessing.  Some best guess better than others.
If it's a soft error (most common) the best guess is pretty lousy.
If it's a hard error the best guess is pretty close or good.
If the error is actually in row 0, I don't believe any software in the
world exists to identify the defectice chip better than 1/9.
Most commonly, rows of chips come from the same mfg lot.  My experience
indicates that the tend to develope soft errors in close time related
batches.
al