The error is a general purpose execution error by the runtime. That means the runtime had a fatal error so it immediately crashes your app. This is exceedingly rare but can happen for a variety of reasons. We actually saw this error a few weeks back after an app deployment. The fact that there is no useful logged information makes it very difficult to diagnose.
I would start with what might have changed on the server of recent. Did you apply updates or redeploy your app? Barring hardware failures it seems unlikely that your app would suddenly start failing if nothing changed.
Can you determine what the app is doing at the time? For example if the app is under load when it fails then that might point to one set of problems. However if the app is idle at the time then that might indicate something completely different.
Are you using any native components like COM or native binaries in your web app? These can cause the error if they corrupt memory.
Yet another cause that some people have reported is with the concurrent garbage collector. If the GC "messes up" then it can corrupt memory which will cause the crash. This is more likely for older NET Framework installations. What version of NET Framework is installed on the server (e.g. 4.7.2, 4.8, etc)? If you have a really old framework version then updating the framework version may be sufficient. Otherwise you may consider disabling the concurrent GC to see if the problem goes away. Note that this could negatively impact performance so you'd want to test it and turn it back on if it isn't the issue.
If you can reliably crash your app then grab the minidump file that Windows should generate when the process crashes (C:\Windows\minidump
) and load it up in the debugger to see what is going on. If you cannot reliably crash the app then you might need to wait until it replicates and then find the crash dump that is generated for it.