Re: IIS State Log Analysis Needed: dllhost.exe large memory usage

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: David Trebacz (trebacz_at_msn.com)
Date: 10/12/04 

Date: Tue, 12 Oct 2004 09:46:44 -0500

Thanks for the information about the memory link. We will check our various
scripting engines for current versions and a couple 3rd party applications
we use. We'll also monitor memory usage if we do perform any upgrades
(although they should be current with the new install).

What resouce did you use to pinpoint "C0000017 is Out Of Memory"? We agree
with what we were seeing, but is there a web resource to pinpoint the reason
behind the error that we should be using for future errors like this? Any
suggestions for the future would be greatly appreciated.

"Pat [MSFT]" <patfilot@online.microsoft.com> wrote in message
news:ufdLtU#rEHA.4032@TK2MSFTNGP12.phx.gbl...
> C0000017 is Out Of Memory (this refers to the 2GB Virtual Memory map, and
> not to the installed memory of the machine). The crash is most likely the
> result of a dll being unable to allocate memory needed to continue.
>
> Most likely you have a dll that is leaking memory. IISState doesn't track
> memory leaks, so you will likely need to contact MS-Support for additional
> debugging help.
>
> Pat
>
> "David Trebacz" <trebacz@msn.com> wrote in message
> news:epCTEM9rEHA.3396@tk2msftngp13.phx.gbl...
> > Since a move the a new webserver (new machine -Windows 2000, IIS 5.0,
web
> > application) we have been experiencing periods where dllhost.exe reports
> > an
> > "Application Error" in a dialog box. This happens every 2-3 days -but it
> > is
> > random in time of day -or server load.
> >
> > "The exception unknown software exception (0xcOOOOO17) occurred in the
> > application at location 0x77fb14f4. Click on ok to terminate the
program."
> >
> > When the dialogue box appears we check the memory usage of dllhost.exe
and
> > it is exceptionally high (10 times typical -1.7 Gig -obviously a
problem).
> > This morning we were unable to restart Web Services -and had to reboot
> > the
> > server.
> >
> > Below is an IISSTATE log run shortly after confirming that dialog box
this
> > morning. It doesn't appear very helpful since everything seems to be
> > crashing. Is there a better way to run IIState?
> >
> > Opened log file 'D:\Program Files\IIS State\output\IISState-3532.log'
> >
> > ***********************
> > Starting new log output
> > IISState version 3.3.1
> >
> > Mon Oct 11 09:31:00 2004
> >
> > OS = Windows 2000
> > Executable: dllhost.exe
> > PID = 3532
> >
> > Note: Thread times are formatted as HH:MM:SS.ms
> >
> > ***********************
> >
> >
> >
> >
> > Thread ID: 0
> > System Thread ID: 23c
> > Kernel Time: 0:0:0.0
> > User Time: 0:33:31.437
> > *** ERROR: Symbol file could not be found. Defaulted to export symbols
> > for
> > C:\WINNT\system32\msxml4.dll -
> > *** ERROR: Symbol file could not be found. Defaulted to export symbols
> > for
> > C:\WINNT\system32\ntdll.dll -
> >
> > IISState has detected that this thread has thrown an unhandled exception
> > and is about to crash. IISState will now attempt to display the original
> > faulting stack.
> >
> >
> > .cxr 2954fad4
> > *** ERROR: Symbol file could not be found. Defaulted to export symbols
> > for
> > C:\WINNT\system32\CWBUNPLA.dll -
> > # ChildEBP RetAddr
> > 00 2954fdf8 78007108 KERNEL32!RaiseException+0x56
> > 01 2954fe38 6c3adb0c MSVCRT!_CxxThrowException+0x34
> > 02 2954fe4c 6c3e1801 MFC42!AfxThrowNotSupportedException
> > 03 2954fe64 6c3e19e7 MFC42!CThreadSlotData::SetValue+0xa7
> > 04 2954fe78 6c3e0f39 MFC42!CThreadLocalObject::GetData+0x70
> > 05 2954fe84 64bc3dbb MFC42!AFX_MAINTAIN_STATE2::AFX_MAINTAIN_STATE2+0x12
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 06 2954fe9c 64bc3feb CWBUNPLA!Ordinal47+0x7ab
> > 07 2954febc 77f830e7 CWBUNPLA!Ordinal72+0x167
> > 08 2954fedc 77f837f5 ntdll!RtlUnicodeStringToAnsiString+0xa7
> > 09 2954ff30 7c5745e7 ntdll!LdrShutdownThread+0x9f
> > 0a 2954ff98 7c57407b KERNEL32!ExitThread+0x53
> > 0b 2954ffa0 77ab5060 KERNEL32!FreeLibraryAndExitThread+0x24
> > 0c 2954ffb4 7c57438b ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x34
> > 0d 2954ffec 00000000 KERNEL32!BaseThreadStart+0x52
> >
> >
> > **Current Stack State**
> >
> > Thread Type: Other
> > # ChildEBP RetAddr
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 00 2954f4a0 69b3c4c8 msxml4!DllRegisterServer+0x1028
> > 01 2954f4c4 77f830e7 msxml4!DllMain+0x28
> > 02 2954f4e4 77f8ee02 ntdll!RtlUnicodeStringToAnsiString+0xa7
> > 03 2954f54c 7c580ed2 ntdll!LdrShutdownProcess+0xea
> > 04 2954f610 7c004429 KERNEL32!ExitProcess+0x51
> > 05 2954f618 7c00440a MSVCR70!__crtExitProcess+0x2e
> > 06 2954f624 7c00f791 MSVCR70!_cinit+0x101
> > 07 2954f634 7c012ac8 MSVCR70!_exit+0xe
> > 08 2954f67c 7c012799 MSVCR70!raise+0xae
> > 09 2954f6b0 7c020dd0 MSVCR70!abort+0xe
> > 0a 2954f6b8 7c58aa90 MSVCR70!__CxxUnhandledExceptionFilter+0x23
> > 0b 2954f9c0 7c571587 KERNEL32!UnhandledExceptionFilter+0x86
> > 0c 2954ffec 00000000 KERNEL32!BaseThreadStart+0x65
> >
> >
> > *****SUMMARY*****
> >
> >
> > Closing open log file D:\Program Files\IIS
State\output\IISState-3532.log
> > Opened log file 'D:\Program Files\IIS State\output\IISState-3532.log'
> >
> > ***********************
> > Starting new log output
> > IISState version 3.3.1
> >
> > Mon Oct 11 09:35:26 2004
> >
> > OS = Windows 2000
> > Executable: dllhost.exe
> > PID = 3532
> >
> > Note: Thread times are formatted as HH:MM:SS.ms
> >
> > ***********************
> >
> >
> >
> >
> > Thread ID: 0
> > System Thread ID: 23c
> > Kernel Time: 0:0:0.0
> > User Time: 0:36:46.390
> >
> > IISState has detected that this thread has thrown an unhandled exception
> > and is about to crash. IISState will now attempt to display the original
> > faulting stack.
> >
> >
> > .cxr 2954fad4
> > *** ERROR: Symbol file could not be found. Defaulted to export symbols
> > for
> > C:\WINNT\system32\CWBUNPLA.dll -
> > # ChildEBP RetAddr
> > 00 2954fdf8 78007108 KERNEL32!RaiseException+0x56
> > 01 2954fe38 6c3adb0c MSVCRT!_CxxThrowException+0x34
> > 02 2954fe4c 6c3e1801 MFC42!AfxThrowNotSupportedException
> > 03 2954fe64 6c3e19e7 MFC42!CThreadSlotData::SetValue+0xa7
> > 04 2954fe78 6c3e0f39 MFC42!CThreadLocalObject::GetData+0x70
> > 05 2954fe84 64bc3dbb MFC42!AFX_MAINTAIN_STATE2::AFX_MAINTAIN_STATE2+0x12
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 06 2954fe9c 64bc3feb CWBUNPLA!Ordinal47+0x7ab
> > 07 2954febc 77f830e7 CWBUNPLA!Ordinal72+0x167
> > 08 2954fedc 77f837f5 ntdll!LdrpCallInitRoutine+0x14
> > 09 2954ff30 7c5745e7 ntdll!LdrShutdownThread+0xa3
> > 0a 2954ff98 7c57407b KERNEL32!ExitThread+0x53
> > 0b 2954ffa0 77ab5060 KERNEL32!FreeLibraryAndExitThread+0x24
> > 0c 2954ffb4 7c57438b ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x34
> > 0d 2954ffec 00000000 KERNEL32!BaseThreadStart+0x52
> >
> >
> > **Current Stack State**
> >
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 2954f4a0 69b3c4c8 msxml4!Runtime_exit+0x37
> > 01 2954f4a4 69b3c2cb msxml4!DllMain+0x3b
> > 02 2954f4c4 77f830e7 msxml4!_DllMainCRTStartup+0x50
> > 03 2954f4e4 77f8ee02 ntdll!LdrpCallInitRoutine+0x14
> > 04 2954f54c 7c580ed2 ntdll!LdrShutdownProcess+0x11d
> > 05 2954f610 7c004429 KERNEL32!ExitProcess+0x51
> > 06 2954f618 7c00440a MSVCR70!__crtExitProcess+0x2e
> > 07 2954f624 7c00f791 MSVCR70!_cinit+0x101
> > 08 2954f634 7c012ac8 MSVCR70!_exit+0xe
> > 09 2954f67c 7c012799 MSVCR70!raise+0xae
> > 0a 2954f6b0 7c020dd0 MSVCR70!abort+0xe
> > 0b 2954f6b8 7c58aa90 MSVCR70!__CxxUnhandledExceptionFilter+0x23
> > 0c 2954f9c0 7c571587 KERNEL32!UnhandledExceptionFilter+0x86
> > 0d 2954ffec 00000000 KERNEL32!BaseThreadStart+0x65
> >
> >
> > *****SUMMARY*****
> >
> >
> > Closing open log file D:\Program Files\IIS
State\output\IISState-3532.log
> > Opened log file 'D:\Program Files\IIS State\output\IISState-3532.log'
> >
> > ***********************
> > Starting new log output
> > IISState version 3.3.1
> >
> > Mon Oct 11 09:36:42 2004
> >
> > OS = Windows 2000
> > Executable: dllhost.exe
> > PID = 3532
> >
> > Note: Thread times are formatted as HH:MM:SS.ms
> >
> > ***********************
> >
> >
> >
> >
> > Thread ID: 0
> > System Thread ID: 23c
> > Kernel Time: 0:0:0.0
> > User Time: 0:37:43.984
> >
> > IISState has detected that this thread has thrown an unhandled exception
> > and is about to crash. IISState will now attempt to display the original
> > faulting stack.
> >
> >
> > .cxr 2954fad4
> > *** ERROR: Symbol file could not be found. Defaulted to export symbols
> > for
> > C:\WINNT\system32\CWBUNPLA.dll -
> > # ChildEBP RetAddr
> > 00 2954fdf8 78007108 KERNEL32!RaiseException+0x56
> > 01 2954fe38 6c3adb0c MSVCRT!_CxxThrowException+0x34
> > 02 2954fe4c 6c3e1801 MFC42!AfxThrowNotSupportedException
> > 03 2954fe64 6c3e19e7 MFC42!CThreadSlotData::SetValue+0xa7
> > 04 2954fe78 6c3e0f39 MFC42!CThreadLocalObject::GetData+0x70
> > 05 2954fe84 64bc3dbb MFC42!AFX_MAINTAIN_STATE2::AFX_MAINTAIN_STATE2+0x12
> > WARNING: Stack unwind information not available. Following frames may be
> > wrong.
> > 06 2954fe9c 64bc3feb CWBUNPLA!Ordinal47+0x7ab
> > 07 2954febc 77f830e7 CWBUNPLA!Ordinal72+0x167
> > 08 2954fedc 77f837f5 ntdll!LdrpCallInitRoutine+0x14
> > 09 2954ff30 7c5745e7 ntdll!LdrShutdownThread+0xa3
> > 0a 2954ff98 7c57407b KERNEL32!ExitThread+0x53
> > 0b 2954ffa0 77ab5060 KERNEL32!FreeLibraryAndExitThread+0x24
> > 0c 2954ffb4 7c57438b ole32!CRpcThreadCache::RpcWorkerThreadEntry+0x34
> > 0d 2954ffec 00000000 KERNEL32!BaseThreadStart+0x52
> >
> >
> > **Current Stack State**
> >
> > Thread Type: Other
> > # ChildEBP RetAddr
> > 00 2954f4a0 69b3c4c8 msxml4!Runtime_exit+0x37
> > 01 2954f4a4 69b3c2cb msxml4!DllMain+0x3b
> > 02 2954f4c4 77f830e7 msxml4!_DllMainCRTStartup+0x50
> > 03 2954f4e4 77f8ee02 ntdll!LdrpCallInitRoutine+0x14
> > 04 2954f54c 7c580ed2 ntdll!LdrShutdownProcess+0x11d
> > 05 2954f610 7c004429 KERNEL32!ExitProcess+0x51
> > 06 2954f618 7c00440a MSVCR70!__crtExitProcess+0x2e
> > 07 2954f624 7c00f791 MSVCR70!_cinit+0x101
> > 08 2954f634 7c012ac8 MSVCR70!_exit+0xe
> > 09 2954f67c 7c012799 MSVCR70!raise+0xae
> > 0a 2954f6b0 7c020dd0 MSVCR70!abort+0xe
> > 0b 2954f6b8 7c58aa90 MSVCR70!__CxxUnhandledExceptionFilter+0x23
> > 0c 2954f9c0 7c571587 KERNEL32!UnhandledExceptionFilter+0x86
> > 0d 2954ffec 00000000 KERNEL32!BaseThreadStart+0x65
> >
> >
> > *****SUMMARY*****
> >
> >
> > Closing open log file D:\Program Files\IIS
State\output\IISState-3532.log
> >
> >
>
>

