From owner-freebsd-questions@FreeBSD.ORG Fri Nov 26 17:14:50 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5DF8516A4CE for ; Fri, 26 Nov 2004 17:14:50 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 043A043D5A for ; Fri, 26 Nov 2004 17:14:50 +0000 (GMT) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 15918 invoked from network); 26 Nov 2004 17:14:49 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 26 Nov 2004 17:14:49 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id EFE8469; Fri, 26 Nov 2004 12:14:46 -0500 (EST) Sender: lowell@be-well.ilk.org To: freebsd-questions@freebsd.org References: <6FC9F9894A9F8C49A722CF9F2132FC220276581D@ms05.mailstreet2003.net> <20041125234948.R27818@april.chuckr.org> From: Lowell Gilbert Date: 26 Nov 2004 12:14:46 -0500 In-Reply-To: <20041125234948.R27818@april.chuckr.org> Message-ID: <448y8osfax.fsf@be-well.ilk.org> Lines: 14 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: Is this a sign of memory going bad? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Nov 2004 17:14:50 -0000 Chuck Robey writes: > With that in mind, sometimes, the very best memory test programs can give > you better ideas that memory you thought was failing IS failing. The > opposite, proving that memory is good, is just totally, totally useless, > you cannot take any data home at all about your memory being good. That's exactly right. The false negative rate is quite high, but the false positive rate is virtually zero. However, this makes it far from useless, because in cases like the question that started the thread, bad memory *is* extremely likely to be the cause, and a software memory tester is probably going to report that. Given the frequency with which messages on this list say "no, it can't be bad memory because it works under Windows," this is *extremely* useful.