From owner-freebsd-hardware@FreeBSD.ORG Thu Jul 16 20:27:37 2009 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 584F71065672 for ; Thu, 16 Jul 2009 20:27:37 +0000 (UTC) (envelope-from lgusenet@be-well.ilk.org) Received: from mail1.sea5.speakeasy.net (mail1.sea5.speakeasy.net [69.17.117.3]) by mx1.freebsd.org (Postfix) with ESMTP id 318008FC1A for ; Thu, 16 Jul 2009 20:27:37 +0000 (UTC) (envelope-from lgusenet@be-well.ilk.org) Received: (qmail 17779 invoked from network); 16 Jul 2009 20:00:56 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail1.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 16 Jul 2009 20:00:56 -0000 Received: by be-well.ilk.org (Postfix, from userid 1147) id 624A550822; Thu, 16 Jul 2009 16:00:55 -0400 (EDT) To: Adam Townsend To: freebsd-hardware@freebsd.org References: <26d677980907160653u15f26dbes2ddbbbffc5763d63@mail.gmail.com> From: Lowell Gilbert Date: Thu, 16 Jul 2009 16:00:55 -0400 In-Reply-To: <26d677980907160653u15f26dbes2ddbbbffc5763d63@mail.gmail.com> (Adam Townsend's message of "Thu\, 16 Jul 2009 09\:53\:39 -0400") Message-ID: <448wio8kjs.fsf@be-well.ilk.org> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-hardware@freebsd.org Subject: Re: computer keeps rebooting X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2009 20:27:37 -0000 Adam Townsend writes: > If I bump the processor back down to 3.8 GHz > it runs perfectly fine (ran it over 24 hours straight w/o any problems). My > Motherboard won't let me overclock past 4.2, it throws an error in the BIOS > about it, so the hardware can handle 4.0. Not that I'm positive it's your problem, but that last statement is categorically wrong. If the parts were all in spec to run at 4GHz, it wouldn't be called *over*clocking. It may work on some of these systems, but you don't get any guarantees when you go beyond the specifications (in fact, that's what the word "specifications" means).