none
Sporadic Crash - ".NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error ... (80131506)" RRS feed

  • Question

  • While running .NET application, sporadically application crashes with the error logged in Event Viewer (Application): ".NET Runtime version 2.0.50727.3053 - Fatal Execution Engine Error (000006427F44AA6E) (80131506)"

    System settings:  OS: Windows XP, SP2, 64Bit.   .NET Framework: 3.5 SP1

    May I know root cause of this error? Is there is any released patch/service pack from Microsoft which I can deliver along with my application?

    Note that this application should support both 32Bit and 64Bit editions of WindowsXP and Windows7. So I am interested to know patch (if available) for each OS versions.

    Thanks in advance for your support. -Shanavas.

    Wednesday, September 26, 2012 1:00 PM

All replies

  • Hi Shanavas,

    Welcome to the MSDN Forum.

    What is your application platform? x64?x86?anycpu?

    Do you have install the x64 version .net framework? What operation does cause this error?

    Best regards,


    Mike Feng
    MSDN Community Support | Feedback to us
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, September 27, 2012 11:26 AM
    Moderator
  • Hi Mike,

    I am installing 32-bit version of my application on x64-WindowsXP(SP2) machine.

    I am installing "dotnetfx35.exe" which as far as I know it internally detects 32/64 bit and installs accordingly.

    - Shanavas.


    -Shanavas.

    Thursday, September 27, 2012 2:13 PM
  • Hi Shanavas,

    Did you download it here? http://www.microsoft.com/en-us/download/details.aspx?id=21 

    If not, please try to download it and install it again.

    Best regards,


    Mike Feng
    MSDN Community Support | Feedback to us
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Friday, September 28, 2012 11:12 AM
    Moderator
  • Hi Mike,

    I un-installed pre-existing versions of .NET frameworks - 3.5 SP1, 3.0 SP2 and 2.0 SP2 through Add/Remove programs window. Then installed "Full Redistributable Package" available at bottom of the link you mentionedtting a strange error while trying to open a communication channel as below:

    ===============================

    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Runtime.Serialization.InvalidDataContractException: Type '<Type>' cannot be serialized. Consider marking it with the DataContractAttribute attribute, and marking all of its members you want serialized with the DataMemberAttribute attribute.
       at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.ThrowInvalidDataContractException(String message, Type type)
       at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.CreateDataContract(Int32 id, RuntimeTypeHandle typeHandle, Type type)
       at System.Runtime.Serialization.DataContract.DataContractCriticalHelper.GetDataContractSkipValidation(Int32 id, RuntimeTypeHandle typeHandle, Type type)
       at System.Runtime.Serialization.DataContract.GetDataContractSkipValidation(Int32 id, RuntimeTypeHandle typeHandle, Type type)
       at System.Runtime.Serialization.DataContract.GetDataContract(RuntimeTypeHandle typeHandle, Type type, SerializationMode mode)
       at System.Runtime.Serialization.DataContract.GetDataContract(RuntimeTypeHandle typeHandle, Type type)
       at System.Runtime.Serialization.DataContract.GetDataContract(Type type)
       at System.Runtime.Serialization.XsdDataContractExporter.GetSchemaTypeName(Type type)
       at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.ValidateDataContractType(Type type)
       at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.CreatePartInfo(MessagePartDescription part, OperationFormatStyle style, DataContractSerializerOperationBehavior serializerFactory)
       at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter.CreateMessageInfo(DataContractFormatAttribute dataContractFormatAttribute, MessageDescription messageDescription, DataContractSerializerOperationBehavior serializerFactory)
       at System.ServiceModel.Dispatcher.DataContractSerializerOperationFormatter..ctor(OperationDescription description, DataContractFormatAttribute dataContractFormatAttribute, DataContractSerializerOperationBehavior serializerFactory)
       at System.ServiceModel.Description.DataContractSerializerOperationBehavior.GetFormatter(OperationDescription operation, Boolean& formatRequest, Boolean& formatReply, Boolean isProxy)
       at System.ServiceModel.Description.DataContractSerializerOperationBehavior.System.ServiceModel.Description.IOperationBehavior.ApplyDispatchBehavior(OperationDescription description, DispatchOperation dispatch)
       at System.ServiceModel.Description.DispatcherBuilder.BindOperations(ContractDescription contract, ClientRuntime proxy, DispatchRuntime dispatch)
       at System.ServiceModel.Description.DispatcherBuilder.InitializeServiceHost(ServiceDescription description, ServiceHostBase serviceHost)
       at System.ServiceModel.ServiceHostBase.InitializeRuntime()
       at System.ServiceModel.ServiceHostBase.OnOpen(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
       at System.ServiceModel.Channels.CommunicationObject.Open()

       ...

    ===============================

    This portion of code was working fine with previous .NET framework installation. Do you see any potential cause?


    -Shanavas.

    Saturday, September 29, 2012 7:53 PM
  • Hi Shanavas,

    >>Then installed "Full Redistributable Package" available at bottomof the link you mentionedtting a strange error while trying to open a communication channel

    This is at your compile-time? Or just run your application after install the framework?

    Best regards,


    Mike Feng
    MSDN Community Support | Feedback to us
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, October 1, 2012 5:33 AM
    Moderator
  • Hi Mike,

    The error is while running my application after installing the framework.

    -Shanavas.


    -Shanavas.

    Tuesday, October 2, 2012 6:53 AM
  • Hi Shanvas,

    Based on this blog: http://blogs.msdn.com/b/youssefm/archive/2009/08/10/serializing-plain-old-clr-objects-poco-types-with-datacontractserializer.aspx 

    This issue is resolved in .Net Framework 3.5. So would you like to recompile your application on 3.5?

    Best regards,


    Mike Feng
    MSDN Community Support | Feedback to us
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Wednesday, October 3, 2012 5:06 AM
    Moderator
  • Hi Mike,

    Since my application integrates modules from other team working in different location, having different release schedules, it looks like difficult to get their module converted to .NET 3.5.

    Meanwhile with the version of .NET 3.5 full setup I was using before, I attached AdPlus debugger with the proces and got crash dump for the issue. While analyzing the dump with WinDbg, I could see below stack trace for !dumpstack command. Does this give any more information on this issue?

    Please let me know if you need any more information.

    - Shanavas.

    ===============================

    0:036> !dumpstack
    OS Thread Id: 0x151c (36)
    Child-SP         RetAddr          Call Site
    000000004baac828 000006427f8232ba ntdll!DbgBreakPoint
    000000004baac830 000006427fa02f2e mscorwks!CertCreateAuthenticodeLicense+0x21cd1a
    000000004baacfb0 000006427f44aa81 mscorwks!PreBindAssembly+0x99a6e
    000000004baad000 000006427f482c30 mscorwks!GetCLRFunction+0x1126d
    000000004baad040 000006427f482e37 mscorwks!CreateApplicationContext+0x2ecd4
    000000004baad0b0 000006427f44a6e6 mscorwks!CreateApplicationContext+0x2eedb
    000000004baad130 0000000077f2583c mscorwks!GetCLRFunction+0x10ed2
    000000004baad170 0000000077ee58a6 ntdll!RtlQueryProcessLockInformation+0xe0c
    000000004baad200 0000000077ef2c2d ntdll!RtlLookupFunctionEntry+0x4a6
    000000004baad8b0 000006427f50ccf3 ntdll!KiUserExceptionDispatcher+0x2d
    000000004baade48 000006427f447f31 mscorwks!CreateAssemblyNameObject+0x7bc33
    000000004baade50 000006427f45c44c mscorwks!GetCLRFunction+0xe71d
    000000004baade80 000006427f577f7b mscorwks!CreateApplicationContext+0x84f0
    000000004baadec0 000006427f56219d mscorwks!GetMetaDataInternalInterface+0x2943b
    000000004baadf40 000006427f9b87d3 mscorwks!GetMetaDataInternalInterface+0x1365d
    000000004baadfd0 000006427f5ff872 mscorwks!PreBindAssembly+0x4f313
    000000004baae1a0 0000064280494c36 mscorwks!IEE+0x825e
    000000004baae1d0 0000064280495d53 UCF_Common_Diagnostics_Tracing_Impl!UCF.Common.Diagnostics.Tracing.Impl.FTraceImpl.ToString()+0x346
    000000004baae220 0000064280ba4b1a UCF_Common_Diagnostics_Tracing_Impl!UCF.Common.Diagnostics.Tracing.Impl.Trace.Write(System.Type, Int32, UCF.Common.Diagnostics.Tracing.Severity, System.Object)+0x133
    000000004baae2a0 0000064280ba4acd UCF_Common_Diagnostics_Tracing_Impl!UCF.Common.Diagnostics.Tracing.Impl.Trace.Info(System.Type, System.Object)+0x1a
    000000004baae2e0 0000064280bc1ca8 UCF_Common_Diagnostics_Tracing!UCF.Common.Diagnostics.Trace.Info(System.Type, System.Object)+0x2d
    000000004baae320 00000000206c58a0 Siemens_Ultrasound_Bedrock_Services_Renderer_BedrockSceneProvider_Core!Siemens.Ultrasound.Bedrock.Services.Renderer.BedrockSceneProvider.Core.BedrockScene.renderSceneCBFunc(Void*, SoSceneManager*)+0x28
    000000004baae350 00000000205ef6fe Inv701!SoSceneManager::redraw+0x20
    000000004baae380 00000000205f0671 Inv701!SoDataSensor::trigger+0xe
    000000004baae3b0 00000000205f0799 Inv701!SoSensorManager::doSelect+0x171
    000000004baae3f0 000006427f6020b2 Inv701!SoSensorManager::doSelect+0x299
    000000004baae420 0000064280bc19c7 mscorwks!IEE+0xaa9e
    000000004baae4b0 0000064280ba08ad Siemens_Ultrasound_Bedrock_Services_Renderer_BedrockSceneProvider_Core!Siemens.Ultrasound.Bedrock.Services.Renderer.BedrockSceneProvider.Core.BedrockScene.ScheduleProcessQueues(Boolean)+0xd7
    000000004baae5e0 000006427830c878 siemens_ultrasound_bedrock_services_renderer_ultrasoundscenegraphsc_core!Siemens.Ultrasound.Bedrock.Services.Renderer.UltrasoundSceneGraphSC.Core.UltrasoundSceneGraphSC.ChildThreadStartFunction()+0x132d
    000000004baae860 000006427f602672 mscorlib_ni!System.Threading.ExecutionContext.runTryCode(System.Object)+0x178
    000000004baae920 000006427f50c053 mscorwks!IEE+0xb05e
    000000004baae970 000006427f4fd09f mscorwks!CreateAssemblyNameObject+0x7af93
    000000004baaea10 000006427f49bae2 mscorwks!CreateAssemblyNameObject+0x6bfdf
    000000004baaec70 000006427fa5eed2 mscorwks!CreateAssemblyNameObject+0xaa22
    000000004baaef00 00000642782f1702 mscorwks!CorLaunchApplication+0x25a42
    000000004baaf110 000006427838959d mscorlib_ni!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)+0x62
    000000004baaf160 000006427f602672 mscorlib_ni!System.Threading.ThreadHelper.ThreadStart()+0x4d
    000000004baaf1b0 000006427f50c053 mscorwks!IEE+0xb05e
    000000004baaf200 000006427f4fd09f mscorwks!CreateAssemblyNameObject+0x7af93
    000000004baaf2a0 000006427f406245 mscorwks!CreateAssemblyNameObject+0x6bfdf
    000000004baaf4f0 000006427f447ee8 mscorwks+0xd6245
    000000004baaf810 000006427f556aa9 mscorwks!GetCLRFunction+0xe6d4
    000000004baaf860 000006427f43afdd mscorwks!GetMetaDataInternalInterface+0x7f69
    000000004baaf930 000006427f581acd mscorwks!GetCLRFunction+0x17c9
    000000004baaf970 000006427f581ba7 mscorwks!GetMetaDataInternalInterface+0x32f8d
    000000004baaf9d0 000006427f41f9a0 mscorwks!GetMetaDataInternalInterface+0x33067
    000000004baafab0 0000000077d6b71a mscorwks+0xef9a0
    000000004baaff80 0000000000000000 kernel32!BaseThreadStart+0x3a

    ===============================


    -Shanavas.

    Friday, October 5, 2012 5:16 PM
  • Hi Mike,

    I got one more occurence of this issue with AdPlus debugger tool attached.

    Below is the result of "!dumpstack" command.

    Note that first 11 lines in stack trace of this occurrence is same as that mentioned in my previous reply.

    I hope this will help us.

    Thanks in advance for your support.

    -Shanavas.

    ====================================

    0:036> !dumpstack
    OS Thread Id: 0x1a0c (36)
    Child-SP         RetAddr          Call Site
    000000004baacb78 000006427f8232ba ntdll!DbgBreakPoint
    000000004baacb80 000006427fa02f2e mscorwks!CertCreateAuthenticodeLicense+0x21cd1a
    000000004baad300 000006427f44aa81 mscorwks!PreBindAssembly+0x99a6e
    000000004baad350 000006427f482c30 mscorwks!GetCLRFunction+0x1126d
    000000004baad390 000006427f482e37 mscorwks!CreateApplicationContext+0x2ecd4
    000000004baad400 000006427f44a6e6 mscorwks!CreateApplicationContext+0x2eedb
    000000004baad480 0000000077f2583c mscorwks!GetCLRFunction+0x10ed2
    000000004baad4c0 0000000077ee58a6 ntdll!RtlQueryProcessLockInformation+0xe0c
    000000004baad550 0000000077ef2c2d ntdll!RtlLookupFunctionEntry+0x4a6
    000000004baadc00 000006427f4f633d ntdll!KiUserExceptionDispatcher+0x2d
    000000004baae1a0 000006427f5ff81f mscorwks!CreateAssemblyNameObject+0x6527d
    000000004baae1d0 0000064280494c36 mscorwks!IEE+0x820b
    000000004baae200 0000064280495d53 0000064280494c36
    000000004baae250 0000064280ba4b1a 0000064280495d53
    000000004baae2d0 0000064280ba4acd 0000064280ba4b1a
    000000004baae310 0000064280bc1ca8 0000064280ba4acd
    000000004baae350 00000000206758a0 0000064280bc1ca8
    000000004baae380 000000002059f6fe Inv701!SoSceneManager::redraw+0x20
    000000004baae3b0 00000000205a0671 Inv701!SoDataSensor::trigger+0xe
    000000004baae3e0 000006427f6020b2 Inv701!SoSensorManager::doSelect+0x171
    000000004baae420 0000064280bc19e7 mscorwks!IEE+0xaa9e
    000000004baae4b0 0000064280ba08ad Siemens_Ultrasound_Bedrock_Services_Renderer_BedrockSceneProvider_Core!Siemens.Ultrasound.Bedrock.Services.Renderer.BedrockSceneProvider.Core.BedrockScene.ScheduleProcessQueues(Boolean)+0xf7
    000000004baae5e0 000006427830c878 siemens_ultrasound_bedrock_services_renderer_ultrasoundscenegraphsc_core!Siemens.Ultrasound.Bedrock.Services.Renderer.UltrasoundSceneGraphSC.Core.UltrasoundSceneGraphSC.ChildThreadStartFunction()+0x132d
    000000004baae860 000006427f602672 mscorlib_ni!System.Threading.ExecutionContext.runTryCode(System.Object)+0x178

    ====================================


    -Shanavas.

    Sunday, October 7, 2012 7:37 AM
  • The nature of these issues with FEEE is such that, from a support perspective this is really beyond what we can do here in the forums. If you cannot determine your answer here or on your own, consider opening a support case with us. Visit this link to see the various support options that are available to better meet your needs:  http://support.microsoft.com/default.aspx?id=fh;en-us;offerprophone.

    Trevor Hancock (Microsoft)
    Please remember to "Mark As Answer" the replies that help.

    Monday, October 8, 2012 3:59 PM
    Moderator