X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=rLu53h5gpWXijxmaNHONUXDMmRkALUmeN3NF1Q+Wtzx v3lEeRJdDEUeBXDkzn7cPG12TXiUjEz9LnKVlxXXrruFXIwSEFxnikvO3rtaZQ+4 vMk+kPNhHe/fHGWu1Fwtm7l8xgAZBW4JAvDJMXFrSVN62oTmIC9uzLWKoiQvYIqc = DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=eImXLA1Q6fIgIj+3zXdy/oePebs=; b=xDefy0uXYiR5TF29e 0KnizV04GIcBmCwFfmtfaxxntRyjj0aKts/x2SZExTKkrFXWhXlLJG6NfZbHeQHf upvX/OG4phTEoLwST8f3oU5S4Lmy3Qb8Jjgjfd9M0m+Aqji+bzdFN/OeUYGZhiKV /NKLkathN08ZDZ73FNDZOwM9qE= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-6.9 required=5.0 tests=BAYES_00,GIT_PATCH_2 autolearn=ham version=3.3.2 spammy=displays, H*r:192.168.3, opportunity X-HELO: Ishtar.sc.tlinx.org Message-ID: <5AFD4346.9060207@tlinx.org> Date: Thu, 17 May 2018 01:54:30 -0700 From: L A Walsh User-Agent: Thunderbird MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached) References: <5AFAD73A DOT 9090806 AT tlinx DOT org> <405455534 DOT 20180516183915 AT yandex DOT ru> In-Reply-To: <405455534.20180516183915@yandex.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Andrey Repin wrote: > After BSOD, there should be at least aminibump. > You can use http://nirsoft.net/utils/blue_screen_view.html to examine it. ---- Tried it...showed nothing. Checked sysprops and the small memory dump (256KB) is enabled -- should have dumped in C:\windows\Minidump, but nothing was there. I did try to see the module when the blue screen was up, but it rebooted too quickly. > Do you perhaps have some misbehaving drivers in your system? > Try clearing up your device manager. > > SET DEVMGR_SHOW_NONPRESENT_DEVICES=1 && mmc.exe devmgmt.msc --- Didn't see anything that stood out, but took the opportunity to remove all the ones that didn't refer to existing HW. FWIW --- It almost has to be some misconfigured SW -- not any specific HW, since this windows image did the same thing on my last system. I had to get a new system and moved over the hard disk - updated needed drives and I was up (about 4-5 months ago). Very wierd. It triggers so fast, and whatever is causing it, likely happens on a probe by 'ls' before ls even displays any output. I 'can' go into the same directory and do a "echo *" (or better, printf "%s\n" * --- and that doesn't trigger it. I think I also triggered it once with 'tree'. Very annoying. Oh well, I suspected it wouldn't be simple, which is why I just try to "not do that"...but it had been a while, and thought maybe... *grumble* thanks for the ideas all... -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple