Windows 10: Applications using .NET Framework consistently CTD with internal CLR error 0x80131506,...

Any and all applications that use dotnet, such as paintdotnet.exe, will briefly function before closing with an internal CLR error 0x80131506. The applications' individual error logs cite different and inconsistent paths each crash, which gives me the impression that this is specifically the framework itself. All existing threads involving these errors are made by developers, not users, so I have not been able to find a solution on this forum.The event viewer consistently logs these crashes in quick succession as follows, using paintdotnet.exe as an example:1Application: paintdotne

:)

 

Applications using .NET Framework consistently CTD with internal CLR error (0x80131506), event viewer blames coreclr.dll

Any and all applications that use dotnet, such as paintdotnet.exe, will briefly function before closing with an internal CLR error (0x80131506). The applications' individual error logs cite different and inconsistent paths each crash, which gives me the impression that this is specifically the framework itself. All existing threads involving these errors are made by developers, not users, so I have not been able to find a solution on this forum.

The event viewer consistently logs these crashes in quick succession as follows, using paintdotnet.exe as an example:

Solutions I have tried include:
- Uninstalling and reinstalling the program in question. Reinstallation occasionally fails with the same error shown in event viewer.
- Uninstalling and reinstalling the respective .NET Frameworks versions. However, as the programs in question have pre-packaged files, this likely didn't do anything.
- sfc /scannow and the DISM triad (check/scan/restore).
- Running the .NET Framework repair tool,
- Uninstalling and reinstalling drivers.
- Running MSERT and other programs to check for malware.
- Running ProcessMonitor to pinpoint the exact moment the issue occurs.
Notably, dotnet.exe calls for HKLM/SOFTWARE/Microsoft/Rpc/SecurityService, vssvc.exe creates a thread, mmc.exe enters HKCU, and dotnet.exe subsequently calls for WerFault.exe to (presumably) begin the error log.
- Uninstalling and reinstalling windows updates, and preventing the update service from running.
After uninstalling update KB5031356, the issue appeared to have been resolved; however, now that it has been reinstalled, it produces error 0x800f0905 when I attempt to uninstall it a second time.

I've been troubleshooting this for about a week now, and I'm a bit stumped. I don't want to reset this PC yet, though. Thank you in advance.

EDIT: Attempting to reinstall Windows 10 while keeping all files and apps did not fix the issue.
The event viewer recently portrayed the same error as "System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt."

 

Microsoft .Net Framework

Basically, to sum up what I can tell:
-The application(s) that crashed use .NET Framework 2.0 or 3.5.
-First error is it getting nothing when it expected something (not very telling).
-Second error occured in "System.Data.SQLite" which is not .NET Framework. I repeat, not .NET Framework.
-SQLite is is a GNU licenced, free to use library.
-Any .NET-compiled service or process could be causing the error. If you watch the Task Manager, you might be able to tell which process closes after you click on "Quit."

I suggest you search your computer for sqlite*.dll. Whatever programs it is found in close proximity to are most likely the culprits for the crashes.

 

Microsoft .NET Framework, Unhandled exception

Hi,

Welcome to Microsoft Community.

I suggest you to un-check and recheck .Net framework 3.5 and .Net framework 4.6 advance series from Windows features.

Try the following steps:

• Press Windows + R keys to open Run command.
• Type Appwiz.cpl and select "turn Windows feature on or off" from the left
• Uncheck .Net framework 3.5 and .Net framework 4.6 advance series.
• Restart the computer
• Repeat step 1 and 2 and check .Net framework 3.5 and .Net framework 4.6 advance series.
• Restart the computer.

Regards,