none
KERNELBASE - UnhandledException is NOT terminating the exception RRS feed

  • Question

  • IN my application there is unhandled exception from threadpoll thread as shown below in memorey dump. But it's not causing application to terminate. What could be the reason? Any help is very much appreciated.


      31  Id: 2124.364c Suspend: 1 Teb: 00007ff5`ff43e000 Unfrozen
    RetAddr           : Args to Child                                                           : Call Site
    00007ffc`695513ed : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!ZwWaitForMultipleObjects+0xa
    00007ffc`69f67d51 : 00000000`00000002 00007ff5`ff657000 00000095`00000000 00000000`d000022d : KERNELBASE!WaitForMultipleObjectsEx+0xe1 [d:\blue\minkernel\kernelbase\synch.c @ 1471]
    00007ffc`69f67773 : 00000000`00000000 00000000`00000001 00000095`b7e5d270 ffffffff`ffffffff : kernel32!WerpReportFaultInternal+0x581 [d:\9147\windows\feedback\faultrep\faultrep.cpp @ 948]
    00007ffc`69631fdf : 00000000`00000000 00000000`00000001 00000000`00000000 00007ffc`00000000 : kernel32!WerpReportFault+0x83 [d:\9147\windows\feedback\faultrep\faultrep.cpp @ 1205]
    00007ffc`6c3ff133 : 00000000`00000000 00007ffc`69631da0 00000000`00000000 00000095`b7e5f000 : KERNELBASE!UnhandledExceptionFilter+0x23f [d:\blue\minkernel\kernelbase\xcpt.c @ 609]
    00007ffc`6c3e1d86 : 00007ffc`62a0c0a8 00000000`00000000 00000095`b7e5db80 00007ffc`6289954f : ntdll!memset+0xaaf3
    00007ffc`6c3f33fd : 00000000`00000000 00000095`b7e5d3e0 00000095`b7e5e190 00000095`b7e5e190 : ntdll!_C_specific_handler+0x96
    00007ffc`6c3b4847 : 00000000`00000001 00007ffc`6c360000 00000000`00000000 00007ffc`6c49409c : ntdll!_chkstk+0x9d
    00007ffc`6c3b3a6d : 00007ffc`03f752e0 00000000`00000000 00000095`b7e5e190 00007ffc`00000000 : ntdll!RtlRaiseException+0xf67
    00007ffc`69558a5c : 00000000`00000000 00000000`00000001 00000095`b7e5e2e8 00000000`00000005 : ntdll!RtlRaiseException+0x18d
    00007ffc`62b55294 : 00000000`00000001 00000095`b7e5e218 00000091`f91909a0 00000000`00000000 : KERNELBASE!RaiseException+0x68 [d:\blue\minkernel\kernelbase\xcpt.c @ 828]
    00007ffc`62b5508e : 00000092`efcebaf8 00000000`00000001 00000000`00000000 00000093`ef98dbb8 : clr!RaiseTheExceptionInternalOnly+0x2fe [f:\dd\ndp\clr\src\vm\excep.cpp @ 3134]
    00007ffc`03f746d1 : 00000091`f9190a78 00000091`f91909a0 00000095`b7e5e330 00000000`00000001 : clr!IL_Throw+0x11b [f:\dd\ndp\clr\src\vm\jithelpers.cpp @ 5017]
    00007ffc`03f72d04 : 00000091`f914c138 00000091`f914c570 00000000`0000012c 00000091`f914c5c6 : AzureCommonLibrary!MS.Msn.Messenger.AzureCommonLibrary.AzureEncryptionKeys.Initialize(System.String, Int32)+0x351
    00007ffc`03cbcd0b : 00000000`00001518 00000000`00000bb8 00000093`7679e480 00000000`000493e0 : NTPS!MS.Msn.Messenger.PresenceService.PSMain.LoadAzureConfiguration()+0x164
    00007ffc`03cb7e03 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`07ffffff : NTPS!MS.Msn.Messenger.PresenceService.PSMain.OnServerParametersChanged(System.Object, System.EventArgs)+0x29b
    00007ffc`03cb7619 : 00000091`6f9828e0 88d43af7`5b96e9e9 00000000`00000002 00000000`00000000 : NTPS!MS.Msn.Messenger.PresenceService.PresenceServiceProxy.Start()+0x7c3
    00007ffc`03cb75e9 : 00000091`6f9828e0 88d43af7`5b96e9e9 00000000`00000002 00000000`00000000 : NTPS!MS.Msn.Messenger.PresenceService.PresenceServiceApplication.OnComingUp()+0x9
    00007ffc`039dd5d4 : 00000092`f6b73d30 00000092`f6b73ff8 00000092`f6b73fb8 00000000`00000000 : NTPS!MS.Msn.Messenger.PresenceService.StartupSequence+<>c__DisplayClass9.<Start>b__2()+0x139
    00007ffc`615939a5 : 00000091`ef9a9238 00000000`00000000 00000000`00000000 ffffffff`fffffffe : NTPS!MS.Msn.Messenger.PresenceService.Sequencer.Tick()+0xa4
    00007ffc`61593719 : 0000cad4`ceb3ff2e 00007ffc`630d0008 00000095`b7e5f048 00007ffc`611e1830 : mscorlib_ni!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)+0x285 [f:\dd\ndp\clr\src\BCL\System\Threading\ExecutionContext.cs @ 581]
    00007ffc`6163be92 : 00000092`f6b753f0 00000095`b7e5e9d0 00000095`b7e5eaa0 00000095`bc30ae30 : mscorlib_ni!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)+0x9 [f:\dd\ndp\clr\src\BCL\System\Threading\ExecutionContext.cs @ 530]
    00007ffc`6163bc7e : 00000000`00000001 00000091`ef9a9280 00000395`52792e64 00000000`00000000 : mscorlib_ni!System.Threading.TimerQueueTimer.CallCallback()+0x172 [f:\dd\ndp\clr\src\BCL\System\Threading\Timer.cs @ 714]
    00007ffc`615f12e4 : 00000092`f6b753f0 00000000`00000000 00000001`177bc01e 00007ffc`032c2020 : mscorlib_ni!System.Threading.TimerQueueTimer.Fire()+0x10e [f:\dd\ndp\clr\src\BCL\System\Threading\Timer.cs @ 670]
    00007ffc`62a0a7f3 : 00000091`ef9a9280 00000000`00000000 ffffffff`fffffffe 00000000`00000000 : mscorlib_ni!System.Threading.TimerQueue.FireNextTimers()+0x224 [f:\dd\ndp\clr\src\BCL\System\Threading\Timer.cs @ 421]
    00007ffc`62a0a6de : 00000000`00000000 00000000`00000004 00000095`b7e5f008 00000095`b7e5ee38 : clr!CallDescrWorkerInternal+0x83 [f:\dd\ndp\clr\src\vm\amd64\CallDescrWorkerAMD64.asm @ 100]
    00007ffc`62a0ae76 : 00000000`00000000 00000000`00000004 00000095`b7e5f048 00000095`b7e5ee78 : clr!CallDescrWorkerWithHandler+0x4a [f:\dd\ndp\clr\src\vm\callhelpers.cpp @ 93]
    00007ffc`62ac9033 : 00000095`b7e5f0b0 00000000`00000001 00000095`b7e5f0b0 00007ffc`63111d88 : clr!MethodDescCallSite::CallTargetWorker+0x251 [f:\dd\ndp\clr\src\vm\callhelpers.cpp @ 600]
    00007ffc`62a0c121 : 00000004`00000000 00000000`00000000 ffffffff`fffffffe 00000095`bc30ae30 : clr!AppDomainTimerCallback_Worker+0x23 [f:\dd\ndp\clr\src\vm\comthreadpool.cpp @ 903]
    00007ffc`62a0c0a8 : 00000095`b7e5f0b0 00000095`b7e5f310 00000000`00000001 00007ffc`62a0b9da : clr!ManagedThreadBase_DispatchInner+0x2d [f:\dd\ndp\clr\src\vm\threads.cpp @ 18331]
    00007ffc`62a0c019 : 0000cad4`ceb3ff2e 00007ffc`630e02c8 ffffffff`ffffffff 00007ffc`6c39773a : clr!ManagedThreadBase_DispatchMiddle+0x6c [f:\dd\ndp\clr\src\vm\threads.cpp @ 18384]
    00007ffc`62a0c15f : ffffffff`ffffffff 00000095`bc30ae30 00000095`bc30ae30 00007ffc`62ac8f00 : clr!ManagedThreadBase_DispatchOuter+0x75 [f:\dd\ndp\clr\src\vm\threads.cpp @ 18639]
    00007ffc`62ac8fc1 : 00000000`00000000 ffffffff`f4143e00 00000000`00000048 00007ffc`00000001 : clr!ManagedThreadBase_FullTransitionWithAD+0x2f [f:\dd\ndp\clr\src\vm\threads.cpp @ 18703]
    00007ffc`62ac8f35 : 00000095`bab1d3f0 00000095`bab1d3f0 00000095`b7e5f308 00007ffc`62ac8c31 : clr!AppDomainTimerCallback+0x66 [f:\dd\ndp\clr\src\vm\comthreadpool.cpp @ 936]
    00007ffc`62ac8b42 : 00007ffc`632fc990 00000095`bab1d3f0 00007ffc`62ac8f00 00000095`b7e5f308 : clr!ThreadpoolMgr::AsyncTimerCallbackCompletion+0x36 [f:\dd\ndp\clr\src\vm\win32threadpool.cpp @ 5314]
    00007ffc`62a8f046 : 00000095`b7e5f310 00000095`b7e5f200 00000000`177bc32b 00000000`00000001 : clr!UnManagedPerAppDomainTPCount::DispatchWorkItem+0x122 [f:\dd\ndp\clr\src\vm\threadpoolrequest.cpp @ 544]
    00007ffc`62a8ef3a : 00000095`bc30ae30 00000095`bc30ae30 00000000`00000000 00000000`ffff0000 : clr!ThreadpoolMgr::ExecuteWorkRequest+0x46 [f:\dd\ndp\clr\src\vm\win32threadpool.cpp @ 2009]
    00007ffc`62b4fcb6 : 00000000`00000000 00000095`bc2fc801 00000095`bc2fc801 00000091`00000409 : clr!ThreadpoolMgr::WorkerThreadStart+0xf4 [f:\dd\ndp\clr\src\vm\win32threadpool.cpp @ 2479]
    00007ffc`69e613d2 : 00007ffc`62b4fc40 00000095`bab09fa0 00000000`00000000 00000000`00000000 : clr!Thread::intermediateThreadProc+0x7d [f:\dd\ndp\clr\src\vm\threads.cpp @ 3458]
    00007ffc`6c3754e4 : 00007ffc`69e613b0 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x22 [d:\9147\base\win32\client\thread.c @ 78]
    00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x34

    Friday, January 13, 2017 8:30 PM

All replies

  • Hi saif50,

    I am not completely sure what the real scenario is, Could you help give a simplified demo to help me reproduce it?

    Just based in your memory dump from the following is not enough.

    AzureCommonLibrary!MS.Msn.Messenger.AzureCommonLibrary.AzureEncryptionKeys.Initialize

     

    From above code, does it an Azure app? This is really too generic for us to be of much use. You need to debug your application to determine whether the problem is with your reading code or your UI. Once you've narrowed it down to the code that is having issues we may be able to help you. Thanks for your understanding.

    Best regards,

    Kristin


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, January 16, 2017 3:16 AM