From owner-freebsd-chat@FreeBSD.ORG  Mon Sep 22 11:50:25 2003
Return-Path: <owner-freebsd-chat@FreeBSD.ORG>
Delivered-To: freebsd-chat@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 71E5716A501
	for <freebsd-chat@freebsd.org>; Mon, 22 Sep 2003 11:50:20 -0700 (PDT)
Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [204.127.202.55])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E9A2543FF2
	for <freebsd-chat@freebsd.org>; Mon, 22 Sep 2003 11:50:18 -0700 (PDT)
	(envelope-from freebsd-chat-local@be-well.no-ip.com)
Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37])
          by comcast.net (sccrmhc11) with ESMTP
          id <2003092218501801100doltle>; Mon, 22 Sep 2003 18:50:18 +0000
Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37]
	(may be forged))
	by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h8MIoH5k046017;
	Mon, 22 Sep 2003 14:50:17 -0400 (EDT)
	(envelope-from freebsd-chat-local@be-well.no-ip.com)
Received: (from lowell@localhost)
	by be-well.ilk.org (8.12.9/8.12.6/Submit) id h8MIoG6E046014;
	Mon, 22 Sep 2003 14:50:16 -0400 (EDT)
X-Authentication-Warning: be-well.ilk.org: lowell set sender to
	freebsd-chat-local@be-well.ilk.org using -f
Sender: lowell@be-well.no-ip.com
To: Stijn Hoop <stijn@win.tue.nl>
References: <200309221425.h8MEPWY68417@alogis.com>
	<20030922171115.GB45499@freebie.xs4all.nl>
	<20030922182130.GA663@pcwin002.win.tue.nl>
From: Lowell Gilbert <freebsd-chat-local@be-well.no-ip.com>
Date: 22 Sep 2003 14:50:16 -0400
In-Reply-To: <20030922182130.GA663@pcwin002.win.tue.nl>
Message-ID: <44brtc4pzr.fsf@be-well.ilk.org>
Lines: 18
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: freebsd-chat@freebsd.org
Subject: Re: faulty memory (was Re: Gcc 3.2.2 vs gcc 3.2.3)
X-BeenThere: freebsd-chat@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Non technical items related to the community
	<freebsd-chat.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chat>,
	<mailto:freebsd-chat-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chat>
List-Post: <mailto:freebsd-chat@freebsd.org>
List-Help: <mailto:freebsd-chat-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chat>,
	<mailto:freebsd-chat-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Sep 2003 18:50:25 -0000

Stijn Hoop <stijn@win.tue.nl> writes:

> I just had this problem, P4 on Gigabyte mainboard, DDR400 memory, 2 DIMMs
> of 512 MB each. With a single DIMM (both DIMMs tested) memtest didn't
> find anything and the machine was rock stable, but in any combo of the
> 2 DIMMs, dual channel or not, the machine would lock up / throw
> gcc ICE everytime.
> 
> When I ran memtest on the machine with both DIMMs in, it would consistently
> show errors in one 512 half though, and so I returned the one 'faulty' DIMM
> and all was well.
> 
> Talk about strange...

Not that strange.  The second socket was having problems.  
Maybe just couldn't handle the capacitance load it was 
getting (which could be different with other modules; 
other sized modules, anyway).