Today’s work is… previous: Everything falls down in its proper place next: My poor little blameless Voron It isn’t enough to have just an ExecutionEngineException, I had to have this: Comments 03/24/2014 12:36 PM by Bartosz Adamczewski That's a good thing. Error code, address and thread are useful hint's to start diagnosing, a full dump might have been better and perhaps the EE should try to create one upon blowing up (but that might be impossible). 03/24/2014 02:51 PM by bhargav Try to go in detail .you will find the exact cause of error. 03/24/2014 09:56 PM by Alois Kraus Can be easy if you did only corrupt the stack and this is reproducible. But if you get this AccessViolation during a GC then it can become quite hard to get down to the root cause. In any case you need to check what did trigger the Exception. It can also be invalid IL generated by a Buggy code generator. Comments have been closed on this topic.