WoADialer.exe hangs on Windows 10

[leizhangax]

LumiaWOA.Dialer

Windows 10
18995 19041 18362
ARM64
WoADialer.exe hangs on Windows 10.  

PROCESS_NAME:  WoADialer.exe WATSON_BKT_EVENT:  AppHang   ERROR_CODE: (NTSTATUS) 0xcfffffff - EXCEPTION_CODE_STR:  cfffffff   STACK_TEXT:  0000009fb1bfea30 00007fff09c8a2e0 : 0000009fb1bfea40 00007fff09c8a234 0000009fb1bfeaa0 00007fff0ac1ecb0 : win32u!ZwUserMsgWaitForMultipleObjectsEx+0x4 0000009fb1bfea30 00007fff09c8a234 : 0000009fb1bfea40 00007fff09c8a234 0000009fb1bfeaa0 00007fff0ac1ecb0 : user32!RealMsgWaitForMultipleObjectsEx+0x20 0000009fb1bfea40 00007fff0ac1ecb0 : 0000009fb1bfeaa0 00007fff0ac1ecb0 0000021600e807f0 0000000000000004 : user32!MsgWaitForMultipleObjectsEx+0x64 0000009fb1bfea80 00007fff0ac1e418 : fffffffffffffffe 00007fff05a1d4b8 0000000000000000 0000000000000000 : combase!ModernSTAWaitContext::KernelWait+0x80 0000009fb1bfeb00 00007fff0ac1fd9c : 0000009fb1bfecd0 00007fff09c7f5d0 0000000000000001 0000000000000000 : combase!ModernSTAWaitContext::Wait+0x330 0000009fb1bfeea0 00007ffefe4f131c : 0000009fb1bfef80 00007ffefe4f131c 0000000000000000 0000000600001cff : combase!CoMsgWaitInProcessEvents+0xac 0000009fb1bfeef0 00007ffefe4f25e4 : 0000000000000001 00007ffefe5b74d8 0000000000000398 00000000000005e8 : Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessagesInternal+0xfc 0000009fb1bfefe0 00007fff05d87764 : 0000009fb1bff000 00007fff05d87764 0000021600e84478 00007ffefe4f25a0 : Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessages+0x44 0000009fb1bff000 00007fff05d95b28 : 0000009fb1bff060 00007fff05d95b28 0000021600e84478 fffffffffffffffe : twinapi_appcore!Event::WaitAndProcessEvents+0xcc 0000009fb1bff060 00007fff05da96e4 : 0000009fb1bff260 00007fff05da96e4 0000021600e9c530 0000000000000000 : twinapi_appcore!Windows::ApplicationModel::SuspendingOperation::WaitForAnyOutstandingDeferrals+0x58 0000009fb1bff0c0 00007fff05d882ac : 0000000000000000 00007fff09d233b8 0000000000000250 00007fff05a1d514 : twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::SuspendResume+0x244 0000009fb1bff2c0 00007ffefe4f02e8 : fffffffffffffffe 000002161c9274c0 00007fff09d23001 00007fff05f05c18 : twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::SuspendResumeHandler::Invoke+0x13c 0000009fb1bff470 00007ffefe4f1688 : 0000009fb1bff530 00007ffefe4f1688 00007fff05a1d470 00007fff0b1612b0 : Windows_UI!Windows::UI::Core::CDispatcher::ProcessInvokeItem+0x260 0000009fb1bff520 00007ffefe4f12dc : 00000000000002d4 0000021600e84440 0000009fb1bff660 00007ffefe4f12dc : Windows_UI!Windows::UI::Core::CDispatcher::ProcessMessage+0x238 0000009fb1bff5d0 00007ffefe4f25e4 : 0000009fb1bf0000 00007ffefe5b74d8 0000000000000398 00000000000002d4 : Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessagesInternal+0xbc 0000009fb1bff6c0 00007fff05d87764 : 0000009fb1bff6e0 00007fff05d87764 0000021600e84478 00007ffefe4f25a0 : Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessages+0x44 0000009fb1bff6e0 00007fff05d8e988 : 0000009fb1bff740 00007fff05d8e988 0000021600e84478 fffffffffffffffe : twinapi_appcore!Event::WaitAndProcessEvents+0xcc 0000009fb1bff740 00007fff05d8dcd4 : 0000009fb1bff7d0 00007fff05d8dcd4 0000021600e7a480 0000021600e723f0 : twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationViewAgileContainer::WaitForViewReady+0x60 0000009fb1bff790 00007fff09e82cd0 : 0000021600e7a480 0000021600e723f0 fffffffffffffffe 00007fff05f28e30 : twinapi_appcore!<lambda_643db08282a766b00cec20194396f531>::<lambda_invoker_cdecl>+0xb4 0000009fb1bff810 00007fff09bb4974 : 0000009fb1bff900 00007fff09bb4974 0000000000000000 0000000000000000 : SHCore!_WrapperThreadProc+0x1f0 0000009fb1bff900 00007fff0b1a96f4 : 0000009fb1bff940 00007fff0b1a96f4 0000000000000000 0000000000000000 : kernel32!BaseThreadInitThunk+0x34 0000009fb1bff940 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : ntdll!RtlUserThreadStart+0x44  
IMAGE_NAME:  twinapi.appcore.dll
OS_VERSION:  10.0.18363.1
OSPLATFORM_TYPE:  arm64
OSNAME:  Windows 10

[DjArt]

What action led to a hang? Or does this happen at startup?