Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Sun, 20 Jan 2002 18:29:00 GMT Message-Id: <200201201829.SAA29423@london.beasys.com> X-Resent-Mailer: 21.5 (beta4) "bamboo" XEmacs Lucid (via feedmail 10 I) Resent-From: "Philip Aston" Resent-Message-ID: <15435.2985.182000.785672@bea.com> Resent-Date: Sun, 20 Jan 2002 18:25:45 +0000 Resent-To: cygwin@cygwin.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit From: "Philip Aston" To: Charles Wilson Cc: cygwin@cygwin.com Subject: Re: touch caused BSOD! In-Reply-To: <3C4B0704.201@ece.gatech.edu> References: <200201201652.QAA28969@london.beasys.com> <3C4B0704.201@ece.gatech.edu> X-Mailer: 21.5 (beta4) "bamboo" XEmacs Lucid (via feedmail 10 Q); VM 7.00 under 21.5 (beta4) "bamboo" XEmacs Lucid Charles Wilson writes: > Go to "My Computer"->Properties->"Advanced Tab"->"Startup and Recovery" > > Then, in the "Write debugging information" chooser, pick "Small Memory > Dump (64k)". Make a note of the filenmae to which the memory dump will > be saved. Then Exit. > > Now, make your system BSOD again. Then, you'll have a debuggable dump > of kernel memory. At that point, somebody on this list should be able > to identify what module in memory caused the BSOD -- but you probably > don't want to post the dump to the list for size & privacy reasons. So, > once you have the dump, ask again for help in unraveling it. (You need > MSVC with kernel symbols installed; I don't have that so I can't help > you-- but hopefully someone can). Thanks Chuck, I have several of these dumps - anyone care to volunteer to analyze one or two? Thanks, - Phil -- 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/