locked
Faulting module name: clr.dll RRS feed

  • Question

  • I have a WPF application targeted on Win 7. While working on the app I suddenly got the Application closing error.

    When i checked the event logs i got the following error:

    Machine Details:

    4 GB Ram, Win 7 Professional and 64 Bit machine.

    Log Name:      Application
    Source:        Application Error
    Date:          4/9/2013 2:28:54 PM
    Event ID:      1000
    Task Category: Application Crashing Events
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      CHNVSBTTC135PC
    Description:
    Faulting application name: ConnectClient.exe, version: 1.1.0.14, time stamp: 0x516328ad
    Faulting module name: clr.dll, version: 4.0.30319.544, time stamp: 0x4ee9a8e7
    Exception code: 0xc0000005
    Fault offset: 0x0010943a
    Faulting process id: 0xc14
    Faulting application start time: 0x01ce34fde4195884
    Faulting application path: C:\Program Files (x86)\ConnectClient.exe
    Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
    Report Id: b4329b51-a0f3-11e2-86c9-082e5f2a7903
    Event Xml:
    <Event xmlns=

      <System>
        <Provider Name="Application Error" />
        <EventID Qualifiers="0">1000</EventID>
        <Level>2</Level>
        <Task>100</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-04-09T08:58:54.000000000Z" />
        <EventRecordID>7917</EventRecordID>
        <Channel>Application</Channel>
        <Computer>XYZ</Computer>
        <Security />
      </System>
      <EventData>
        <Data>ConnectClient.exe</Data>
        <Data>1.1.0.14</Data>
        <Data>516328ad</Data>
        <Data>clr.dll</Data>
        <Data>4.0.30319.544</Data>
        <Data>4ee9a8e7</Data>
        <Data>c0000005</Data>
        <Data>0010943a</Data>
        <Data>c14</Data>
        <Data>01ce34fde4195884</Data>
        <Data>C:\Program Files (x86)\ConnectClient.exe</Data>
        <Data>C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll</Data>
        <Data>b4329b51-a0f3-11e2-86c9-082e5f2a7903</Data>
      </EventData>
    </Event>

    Plus i got another related error

    Log Name:      Application
    Source:        .NET Runtime
    Date:          4/9/2013 2:28:52 PM
    Event ID:      1023
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      XYZ
    Description:
    Application: ConnectClient.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 743C943A (742C0000) with exit code 80131506.

    Event Xml:
    <Event xmlns

      <System>
        <Provider Name=".NET Runtime" />
        <EventID Qualifiers="0">1023</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2013-04-09T08:58:52.000000000Z" />
        <EventRecordID>7916</EventRecordID>
        <Channel>Application</Channel>
        <Computer>XYZ</Computer>
        <Security />
      </System>
      <EventData>
        <Data>Application: ConnectClient.exe
    Framework Version: v4.0.30319
    Description: The process was terminated due to an internal error in the .NET Runtime at IP 743C943A (742C0000) with exit code 80131506.
    </Data>
      </EventData>
    </Event>

    I had got the same error(s) with clr.dll v  4.0.30319.269, i searched the community and installed the fix given in

    KB Article : 2640103 article.

    After the installtion of the fix the old clr.dll(4.0.30319.269) was replaced with new version 4.0.30319.544, but today i still got this error.

    Is there any solution for the above crash, is it an issue with the framework or the exe ? 


    • Edited by ManeeshSiva Thursday, April 11, 2013 8:26 AM
    Wednesday, April 10, 2013 4:18 AM

All replies

  • Hi ManeeshSiva,

    Please check these links:

    Random AppCrashes in clr.dll with .NET 4.0

    "Faulting module name: clr.dll" error message when you run a Microsoft .NET Framework 4-based application

    Good day.


    Yoyo Jiang[MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, April 11, 2013 6:53 AM
  • Hi Yoyo,

    Thank you for responding. I checked the second link and as said in my initial thread I had already installed the fix given in the

    KB Article : 2640103 article.

    , but the issue occured again yesterday too i received the same error on the same machine ( win 64 bit machine ).

    Is this a issue in the .NET framework or is it some issue in my application.
    Also I noticed that i had disabled concurrent garbage collection. ( this was one of the possible solution to fix this in one of the forums) but i felt that due to this setting i started getting this runtime error frequently.

    I have reset the concurrent garbage collection to true now and will run and test my application today. and hopefully i do not see this issue coming.

    Couple of questions:

    1) Is this a .NET runtime framework issue or is that our applicaiton is doing something that results in this error.

    2) was the disabling of concurrent garbage collection an issue that resulted this runtime error?

    Expecting your views on this...


    • Edited by ManeeshSiva Thursday, April 11, 2013 8:39 AM
    Thursday, April 11, 2013 8:35 AM
  • Hi ManeeshSiva,

    Sorry about the late response.

    According to the second link, "this fix related ONLY to .NET Framework 4.0 Client Profile".  So would you please check if you are using .NET framwork 4.0 or .NET Framework 4.0 Client?

    Thanks.


    Yoyo Jiang[MSFT]
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Tuesday, April 23, 2013 9:05 AM