[Skimmertalk] Can't keep SkimSrv/SkimSrv2 running any more, "Error writing to xxxx" 0xc0000005 in ntdll.dll

[N4ZR]

Hi Bob - my similar error didn't name the DLL, but the access violation 
was similar - trying to write to "0014".  I surmise that the problem 
lies in the operating system somewhere.  My computer where this was 
happening dies during WAE, so we will never know.

73, Pete N4ZR
Check out the Reverse Beacon Network
at <http://reversebeacon.net>, now
spotting RTTY activity worldwide.
For spots, please use your favorite
"retail" DX cluster.

On 8/16/2018 4:40 AM, Bob Wilson, N6TV wrote:
> After working very reliably for months, my CW Skimmer Servers are now
> crashing every few hours, starting about 2 days ago, after a Windows 10
> service upgrade.  I'm running two Skimmers, from independent directories,
> using independent Red Pitayas (but the same disk and same gigabit switch to
> connect to them both to the same PC).
>
> The Windows Event Viewer, under Windows Logs, Application, shows a similar
> error each time:
>
> Faulting application name: SkimSrv2.exe, version: 1.6.0.145, time stamp:
> 0x2a425e19
> Faulting module name: ntdll.dll, version: 10.0.17134.228, time stamp:
> 0x2c71c7b8
> Exception code: 0xc0000005
> Fault offset: 0x00022e19
> Faulting process id: 0x890
> Faulting application start time: 0x01d4352a4ed8c491
> Faulting application path: C:\Program Files
> (x86)\Afreet\SkimSrv2\SkimSrv2.exe
> Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
> Report Id: 9b63df89-caba-4a8a-8163-c078fdeb2423
> Faulting package full name:
> Faulting package-relative application ID:
>
> The failure symptom is a pop-up window "Error writing to ...." , close that
> and one skimmer server goes away, but the other shows zero decoders and has
> to be restarted too.  Both seem to die at the same time.  Both are using
> CWSL_Tee.
>
> I think I received some private email from someone (N4ZR?) saying they were
> seeing the same thing, a month or so ago.
>
> Wonder if anyone else is seeing this now.  I have no idea how to fix this.
> I tried running a Windows Update again and it found some things, but now it
> reports I am on the latest and there's nothing to upgrade.  SFC also found
> no errors.   I can't find any pattern to the failures, they just happen
> every few hours.
>
> In the Windows logs, before every failure, I see a many informational
> messages that all look like this:
>
> svchost (6780,G,98) The beta feature EseDiskFlushConsistency is enabled in
> ESENT due to the beta site mode settings 0x800000.
>
> But I don't know if that would have anything to do with this.  My C: drive
> is an SSD.
>
> The Red Pitayas are fine, they're not crashing.  I just have to keep
> restarting the Windows apps.  Of course I already tried rebooting
> everything but it didn't seem to help.
>
> 73,
> Bob, N6TV
> _______________________________________________
> Skimmertalk mailing list
> Skimmertalk at contesting.com
> http://lists.contesting.com/mailman/listinfo/skimmertalk
>