On 2018-05-15 18:22, L A Walsh wrote:
> Someone wrote:
>> I tried it for the hell of it. It worked ok for me. 
>> Running windows 10 - build 1803 -
>>
>> $ uname -a
>> CYGWIN_NT-10.0 spiro1 2.9.0(0.318/5/3) 2017-09-12 10:18 x86_64 Cygwin
>>
>> Running as an normal user - I did not try an admin acct.
>>
>> Good luck, someone
> ----
>     (FYI -- replying to this "on-list", but anonymizing the sender's
> info in case they didn't want it posted.)
> 
>     I wonder if it is Win7 specific or a quirk in my system.
> Too often it is some peculiarity in my system.
> 
> Thanks for the data point.

Here's another one: works4me on my Windows 7.
> CYGWIN_NT-6.1 Bahamut 2.10.0(0.325/5/3) 2018-02-02 15:16 x86_64 Cygwin

No BSOD when running that in my home directory.

I was lead to believe that no userland code could trigger BSODs anymore
so I don't think that is normal.  But maybe that is was only for 8+.
Next time you feel like triggering one read what "module" the fault was
in.  Last time I got one (caused by OC instability) I think it was in
ntfs.sys.