Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <002801c23fac$07ce4a80$ca285386@pinnacles>
From: Thomas Dewez <thomas DOT dewez AT brunel DOT ac DOT uk>
To: cygwin <cygwin AT cygwin DOT com>
Subject: Cygwin crashes XP Pro
Date: Fri, 9 Aug 2002 14:52:41 +0100
Organization: Brunel University
X-Priority: 3
X-MSMail-Priority: Normal
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-transfer-encoding: 7bit

Hi there,

I am totally baffled by this problem and would appreciate any help. I have
been experiencing constant crashes of XP Pro on a laptop Compaq Presario
2700 (intel 1GHz) running Cygwin 1.3.12-4.

The most noticeable symptom of an imminent crash is the fan speeding up. The
crash produces a Blue Screen of Death with error 0x96 or error 0xA (writing
operation). I have checked the Microsoft knowledge base to troubleshoot but
none of the explanations proved relevant (as far as I could see).

I can use cygwin for a long time if I am not asking it to perform a CPU
intensive task. However as soon as the task becomes too CPU intensive, the
fan starts speeding up and will eventually crash. The time between the fan
speeding up and a crash is variable and can last a few hours if the CPU
demand slows down.

I observed another symptom with the Task Manager. The "System" process takes
over 90% of the CPU power when the fan starts speeding up. I tried compiling
GRASS GIS yesterday and whilst XP crashed after a while of executing the
make command and outputing the result on the screen, it remained perfectly
intact if I directed the output to a log file. Is this a sign of a poor
interaction between XP and Cygwin? It looks as though the memory cannot be
released and the system dies when the memory is filled up (I have 512Mb of
RAM and 1350Mb of page file).

Any hint would be most appreciated

Thomas


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/