Intermittenty w3wp.exe terminating and recorver by itself. This interupte user connection to applicaiton.

Question

I have a web application hosted in IIS. Intermittently my logon connect would fault causing user to re-logon again.  Sometime user has to re-logon a few times a day. Investigating the issue, it's cause with w3wp.exe terminating.   This happen intermittently and w3wp.exe would show it terminated a few times or 20 times a day.  Event log did how show any other activity leading up the the w3wp crashing. It's sporadic.  This is a dmp I am able to capture.   Can anyone explain what is this happening.  Some setting in IIS?   


KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1936

    Key  : Analysis.Elapsed.mSec
    Value: 3839

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 0

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 155

    Key  : Analysis.Init.Elapsed.mSec
    Value: 5313

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 167

    Key  : CLR.BuiltBy
    Value: NET472REL1LAST_B

    Key  : CLR.Engine
    Value: CLR

    Key  : CLR.NOSOS
    Value: 1

    Key  : CLR.Version
    Value: 4.7.4108.0

    Key  : Failure.Bucket
    Value: BREAKPOINT_NOSOS_80000003_wow64cpu.dll!CpupSyscallStub

    Key  : Failure.Hash
    Value: {5d009ffa-26a5-16a1-a09c-f0690f332ad6}

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 325394

    Key  : Timeline.Process.Start.DeltaSec
    Value: 114

    Key  : WER.OS.Branch
    Value: rs5_release

    Key  : WER.OS.Version
    Value: 10.0.17763.1

    Key  : WER.Process.Version
    Value: 10.0.17763.1


FILE_IN_CAB:  w3wp.DMP

NTGLOBALFLAG:  0

APPLICATION_VERIFIER_FLAGS:  0

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 0000000000000000
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 0

FAULTING_THREAD:  00001568

PROCESS_NAME:  w3wp.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE_STR:  80000003

ADDITIONAL_DEBUG_TEXT:  SOS.DLL is not loaded for managed code. Analysis might be incomplete

STACK_TEXT:  
00000000`0478ee18 00000000`771b1b1d     : 00000023`77231a9c 00007ffc`b7920023 00000000`04a607c0 00000000`047ce230 : wow64cpu!CpupSyscallStub+0xc
00000000`0478ee20 00000000`771b1199     : 00000000`047cf9d4 00007ffc`b66ed0c4 00000000`0478eef0 00007ffc`b66ec5e7 : wow64cpu!Thunk0ArgReloadState+0x5
00000000`0478eed0 00007ffc`b66ecfda     : 00000000`049ba000 00000000`003200e8 00000000`00000000 00000000`0478f760 : wow64cpu!BTCpuSimulate+0x9
00000000`0478ef10 00007ffc`b66ecea0     : 00000000`00000000 00000000`04be2398 00000000`00000000 00000000`00000000 : wow64!RunCpuSimulation+0xa
00000000`0478ef40 00007ffc`b79a5428     : 00000000`00000010 00000000`00000010 00007ffc`b79efd50 00007ffc`b79efe60 : wow64!Wow64LdrpInitialize+0x120
00000000`0478f1f0 00007ffc`b794887b     : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : ntdll!LdrpInitializeProcess+0x17a4
00000000`0478f640 00007ffc`b7948703     : 00000000`00000000 00007ffc`b78d0000 00000000`00000000 00000000`049bb000 : ntdll!LdrpInitialize+0x15f
00000000`0478f6e0 00007ffc`b79486ae     : 00000000`0478f760 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrpInitialize+0x3b
00000000`0478f710 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe


STACK_COMMAND:  ~0s; .ecxr ; kb

SYMBOL_NAME:  wow64cpu!CpupSyscallStub+c

MODULE_NAME: wow64cpu

IMAGE_NAME:  wow64cpu.dll

FAILURE_BUCKET_ID:  BREAKPOINT_NOSOS_80000003_wow64cpu.dll!CpupSyscallStub

OS_VERSION:  10.0.17763.1

BUILDLAB_STR:  rs5_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

IMAGE_VERSION:  10.0.17763.1

FAILURE_ID_HASH:  {5d009ffa-26a5-16a1-a09c-f0690f332ad6}

Followup:     MachineOwner
---------

Answer

@DukeNN1

There are many reasons for this issue, below are some troubleshooting steps you can use as a reference:

Check Application Pool Settings:
- Ensure that the application pool recycling settings are not too aggressive. Look for conditions like "Idle timeout," "Memory limits," or "Periodic restart."
Enable Memory Dumps for Crashes:
- Set up IIS to generate more detailed memory dumps on crashes. This will help further diagnose issues, especially in managed code.
Analyze .NET Code:
- Since SOS.dll was not loaded, this indicates managed code may be involved. Use debugging tools like WinDbg with SOS.dll loaded to investigate further.
Check 32-bit Compatibility:
- If your web application is running as 32-bit on a 64-bit system, consider testing it in 64-bit mode if possible, or ensure there are no compatibility issues with Wow64.
Update Windows and IIS:
- Ensure your Windows Server and IIS are fully updated, including all relevant patches for .NET Framework.
Review Event Logs:
- Look for any preceding warnings or errors in the Event Viewer that could provide more context leading up to the crash.

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Share via

Intermittenty w3wp.exe terminating and recorver by itself. This interupte user connection to applicaiton.

1 answer

Your answer