none
Faulting module name: clr.dll RRS feed

  • Question

  • We are using .Net Framework 4.0 and while running the console app the application is throwing below the error and exiting with error code 80131506.

    "Faulting module name: clr.dll"

    After restarting the console app it is running fine. This kind of failure is occuring once in a week. Please suggest how to fix it.

    Monday, April 18, 2016 5:37 AM

Answers

  • Hi Hari,

    >>KB2640103 does not apply, or is blocked by another condition on your computer

    Do you mean you have downloaded the KB2640103 successfully? I am afraid as my first reply mentioned, KB2640103 is missing now. This bug is too long time ago. Now this issue is fixed in the next .net framework. You'll need to update your .net framework to the latest or higher. Then try to checki if this issue is missing now. Good luck!

    Best regards,

    Kristin


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, April 25, 2016 2:10 AM

All replies

  • Hi HariKrishna ,

    I wonder if you are using the old version .Net framework 4.0

    Based on your description, since the error information is not detailed, I am not sure if it is the same as the following post as discussed

    https://social.msdn.microsoft.com/Forums/vstudio/en-US/e0de4156-d028-4f01-859e-b20ba3683651/random-appcrashes-in-clrdll-with-net-40?forum=clr

    If yes, Please have a look at the support KB:https://support.microsoft.com/en-us/kb/2640103

    But this KB hotfix is missing, I am afraid you may need to update your .Net framework to the latest or check if there is any updates related to .Net framwork using windows updates.

    For more background information read the following link on MSDN Forums:
    * http://social.msdn.microsoft.com/Forums/en-US/clr/thread/2b89ca3a-6a93-4d21-a5eb-d5b5d44c6dce
    I also recommand you to take a look Jim's Blog, here are someTroubleshooting Internal Error in the .NET Runtime

    http://www.jamesewelch.com/2010/09/30/troubleshooting-internal-error-in-the-net-runtime/

    Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. 

    Microsoft does not control these sites and has not tested any software or information found on these sites;Therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.

    There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.

    Best regards,

    kristin


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, April 19, 2016 5:45 AM
  • Hi Kristin,

    I am using the .NET Framework version V4.0.30319. The issue I am facing is same as that described in the KB:https://support.microsoft.com/en-us/kb/2640103. The application is crashing with the error description as "Faulting module name: clr.dll".

    If I upgrade the .NET version to the latest one does it resolves the issue, please suggest.

    Thanks, Hari

    Tuesday, April 19, 2016 6:36 AM
  • Hi Kristin,

    I am using the .NET Framework version V4.0.30319. The issue I am facing is same as that described in the KB:https://support.microsoft.com/en-us/kb/2640103. The application is crashing with the error description as "Faulting module name: clr.dll".

    If I upgrade the .NET version to the latest one does it resolves the issue, please suggest.

    Thanks, Hari

    @Hari,

    I am not 100% sure. But I would suggest you have a try,

    In additon, you could try to repair your .Net Framework first, please use .NET Framework Repair Tool: http://www.microsoft.com/en-us/download/details.aspx?id=30135If the repair tool doesn't help, I suggest you could visit the following site to post a
    hotfix request for your current environment:
    https://support.microsoft.com/en-us/hotfix/kbhotfix?kbnum=2640103&kbln=en-us

    Hope it helps!

    Best regards,

    Kristin


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Tuesday, April 19, 2016 7:04 AM
  • Hi Kristin,

    I have downloaded the below hot fix and tried to install it but it is throwing the below message and blocking the installation. Could you please suggest is there any other way to fix the error.

    KB2640103 does not apply, or is blocked by another condition on your computer

    Thanks

    Hari

    Friday, April 22, 2016 5:06 AM
  • Hi Hari,

    >>KB2640103 does not apply, or is blocked by another condition on your computer

    Do you mean you have downloaded the KB2640103 successfully? I am afraid as my first reply mentioned, KB2640103 is missing now. This bug is too long time ago. Now this issue is fixed in the next .net framework. You'll need to update your .net framework to the latest or higher. Then try to checki if this issue is missing now. Good luck!

    Best regards,

    Kristin


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, April 25, 2016 2:10 AM
  • Hey folks,

    switch on your brains. Drink some coffee and READ THE ENTIRE ARTICLE of KB2640103, not just goolge for "clr crashes", finding the KB and download the stuff. That's not the way a responsible administrator or IT clerk will work.

    We're living in 2016, this discussion is startd in April, and Microsoft rolled out the .net 4.5 a while ago and 4.6 is that what you'll find on most systems now or what you get when installing the most recent version of .net

    That will change the clr.dll and it's version.
    Current  version is 4.6 where it's 32 bit  clr.dll is datad 07-31-2015 if all recent updates are applied.

    The patch in KB2640103 is simply outdated -> Article ID: 2640103 - Last Review: 01/12/2012 08:53:00 - Revision: 2.0 

    There is a clr.dll inside from Nov 2011

    Clr.dll 4.0.30319.526 6,726,912 04-Nov-2011 12:10 x86

    Of course the installer of the patch will refuse to overwrite a newer version :-( so check this first in C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll 

    or in case it's 64 bit
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

    Systems with .net 4.0 or 4.5 shold show a clr.dll from oct 2013



    IT architect - Terminal servers, virtualizations, SQL servers, file servers, WAN networks and closely related to software devleopment (8 years + experience in VB, C++ and script langugaes), MCP for SQL server and CCAA for Xenapp 6.5

    Thursday, June 9, 2016 7:22 AM