locked
debugging crash dumps with VS 2013, error,cpp & parameters

    Question

  • Some more dumb questions:

    I got my app in the store a couple of weeks ago, and now I see that there have been 15 crashes reported, all with the same dump file.  I downloaded the dump file to the Release folder where the executable and symbol files reside on my machine, added the Release folder to the symbol paths, opened the dump file in VS 2013 Express and clicked on Debug with Mixed.

    The first thing to come up was a window titled "Find Source error.cpp."  What is error.cpp?  Do I need to find it to locate the bug?  If so, how do I find it?

    Giving up on finding error.cpp, I clicked on cancel, and the next thing to come up was the unhandled exception window.  The exception code was the old 27B, not too useful.  There were parameters (0x00ABD140, 0x00000002) which I understand can be used to find the real error code.  Is there a way to do that with VS 2013, or do I have to use WinDbg and/or SOS (which I hear are not terribly user friendly)?

    Tuesday, June 24, 2014 12:26 PM

Answers

  • Here's a simple walkthrough. If it doesn't help, please post the dump to OneDrive and paste the link here.

    Matt Small - Microsoft Escalation Engineer - Forum Moderator
    If my reply answers your question, please mark this post as answered.

    NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.

    • Marked as answer by P Granbery Sunday, July 6, 2014 7:37 PM
    Wednesday, June 25, 2014 12:09 PM
    Moderator

