Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Message-ID: <0d5601c1a9c7$3646f310$0200a8c0@lifelesswks>
From: "Robert Collins" <robert.collins@itdomain.com.au>
To: "Brian Genisio" <briangenisio@yahoo.com>, <cygwin@cygwin.com>
References: <20020130175547.31670.qmail@web20802.mail.yahoo.com>
Subject: Re: Blue Screen Of Death
Date: Thu, 31 Jan 2002 06:49:20 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


===
----- Original Message -----
From: "Brian Genisio" <briangenisio@yahoo.com>
To: "Robert Collins" <robert.collins@itdomain.com.au>;
<cygwin@cygwin.com>
Sent: Thursday, January 31, 2002 4:55 AM
Subject: Re: Blue Screen Of Death


> So, does that mean I need to restructure my question?  I will try
again...
>
> If anybody knows why this might be happening, would you be so kind as
to tell
> me what your ideas on this matter are?

Yes, you are triggering a fault in a device driver on your system, it
may be a MS fault, or a third party driver fault.

Get a minidump or a full dump, and use the kernel debugger kdi386.exe
from http://www.microsoft.com/ddk/debugging/ to get a backtrace with
symbols. That should help figure out whether it's MS or someone else you
need to go beat up on.

Oh, and it's not Cygwin, irrespective of the appearance: This is a
kernel mode   fault that isn't being handled, and Cygwin doesn't have
any ring-0/NT native code in it. Cygwin may just be setting things up so
that the bug is exposed.

Rob


--
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/