open https://gitlab.synchro.net/main/sbbs/-/issues/1089

Initially reported via IRC:
```
<esc> Faulting application name: sbbs.exe, version: 0.0.0.0, time stamp: 0x699eb724
<esc> Faulting module name: MSVCP140.dll, version: 14.16.27024.1, time stamp: 0x5be33050
<esc> Exception code: 0xc0000005
<esc> Fault offset: 0x0001d387
<esc> Faulting process id: 0x3C8C
<esc> Faulting application start time: 0x1DCA6A906E467D0
<esc> Faulting application path: C:\sbbs\exec\sbbs.exe
<esc> Faulting module path: C:\Windows\SYSTEM32\MSVCP140.dll
<esc> Report Id: 1cc1926a-f349-47ec-8dff-159e958a099a
<esc> Faulting package full name:
<esc> Faulting package-relative application ID:
<DigitalMan> definitely looks like a crash
<DigitalMan> this is a fresh install or an upgrade?
<esc> This is an upgrade but I had the same behavior on a fresh install <DigitalMan> weird that there's no log output
<esc> Reinstalled msvc++ 2015-2022 x86 and the crash is gone. Woot!
```
Apparently reinstalling or upgrading the Microsoft C++ runtime fixed the issue. --- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/1089#note_8470

Another report (by Biggieb)
```
Faulting module name: MSVCP140.dll, version: 14.0.24215.1, time stamp: 0x57bfd592
```
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/1089#note_8471

This looks like the link to use to update the MS C++ runtime for x86: https://aka.ms/vc14/vc_redist.x86.exe
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/1089#note_8473

It appears disabling the Filter File Cache (in SCFG->System->Advanced Options) is another work-around:
``` ╔[■][?]══════════════════════════════════════════╗
║ Advanced Options ║ ╠════════════════════════════════════════════════╣
║ │Output SIF Questionnaire ║
║ │Credits Per Dollar 2,097,152 ║
║ │Minutes Per 100K Credits 6 ║
║ │Maximum Number of Minutes Unlimited ║
║ │Warning Days Till Expire 30 ║
║ │Last Displayable Node 250 ║
║ │Phone Number Format !!!!!!!!!!!! ║
║ │Sysop Chat Override ║
║ │User Database Backups 5 ║
║ │Mail Database Backups 5 ║
║ │Configuration Backups 5 ║
║ │Maximum Log File Size 10M bytes, keep 10 ║
║ │Maximum User Inactivity 15 minutes ║
║ │User Inactivity Warning 75 percent ║
║ │Control Key Pass-through 0 ║
║ │Statistics Interval 10 seconds ║
║->Cache Filter Files <disabled> <- ║ ╚════════════════════════════════════════════════╝
```
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/1089#note_8475

Appears to be triggered by use of std::mutex
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/issues/1089#note_8480

It's crashing in filterFile::listed() upon mutex acquisition.

This happens whether using std::mutex or our pthread_mutex wrappers around Win32 Critical Sections. Using *actual* Win32 Mutexes (defining PTHREAD_MUTEX_AS_WIN32_MUTEX) seems to solve the problem as well (but undesirable due to performance).
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

close https://gitlab.synchro.net/main/sbbs/-/issues/1089
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)