Share via

Need assistance with .Net Framework runtime error on ver 4.8 .

Avinash M 0 Reputation points
2025-11-20T10:53:18.3066667+00:00

I'm using Fortra's Automate software which uses .Net and when running tasks, it's erroring out and before the application error there's .Net runtime error.

Vendor advised that the issue is with .Net and not their application. However unable to make changes (install / uninstall / reinstall / disable / enable) to .Net framework on the server. So, .net repair tool hasn't been of much help.

Also, CPU usage would be fluctuation and does hit 100% at times.

I see that Services and Controller app, Windows Power Shell, System and the BPATask are the ones consuming most CPU during peak CPU usage, don't see any heavy usage of RAM, is it possible that high CPU utilization is causing

Has anyone come across any such issues and have any idea on how to fix this?

Below are application error logs.

Application: BPATask.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 00007FFD3725BAB6 (00007FFD371C0000) with exit code 80131506.
Faulting application name: BPATask.exe, version: 24.2.0.24, time stamp: 0x66743a4f Faulting module name: clr.dll, version: 4.8.4795.0, time stamp: 0x6837ce52 Exception code: 0xc0000005 Fault offset: 0x000000000009bab6 Faulting process id: 0x74c Faulting application start time: 0x01dc54a3b8d8b349 Faulting application path: C:\Program Files\Automate 2024 Agent\BPATask.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: 567e7ae3-1d00-438c-b9f0-bbd8ac696ab1 Faulting package full name:  Faulting package-relative application ID:
Application: NewChkLck.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 7135A653 (71300000) with exit code 80131506.
Faulting application name: NewChkLck.exe, version: 24.2.0.24, time stamp: 0x66743b6b Faulting module name: clr.dll, version: 4.8.4795.0, time stamp: 0x68380c19 Exception code: 0xc0000005 Fault offset: 0x0005a653 Faulting process id: 0x83c Faulting application start time: 0x01dc59cf9c9fae24 Faulting application path: C:\Program Files\Automate 2024 Agent\NewChkLck.exe Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll Report Id: 6dfdacae-e8c0-4450-8dc6-dcbba15c6ab3 Faulting package full name: Faulting package-relative application ID:
Developer technologies | .NET | .NET Runtime

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2025-11-20T10:53:45.1633333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It seems you are encountering a .NET Framework runtime error related to the clr.dll when using Fortra's Automate software. The error code 0xc0000005 typically indicates an access violation, which can occur due to various reasons such as corrupted installation, insufficient permissions, or conflicts with other software.

    Here are some steps you can take to troubleshoot and potentially resolve the issue:

    1. Check Permissions: Ensure that the user account running the application has sufficient privileges. You may need to run the application as an administrator.
    2. Repair .NET Framework: Since the .NET Repair Tool hasn't been helpful, you might want to try manually repairing the .NET Framework installation. You can do this through the Control Panel by going to "Programs and Features", selecting the .NET Framework, and choosing the repair option if available.
    3. Reinstall .NET Framework: If repairing does not work, consider uninstalling and then reinstalling the .NET Framework 4.8. Make sure to restart the server after uninstallation and before reinstallation.
    4. Check for Windows Updates: Ensure that your Windows Server is up to date, as updates can sometimes resolve underlying issues with .NET Framework.
    5. Event Viewer Logs: Check the Windows Event Viewer for any additional logs that might provide more context about the error. Look under "Windows Logs" > "Application" for any related entries.
    6. Compatibility Mode: If the application is running in compatibility mode, try disabling it. Right-click on the application executable, go to Properties > Compatibility, and uncheck any compatibility settings.
    7. Check for Conflicts: Ensure that there are no other applications or services that might be conflicting with the .NET Framework or the Automate software.

    If these steps do not resolve the issue, you may need to reach out to Microsoft Support or consult the vendor for more specific guidance related to their software.

    References:

    0 comments
  2. Surya Amrutha Vaishnavi Lanka (INFOSYS LIMITED) 1,115 Reputation points Microsoft External Staff
    2025-11-21T10:59:23.2633333+00:00

    Thanks for reaching out!
    The error means that exit code 0x80131506 is a CLR fatal error this is inside the .NET runtime, typically triggered by native code/third‑party hooks, corrupted native images , or OS/runtime component corruption.
    CPU spikes to 100% do not directly cause CLR internal errors. They can amplify race conditions or starve threads, but the crash signature points to native/CLR corruption, not merely high CPU.
    Here are some steps which are helpful
    1.Repair OS and CLR binaries

    Run these commands in elevated Command Prompt : DISM /Online /Cleanup-Image /RestoreHealth
    2.Regenerate .NET Native Images

    Run all 4commands
    "%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\ngen.exe" update

    "%WINDIR%\Microsoft.NET\Framework64\v4.0.30319\ngen.exe" executequeueditems

    "%WINDIR%\Microsoft.NET\Framework\v4.0.30319\ngen.exe" update

    "%WINDIR%\Microsoft.NET\Framework\v4.0.30319\ngen.exe" executequeueditems
    3.Disable Profilers and Injectors

    Check and clear environment variables:
    Get-ChildItem Env: | Where-Object { $.Name -match '^(COR|COMPlus|CORECLR)' }

    setx COR_ENABLE_PROFILING 0 /M
    4.Align Process Bitness

    Verify Automate tasks run under correct architecture:
    Get-Process BPATask, NewChkLck | Select Name, Id, @{N='Bitness';E={

        if ($_.MainModule.FileName -like 'Framework64') {'x64'} else {'x86'}

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.