Why does the .net application crash?

Question

.NET

Good afternoon.
There is a service that is written in .net. This service crashes periodically in a production environment. In system logs only this. Deployed the service on a new server - the same problem. How can you find out more precisely about the cause of the fall?
A couple of clarifications:

• Falls unpredictably. Can work for days. Maybe 5 minutes.
  
• There is no access to the source.
  

Application: App.Services.Host.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
Stack:
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.b__5(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at
System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
Dispatch()
Faulting application name: App.Services.Host.exe, version: 1.0.38.2, timestamp: 0x56982b83 Faulting
module name: KERNELBASE.dll, version: 6.1.7601.19110, timestamp 0x568429dd Exception code
: 0xe0434352 Error
offset: 0x000000000000b16d
: 0xed4 Faulting
application start time: 0x01d150442a1bacce Faulting application
path: c:\v2_deploy\Backend\App.Services.Host.exe Faulting
module path: C:\Windows\system32\KERNELBASE.dll
Report ID: 1423058b-bc60-11e5-9fbb -0025901e02d9

Answer 1

In general, he asked - he answered. There is a wonderful profiler
https://www.microsoft.com/en-us/download/confirma...

Answer 2

Make the sources yourself, doPeek , create a project from the assembly and debug.
There are many profilers, it is difficult to look for the cause of the fall in it, if possible.
The error is either in the thread pool, the wrong argument was passed - this is " InvalidOperationException ", or in the fact that this should not have happened at all, then the error can be anywhere, far from the Stack trace.
Google - debugging .NET Windows service.
Good luck.

Answer 3

On a test wheelbarrow, try to reproduce, having previously connected to the process from Visual Studio