I keep crashing with the error clr.dll
I’ve already tried everything and hope someone here has an idea
Community folder is empty, steam version
Not sure if you are an AMD user but I just sent this to Asobo/Zendesk:
UPDATE August 19 2021: Soooo…I know this is not a solution BUT it gives me MSFS back without CTDs. MY SOLUTION, after trying all kind of alternatives suggested by Asobo, was to take my AMD GPU driver back from the current 21.6.1 to a November 30 2020 driver 20.11.3. This has always been a stable driver for me. Asobo perhaps you can figure out the difference in handling GPU interfaces with MSFS between these two drivers and get closer to the fixing CTD for many users?
My Community folder has REX Global Airport Textures in it…Store version of MSFS
Thank you very much, I have a nvidia card and have already tried many drivers
Sorry I could not help. I thought Nvidia users were not having the same CTD problems, good luck.
You may have already tried it, but have you ran the system file checker?
I was constantly getting a DLL error and maybe a coincidence but it hasn’t crashed since
Lower A LOT your GPU mhz 
hey man, what brand of NVidia GPU? If you have the MSI Afterburner or ASUS GPU Tweak II, have this two overclock apps disable it completely from the startup. To do this, open Task Manager, click Startup Tab, look for the overclock app, right click on it and select disable.
Start your PC and run again the sim. If its still crash and you have Nvidia GeForce Experience disable that too or better yet remove it completely using DDU and just install the gpu driver.
Hope this helps.
1 Like
I cannot help you, but I got the same problems with constant CTDs caused bei clr.dll (located in /Microsoft.NET\Framework64\v4.0.30319\clr.dll) in 99% of the CTDs. Tried any solution suggested by zendesk and any possible way for solutions found elsewhere to no avail. Windows Resource Protection did not find any integrity violations. As you cannot un- and reinstall Microsoft.Net in a Windows 10 environment I gave up using MSFS for the time beeing…
1 Like
latest I remember ( he reported former same , follow a bit back and forth ):
But we have only the info from heading “clr.dll” from you and so its very hard to say something.
( why users not use the issue template ? )
I did this once with sfc /scannow. initially it was also good
I have an ASUS TUF-RTX3080-10G-GAMING, not overclocked and no tools installed.
I will uninstall geforce expierence again
I’ll also try the sound settings
many thanks
1 Like
Also make sure that all your windows app is up-to-date. To do this, click Microsoft Store, click the 3 dots on the top right corner and select Download and Updates, then click Get Updates. Once all your apps has been updated (subject to GeForce Experience has been uninstall) and try again.
In the standard User Template made by Zendesk they did not include to remove/disable Steam Overlay or GeForce Experience overlay. They need to update that standard template.
They should do that only if this is ensured the reason for issues.
Also in case steam users disable the overlay they are no longer able to buy something in marketplace.
I also assume the overlays are only relevant if users use it, e.g. the new nvidia performance counter.
I personaly see no issues and have no issues with both of the mentioned tools/overlays of it. I assume if there would be a generall issue we had much more issue reports related to steam and/or g.experiance overlay in the forum ( where the solution was ensured to uninstall or deactivate … ) .
But of course, a test case might be it worth 
PS.: what I know is that while ago users report issues with these xbox game tool. Also some users had enabled these “allways” video-recording ( similar to these “highlight” recoding in gerforce exp ) , which caused for some users performacne issues.
true. its vary for one PC to another. I’m baffled and curios because my Windows 10 now just ran the most basic stuff for it to operate.
Still, I’m experiencing CTD. It’s tiring you know to troubleshoot and figuring this out when my PC does not have any issue playing other sim or games.
Anyway… I guess it will go away by itself. More games coming out next months so I will look again at this sim months/year after that.
1 Like
it’s just complex and allways hard to find out what the reason is. Beside of all that horror stories from windows itself, the drivers, effect of parallel running apps, overclocking, etc… have also the mods not less impact. As example the H135 creates ( steam install ) a own dll outside of the packages folder ( which should not happen ). Other mods overwrite completly elements of the game. And in all of these variables around, there are of course in-game bugs possible which can cause a crash ( pretty sure 
).
I assume a game which is modable have allways a higher risc to run into issues.
I have now been able to make several flights without having a crash. even with the Spitfire, and there it always crashed.
-from my Samsung 49" C49RG9x the sound disabled
-uninstalls everything that has to do with Asus, Garmin or Logitech
-under System Sound Input changed from Digital-In to What U Hear
but I don’t want to rejoice too soon, crashed again and again for months, I was already very upset
as mentioned, we can never be sure whether it comes from a mod . ( Unfortunately is also marketplace content not realy quality checked. )
But I seen you own VR hardware… I remember some reports where users mentioned that the trouble started with installing the VR software/drivers. Since then they running also in 2D into issue ( why ever ).
Is the error allways the “clr.dll” , or is it different in latest crash ?
I copied Spitfire back into the community folder and then tried to see if it works again. VR is not connected at the moment, I only plug it back in when I certainly have no more crashes
otherwise only clr.dll crashes
after so many months with the crashes I can finally enjoy the flight simulator and that also in VR… everything runs wonderfully and really nice smooth 
1 Like
so… was realy the Spitfire ?