Date: Mon, 22 Sep 2003 21:20:59 +0200 From: Stijn Hoop <stijn@win.tue.nl> To: Lowell Gilbert <freebsd-chat-local@be-well.no-ip.com> Cc: freebsd-chat@freebsd.org Subject: Re: faulty memory Message-ID: <20030922192059.GB663@pcwin002.win.tue.nl> In-Reply-To: <44brtc4pzr.fsf@be-well.ilk.org> References: <200309221425.h8MEPWY68417@alogis.com> <20030922171115.GB45499@freebie.xs4all.nl> <20030922182130.GA663@pcwin002.win.tue.nl> <44brtc4pzr.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--xgyAXRrhYN0wYx8y Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 22, 2003 at 02:50:16PM -0400, Lowell Gilbert wrote: > Stijn Hoop <stijn@win.tue.nl> writes: > > I just had this problem, P4 on Gigabyte mainboard, DDR400 memory, 2 DIM= Ms > > 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. > >=20 > > When I ran memtest on the machine with both DIMMs in, it would consiste= ntly > > show errors in one 512 half though, and so I returned the one 'faulty' = DIMM > > and all was well. > >=20 > > Talk about strange... >=20 > Not that strange. The second socket was having problems. =20 > Maybe just couldn't handle the capacitance load it was=20 > getting (which could be different with other modules;=20 > other sized modules, anyway). Err, my sentence above tried to convey that, with both DIMMs in the machine, running memtest produced consistent errors _IN ONE DIMM_. That is, I swapped the two DIMMs and memtest started showing errors in the other 512MB.=20 In fact, the machine is running happily with the swapped DIMM in the same socket that the faulty one had. So I doubt that it's the socket :) --Stijn --=20 "Linux has many different distributions, meaning that you can probably find one that is exactly what you want (I even found one that looked like a Unix system)." -- Mike Meyer, from a posting at questions@freebsd.org --xgyAXRrhYN0wYx8y Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/b0ubY3r/tLQmfWcRAktAAJ0f2uC75hH9DY1vmC7tH+b5dzEMqwCbBjA+ B5HWwufDdZKQb+eBr5IMtqU= =kS5I -----END PGP SIGNATURE----- --xgyAXRrhYN0wYx8y--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030922192059.GB663>