Date: Tue, 08 Nov 2005 22:30:56 -0500 From: Chuck Swiger <cswiger@mac.com> To: Vulpes Velox <v.velox@vvelox.net> Cc: freebsd-questions@freebsd.org Subject: Re: Installation problem with Freebsd 5.4 Message-ID: <43716D70.1040604@mac.com> In-Reply-To: <20051108190126.424fc6d6@vixen42.vulpes> References: <e8ecf3c00510250620k648374e1lca149d61d03cc536@mail.gmail.com> <e8ecf3c00510250639xac0f4d3m26b7ec8812e6602d@mail.gmail.com> <20051025135801.GA66887@slackbox.xs4all.nl> <20051108190126.424fc6d6@vixen42.vulpes>
next in thread | previous in thread | raw e-mail | index | archive | help
Vulpes Velox wrote: > On Tue, 25 Oct 2005 15:58:01 +0200 > Roland Smith <rsmith@xs4all.nl> wrote: [ ... ] >> One thing you could try is to burn a 6.0-RC1 CD and try that. Test >> your memory with memtest86 (http://www.memtest86.com/). > > Memtest86 does not tell you if you have bad ram. It just indicates > that something some where is wrong with that system there. I've seen > it hit errors with bad motherboards as well. It's true that problems with overheating or a bad MB will generate errors that memtest86 will see, but memtest86 is really good at noticing bad RAM. It will catch errors that the BIOS self-test won't (which isn't too hard :-), and I've never seen memtest86 fail to detect bad RAM.... -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?43716D70.1040604>