Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <0d5601c1a9c7$3646f310$0200a8c0@lifelesswks> From: "Robert Collins" To: "Brian Genisio" , References: <20020130175547 DOT 31670 DOT qmail AT web20802 DOT mail DOT yahoo DOT 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 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-OriginalArrivalTime: 30 Jan 2002 19:49:10.0715 (UTC) FILETIME=[2FB658B0:01C1A9C7] === ----- Original Message ----- From: "Brian Genisio" To: "Robert Collins" ; 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/