I was looking to setup a blog engine here for testing, so I tried CommunityServer and dasBlog. Both were pretty easy to setup, but what was confusing was that both of these blog servers ended up taking down my IIS process when hitting certain pages. The error messages in the Event Viewer were either:

aspnet_wp.exe  (PID: 936) stopped unexpectedly.

or

Faulting application inetinfo.exe, version 5.1.2600.2180, faulting module aspnet_isapi.dll,
version 1.1.4322.2032, fault address 0x0001e214.

I figured if both of these engines were taking down IIS, it wasn't just a simple bug in the blog software, but something more sinister. Googling came up empty for me, and then I stumbled upon the EventID website. Putting in the information there eventually took me to one possible solution. Namely:

Change the application setting for the website, which you will find under IIS Console. 
There is a button Configuration. There you will find a checkbox "Cache ISAPI Application". 
For asp.net this option must be enabled, otherwise you get this error.

Following this advice, the error did indeed go away. I haven't done anything to IIS to turn that off, so that makes this whole situation even more ridiculous. It's dumb enough to ship IIS with a default setting that makes ASP.NET applciations take down IIS completely, but IMO, it's even dumber to allow IIS to abend like this when Microsoft knows that this option must be enabled to make ASP.NET applications work properly. A simple exception trap to put better information in the EventViewer, or display a message box when the situation is detected, or even use the EventViewer server communication facility to tell you why you're getting the error would all be better than the current situation.