none
Error .NET Runtime version 2.0.50727.1433 in mscorwks.dll RRS feed

  • Question

  • Hi,

    I got this Error messge

    Event Type:    Error
    Event Source:    .NET Runtime
    Event Category:    None
    Event ID:    1023
    Date:        12/19/2008
    Time:        7:00:20 PM
    User:        N/A
    Computer:    FISSECSRV
    Description:
    .NET Runtime version 2.0.50727.1433 - Fatal Execution Engine Error (79FFEE24) (80131506)

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

    And then this
    Event Type:    Error
    Event Source:    .NET Runtime 2.0 Error Reporting
    Event Category:    None
    Event ID:    1000
    Date:        12/19/2008
    Time:        7:00:32 PM
    User:        N/A
    Computer:    FISSECSRV
    Description:
    Faulting application srvbruteforce.exe, version 1.0.0.0, stamp 48221bff, faulting module mscorwks.dll, version 2.0.50727.1433, stamp 471ef729, debug? 0, fault address 0x0014a841.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 00 70 00 70 00 6c 00   A.p.p.l.
    0008: 69 00 63 00 61 00 74 00   i.c.a.t.
    0010: 69 00 6f 00 6e 00 20 00   i.o.n. .
    0018: 46 00 61 00 69 00 6c 00   F.a.i.l.
    0020: 75 00 72 00 65 00 20 00   u.r.e. .
    0028: 20 00 73 00 72 00 76 00    .s.r.v.
    0030: 62 00 72 00 75 00 74 00   b.r.u.t.
    0038: 65 00 66 00 6f 00 72 00   e.f.o.r.
    0040: 63 00 65 00 2e 00 65 00   c.e...e.
    0048: 78 00 65 00 20 00 31 00   x.e. .1.
    0050: 2e 00 30 00 2e 00 30 00   ..0...0.
    0058: 2e 00 30 00 20 00 34 00   ..0. .4.
    0060: 38 00 32 00 32 00 31 00   8.2.2.1.
    0068: 62 00 66 00 66 00 20 00   b.f.f. .
    0070: 69 00 6e 00 20 00 6d 00   i.n. .m.
    0078: 73 00 63 00 6f 00 72 00   s.c.o.r.
    0080: 77 00 6b 00 73 00 2e 00   w.k.s...
    0088: 64 00 6c 00 6c 00 20 00   d.l.l. .
    0090: 32 00 2e 00 30 00 2e 00   2...0...
    0098: 35 00 30 00 37 00 32 00   5.0.7.2.
    00a0: 37 00 2e 00 31 00 34 00   7...1.4.
    00a8: 33 00 33 00 20 00 34 00   3.3. .4.
    00b0: 37 00 31 00 65 00 66 00   7.1.e.f.
    00b8: 37 00 32 00 39 00 20 00   7.2.9. .
    00c0: 66 00 44 00 65 00 62 00   f.D.e.b.
    00c8: 75 00 67 00 20 00 30 00   u.g. .0.
    00d0: 20 00 61 00 74 00 20 00    .a.t. .
    00d8: 6f 00 66 00 66 00 73 00   o.f.f.s.
    00e0: 65 00 74 00 20 00 30 00   e.t. .0.
    00e8: 30 00 31 00 34 00 61 00   0.1.4.a.
    00f0: 38 00 34 00 31 00 0d 00   8.4.1...
    00f8: 0a 00                     ..     

    Can someone please help?

    Thank you very much
    Long
    Tuesday, December 23, 2008 10:42 PM

