


WinDbg is a useful tool to troubleshoot heap corruption issues. However, some causes such as heap corruptions may require a further analysis. Keep your Windows and third-party software updatedĭebugDiag logs provide a valuable information to narrow down the issue.If you have recently upgraded it, the new version might be causing this issue There might be a memory leak due to a logical issue in the application.Temporarily disable any antivirus software and monitor the system It might because of an access violation error.The crash dump should tell the root cause of the issue. The first step would be running DebugDiag tool to collect crash dump.
/ntdll-dll-errors-2624474-5bf84ce546e0fb00511f0427-cc609193561047bd85da19c2c9ba0937.jpg)
This issue could be result of the slow performance of an application. In some cases, w3wp.exe may crash with the error code 0xc0000374 in Event Viewer: Each worker process serves for a specific application pool and each application pool has at least one instance of w3wp.exe. It is a Windows process which handles requests received by the web server. IIS worker process uses w3wp.exe file to process client requests.
