Hi Everyone !
We are developing a 100% managed .NET Application/C# that consists of several Windows-Services and Client-Applications. Until April 2010 the Target was .Net 3.5 SP1. Meanwhile we converted all Projects to target .NET 4.0. And now we are expierencing APP-Crashes which happens every now and then (1 or twice a Week) if we are running our Tests on Win7 or 2008 R2.
The Faults are of Sort:
Faulting application name: DoX.FX.ServerHostLoader.exe, version: 0.1.16070.73, time stamp: 0x4c403ab2
Faulting module name: clr.dll, version: 4.0.30319.1, time stamp: 0x4ba21eeb
Exception code: 0xc0000005
Fault offset: 0x00000000000026fe
Faulting process id: 0x5e8
Faulting application start time: 0x01cb404b8b0740a1
Faulting application path: C:\DoX.FX.ServerHostLoader.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Report Id: 2311172d-afbc-11df-9ded-0002b3c23d42
In some cases I get a Mini-Dump which I was able to debug to a certain point, the Methods where the crash happens are different e.g.
Process Architecture: x64
Exception Code: 0xC0000005
Exception Information: The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
Heap Information: Not Present
System Information
------------------
OS Version: 6.1.7600
CLR Version(s): 4.0.30319.1
> clr.dll!JIT_ChkCastClassSpecial() + 0x1e bytes
[Managed to Native Transition]
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool ignoreSyncCtx) + 0xa1 bytes
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) + 0x3b bytes
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() + 0x4d bytes
[Native to Managed Transition]
kernel32.dll!BaseThreadInitThunk() + 0xd bytes
ntdll.dll!RtlUserThreadStart() + 0x21 bytes
We now rolled back all our projects to .NET 3.5 Target, and the above AppCrash did not occur anymore (In a 1-Week continous Test). So we went searching for this error but suprisingly there are only few others that reported this error. Since this is an internal CLR-Error of .NET 4.0 we cannot believe that we are the only ones having this problem. But maybe the are more around also still trying to find a reason for it ? Would be glad to ge some Idea about this.
Sigi