From owner-freebsd-questions@FreeBSD.ORG Wed Jul 18 04:47:21 2007 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1784416A50D for ; Wed, 18 Jul 2007 04:47:21 +0000 (UTC) (envelope-from mark@giovannetti.ca) Received: from www.giovannetti.ca (www.giovannetti.ca [206.248.136.48]) by mx1.freebsd.org (Postfix) with ESMTP id E09C713C428 for ; Wed, 18 Jul 2007 04:47:20 +0000 (UTC) (envelope-from mark@giovannetti.ca) Received: from t.palaceofretention.ca (intgateway.palaceofretention.ca [10.10.10.42]) by www.giovannetti.ca (Postfix) with ESMTP id 13FA111460 for ; Wed, 18 Jul 2007 00:32:13 -0400 (EDT) Message-ID: <469D964B.70906@giovannetti.ca> Date: Wed, 18 Jul 2007 00:25:47 -0400 From: mark User-Agent: Thunderbird 2.0.0.0 (X11/20070528) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <200706152133.27118.slvhwke@optusnet.com.au> <20070618012935.S5906@fledge.watson.org> <002d01c7b178$a8e65e10$a3fd31d2@daisy> In-Reply-To: <002d01c7b178$a8e65e10$a3fd31d2@daisy> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: KDE 3.5 Crashing X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jul 2007 04:47:21 -0000 Gemma Fletcher wrote: >> I apologize in advance if this advice is too rudimentary. > > Rudimentry is good :) I am a BSD noob :D > >> Sounds more like hardware. You did not say how you tested your memory. If > you >> did not use Memtest86, get and run that. Also run fsck manually. > > I used Memtest and I have had already run fsck since my poor hard drive was > compaining bitterly of so many cold restarts. There were some errors that > were cleaned up - and it seems a bit more stable hours before freezing> > [snip] I've had many freezes with FreeBSD 6.2 and nvidia cards on at least 3 separate systems. The thing that has fixed it on every system has been to use portdowngrade to reset the nvidia driver to: nvidia-driver-1.0.8776 (possibly with an extra _4 in the portdowngrade list) Hope this helps.