X-Spam-Check-By: sourceware.org
Message-ID: <43EC2D6C.D104DE40@dessent.net>
Date: Thu, 09 Feb 2006 22:06:36 -0800
From: Brian Dessent <brian AT dessent DOT net>
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygwin bsod using make after configure on gcc
References: <003601c62e00$a7a194e0$020aa8c0 AT DFW5RB41>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
Reply-To: cygwin AT cygwin DOT com
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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

"Gary R. Van Sickle" wrote:

> The only other help anybody can offer is to look at the BSOD info.  It used
> to tell you what kernel mode component was BSODing on you, but to tell you
> the truth it's been so long since I've seen one I don't know if it does
> anymore.  If it does, it will probably be a driver, and then you're 99% of
> the way towards a solution.

The way to proceed is to get the STOP code number and then go here:
<http://aumha.org/win5/kbestop.php>.

It's very hard for the BSOD screen to print the name of the kernel module that
actually is responsible for the fault, since it could have been the result of a
cascading failure.  Kernel mode stuff is just like that because there are no
restrictions at all as to what a driver can do, so it's entirely possible that
driver FOO might have been executing at the time of the fault but it was
innocent and only crashed because driver BAR overwrote some of its data
structures.  So don't expect to be told in the BSOD screen which driver is at
fault, and even if one is shown don't assume that's the faulty one.  (Some notes
on this issue from Raymond Chen:
<http://blogs.msdn.com/oldnewthing/archive/2004/03/05/84469.aspx#85992>.)

And yes, this likely has nothing to do with Cygwin and everything to do with
some kind of fault in the system (failing hardware, defective ram, a buggy
driver, flakey antivirus software, etc.)  Cygwin is just a regular user-mode
process, it does not install any kernel drivers and therefore cannot (directly)
cause a BSOD.  That's not to say that user-mode processes can't tickle bugs in
kernel drivers, but the fault there lies in the driver, not the user-mode
process.

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/