none
CLR exception - code e0434352 RRS feed

  • Question

  • w3wp.exe process has been crashing with the same stack trace almost every day.

    I tried to analyze the dump file but I could not find the root cause of the problem.

    Can someone help me in this problem analysis?

    This dump file has an exception of interest stored in it.
    The stored exception information can be accessed via .ecxr.
    (3fa4.36b8): CLR exception - code e0434352 (first/second chance not available)
    eax=00000000 ebx=03fee998 ecx=00000000 edx=00000000 esi=00000002 edi=00000000
    eip=77c4015d esp=03fee948 ebp=03fee9e4 iopl=0         nv up ei pl zr na pe nc
    cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000246
    ntdll!NtWaitForMultipleObjects+0x15:
    77c4015d 83c404          add     esp,4

    STACK_TEXT:  
    03fef0d0 7043ac08 e0434352 00000001 00000005 KERNELBASE!RaiseException+0x58
    03fef160 7043ae41 1922f26c 00000000 00000000 clr!RaiseTheExceptionInternalOnly+0x276
    03fef220 0308fc39 00000000 14398e24 14398e78 clr!IL_Throw+0x14c
    WARNING: Frame IP not in any known module. Following frames may be wrong.
    03fef260 70464b01 03fef2ac 7043cc44 03fef478 0x308fc39
    03fef2bc 704649c7 143993b4 094d0b0d 00000000 clr!MethodTable::SetObjCreateDelegate+0xbd
    03fef2e8 70464a56 143993b4 143993b4 00000000 clr!MethodTable::CallFinalizer+0xca
    03fef300 7045f124 143993b4 f369ad68 03fef370 clr!SVR::CallFinalizer+0xa7
    03fef350 7045efe3 02686f90 0000041f 03fef37f clr!SVR::CallFinalizer+0x169
    03fef380 7053cc91 02686f90 00000000 03fef7a0 clr!SVR::CallFinalizer+0x345
    03fef394 70465c05 03fef60c 03fef478 02686f90 clr!SVR::ProfScanRootsHelper+0x7b
    03fef3a8 70465c87 03fef7a0 f369aa60 03fef7a0 clr!Thread::DoExtraWorkForFinalizer+0x114
    03fef458 70465d42 03fef7a0 f369aa80 02686f90 clr!Thread::ShouldChangeAbortToUnload+0x101
    03fef4b8 704537a2 026b6cc0 03fef59c 706b6cb6 clr!Thread::ShouldChangeAbortToUnload+0x399
    03fef4c4 706b6cb6 03fef7a0 f369aba4 02686f90 clr!Thread::RaiseCrossContextException+0x3f8
    03fef59c 7053cca8 026d5a60 7045378b 03fef7a0 clr!Thread::DoADCallBack+0x33a
    03fef5c0 7053cbda 03fef7a0 03fef628 7053cc44 clr!Thread::DoExtraWorkForFinalizer+0x10c
    03fef5cc 7053cc44 026d5a60 7053cc76 03fef60c clr!ManagedThreadBase::FinalizerAppDomain+0x27
    03fef628 7045efe3 02686f90 00000000 03fef657 clr!SVR::CallFinalizer+0x213
    03fef658 7045f2d0 02686f90 00000000 02686f90 clr!SVR::CallFinalizer+0x345
    03fef674 70465c05 00000001 03fef758 02686f90 clr!SVR::GCHeap::FinalizerThreadWorker+0xcd
    03fef688 70465c87 03fef7a0 f369a900 03fef7a0 clr!Thread::DoExtraWorkForFinalizer+0x114
    03fef738 70465d42 03fef7a0 f369a9a0 00000000 clr!Thread::ShouldChangeAbortToUnload+0x101
    03fef798 704578be 00000000 026d5a60 00000000 clr!Thread::ShouldChangeAbortToUnload+0x399
    03fef7bc 704578d1 7045f226 00000008 03fef804 clr!ManagedThreadBase_NoADTransition+0x35
    03fef7cc 7054da7b 7045f226 f369a63c 00000000 clr!ManagedThreadBase::FinalizerBase+0xf
    03fef804 70465a08 00000000 00000000 00000000 clr!SVR::GCHeap::FinalizerThreadStart+0x10c
    03fef8a0 76ef338a 00f9ee48 03fef8ec 77c59f72 clr!Thread::intermediateThreadProc+0x4b
    03fef8ac 77c59f72 00f9ee48 3b6fdc01 00000000 kernel32!BaseThreadInitThunk+0xe
    03fef8ec 77c59f45 704659c0 00f9ee48 ffffffff ntdll!__RtlUserThreadStart+0x70
    03fef904 00000000 704659c0 00f9ee48 00000000 ntdll!_RtlUserThreadStart+0x1b


    FOLLOWUP_IP: 
    clr!MethodTable::SetObjCreateDelegate+bd
    70464b01 897de0          mov     dword ptr [ebp-20h],edi

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  clr!MethodTable::SetObjCreateDelegate+bd

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: clr

    IMAGE_NAME:  clr.dll

    Friday, February 20, 2015 3:51 PM

Answers

  • I don't see anything useful in the KB on crashes in SetObjCreateDelegate. Of course you've got numerous non-public functions above that in the stack. It's either a problem with the object reference passed into the function, or maybe a bug in the CLR.

    First, make sure you have the latest version of the runtime possible, i.e. the latest SP/hotfix build for whatever version you're using so you pick up all bug fixes possible.

    Second is to create a support case on this. We'll need the dump for analysis and that's beyond the scope of what we can do in the forums.

    Saturday, February 21, 2015 1:44 AM

All replies

  • I don't see anything useful in the KB on crashes in SetObjCreateDelegate. Of course you've got numerous non-public functions above that in the stack. It's either a problem with the object reference passed into the function, or maybe a bug in the CLR.

    First, make sure you have the latest version of the runtime possible, i.e. the latest SP/hotfix build for whatever version you're using so you pick up all bug fixes possible.

    Second is to create a support case on this. We'll need the dump for analysis and that's beyond the scope of what we can do in the forums.

    Saturday, February 21, 2015 1:44 AM
  • What was the exception type and its message? You could try to run !dso on the finalizer thread which crashed to find the offending object. Are in one of your finalizers delegates used which were already collected by the garbage collector?

    Sunday, March 1, 2015 7:06 PM