0

I have written a couple of file processing services in .NET 6.0. These are hosted elsewhere, so I can only check in on them periodically.

However, I was surprised today to find that one of them had stopped due to a .NET error, which I have pasted below from the Windows Event Logs:

Application: FileProcessingService.exe
CoreCLR Version: 6.0.21.52210
.NET Version: 6.0.0
Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFA099ECF41 (00007FFA09820000) with exit code c0000005.

And:

Faulting application name: FileProcessingService.exe, version: 1.0.0.0, time stamp: 0x61735063
Faulting module name: coreclr.dll, version: 6.0.21.52210, time stamp: 0x61734c6b Exception code: 0xc0000005
Fault offset: 0x00000000001ccf41
Faulting process id: 0xc58
Faulting application start time: 0x01d7db3bbdd56f4f
Faulting application path: C:\FileProcessingService\FileProcessingService.exe Faulting module path: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.0\coreclr.dll Report Id: 774a8d1d-47af-11ec-80bd-000c291ea09b
Faulting package full name:
Faulting package-relative application ID:

This is the second time this has happened in around 5 weeks (the first time the error was the same but the application was targetting .NET 5.0).

What can I do about this? It seems completely random and no exceptions were thrown that I caught. It's not a good system if I have to keep checking more often in case it has happened again, there must be a reason behind it.

Any advice would be much appreciated.

Greg
  • 1,643
  • 3
  • 19
  • 27
  • From reading around, it might be connected to something trying to access a memory address without permission. I do have a third-party library so I guess this is possible, though it is strange how rare it is. Regardless of the cause, how can I catch it so my application does not crash? – Greg Nov 17 '21 at 21:15

0 Answers0