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 Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Dave Korn" To: Subject: RE: cygwin reboots my PC randomly Date: Thu, 30 Dec 2004 19:55:10 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit In-Reply-To: Message-ID: X-OriginalArrivalTime: 30 Dec 2004 19:55:10.0671 (UTC) FILETIME=[783305F0:01C4EEA9] > -----Original Message----- > From: cygwin-owner On Behalf Of Andrew DeFaria > Sent: 29 December 2004 23:28 > Marc J wrote: > > > I am not getting BSOD. > > > > Checked the event log: > > dec 25 108am Source Save Dump, event 1001 > > The computer has rebooted from a bugcheck. The bugcheck > was: 0x000000d4 > > (0xbad0b0e4, 0x00000002, 0x00000001, > > 0x8006543a). Microsoft Windows 2000 [v15.2195]. A dump was saved in: > > C:\WINNT\Minidump\Mini122504-01.dmp. > > BTW, you might want to turn off that minidump thing. I can't recall a > single time that anyone has ever actually used one of them! Nonsense! All those bugcheck codes are excellent indicators of a faulty kernel-mode driver and if he was to open one up in windbg it would tell him in an instant which driver was at fault. They are very useful postmortem diagnostics! Not as much as a full memory dump of course, but they'll let you narrow it down; I've frequently diagnosed faulty drivers this way. cheers, DaveK -- Can't think of a witty .sigline today.... -- 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/