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
Message-ID:	<004701c4edce$3561e330$05010e0a@2mbit.com>
From:	"Brian Bruns" <bruns AT 2mbit DOT com>
To:	<cygwin AT cygwin DOT com>
References:	<01f201c4ed61$52bc4fa0$cc01a8c0 AT p43000> <Pine DOT GSO DOT 4 DOT 61 DOT 0412291130230 DOT 8337 AT slinky DOT cs DOT nyu DOT edu>
Subject:	Re: cygwin reboots my PC randomly
Date:	Wed, 29 Dec 2004 12:45:35 -0500
MIME-Version:	1.0
X-Scan-Signature:	fb6800ab2c40e5c0a4c38b7dac67b41f
X-SA-Exim-Connect-IP:	138.89.18.207
X-SA-Exim-Mail-From:	bruns AT 2mbit DOT com
X-IsSubscribed:	yes

On Wednesday, December 29, 2004 11:31 AM [EST], Igor Pechtchanski
wrote:

>
> Unless you have a cron job that runs "shutdown -r" or "reboot" :-),
> Brian's reply pretty much explains it...
> Igor


A suggestion too - if you have mysterious reboots, turn off
"Automatically reboot" in the System control panel, under the Advanced
tab, and click the Startup and Recovery button.  That way, you
actually see the blue screen with the information that caused the
BSOD.

Otherwise, check the Event Logs, but I've seen times where crashes
were not properly recorded in the event logs.  So, turn off auto
reboot may be the best option.


-- 
Brian Bruns
The Summit Open Source Development Group
http://www.sosdg.org  /  http://www.ahbl.org


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

- Raw text -