DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=fe+oC9Kebv7DX4Dk
	sajA/TLXIAhZccvNStNYSGkDQMPux226AEuZX+F56M4nULbWh2sd/MyPhMFMh3jn
	yywPfZhkKiukqxpQL0xUVQYiWJ7jwsxCLZrnGAsulLtMBTY1/n/5EiBrIkwnj4mz
	qKK8iKytUQrGykv9Z8bPBrQVidU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached)
To: cygwin AT cygwin DOT com
References: <5AFAD73A DOT 9090806 AT tlinx DOT org> <405455534 DOT 20180516183915 AT yandex DOT ru> <5AFD4346 DOT 9060207 AT tlinx DOT org>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp: preference=signencrypt
Message-ID: <4310b729-b8b1-03aa-1c59-7a9c902edfef@SystematicSw.ab.ca>
Date: Thu, 17 May 2018 09:04:17 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <5AFD4346.9060207@tlinx.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Note-from-DJ: This may be spam

On 2018-05-17 02:54, L A Walsh wrote:
> 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...

Run "cygcheck ls" to see if any Windows installs added to your path pick up
api-ms-win-core-... intercept dlls e.g. Firefox, Tortoise, etc.
Tried running same command under strace?
BLODA possibly messing up net access to AD?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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