Share via

Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll

Jayanthi Iyer 0 Reputation points
2025-02-28T16:00:22.73+00:00

My application running on Windows server 2016 keeps crashing. I have updated the .Net Framework to 4.8. But the issue still persists.

I have replaced application specific data with xxx in the log details below. Any suggestions for me to try and fix it?

Log Name:      Application Source:        Application Error Date:          2/28/2025 9:00:06 AM Event ID:      1000 Task Category: (100) Level:         Error Keywords:      Classic User:          N/A Computer:      xxxx Description: Faulting application name: xxx.exe, version: 1.0.0.0, time stamp: 0x61a671dc Faulting module name: clr.dll, version: 4.8.4775.0, time stamp: 0x674e9bae Exception code: 0xc0000005 Fault offset: 0x0000000000082dd6 Faulting process id: 0x15cc Faulting application start time: 0x01db89f1712d813f Faulting application path: xxx.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: 891c4a86-3cb1-47bf-b5f5-bc9f0097b7fb Faulting package full name:  Faulting package-relative application ID: 

Visual Studio Debugging
Visual Studio Debugging
Visual Studio: A family of Microsoft suites of integrated development tools for building applications for Windows, the web and mobile devices.Debugging: The act or process of detecting, locating, and correcting logical or syntactical errors in a program or malfunctions in hardware. In hardware contexts, the term troubleshoot is the term more frequently used, especially if the problem is major.
1,031 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dou Xu-MSFT 400 Reputation points Microsoft External Staff
    2025-03-03T05:51:32.0366667+00:00

    Hello @Jayanthi Iyer ,

    Welcome to Microsoft Q&A forum.

    From looking at the Exception code: 0xc0000005, also known as an Access Violation, occurs when an application tries to read, write, or execute memory that it doesn't have permission to access. There are many reasons for this problem, it would be nice to help debug if you could provide a minimal and reproduceable example. However, here are suggestions i would suggest you check:

    1.Please do a quick test to check if your .NET Framework damaged.

    • Create a new project as the same project type of the application crashed, then run the new project.
    • If the new application keeps crashing, please try to Repair your .NET Framework install using this tool: Repair .NET Framework
    • If not, looks like the .NET runtime is not the cause of the issue.

    2.Please check if you have any anti-virus installed (e.g:CylancePROTECT). If so, try to disable them then run the application again.

    3.Make sure that the operating system on your machine is fully updated. Sometimes, updates can fix compatibility issues with certain applications.

    Best Regards,

    Dou

    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments

Your answer

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