Date: Mon, 11 Sep 2006 09:54:50 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: setup.exe -> BSOD
Message-ID: <20060911135450.GA26747@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20060911124918 DOT GB10375 AT localhost DOT localdomain> <450561E6 DOT 6020308 AT cygwin DOT com> <20060911134640 DOT GA12656 AT localhost DOT localdomain>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060911134640.GA12656@localhost.localdomain>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

On Mon, Sep 11, 2006 at 02:46:40PM +0100, John Smith wrote:
>On Mon, Sep 11, 2006 at 09:17:26AM -0400, Larry Hall (Cygwin) wrote:
>>BSOD situations point to a problem with the O/S kernel, not the app
>>that may be running at the time they occur.  Problematic drivers are
>>the most common causes here.  I'd recommend un-installing any recent
>>additions made in this area and see if it helps.
>
>Difficult to guess what might be at fault.  First guess (NX client)
>made no difference.
>
>>On the flip side, if you'd like to get a better look at the BSOD, you
>>can turn off the automatic reboot using the "System" applet in your
>>control panel.
>
>This identifies the problem as DRIVER_IRQL_NOT_LESS_OR_EQUAL, and cites
>the following technical info:
>
>*** STOP: 0X000000D1 (0X82400000, 0X00000002, 0X00000000, 0XF80B4988)
>
>*** w22n51.sys - Address F80B4988 base at F8040000, Datestamp 404c5c4c

google would seem to be pretty instructive here.

cgf

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