The just means the asp.net core application throw an uncaught error. The app should have implemented error logging. If not, there may be a message in the event logs.
Unhandled exception in CoreCLR
The following error was raised in IIS on Production Server.
Application: w3wp.exe CoreCLR Version: 8.0.724.31311 .NET Version: 8.0.7 Description: The process was terminated due to an unhandled exception. Exception Info: exception code c0000005, exception address 0000000055B4E30A
Developer technologies | ASP.NET | ASP.NET API
2 answers
Sort by: Most helpful
-
Bruce (SqlWork.com) 79,101 Reputation points Volunteer Moderator
2025-04-18T15:13:17.8433333+00:00 -
Danny Nguyen (WICLOUD CORPORATION) 725 Reputation points Microsoft External Staff
2025-07-10T06:23:44.26+00:00 Hi,
The error "exception code c0000005, exception address 0000000055B4E30A" inw3wp.exe
with .NET 8.0.7 typically indicates an Access Violation. This is a severe error that means the application tried to access memory it wasn't allowed to, leading to its termination.Please check your Application's Logs to look for any errors, warnings, or detailed logs from your ASP.NET Core application immediately preceding the crash. These might give clues about what the application was doing when it crashed.
In Windows Event Viewer:
- Application Logs: Filter for errors and warnings from the "Application" source around the time of the crash.
- System Logs: Check for any system-level errors or warnings that might indicate broader server issues.
- .NET Runtime Logs: Look for events related to
.NET Runtime
orASP.NET Core
that might provide more context.
Also check out these official troubleshooting guide:
Troubleshoot a Process Crash in an IIS Application Pool: This is a highly relevant article that walks you through identifying process crashes, understanding common error codes (including
0xC0000005
), and most importantly, how to use tools likeDebug Diagnostic Tool
(DebugDiag) orProcDump
to collect crash dumps. It then touches on analyzing these dumps.Troubleshoot ASP.NET Core on Azure App Service and IIS: While some parts are Azure-specific, many troubleshooting techniques for ASP.NET Core on IIS are universal. This article covers enabling detailed logging, collecting stdout logs, and obtaining crash dumps using PowerShell scripts (
EnableDumps.ps1
) for both in-process (w3wp.exe
) and out-of-process (dotnet.exe
) hosting models.Troubleshoot Permission and Security Issues (ASP.NET): Although
c0000005
is often a memory access issue, sometimes underlying permission problems can lead to unexpected crashes. This documentation provides good steps for checking application pool identity permissions.If these didn't pinpoint your problem, please try to recreate your problem in a fresh project to narrow it down and give me the detailed logs of your error.