This is a crash that occurs during shutdown of the process - so nothing was
actually running at the time.
Basically VB was working through some cleanup and crashed b/c one of the
structures had become corrupt. This should not affect normal runtime.
You may be able to isolate the issue with PageHeap and a more invasive
debugging session using WinDBG.
Pat
<finn.bjornsen.RemoveThis@hotmail.com> wrote in message
news:1131448966.141751.61230@g49g2000cwa.googlegroups.com...
> To all of my online friends.
>
> I have a problem with my Windows Server 2003 SP 1 servers. I run IIS6
> on the servers, and the w3wp.exe processes keep crashing.
>
> I ran IISState and extracted the following log:
>
>
> ***********************
>
>
> IIS has crashed...
> Beginning Analysis
> DLL (!FunctionName) that failed: ntdll!RtlFreeHeap
>
>
>
>
> Thread ID: 0
> System Thread ID: 974
> Kernel Time: 0:0:0.109
> User Time: 0:0:0.93
> Thread Type: Other
> # ChildEBP RetAddr
> WARNING: Stack unwind information not available. Following frames may
> be wrong.
> 00 0006fcd4 0f001f99 ntdll!RtlFreeHeap+0x2c
> 01 0006fcec 0f012c1a MSVBVM50!CFileRep::~CFileRep+0x26
> 02 0006fcfc 0f012bc0 MSVBVM50!_cexit+0x65
> 03 0006fd0c 0f001db3 MSVBVM50!_cexit+0xb
> 04 0006fd10 0f001c84 MSVBVM50!_CRT_INIT+0x114
> 05 0006fd30 7c82257a MSVBVM50!_DllMainCRTStartup+0x9d
> 06 0006fd50 7c8118b0 ntdll!LdrInitializeThunk+0x24
> 07 0006fdec 77e52fea ntdll!RtlEnumerateGenericTableWithoutSplaying+0x9b
> 08 0006fed8 77e5304d kernel32!_ExitProcess+0x43
> 09 0006feec 79215e7c kernel32!ExitProcess+0x14
> 0a 0006fef8 7921d4dc mscorwks!SafeExitProcess+0x38
> 0b 0006ff04 79215ab6 mscorwks!ForceEEShutdown+0x53
> 0c 0006ff10 78810918 mscorwks!CorExitProcess+0x5f
> 0d 0006ff20 77bcaddb mscoree!CorExitProcess+0x46
> 0e 0006ff2c 77bcaefb msvcrt!__crtExitProcess+0x29
> 0f 0006ff5c 77bcaf52 msvcrt!_cinit+0xd2
> 10 0006ff70 01001a38 msvcrt!exit+0x11
> 11 0006ffc0 77e523cd w3wp!wmainCRTStartup+0x140
> 12 0006fff0 00000000 kernel32!BaseProcessStart+0x23
> Closing open log file F:\Program Files\IIS
> Resources\IISState\output\IISState.log
> Opened log file 'F:\Program Files\IIS
> Resources\IISState\output\IISState.log'
>
>
> It seems as if there is a problem with the MSVBVM50 (Microsoft Visual
> Basic Virtual Machine v5.0).
>
> I've tried isolating the problem using Application Pools, and have
> traced crashed both in old style asp application and new asp.net
> application based on .net framework 1.1.
>
> Any help appreciated.
>
> PS! Please do not post answers like "Contact MS support" and "Reinstall
> everything".
>
>> Stay informed about: IIS6 w3wp.exe crashes (rtlfreeheap)