All replies

  • Here's a simple walkthrough. If it doesn't help, please post the dump to OneDrive and paste the link here.

    Matt Small - Microsoft Escalation Engineer - Forum Moderator
    If my reply answers your question, please mark this post as answered.

    NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.

    • Marked as answer by P Granbery Sunday, July 6, 2014 7:37 PM
    Wednesday, June 25, 2014 12:09 PM
    Moderator
  • Matt:

    I tried, but I don't think I am going to figure this out any time soon.

    I uploaded the triage dump file here:

     https://onedrive.live.com/?cid=3AF7BBA8877EAF91&id=3AF7BBA8877EAF91%21109

    If it is worth anything, this is the verbose exception analysis output I got:

    0:004> !analyze -v
    *******************************************************************************
    *                                                                             *
    *                        Exception Analysis                                   *
    *                                                                             *
    *******************************************************************************

    Unable to load image mscorlib.ni.dll, Win32 error 0n2
    Unable to load image System.Runtime.WindowsRuntime.ni.dll, Win32 error 0n2
    *** WARNING: Unable to verify checksum for System.Runtime.WindowsRuntime.ni.dll
    *** WARNING: Unable to verify checksum for Windows.UI.ni.dll
    *** ERROR: Module load completed but symbols could not be loaded for Windows.UI.ni.dll
    Unable to load image Windows.UI.Xaml.ni.dll, Win32 error 0n2
    *** WARNING: Unable to verify checksum for Windows.UI.Xaml.ni.dll
    *** ERROR: Module load completed but symbols could not be loaded for Windows.UI.Xaml.ni.dll
    Unable to load image Windows.ApplicationModel.Store.dll, Win32 error 0n2
    *** WARNING: Unable to verify timestamp for Windows.ApplicationModel.Store.dll
    *** ERROR: Module load completed but symbols could not be loaded for Windows.ApplicationModel.Store.dll

    FAULTING_IP: 
    combase!RoFailFastWithErrorContextInternal+10b [d:\blue_gdr\com\combase\winrt\error\error.cpp @ 948]
    762bb152 5f              pop     edi

    EXCEPTION_RECORD:  ffffffff -- (.exr 0xffffffffffffffff)
    ExceptionAddress: 762bb152 (combase!RoFailFastWithErrorContextInternal+0x0000010b)
       ExceptionCode: c000027b
      ExceptionFlags: 00000001
    NumberParameters: 2
       Parameter[0]: 00abd140
       Parameter[1]: 00000002

    CONTEXT:  00000000 -- (.cxr 0x0;r)
    eax=aaaaaaaa ebx=00000000 ecx=00000000 edx=00000000 esi=04f5f230 edi=aaaaaaaa
    eip=762bb01f esp=04f5f1e4 ebp=04f5f28c iopl=0         nv up ei pl nz ac po nc
    cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000212
    combase!RoFailFastWithErrorContextInternal2+0x10a:
    762bb01f 6a03            push    3

    DEFAULT_BUCKET_ID:  WRONG_SYMBOLS

    PROCESS_NAME:  BridgeCoach.exe

    OVERLAPPED_MODULE: Address regions for 'Windows_UI_Xaml_ni' and 'Windows.ApplicationModel.dll' overlap

    ERROR_CODE: (NTSTATUS) 0xc000027b - An application-internal exception has occurred.

    EXCEPTION_CODE: (NTSTATUS) 0xc000027b - An application-internal exception has occurred.

    EXCEPTION_PARAMETER1:  00abd140

    EXCEPTION_PARAMETER2:  00000002

    NTGLOBALFLAG:  0

    APP:  bridgecoach.exe

    ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) x86fre

    MANAGED_STACK: !dumpstack -EE
    No export dumpstack found

    PRIMARY_PROBLEM_CLASS:  WRONG_SYMBOLS

    BUGCHECK_STR:  APPLICATION_FAULT_WRONG_SYMBOLS

    LAST_CONTROL_TRANSFER:  from 762bb152 to 762bb01f

    STACK_TEXT:  
    04f5f28c 762bb152 aaaaaaaa aaaaaaaa aaaaaaaa combase!RoFailFastWithErrorContextInternal2+0x10a
    04f5f2b8 663698df aaaaaaaa aaaaaaaa aaaaaaaa combase!RoFailFastWithErrorContextInternal+0x10b
    04f5f2e0 66369567 aaaaaaaa aaaaaaaa aaaaaaaa Windows_UI_Xaml!DirectUI::ErrorHelper::ProcessUnhandledError+0xb8
    04f5f344 663693fb 00000000 05d65d50 00000000 Windows_UI_Xaml!DirectUI::FinalUnhandledErrorDetectedRegistration::OnFinalUnhandledErrorDetected+0xad
    04f5f358 71885479 00d39888 00000000 05d65d50 Windows_UI_Xaml!Microsoft::WRL::Details::InvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::Foundation::IEventHandler<Windows::ApplicationModel::Core::UnhandledErrorDetectedEventArgs *>,Microsoft::WRL::FtmBase,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil>,long (__stdcall*)(IInspectable *,Windows::ApplicationModel::Core::IUnhandledErrorDetectedEventArgs *),2>::Invoke+0x12
    04f5f374 718854aa 00ab90e0 00000000 05d65d50 twinapi_appcore!Windows::Internal::Details::GitInvokeHelper<Windows::Foundation::IEventHandler<Windows::ApplicationModel::Core::UnhandledErrorDetectedEventArgs *>,Windows::Internal::GitPtr,2>::Invoke+0x3c
    04f5f38c 7187e2d3 00ab9110 00000000 05d65d50 twinapi_appcore!Windows::ApplicationModel::Core::UnhandledErrorInvokeHelper::Invoke+0x19
    04f5f3b4 7187d892 00000000 05d65d50 05d65d50 twinapi_appcore!Microsoft::WRL::InvokeTraits<2>::InvokeDelegates<<lambda_c04829f622ac42d37c50025c6cdad004>,Windows::Foundation::IEventHandler<Windows::ApplicationModel::Core::UnhandledErrorDetectedEventArgs *> >+0x32
    04f5f3d4 71882ec2 00000000 05d65d50 0b005870 twinapi_appcore!Microsoft::WRL::EventSource<Windows::Foundation::IEventHandler<Windows::ApplicationModel::Core::UnhandledErrorDetectedEventArgs *>,Microsoft::WRL::InvokeModeOptions<2> >::DoInvoke<<lambda_c04829f622ac42d37c50025c6cdad004> >+0x42
    04f5f3f8 71882f31 00ab286c 05d65d50 00000000 twinapi_appcore!Windows::ApplicationModel::Core::CoreApplication::ForwardLocalError+0x58
    04f5f410 762bace4 00ab281c 0b005870 04f5f474 twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationFactory::ForwardLocalError+0x30
    04f5f458 762bb2c6 0b005870 04f5f4c4 6b153c9e combase!CallErrorForwarder+0x9d
    04f5f464 6b153c9e 0b005870 eb8e7ea9 6b848bc8 combase!RoReportUnhandledError+0x18
    04f5f4c4 6b1f19d5 00000000 04f5f47c 00000000 mscorlib_ni+0x9b3c9e
    04f5f4e4 6b1f15d5 00000000 0ac78a34 049fc16c mscorlib_ni+0xa519d5
    04f5f514 7084f9df 04f5f6c8 6b9e7da5 04f5f758 mscorlib_ni+0xa515d5
    04f5f604 7084f965 6aaddf17 02592ba0 00000000 System_Runtime_WindowsRuntime_ni+0x1f9df
    04f5f66c 6aadde66 00000001 02661604 00000000 System_Runtime_WindowsRuntime_ni+0x1f965
    04f5f680 7084f934 00000001 02661604 00000000 mscorlib_ni+0x33de66
    04f5f69c 7095ff16 7084f8f0 0515e8e8 04f5f4fc System_Runtime_WindowsRuntime_ni+0x1f934
    WARNING: Stack unwind information not available. Following frames may be wrong.
    04f5f6c0 6b842a36 04f5fb6c 6b961896 04f5f758 Windows_UI_ni+0x9ff16
    04f5f740 70a03fb5 76200d80 aaaaaaaa 06a391f4 clr!COMToCLRDispatchHelper+0x28
    04f5f7c0 70a043ba 00000000 00ab7758 05d0d3f4 Windows_UI!Windows::UI::Core::CDispatcher::ProcessInvokeItem+0x4d0
    04f5f858 71856e77 00ab7770 00000674 00ab7758 Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessages+0x2e7
    04f5f878 71856edd 00ab7758 05d0d528 00ab8ef0 twinapi_appcore!Event::WaitAndProcessEvents+0x43
    04f5f888 718570a3 76200d80 aaaaaaaa 06a391f4 twinapi_appcore!Windows::ApplicationModel::SuspendingDeferral::WaitForOutstandingDeferrals+0x31
    04f5f8b4 71856fae 00ab8ef0 000002f4 aaaaaaaa twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::SuspendResume+0xc8
    04f5f8cc 71856e19 aaaaaaaa 04f5f938 70a03fb5 twinapi_appcore!Windows::ApplicationModel::SuspendingDeferral::Complete+0xc0
    04f5f8d8 70a03fb5 05dbc588 00ab7770 00000000 twinapi_appcore!Microsoft::WRL::Details::InvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::UI::Core::IDispatchedHandler,Microsoft::WRL::FtmBase,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil>,<lambda_6dacf28f2573a228f76b629e33cc6ce6>,0>::Invoke+0x11
    04f5f938 70a037e7 aaaaaaaa 00ab7770 00ab7758 Windows_UI!Windows::UI::Core::CDispatcher::ProcessInvokeItem+0x4d0
    04f5f9d4 70a016dc 00ab7770 00000000 00d4a688 Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessages+0x271
    04f5fa34 6607ed61 00ab7758 aaaaaaaa 00ab7fd8 Windows_UI!Windows::UI::Core::CDispatcher::ProcessEvents+0x60
    04f5fa7c 718562f7 00d08d6c 04f5faa8 718561d0 Windows_UI_Xaml!DirectUI::FrameworkView::Run+0x5e
    04f5fa88 718561d0 00ab8ef0 00000000 00000000 twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::Run+0x27
    04f5faa8 753ba879 00ab2850 00000000 00000000 twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::SetWindowAndGetDispatcher+0x320
    04f5fb2c 7565919f 009bee48 04f5fb7c 77c4a8cb SHCore!Microsoft::WRL::RuntimeClass<Microsoft::WRL::RuntimeClassFlags<2>,CScalingInfoBase,Microsoft::WRL::FtmBase,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil,Microsoft::WRL::Details::Nil>::`vector deleting destructor'+0x103
    04f5fb38 77c4a8cb 009bee48 aaaaaaaa 00000000 kernel32!BaseThreadInitThunk+0xe
    04f5fb7c 77c4a8a1 aaaaaaaa 77c3f69c 00000000 ntdll!__RtlUserThreadStart+0x20
    04f5fb8c 00000000 753ba797 009bee48 00000000 ntdll!_RtlUserThreadStart+0x1b


    STACK_COMMAND:  ~4s; .ecxr ; kb

    FOLLOWUP_IP: 
    Windows_UI_Xaml!Microsoft::WRL::Details::InvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::Foundation::IEventHandler<Windows::ApplicationModel::Core::UnhandledErrorDetectedEventArgs *>,Microsoft::WRL::FtmBase,Microsoft::WRL+12 [d:\blue_gdr.public.x86fre\sdk\inc\wrl\event.h @ 259]
    663693fb 8bf0            mov     esi,eax

    FAULTING_SOURCE_LINE:  d:\blue_gdr.public.x86fre\sdk\inc\wrl\event.h

    FAULTING_SOURCE_FILE:  d:\blue_gdr.public.x86fre\sdk\inc\wrl\event.h

    FAULTING_SOURCE_LINE_NUMBER:  259

    SYMBOL_STACK_INDEX:  4

    SYMBOL_NAME:  windows_ui_xaml!Microsoft::WRL::Details::InvokeHelper<Microsoft::WRL::Implements<Microsoft::WRL::RuntimeClassFlags<2>,Windows::Foundation::IEventHandler<Windows::ApplicationModel::Core::UnhandledErrorDetectedEventArgs *>,Microsoft::WRL::FtmBase,Microsoft::WRL+12

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Windows_UI_Xaml

    IMAGE_NAME:  Windows.UI.Xaml.ni.dll

    DEBUG_FLR_IMAGE_TIMESTAMP:  53413fdc

    BUCKET_ID:  APPLICATION_FAULT_WRONG_SYMBOLS_windows_ui_xaml!Microsoft::WRL::Details::InvokeHelper_Microsoft::WRL::Implements_Microsoft::WRL::RuntimeClassFlags_2_,Windows::Foundation::IEventHandler_Windows::ApplicationModel::Core::UnhandledErrorDetectedEventArgs_*_,Micros

    FAILURE_BUCKET_ID:  WRONG_SYMBOLS_c000027b_Windows.UI.Xaml.ni.dll!Microsoft::WRL::Details::InvokeHelper_Microsoft::WRL::Implements_Microsoft::WRL::RuntimeClassFlags_2_,Windows::Foundation::IEventHandler_Windows::ApplicationModel::Core::UnhandledErrorDetectedEventArgs_*_,Microsoft::WRL::FtmBase,Microsoft::WRL

    ANALYSIS_SOURCE:  UM

    FAILURE_ID_HASH_STRING:  um:wrong_symbols_c000027b_windows.ui.xaml.ni.dll!microsoft::wrl::details::invokehelper_microsoft::wrl::implements_microsoft::wrl::runtimeclassflags_2_,windows::foundation::ieventhandler_windows::applicationmodel::core::unhandlederrordetectedeventargs_*_,microsoft::wrl::ftmbase,microsoft::wrl

    FAILURE_ID_HASH:  {a5227a92-d75e-c229-d296-881ad0df43b0}

    Followup: MachineOwner

    Saturday, June 28, 2014 12:41 PM
  • In your appx package, there's a file with the suffix .appxsym.  Can you also upload that to the same OneDrive share?

    Matt Small - Microsoft Escalation Engineer - Forum Moderator
    If my reply answers your question, please mark this post as answered.

    NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.

    Monday, June 30, 2014 6:15 PM
    Moderator
  • Matt:

    I have uploaded the symbols file to the OneDrive share.

    https://onedrive.live.com/?cid=3AF7BBA8877EAF91&id=3AF7BBA8877EAF91%21109

    Thursday, July 3, 2014 5:26 AM
  • Here's the exception causing the crash:

    EXCEPTION_OBJECT: !pe 265d9e4
    Exception object: 0265d9e4
    Exception type:   System.Runtime.InteropServices.COMException
    Message:          <Invalid Object>
    InnerException:   <none>
    StackTrace (generated):
        SP       IP       Function
        00000000 00000001 Windows_UI_Xaml_ni!Windows.UI.Xaml.Controls.Frame.GetNavigationState()+0x2
        04F5F498 099BF69D BridgeCoach!BridgeCoach.Common.SuspensionManager.SaveFrameNavigationState(Windows.UI.Xaml.Controls.Frame)+0x1d
        04F5F4A8 099BF0DB BridgeCoach!BridgeCoach.Common.SuspensionManager+<SaveAsync>d__0.MoveNext()+0xa3

    The code is:
    private static void SaveFrameNavigationState(Frame frame)
    {
        Dictionary<stringobject> dictionary = SuspensionManager.SessionStateForFrame(frame);
        dictionary["Navigation"] = frame.GetNavigationState();
    }


    It's trying to serialize the frame into a string but is failing. Additional information is this:
    BUCKET_ID:  APPLICATION_FAULT_STATUS_STOWED_EXCEPTION_AFTER_CALL__SYSTEM.RUNTIME.INTEROPSERVICES.COMEXCEPTION__SYSTEM.RUNTIME.INTEROPSERVICES.COMEXCEPTION_bad_dump!structure_version_not_supported

    We see this often when the frame itself has had information passed to it in a Navigate method call that can't be serialized. 

    I hope this helps.


    FYI: I followed the exact same process as was shown in the blog to get the symbols to resolve and that made !analyze -v work.


    Matt Small - Microsoft Escalation Engineer - Forum Moderator
    If my reply answers your question, please mark this post as answered.

    NOTE: If I ask for code, please provide something that I can drop directly into a project and run (including XAML), or an actual application project. I'm trying to help a lot of people, so I don't have time to figure out weird snippets with undefined objects and unknown namespaces.


    Thursday, July 3, 2014 3:16 PM
    Moderator
  • Matt:

    Yes, that was very helpful.  I am still not sure specifically what I was doing wrong, but I was trying to do something tricky by accessing the pageState of a navigated from page.  I must have been messing something up because whenever I did that, the next time I navigated to a child page, it would crash on suspend.  Clearly a bad idea to try to be tricky when you don't understand all the implications of what you are doing.  I rewrote the code to do what I wanted in a straightforward way.

    I am going to mark your first response as answering my dumb question.  My dumb question was essentially "can you analyze a triage dump without learning how to use WinDbg," and your first response made it clear the answer is "no."  That certainly doesn't mean I don't appreciate all you did after the first response.  I would have been lost without you.

    Sunday, July 6, 2014 7:37 PM