w3wp.exe crashing issue - Inetserver

This is a discussion on w3wp.exe crashing issue - Inetserver ; Our server has been experiencing AppPool crashes. These occur frequently. In the system event log we see the following: Faulting application w3wp.exe, version 6.0.3790.1830, faulting module jvm. dll, version 0.0.0.0, fault address 0x0007b392. The application starts functioning again once we ...

+ Reply to Thread
Results 1 to 3 of 3

w3wp.exe crashing issue

  1. Default w3wp.exe crashing issue

    Our server has been experiencing AppPool crashes. These occur frequently.

    In the system event log we see the following:
    Faulting application w3wp.exe, version 6.0.3790.1830, faulting module jvm.
    dll, version 0.0.0.0, fault address 0x0007b392.

    The application starts functioning again once we recycle the appPool.

    I have also gone through David Wang's blog here http://blogs.msdn.com/david.
    wang/archive/2005/08/29/HOWTO_Understand_and_Diagnose_an_AppPool_Crash.aspx.


    I have installed DebugDiag and waited until the problem happened again. It
    gave out dumps and I have used the DebugDiag advanced ****ysis tool which
    gave me the below output.
    Looking at it, it seems msxml4.dll is causing the failure. But I still am
    not sure what could be reason. I have pasted below portion of the log.

    Any help is much appreciated.

    Error In w3wp__PID__64256__Date__05_24_2007__Time_09_52_43AM__796__First
    chance exception 0XE0000001.dmp the assembly instruction at kernel32!
    RaiseException+3c in C:\WINDOWS\system32\kernel32.dll from Microsoft
    Corporation has caused an unknown exception (0xe0000001) on thread 109

    This exception originated from msxml4!DllUnregisterServer+1db7. Review the
    faulting call stack for thread 109 to determine root cause for the exception.


    Please follow up with vendor Microsoft Corporation for problem resolution
    concerning the following file: C:\WINDOWS\system32\msxml4.dll.


    -----------------

    Warning The following threads in
    w3wp__PID__64256__Date__05_24_2007__Time_09_52_40AM__593__First chance
    exception 0XE0000001.dmp are making a network call using WinHTTP library.
    The call to WinHTTP originated from kernel32!GetModuleFileNameA+eb

    ( 54 )

    0.75% of threads blocked

    Using WinHTTP in server-side applications is the recommended alternative to
    using Wininet. If you are experiencing slow response time from IIS, the
    problem could be due to WinHTTP calling a remote server which is slow to
    respond, therefore, you may want to verify network latency of the applicable
    remote machine is at a minimum.

    Please follow up with vendor Microsoft Corporation for problem resolution
    concerning the following file: C:\WINDOWS\system32\kernel32.dll.


    -----------------

    Thread 109 - System ID 39356
    Entry point msvcrt!endthreadex+2f
    Create time 5/24/2007 9:52:23 AM
    Time spent in user mode 0 Days 00:00:00.046
    Time spent in kernel mode 0 Days 00:00:00.015

    This thread is not fully resolved and may or may not be a problem. Further
    ****ysis of these threads may be required.

    Function Source
    kernel32!RaiseException+3c
    msxml4!DllUnregisterServer+1db7
    msxml4!DllRegisterServer+c453
    msxml4!DllGetClassObject+237b
    msxml4!DllUnregisterServer+1658f
    msxml4!DllUnregisterServer+9be
    msxml4!DllUnregisterServer+a85
    msxml4!DllUnregisterServer+16b0e
    msxml4!DllUnregisterServer+131
    msxml4!DllUnregisterServer+1495f
    vbscript+9e6e
    vbscript+6f00
    vbscript+6e72
    vbscript+6b85
    vbscript+7bb6
    vbscript+8fbd
    vbscript+4940
    vbscript+4cd2
    vbscript!DllGetClassObject+2f26
    vbscript+9e6e
    vbscript+6f00
    vbscript+6e72
    vbscript+6b85
    vbscript+7bb6
    vbscript+8fbd
    vbscript+4940
    vbscript+4cd2
    vbscript!DllGetClassObject+2f26
    vbscript+9e6e
    vbscript+6f00
    vbscript+6e72
    vbscript+6b85
    vbscript+7bb6
    vbscript+8fbd
    vbscript+4940
    vbscript+4cd2
    vbscript+5522
    vbscript+189b
    asp+2f5a
    asp+2f1a
    asp+2e50
    asp+2d54
    asp+2c7f
    asp+2a4d
    asp+271a
    comsvcs!CoCreateActivity+4f57
    ole32!CoQueryAuthenticationServices+2afb
    ole32!CoQueryAuthenticationServices+3548
    ole32!CoQueryAuthenticationServices+3a52
    ole32!GetHGlobalFromStream+46a
    ole32!CoCreateObjectInContext+fb4
    comsvcs!CoCreateActivity+52fb
    comsvcs!CoCreateActivity+5657
    comsvcs!CoCreateActivity+5ff0
    comsvcs!CoCreateActivity+643c
    msvcrt!endthreadex+a3
    kernel32!GetModuleFileNameA+eb


    --------------------

    Thread 54 - System ID 131396
    Entry point winhttp!WinHttpReceiveResponse+b641
    Create time 5/24/2007 9:49:13 AM
    Time spent in user mode 0 Days 00:00:00.00
    Time spent in kernel mode 0 Days 00:00:00.015


    This thread is making a network call using WinHTTP library. The call to
    WinHTTP originated from kernel32!GetModuleFileNameA+eb

    Function Source
    ntdll!KiFastSystemCallRet
    kernel32!Sleep+f
    winhttp!WinHttpReceiveResponse+b654
    kernel32!GetModuleFileNameA+eb

  2. Default Re: w3wp.exe crashing issue

    Your current issue (below) is not really related to your original
    issue with the Java Virtual Machine that you are using server-side.

    Symbols were not available at time of stack trace so we don't know why
    MSXML4 is raising an exception, but it's not the crash (0xC0000005)
    that you were looking for.

    Unfortunately, none of this is really actionable towards resolving the
    code that is crashing in your IIS6 w3wp.exe. You don't have symbols
    for the failing issue, and you did not reproduce your original issue
    of interest. Debugging tends to take patience.


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





    On May 23, 8:56 pm, "Rocky"<R...@Nospam.com> wrote:
    > Our server has been experiencing AppPool crashes. These occur frequently.
    >
    > In the system event log we see the following:
    > Faulting application w3wp.exe, version 6.0.3790.1830, faulting module jvm.
    > dll, version 0.0.0.0, fault address 0x0007b392.
    >
    > The application starts functioning again once we recycle the appPool.
    >
    > I have also gone through David Wang's blog herehttp://blogs.msdn.com/david.
    > wang/archive/2005/08/29/HOWTO_Understand_and_Diagnose_an_AppPool_Crash.aspx.
    >
    > I have installed DebugDiag and waited until the problem happened again. It
    > gave out dumps and I have used the DebugDiag advanced ****ysis tool which
    > gave me the below output.
    > Looking at it, it seems msxml4.dll is causing the failure. But I still am
    > not sure what could be reason. I have pasted below portion of the log.
    >
    > Any help is much appreciated.
    >
    > Error In w3wp__PID__64256__Date__05_24_2007__Time_09_52_43AM__796__First
    > chance exception 0XE0000001.dmp the assembly instruction at kernel32!
    > RaiseException+3c in C:\WINDOWS\system32\kernel32.dll from Microsoft
    > Corporation has caused an unknown exception (0xe0000001) on thread 109
    >
    > This exception originated from msxml4!DllUnregisterServer+1db7. Review the
    > faulting call stack for thread 109 to determine root cause for the exception.
    >
    > Please follow up with vendor Microsoft Corporation for problem resolution
    > concerning the following file: C:\WINDOWS\system32\msxml4.dll.
    >
    > -----------------
    >
    > Warning The following threads in
    > w3wp__PID__64256__Date__05_24_2007__Time_09_52_40AM__593__First chance
    > exception 0XE0000001.dmp are making a network call using WinHTTP library.
    > The call to WinHTTP originated from kernel32!GetModuleFileNameA+eb
    >
    > ( 54 )
    >
    > 0.75% of threads blocked
    >
    > Using WinHTTP in server-side applications is the recommended alternativeto
    > using Wininet. If you are experiencing slow response time from IIS, the
    > problem could be due to WinHTTP calling a remote server which is slow to
    > respond, therefore, you may want to verify network latency of the applicable
    > remote machine is at a minimum.
    >
    > Please follow up with vendor Microsoft Corporation for problem resolution
    > concerning the following file: C:\WINDOWS\system32\kernel32.dll.
    >
    > -----------------
    >
    > Thread 109 - System ID 39356
    > Entry point msvcrt!endthreadex+2f
    > Create time 5/24/2007 9:52:23 AM
    > Time spent in user mode 0 Days 00:00:00.046
    > Time spent in kernel mode 0 Days 00:00:00.015
    >
    > This thread is not fully resolved and may or may not be a problem. Further
    > ****ysis of these threads may be required.
    >
    > Function Source
    > kernel32!RaiseException+3c
    > msxml4!DllUnregisterServer+1db7
    > msxml4!DllRegisterServer+c453
    > msxml4!DllGetClassObject+237b
    > msxml4!DllUnregisterServer+1658f
    > msxml4!DllUnregisterServer+9be
    > msxml4!DllUnregisterServer+a85
    > msxml4!DllUnregisterServer+16b0e
    > msxml4!DllUnregisterServer+131
    > msxml4!DllUnregisterServer+1495f
    > vbscript+9e6e
    > vbscript+6f00
    > vbscript+6e72
    > vbscript+6b85
    > vbscript+7bb6
    > vbscript+8fbd
    > vbscript+4940
    > vbscript+4cd2
    > vbscript!DllGetClassObject+2f26
    > vbscript+9e6e
    > vbscript+6f00
    > vbscript+6e72
    > vbscript+6b85
    > vbscript+7bb6
    > vbscript+8fbd
    > vbscript+4940
    > vbscript+4cd2
    > vbscript!DllGetClassObject+2f26
    > vbscript+9e6e
    > vbscript+6f00
    > vbscript+6e72
    > vbscript+6b85
    > vbscript+7bb6
    > vbscript+8fbd
    > vbscript+4940
    > vbscript+4cd2
    > vbscript+5522
    > vbscript+189b
    > asp+2f5a
    > asp+2f1a
    > asp+2e50
    > asp+2d54
    > asp+2c7f
    > asp+2a4d
    > asp+271a
    > comsvcs!CoCreateActivity+4f57
    > ole32!CoQueryAuthenticationServices+2afb
    > ole32!CoQueryAuthenticationServices+3548
    > ole32!CoQueryAuthenticationServices+3a52
    > ole32!GetHGlobalFromStream+46a
    > ole32!CoCreateObjectInContext+fb4
    > comsvcs!CoCreateActivity+52fb
    > comsvcs!CoCreateActivity+5657
    > comsvcs!CoCreateActivity+5ff0
    > comsvcs!CoCreateActivity+643c
    > msvcrt!endthreadex+a3
    > kernel32!GetModuleFileNameA+eb
    >
    > --------------------
    >
    > Thread 54 - System ID 131396
    > Entry point winhttp!WinHttpReceiveResponse+b641
    > Create time 5/24/2007 9:49:13 AM
    > Time spent in user mode 0 Days 00:00:00.00
    > Time spent in kernel mode 0 Days 00:00:00.015
    >
    > This thread is making a network call using WinHTTP library. The call to
    > WinHTTP originated from kernel32!GetModuleFileNameA+eb
    >
    > Function Source
    > ntdll!KiFastSystemCallRet
    > kernel32!Sleep+f
    > winhttp!WinHttpReceiveResponse+b654
    > kernel32!GetModuleFileNameA+eb




  3. Default Re: w3wp.exe crashing issue

    Thanks for the response David. I am downloading the symbols right now
    from here--> http://msdl.microsoft.com/download/
    As you mentioned symbols should be present at the time of stack
    trace. So I guess I have to install it and then wait for these
    problems to happen again.



+ Reply to Thread

Similar Threads

  1. w3wp.exe exception
    By Application Development in forum Inetserver
    Replies: 10
    Last Post: 10-02-2007, 01:37 AM
  2. w3wp.exe error
    By Application Development in forum Sharepoint
    Replies: 1
    Last Post: 08-21-2007, 01:14 PM
  3. w3wp.exe CPU Utilization
    By Application Development in forum Inetserver
    Replies: 3
    Last Post: 08-20-2007, 07:41 AM
  4. Win 2003 x64 asp 3.0 w3wp.exe
    By Application Development in forum Inetserver
    Replies: 1
    Last Post: 05-22-2007, 11:49 AM
  5. After Effects 7 crashing, crashing AND crashing....
    By Application Development in forum Adobe After Effects
    Replies: 7
    Last Post: 11-05-2006, 02:10 PM