IIS crashes with pop up window

Hello All,

I've been searching high and low without luck...

I have IIS6 running on Win2003 with a bunch of asp pages.
Several times a day I will get a pop up window on the server that
states: Memory could not be read at address xxxx error code yyy.
(Window title is w3wp.exe) Same message shows up in event log.

The horrible part is that the server becomes totally unresponsive
until I click the OK button and close the window. Sometimes it's just
1 window, sometimes it's 15 and I have to close them one by one.

Short term I moved each individual website into it's own application
pool. This causes IIS to respond for all application pools except for
the one that crashed.
So it seems like, the application pool crashes not IIS in general. All
application Pools are .Net 2.0

This has started a few months back and I have yet to find a solution.
Any input would be greatly appreciated!

Re: IIS crashes with pop up window

Follow instructions in thsi blog to get a stack trace of your crash,
and we should be able to identify the culprit and possibly even page
name/line number.

http://blogs.msdn.com/david.wang/archive/2005/08/29/HOWTO_Un derstand_and_Diagnose_an_AppPool_Crash.aspx


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Sep 27, 3:15 am, alfonso.mex...@yahoo.com wrote:
> Hello All,
>
> I've been searching high and low without luck...
>
> I have IIS6 running on Win2003 with a bunch of asp pages.
> Several times a day I will get a pop up window on the server that
> states: Memory could not be read at address xxxx error code yyy.
> (Window title is w3wp.exe) Same message shows up in event log.
>
> The horrible part is that the server becomes totally unresponsive
> until I click the OK button and close the window. Sometimes it's just
> 1 window, sometimes it's 15 and I have to close them one by one.
>
> Short term I moved each individual website into it's own application
> pool. This causes IIS to respond for all application pools except for
> the one that crashed.
> So it seems like, the application pool crashes not IIS in general. All
> application Pools are .Net 2.0
>
> This has started a few months back and I have yet to find a solution.
> Any input would be greatly appreciated!