X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4045F53376 for ; Sun, 17 Apr 2005 22:43:01 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 71879-06 for ; Mon, 18 Apr 2005 01:42:52 +0000 (GMT) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [204.127.202.59]) by svr1.postgresql.org (Postfix) with ESMTP id EC92553442 for ; Sun, 17 Apr 2005 22:42:50 -0300 (ADT) Received: from spectre (c-66-30-216-118.hsd1.ma.comcast.net[66.30.216.118]) by comcast.net (sccrmhc14) with SMTP id <2005041801425301400h3gs5e>; Mon, 18 Apr 2005 01:42:54 +0000 From: "Ian Westmacott" To: "Brennan Stewart" Cc: Subject: Re: database corruption Date: Sun, 17 Apr 2005 21:20:00 -0400 Message-ID: <000101c543b4$bd7eb860$76d81e42@hsd1.ma.comcast.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-Reply-To: <425691EC.1050709@ideahamster.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.204 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200504/219 X-Sequence-Number: 17232 > In your previous emails, you stated that these errors were seen on > multiple systems. Multiple systems, configured identically, with > diverse motherboards/hardware or always identical hardware except for > the sata/IDE drives? > > I ask, because I noted that you are using the Neo 2 ATX motherboard that > has the "dynamic overclocking" feature. This can cause grave > instability in systems when it set to an aggressive setting. This > motherboard is not compatible with low quality ram either. This > motherboard also is prone to heat problems, and requires extra cooling. > If you have multiple systems failing, using this motherboard, then that > particular model could be the culprit. We have seen this using at least one other motherboard besides the Neo 2 ATX. And (fortunately or unfortunately) we don't use the dynamic overclocking feature. Do you know how the RAM incompatibility is manifest? Thanks, --Ian