public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: normal to blue-screen windows when doing 'ls -CF' of /proc/sys/GLOBAL?? (bug? cygcheck attached)
Date: Thu, 17 May 2018 13:22:00 -0000	[thread overview]
Message-ID: <5AFD4346.9060207@tlinx.org> (raw)
In-Reply-To: <405455534.20180516183915@yandex.ru>

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

  reply	other threads:[~2018-05-17  8:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 12:58 L A Walsh
     [not found] ` <000a01d3ec54$a2bb2ca0$e83185e0$@rogers.com>
2018-05-15 16:51   ` L A Walsh
2018-05-15 17:18     ` James Darnley
     [not found]     ` <2b3cf1ed-1a3f-d8ff-136b-0ee533ae9e59@wagner.is>
2018-05-15 19:54       ` L A Walsh
2018-05-16 17:26 ` Andrey Repin
2018-05-17 13:22   ` L A Walsh [this message]
2018-05-17 19:41     ` Brian Inglis
2018-05-17 20:38       ` L A Walsh
2018-05-17 22:09       ` Michel LaBarre
2018-05-18  4:49         ` L A Walsh
2018-05-20 11:37 David Conrad
2018-05-21 20:18 ` L A Walsh
2018-05-22  2:07   ` Michel LaBarre
2018-05-22 10:48     ` L A Walsh
2018-05-23 20:13   ` Andrey Repin
2018-05-25  3:25     ` L A Walsh
2018-05-25 14:56       ` Andrey Repin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5AFD4346.9060207@tlinx.org \
    --to=cygwin@tlinx.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).