IIS 7 application pool crashing

I am running win 2008 R2, with IIS7.  I have multiple application pools and so far, two separate ones have crashed at different times. This error repeats almost every 30 min in my application event log. Not sure if this error is the cause, but it sure looks like it to me, as there's no other error.  Also, in looking at the event log, it looks like this error was occurring every 10 minutes for a few hours before it crashed.

Log Name:      Application
Source:        Application Error
Date:          5/20/2013 9:51:13 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      webserver
Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7a5f8
Faulting module name: nlssorting.dll, version: 4.0.30319.296, time stamp: 0x50484762
Exception code: 0xc00000fd
Fault offset: 0x000020d4
Faulting process id: 0xcc8
Faulting application start time: 0x01ce55decafb105c
Faulting application path: C:\Windows\SysWOW64\inetsrv\w3wp.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll
Report Id: 0fd54190-c1d2-11e2-9ce4-001ec9b51edb
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <TimeCreated SystemTime="2013-05-21T04:51:13.000000000Z" />
    <Security />
afactsNetwork EngineerAsked:
Who is Participating?
Meir RivkinConnect With a Mentor Full stack Software EngineerCommented:
usually, it causes due to space allocation exception.
to detect the code that might causes this, download WinDbg x64:  http://rxwen-blog-stuff.googlecode.com/files/windbg_6.12.0002.633_64_installer.zip
install it on the same machine where it crushes.
go to C:\ProgramData\Microsoft\Windows\WER\ReportQueue
all the debbuging files are dumped there.

run the WinDbg tool and select File > Open Crash Dump, choose the larget .tmp file in the dump folder above.
run the following in the command window:
.loadby sos clr

Open in new window

you gonna see a stack trace of your code before the crush which can assist you to detect the fault in your code.
also check this usefull post of debugging Faulting Application w3wp.exe Crashes:
afactsNetwork EngineerAuthor Commented:
Thanks for the suggestion
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.