Relevant Pages

  • Re: IIS State Log Analysis Needed: dllhost.exe large memory usage
    ... C0000017 is Out Of Memory (this refers to the 2GB Virtual Memory map, ... The crash is most likely the ... > Below is an IISSTATE log run shortly after confirming that dialog box this ... Stack unwind information not available. ...
    (microsoft.public.inetserver.iis)
  • Re: IISState Debug Help Needed
    ... that low memory is causing the problem. ... etc.) when IISState was run. ... > server stops serving asp pages, ...
    (microsoft.public.inetserver.iis)
  • Re: IIS State Log
    ... Other times the CPU was ... But I noticed that most of the memory is used and split between ... Do you think that a DLL required by asp.net got overwritten or got messed up ... >> the control panel got locked this morning I ran the IISState on the PID ...
    (microsoft.public.inetserver.iis)
  • Re: DLLHOST Memory Overload
    ... IISState just takes a snapshot of what is running at the moment you run it. ... It is not appropriate for tracking memory, it is appropriate for high CPU; ... Based on the number of ASP threads, I would say that you have a medium sized ... They show a large amount of threads, over 60, and a large amount of ...
    (microsoft.public.inetserver.iis)
  • Re: Time to fix my PC
    ... intermittently bad) is the power supply 'system'. ... Intermittent memory often passes all tests at room temperature. ... Responsible computer manufacturers provide comprehensive hardware ... such as the crash code or data from system logs in the OS ...
    (comp.os.linux.hardware)