IIS APP Crash, debug crash dump

Anonymous
2024-06-28T08:21:51+00:00

Hello,

I have an a ASP .net 3 web site and i have many crash of my app pool.

I have dump the crash and use diag tool analysis but i don't understand the crash cause.

I have desactivate this setting to avoid crash.

This is my event log before crash

Could you help me ?

Windows for business Windows Server Performance Application technologies and compatibility

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-06-28T12:14:20+00:00

    Hello

    Thank you for posting in Microsoft Community forum.

    Since it is an APP crash, you can try to collect a user mode dump and send the result of the WinDbg tool analysis <!analyze -v> here for analysis.

    User-mode Dump Files - Windows drivers | Microsoft Learn

    !analyze (WinDbg) - Windows drivers | Microsoft Learn

    Best Regards,

    Wesley Li

    0 comments No comments
  2. Anonymous
    2024-07-01T08:09:28+00:00

    Hello,

    My 2 first capture come from DebugDiag Tool 3.2 analyzer

    This is result of the NTDLL ZW terminate process file dump:

    0:000> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************
    
    *** WARNING: Check Image - Checksum mismatch - Dump: 0x206cd2, File: 0x208012 - C:\symbols\ntdll.dll\86A81BE0203000\ntdll.dll
    WARNING: Teb 6 pointer is NULL - defaulting to 00000000`7ffde000
    WARNING: 00000000`7ffde000 does not appear to be a TEB
    WARNING: Teb 6 pointer is NULL - defaulting to 00000000`7ffde000
    WARNING: 00000000`7ffde000 does not appear to be a TEB
    WARNING: Teb 6 pointer is NULL - defaulting to 00000000`7ffde000
    WARNING: 00000000`7ffde000 does not appear to be a TEB
    WARNING: Teb 6 pointer is NULL - defaulting to 00000000`7ffde000
    WARNING: 00000000`7ffde000 does not appear to be a TEB
    WARNING: Teb 6 pointer is NULL - defaulting to 00000000`7ffde000
    WARNING: 00000000`7ffde000 does not appear to be a TEB
    WARNING: Teb 6 pointer is NULL - defaulting to 00000000`7ffde000
    WARNING: 00000000`7ffde000 does not appear to be a TEB
    WARNING: Teb 6 pointer is NULL - defaulting to 00000000`7ffde000
    WARNING: 00000000`7ffde000 does not appear to be a TEB
    
    KEY_VALUES_STRING: 1
    
        Key  : Analysis.CPU.mSec
        Value: 1530
    
        Key  : Analysis.Elapsed.mSec
        Value: 1527
    
        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: 218
    
        Key  : Analysis.Init.Elapsed.mSec
        Value: 2514
    
        Key  : Analysis.Memory.CommitPeak.Mb
        Value: 126
    
        Key  : Failure.Bucket
        Value: BREAKPOINT_80000003_dllhost.exe!wWinMain
    
        Key  : Failure.Hash
        Value: {71bdd4d4-4970-a0a6-797b-9227260d0826}
    
        Key  : Timeline.OS.Boot.DeltaSec
        Value: 153790
    
        Key  : Timeline.Process.Start.DeltaSec
        Value: 7
    
        Key  : WER.OS.Branch
        Value: fe_release
    
        Key  : WER.OS.Version
        Value: 10.0.20348.1
    
        Key  : WER.Process.Version
        Value: 6.2.20348.1
    
    FILE_IN_CAB:  DllHost__PID__1944__Date__06_28_2024__Time_09_35_56AM__804__Ntdll!ZwTerminateProcess.dmp
    
    COMMENT:  Dump created by DbgHost. Ntdll!ZwTerminateProcess
    
    NTGLOBALFLAG:  0
    
    APPLICATION_VERIFIER_FLAGS:  0
    
    CONTEXT:  (.ecxr)
    rax=0000000000000000 rbx=ffffffffffffffff rcx=ffffffffffffffff
    rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
    rip=00007ff86d060740 rsp=0000002c57d5f708 rbp=0000000000000000
     r8=0000000000000000  r9=0000002c57d5f0e0 r10=000000000000009e
    r11=0000002c57d5f6e0 r12=0000000000000000 r13=0000000000000000
    r14=0000000000000000 r15=0000000000000000
    iopl=0         nv up ei pl zr na po nc
    cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000244
    ntdll!NtTerminateProcess:
    00007ff8`6d060740 4c8bd1          mov     r10,rcx
    Resetting default scope
    
    EXCEPTION_RECORD:  (.exr -1)
    ExceptionAddress: 00007ff86d063d80 (ntdll!DbgBreakPoint)
       ExceptionCode: 80000003 (Break instruction exception)
      ExceptionFlags: 00007ff8
    NumberParameters: 1
       Parameter[0]: 0000000000000000
    PROCESS_NAME:  dllhost.exe
    ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Point d arr t  Un point d arr t a  t  atteint.
    EXCEPTION_CODE_STR:  80000003
    EXCEPTION_PARAMETER1:  0000000000000000
    STACK_TEXT:  
    0000002c`57d5f708 00007ff8`6a6ef9a0     : 00000000`00000000 00000000`00000000 ffffffff`ffffffff 00000000`00000000 : ntdll!NtTerminateProcess
    0000002c`57d5f710 00007ff7`2bad1193     : 00000000`00000076 00000000`00000000 00000000`00000000 00000000`00009000 : KERNELBASE!TerminateProcess+0x30
    0000002c`57d5f740 00007ff7`2bad1450     : 00000000`0000000a 00007ff7`2bad14d9 00000000`00000000 00000000`00000000 : dllhost!wWinMain+0x18b
    0000002c`57d5fa00 00007ff8`6bd54cb0     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : dllhost!__scrt_common_main_seh+0x110
    0000002c`57d5fa40 00007ff8`6d03eceb     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x10
    0000002c`57d5fa70 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x2b
    
    SYMBOL_NAME:  dllhost!wWinMain+18b
    MODULE_NAME: dllhost
    IMAGE_NAME:  dllhost.exe
    STACK_COMMAND:  dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s; .ecxr ; kb
    FAILURE_BUCKET_ID:  BREAKPOINT_80000003_dllhost.exe!wWinMain
    OS_VERSION:  10.0.20348.1
    BUILDLAB_STR:  fe_release
    OSPLATFORM_TYPE:  x64
    OSNAME:  Windows 10
    IMAGE_VERSION:  6.2.20348.1
    FAILURE_ID_HASH:  {71bdd4d4-4970-a0a6-797b-9227260d0826}
    
    0 comments No comments
  3. Anonymous
    2024-07-10T08:08:25+00:00

    The error code 0x80000003 indicates a breakpoint exception, which usually means that there is an intentional stop or an unexpected issue in the code. The dllhost.exe is related to the COM Surrogate process, which is used to run COM objects in isolation from the original process that requested it, often for stability purposes.

    Use DebugDiag 2 Collection to set up crash rules for your application pool. This tool can help you capture detailed information about the crash, including the state of the process when it crashed.

    Troubleshoot application pool crashes on Cloud Services - Azure | Microsoft Learn

    Check for any known issues with the .NET Core Hosting Bundle if you're using it, as a corrupted installation can cause startup problems.

    Troubleshoot ASP.NET Core on Azure App Service and IIS | Microsoft Learn

    0 comments No comments