Answers

  • Hello,
    This error (Fatal Execution Engine Error (79FFEE24) (80131506)) indicates that CLR found corrupted internal data structures. At that point it couldn't tell who corrupted the data. It might be caused by corrupted memory (e.g. invalid PInvoke or COM interop in your application or hardware error), or it can indicate a bug in CLR.
    If it fails on more than one machine (i.e. it's likely not a hardware error), I would recommend to look into used libraries and native/COM interop features (using tools like Heap Verifier might help here).
    If you are sure that it is not a problem with your application or used library, then try to isolate the problem and minimize the repro as much as possible, then file a bug via Microsoft Connect.

    A quick search through the internet shows that people hit this type of error (Fatal Execution Engine Error (79FFEE24) (80131506)) in various situations. Some of them were caused by invalid COM interop. Most of them are never solved (because it's pretty hard to find invalid COM interop). Some of them are solved by reinstalling .NET Framework or by upgrading to latest SP (IMO this usually just hides the interop error, but if it helps, why not to use it ...).
    Here's a thread about similar error caused by third party driver as an example what could corrupt the memory.

    I hope it helps,
    -Karel
    • Marked as answer by Zhi-Xin Ye Tuesday, December 30, 2008 7:10 AM
    Monday, December 29, 2008 5:24 PM
    Moderator

All replies

  • Hello,
    This error (Fatal Execution Engine Error (79FFEE24) (80131506)) indicates that CLR found corrupted internal data structures. At that point it couldn't tell who corrupted the data. It might be caused by corrupted memory (e.g. invalid PInvoke or COM interop in your application or hardware error), or it can indicate a bug in CLR.
    If it fails on more than one machine (i.e. it's likely not a hardware error), I would recommend to look into used libraries and native/COM interop features (using tools like Heap Verifier might help here).
    If you are sure that it is not a problem with your application or used library, then try to isolate the problem and minimize the repro as much as possible, then file a bug via Microsoft Connect.

    A quick search through the internet shows that people hit this type of error (Fatal Execution Engine Error (79FFEE24) (80131506)) in various situations. Some of them were caused by invalid COM interop. Most of them are never solved (because it's pretty hard to find invalid COM interop). Some of them are solved by reinstalling .NET Framework or by upgrading to latest SP (IMO this usually just hides the interop error, but if it helps, why not to use it ...).
    Here's a thread about similar error caused by third party driver as an example what could corrupt the memory.

    I hope it helps,
    -Karel
    • Marked as answer by Zhi-Xin Ye Tuesday, December 30, 2008 7:10 AM
    Monday, December 29, 2008 5:24 PM
    Moderator
  • I am also getting the same error

    Faulting application test.exe, version 1.0.0.0, stamp 498358a6, faulting module mscorwks.dll, version 2.0.50727.1433, stamp 471ef729, debug? 0, fault address 0x000f675b.


    It is happening randomly. Generally my win32 application works fine and some time it suddenly stops.

    Any help would be appreciated!

    Thursday, February 5, 2009 4:49 PM
  • Hello,

    If you can provide a reasonably small repro (sources would be helpful), I would be interested in exploring new techniques in tracking down this type of issue.

    Thanks,
    -Karel Zikmund
    Wednesday, February 11, 2009 7:11 PM
    Moderator
  • I am also getting the same error. But It occurs only in one application. All other .Net applications run fine on the same server.
    Any idea what could be the reason. It looks more like a library error.
    Prince
    Monday, March 2, 2009 3:54 PM
  • Please check out my first answer (2nd post in this thread). It summarizes the troubleshooting techniques I know about. Start with asking yourself these questions:
    • Does your application fail on more than one machine?
    • Does your application use native/COM interop?
    • Does your application use other libraries (other than .NET Framework itself)?

    -Karel

    Monday, March 2, 2009 11:11 PM
    Moderator
  • .NET Runtime version 2.0.50727.3643 - Fatal Execution Engine Error (000006427F55508A) (80131506)
    Friday, January 4, 2013 8:15 AM
  • .Net Runtime version 2.0.50727.5420 - same error.

    I have the error on Windows 2008 R2 SE and EE (Russian and English version) x64.

    I use .net application (x86) with data storing and retriving from Oracle database (Oracle 11g R2 x64).

    It seems error in code with unsafe code block (I use structure of binary data for storing into the database and for retrive data from database):

    T ret = new T();
                GCHandle gch = GCHandle.Alloc(arr, GCHandleType.Pinned); // зафиксировать в памяти
                int str_size = Marshal.SizeOf(typeof(T));
                IntPtr ptr = Marshal.AllocHGlobal(str_size);//Marshal.UnsafeAddrOfPinnedArrayElement(arr, 0); // и взять его адрес
                Marshal.Copy(arr, 0, ptr, str_size);
                ret = (T)Marshal.PtrToStructure(ptr, typeof(T)); // создать структуру из данных с адреса ptr
                Marshal.FreeHGlobal(ptr); // снять фиксацию
                return ret;


    int str_size = Marshal.SizeOf(value);
                byte[] arr = new byte[str_size];
                IntPtr ptr_str = Marshal.AllocHGlobal(str_size);
    
                Marshal.StructureToPtr(value, ptr_str, true);
                Marshal.Copy(ptr_str, arr, 0, str_size);
                Marshal.FreeHGlobal(ptr_str);
    
                return arr;

    Before using this code there was not this error.

    I have AppCrash files for a lot of cases:

    Report.wer (first part):

    Version=1
    EventType=APPCRASH
    EventTime=130002929223495244
    ReportType=2
    Consent=1
    ReportIdentifier=edca97cc-48ec-11e2-ad73-e4115bed9622
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=gdasuc_service.exe
    Sig[1].Name=Application Version
    Sig[1].Value=1.11.305.0
    Sig[2].Name=Application Timestamp
    Sig[2].Value=50cd5bd3
    Sig[3].Name=Fault Module Name
    Sig[3].Value=mscorwks.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=2.0.50727.5420
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=4ca2b7e1
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000005
    Sig[7].Name=Exception Offset
    Sig[7].Value=00000000002be4dc
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=6.1.7601.2.1.0.272.7
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1049

    WERB54B.tmp.WERInternalMetadata.xml:

    <?xml version="1.0" encoding="UTF-16"?>
    <WERReportMetadata>
    	<OSVersionInformation>
    		<WindowsNTVersion>6.1</WindowsNTVersion>
    		<Build>7601 Service Pack 1</Build>
    		<Product>(0x7): Windows Server 2008 R2 Standard</Product>
    		<Edition>ServerStandard</Edition>
    		<BuildString>7601.17514.amd64fre.win7sp1_rtm.101119-1850</BuildString>
    		<Revision>1130</Revision>
    		<Flavor>Multiprocessor Free</Flavor>
    		<Architecture>X64</Architecture>
    		<LCID>1033</LCID>
    	</OSVersionInformation>
    	<ParentProcessInformation>
    		<ParentProcessId>592</ParentProcessId>
    		<ParentProcessPath>C:\Windows\System32\services.exe</ParentProcessPath>
    		<ParentProcessCmdLine>C:\Windows\system32\services.exe</ParentProcessCmdLine>
    	</ParentProcessInformation>
    	<ProblemSignatures>
    		<EventType>APPCRASH</EventType>
    		<Parameter0>gdasuc_service.exe</Parameter0>
    		<Parameter1>1.11.305.0</Parameter1>
    		<Parameter2>50cd5bd3</Parameter2>
    		<Parameter3>mscorwks.dll</Parameter3>
    		<Parameter4>2.0.50727.5420</Parameter4>
    		<Parameter5>4ca2b7e1</Parameter5>
    		<Parameter6>c0000005</Parameter6>
    		<Parameter7>00000000002be4dc</Parameter7>
    	</ProblemSignatures>
    	<DynamicSignatures>
    		<Parameter1>6.1.7601.2.1.0.272.7</Parameter1>
    		<Parameter2>1049</Parameter2>
    	</DynamicSignatures>
    	<SystemInformation>
    		<MID>6F4591D8-5C8A-4773-BAE2-0544DFC6B4B9</MID>
    		<SystemManufacturer>HP</SystemManufacturer>
    		<SystemProductName>ProLiant DL360 G7</SystemProductName>
    		<BIOSVersion>P68</BIOSVersion>
    	</SystemInformation>
    </WERReportMetadata>


    Friday, January 11, 2013 12:13 PM