From owner-freebsd-hackers Wed Jul 12 11: 5:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id E202B37BCD4; Wed, 12 Jul 2000 11:05:07 -0700 (PDT) (envelope-from simon@optinet.com) Received: from station1 (adsl-151-202-97-90.bellatlantic.net [151.202.97.90]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id LAA03843; Wed, 12 Jul 2000 11:59:23 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200007121759.LAA03843@mail.fpsn.net> From: "Simon" To: "Essenz Consulting" , "hackers@FreeBSD.ORG" , "hardware@FreeBSD.ORG" Date: Wed, 12 Jul 2000 14:08:06 -0500 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: System Crash Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I say it's a bad memory. I had the same problem. -Simon On Wed, 12 Jul 2000 13:45:56 -0400 (EDT), 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? > >-john v. e. > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message