Note that there are some explanatory texts on larger screens.

plurals
  1. POFaulting module name: clr.dll, version: 4.0.30319.544
    text
    copied!<p>I have a WPF application targeted on Win 7. While working on the app I suddenly got the Application closing error. </p> <p>When i checked the event logs i got the following error: </p> <p>Machine Details: </p> <p>4 GB Ram, Win 7 Professional and 64 Bit machine.</p> <pre><code>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: HOME Description: Faulting application name: Client.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)\MyClient\Client.exe Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Report Id: b4329b51-a0f3-11e2-86c9-082e5f2a7903 Event Xml: &lt;Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"&gt; &lt;System&gt; &lt;Provider Name="Application Error" /&gt; &lt;EventID Qualifiers="0"&gt;1000&lt;/EventID&gt; &lt;Level&gt;2&lt;/Level&gt; &lt;Task&gt;100&lt;/Task&gt; &lt;Keywords&gt;0x80000000000000&lt;/Keywords&gt; &lt;TimeCreated SystemTime="2013-04-09T08:58:54.000000000Z" /&gt; &lt;EventRecordID&gt;7917&lt;/EventRecordID&gt; &lt;Channel&gt;Application&lt;/Channel&gt; &lt;Computer&gt;HOME&lt;/Computer&gt; &lt;Security /&gt; &lt;/System&gt; &lt;EventData&gt; &lt;Data&gt;Client.exe&lt;/Data&gt; &lt;Data&gt;1.0.0.14&lt;/Data&gt; &lt;Data&gt;516328ad&lt;/Data&gt; &lt;Data&gt;clr.dll&lt;/Data&gt; &lt;Data&gt;4.0.30319.544&lt;/Data&gt; &lt;Data&gt;4ee9a8e7&lt;/Data&gt; &lt;Data&gt;c0000005&lt;/Data&gt; &lt;Data&gt;0010943a&lt;/Data&gt; &lt;Data&gt;c14&lt;/Data&gt; &lt;Data&gt;01ce34fde4195884&lt;/Data&gt; &lt;Data&gt;C:\Program Files (x86)\MyClient\client.exe&lt;/Data&gt; &lt;Data&gt;C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll&lt;/Data&gt; &lt;Data&gt;b4329b51-a0f3-11e2-86c9-082e5f2a7903&lt;/Data&gt; &lt;/EventData&gt; &lt;/Event&gt; </code></pre> <p>Plus i got another related error</p> <pre><code>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: HOME Description: Application: Client.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: &lt;Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"&gt; &lt;System&gt; &lt;Provider Name=".NET Runtime" /&gt; &lt;EventID Qualifiers="0"&gt;1023&lt;/EventID&gt; &lt;Level&gt;2&lt;/Level&gt; &lt;Task&gt;0&lt;/Task&gt; &lt;Keywords&gt;0x80000000000000&lt;/Keywords&gt; &lt;TimeCreated SystemTime="2013-04-09T08:58:52.000000000Z" /&gt; &lt;EventRecordID&gt;7916&lt;/EventRecordID&gt; &lt;Channel&gt;Application&lt;/Channel&gt; &lt;Computer&gt;HOME&lt;/Computer&gt; &lt;Security /&gt; &lt;/System&gt; &lt;EventData&gt; &lt;Data&gt;Application: Client.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. &lt;/Data&gt; &lt;/EventData&gt; &lt;/Event&gt; </code></pre> <p>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 </p> <p><a href="http://support.microsoft.com/kb/2640103" rel="nofollow">http://support.microsoft.com/kb/2640103</a> article. </p> <p>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. </p> <p>Is there any solution for the above crash, is it an issue with the framework or the exe ? </p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload