From owner-freebsd-hardware Wed Jul 12 10:30:11 2000 Delivered-To: freebsd-hardware@freebsd.org Received: from envy.vuurwerk.nl (envy.vuurwerk.nl [194.178.232.112]) by hub.freebsd.org (Postfix) with SMTP id 146F837BE5D for ; Wed, 12 Jul 2000 10:29:44 -0700 (PDT) (envelope-from petervd@daemon.vuurwerk.nl) Received: (qmail 68391 invoked from network); 12 Jul 2000 17:29:35 -0000 Received: from kesteren.vuurwerk.nl (HELO daemon.vuurwerk.nl) (194.178.232.59) by envy.vuurwerk.nl with SMTP; 12 Jul 2000 17:29:35 -0000 Received: (nullmailer pid 96704 invoked by uid 11109); Wed, 12 Jul 2000 17:29:35 -0000 Date: Wed, 12 Jul 2000 19:29:35 +0200 From: Peter van Dijk To: hackers@FreeBSD.ORG, hardware@freebsd.org Subject: Re: System Crash Message-ID: <20000712192935.G95013@vuurwerk.nl> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from john@essenz.com on Wed, Jul 12, 2000 at 01:45:56PM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Jul 12, 2000 at 01:45:56PM -0400, Essenz Consulting wrote: > Question. > > I have a machine that is crashing. Basically, random processes will die > off and give SEGMENTATION FAULTS, then followed by a core dump, and the > machine halts. Has to be manual rebooted after that. I tryed another hard > drive in the machine, and same problems come up. So I am not sure if it is > bad memory or a bad processor, or a bad motherboard. Is there anyway to > find out? Replace one part at a time until the problems go away. Usually bad memory. Adjusting memory timings in your BIOS setup might help too. Greetz, Peter. -- petervd@vuurwerk.nl - Peter van Dijk [student:developer:ircoper] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message