IIS Application Pool Fails with Exception 0xc0000005

Question

My application pool continues to crash when I use a third party .net provider. I don’t know where to even start fixing the problem.

I used Event Viewer to get the following information:

  Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7a5f8
 Faulting module name: ntdll.dll, version: 6.1.7601.17514, time stamp: 0x4ce7b96e
 Exception code: 0xc0000005
 Fault offset: 0x00052d94
 Faulting process id: 0x162c
 Faulting application start time: 0x01cd8ad4f6ad757b
 Faulting application path: c: \ windows \ system32 \ inetsrv \ w3wp.exe
 Faulting module path: C: \ windows \ SYSTEM32 \ ntdll.dll
 Report Id: 36661c3b-f6c8-11e1-830c-180373c0a6cd  

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2012-09-04T19:39:17.000000000Z" /> <EventRecordID>26328</EventRecordID> <Channel>Application</Channel> <Computer>my computer</Computer> <Security /> </System> <EventData> <Data>w3wp.exe</Data> <Data>7.5.7601.17514</Data> <Data>4ce7a5f8</Data> <Data>ntdll.dll</Data> <Data>6.1.7601.17514</Data> <Data>4ce7b96e</Data> <Data>c0000005</Data> <Data>00052d94</Data> <Data>162c</Data> <Data>01cd8ad4f6ad757b</Data> <Data>c:\windows\system32\inetsrv\w3wp.exe</Data> <Data>C:\windows\SYSTEM32\ntdll.dll</Data> <Data>36661c3b-f6c8-11e1-830c-180373c0a6cd</Data> </EventData> </Event> 

Answer 1

Please check if the account under which the w3wp.exe workflow runs has read / write permissions for your hosting folder (for example, Inetpub).

Answer 2

I had the same problem. In my code, I had the following line of vb.net code:

 Dim mPath as string = Environment.GetFolderPath(Environment.SpecialFolder.Desktop) 

All of my ASP.NET crashed because it cannot access this folder at runtime. Error handling does not work. Clr just falls.

Replacing this line with an existing directory solved my problem.

Answer 3

I had the same problem and it took me two days to find a solution. So even if this topic is almost three years old, I am posting my answer. Maybe this helps someone save a lot of time.

I had to disable the caching function in web.config. I used "caching" as well as the "staticContent" tag. I had to remove both.

Answer 4

I had the same problem, but it was solved by manually deleting the MVK files of the MVC and obj project.