Saturday, November 30, 2013

ASP.NET Web Application crash, faulting module KERNELBASE.dll, exception code 0xe053534f


Stressing your ASP.NET application you may bring the whole Website out-of-order. The application pool will stop after numerous crashes: look for system event log entry

Application pool '<your pool name>' is being automatically disabled due to a series of failures in the process(es) serving that application pool.

Referring application log event log entries are:

Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7afa2
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18229, time stamp: 0x51fb1677
Exception code: 0xe053534f
Fault offset: 0x000000000000940d
Faulting process id: 0x%9
Faulting application start time: 0x%10
Faulting application path: %11
Faulting module path: %12
Report Id: %13


Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: w3wp.exe
P2: 7.5.7601.17514
P3: 4ce7afa2
P5: 6.1.7601.18229
P6: 51fb1677
P7: e053534f
P8: 000000000000940d

Attached files:

These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: 922480ec-59e6-11e3-b316-00155d49e7d5
Report Status: 4

There are some useful articles how to debug such crash. One of my favorite is this article from Tess Fernandez:

Debugging a .NET crash with rules in Debug Diag

If you use SQL database for ASP.NET state management, you may try this quick fix:

  • go to ASPState database (for example, using SQL Management Studio)
  • clear ASPStateTempSessions table:

      delete FROM [ASPState].[dbo].[ASPStateTempSessions]

This fix helped us to bring the pool to run again.


No comments: