Our very first post on the “Has Stopped Working” website has to do with a very annoying problem that is affecting thousands, if not, tens and hundreds of thousands of users from all over the world – the CLR20r3 event issues which appear after various software give the “has stopped working” alarm. Of course, this happens in Windows when using different applications, such as Puush, FileHippo, MediaPortal, Windows Media Center, 3DMark and many others. Here’s what some users had to say with regards to this annoying problem:
hi, I’ve been having problems everytime I open a program.. it say the program has stopped working and shows this message:
Problem Event Name: CLR20r3
Problem Signature 01: article submitter.exe
Problem Signature 02: 18.104.22.168
Problem Signature 03: 4d41115f
Problem Signature 04: System.Drawing
Problem Signature 05: 22.214.171.124
Problem Signature 06: 4a275e83
Problem Signature 07: 7af
Problem Signature 08: 6c
Problem Signature 09: System.ArgumentException
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
this also happen with some of the programs installed on my machine too. any suggestions??? thanks.
And another weighs in with his problem, as well:
Hi, I have a VB application which will not run on a W2008R2 terminal server but works fine on other PCs. This application ran fine till recently. All PCs run the application from a common network directory. The application was originally compiled to .NET 2.0 & worked on all platforms. Then I recompiled it to .NET 4.0. There were various issues on the other PCs so I took it back to .NET 2.0. Now on trying to start it on the server I get “The application has stopped working” with a CLR20r3 error. Google seems to imply this is a .NET problem. I have removed .NET 4 – no change & reinstalled it again – no change. Tried to reinstall .NET 2 but I get an error saying it’s part of the operating system..
Possible solutions for CLR20r3 Windows issue
First of all, we need to tell you that this issue has been very present with Windows 7 machines, and as Windows 7 is still the absolute leader, the annoying issue that is identified as event CLR20r3 is still present. It might sound dumb, but the first suggestion is to upgrade your machine to Windows 8 or Windows 8.1, as the latest operating system, despite all the criticism, is much secure and has less bugs. Also, another useful advice is to check whether you have the latest version of framework installed (you can check the link at the end).
Now, this issue has been affecting many developers of applications, so if your app is built in non Unicode language fonts and the system that you are running is on Unicode fonts, then you’ll just have to change the default to non Unicode fonts. Also, you will need to make sure that the client system is running the same or a higher version of the .NET framework that you used to build the app or the program.
After reading through multiple forums, I’ve seen that the SQLDMO.Dll file could be causing this problem. A solution would be to install the latest version of Microsoft SQL Server (download link at the end of the article). If that doesn’t work, try running a previous version. And just to be sure, download and install the SAP Crystal Reports Runtime engine for the .Net framework (32 bit or 64 bit), as well. You could also try to add or update the app.config in your project, this is a solution that worked for many on StackOverflow.
Also, you can try out the .NET Framework Setup Verification Tool User’s Guide, which is an official resource from MSDN (link also at the end). If the CLR20r3 problem is caused by your Windows Media Center, you might try and use the solutions provided here. What are your experiences with these annoying problems that are identified as the CLR20r3 event. Do you happen to know any working fixes? If so, do share it with us by leaving your comment below.
Another potential fix for CLR20r3 problems
Thanks to our reader Revaz Kavtiashvili, we now have another potential fix. Here’s what he is suggesting:
Local User Policy \ Computer Configuration \ Windows Settings \ Security Settings \ Local Policies \ Security Options – System cryptography: Use FIPS 140 compliant cryptographic algorithms, including encryption, hashing and signing – Disable
Let us know if this solved it for you!