locked
VS2015: WPF Native Mode: Intel Apollo lake Processor: The remote debugger has encountered a serious internal error, and must abort the remote debugging session. Please restart the debugger. RRS feed

  • Question

  • UPDATE:  Added contents of report.wer at bottom of post.

    We are developing a product on the following Intel processor:  Intel Apollo lake N4200.  This is released silicon.  When using a core i7 on the target we can remote debug without issue.  When we have the Intel Apollo Lake on the target we get the below error message: 

    The remote debugger has encountered a serious internal error, and must abort the remote debugging session.  Please restart the debugger.


    We have tried both an commercially available consumer grade motherboard from ASROCK.  We have also tried our commercial grade COM-E module with the same result.

    This happens with our WPF application when native debugging is checked.  We do not see this issue with MFC applications.

    Below are the stack traces:

    Windows 10 Version 14393 MP (4 procs) Free x64 Product: WinNt, suite: SingleUserTS Built by: 10.0.14393.0 (rs1_release.160715-1616) Machine Name: Debug session time: Thu Mar 16 16:20:34.000 2017 (UTC - 7:00) System Uptime: 0 days 1:20:09.160 Process Uptime: 0 days 0:01:22.000 ................................................................ ............................... Loading unloaded module list .... ntdll!NtWaitForSingleObject+0x14: 00007ffb`98ca4ed4 c3              ret 0:000> kb RetAddr           : Args to Child                                                           : Call Site 00007ffb`952175ff : 00000000`000001d8 00000000`00000000 00000000`00000000 00000000`00000003 : ntdll!NtWaitForSingleObject+0x14 00007ff7`d08d10fe : 00000039`1bd0f3e0 00000039`1bd0f308 00000000`00000000 00000000`00000178 : KERNELBASE!WaitForSingleObjectEx+0x8f 00007ff7`d08d106f : 00000000`00000000 00000000`00000000 00000000`00000000 000001f7`5e5c4670 : msvsmon!msvsmon::CRootServer::WaitForExitProcess+0x3cd 00007ff7`d08d11ce : 00000039`1bd0f3e0 00000039`1bd0f6a0 00000039`1bd0f3e0 00000039`1bd0f3e0 : msvsmon!msvsmon::CRootServer::MainThreadFunction+0x17 00007ff7`d08d1aeb : 00000000`00000000 00000039`1bd0f780 00000000`00000001 00000039`1bd0f6a0 : msvsmon!msvsmon::CRootServer::Run+0x146 00007ff7`d08d1a33 : 00000000`00000000 00000000`00000000 000001f7`5e5720c4 00000000`00000000 : msvsmon!msvsmon::CRootServer::Main+0xa7 00007ff7`d09365d6 : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : msvsmon!WinMain+0x255 00007ffb`96638364 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msvsmon!__scrt_common_main_seh+0x11e 00007ffb`98c65e91 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

    Also the second stack:

    Windows 10 Version 14393 MP (4 procs) Free x64 Product: WinNt, suite: SingleUserTS Built by: 10.0.14393.0 (rs1_release.160715-1616) Machine Name: Debug session time: Thu Mar 16 16:20:43.000 2017 (UTC - 7:00) System Uptime: 0 days 1:20:18.255 Process Uptime: 0 days 0:01:31.000 ................................................................ ........... Loading unloaded module list . ntdll!NtWaitForMultipleObjects+0x14: 00007ffb`98ca59a4 c3              ret 0:000> kb RetAddr           : Args to Child                                                           : Call Site 00007ffb`9524c19f : 0000022a`00000014 00000000`0000000a 00000000`00000000 00000000`00000100 : ntdll!NtWaitForMultipleObjects+0x14 00007ffb`98516f54 : 0000022a`7c504be0 000000c5`00000000 00000000`00000000 00000000`00000001 : KERNELBASE!WaitForMultipleObjectsEx+0xef 00007ffb`98516dd5 : 00000000`00000000 000000c5`eb0ff518 00000000`00000001 000000c5`eb0ff510 : combase!DefaultWaitForHandles+0x44 [d:\rs1\onecore\com\combase\dcomrem\sync.cxx @ 39] 00007ffb`79432df4 : 00000000`00000000 00000000`00000000 000000c5`eb0ff528 00000000`00000001 : combase!CoWaitForMultipleHandles+0x85 [d:\rs1\onecore\com\combase\dcomrem\sync.cxx @ 124] 00007ffb`79434f4b : 0000022a`189bf9d0 0000022a`7c5c0e00 0000022a`7c504720 00000000`000000e4 : VSDebugEng!dispatcher::XapiWorkerThread::ExecuteSyncTask+0x90 00007ffb`79434ee1 : 000000c5`eb0ff550 0000022a`7c5c0d30 0000022a`7c4f18e0 0000022a`7c4f24f0 : VSDebugEng!dispatcher::CXapiPhase2ObjectQueue::Flush+0x86 00007ffb`79444613 : 0000022a`7c5c0d30 0000022a`7c48d170 00000000`80004005 00000000`0000014c : VSDebugEng!dispatcher::CXapiPhase2ObjectQueue::~CXapiPhase2ObjectQueue+0x12 00007ffb`79433e47 : 00000000`00000000 0000022a`7c5c0d30 00000000`80004005 00000000`0000000a : VSDebugEng!dispatcher::DkmDataContainer::DispatcherClose+0x4c 00007ffb`79431359 : 0000022a`7c5c0d30 0000022a`7c48a710 00007ffb`7968a100 0000022a`7c48a700 : VSDebugEng!dispatcher::CServerTransportFactory::Uninitialize+0x85 00007ff7`d08d138e : 00000000`80070000 0000022a`7c49dfa0 0000022a`7c48a700 00000000`00000004 : VSDebugEng!DkmDllUninitialize+0x9 00007ff7`d08d1991 : 000000c5`eb0f0202 00000000`00000000 0000022a`7c4820f0 00000000`00000001 : msvsmon!msvsmon::CChildServer::Listen+0x1d2 00007ff7`d08d1812 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000000 : msvsmon!msvsmon::CChildServer::Main+0x159 00007ff7`d09365d6 : 00000000`0000000a 00000000`00000000 00000000`00000000 00000000`00000000 : msvsmon!WinMain+0x228 00007ffb`96638364 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : msvsmon!__scrt_common_main_seh+0x11e 00007ffb`98c65e91 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21

    ADDING WER REPORT:

    Version=1
    EventType=APPCRASH
    EventTime=131341649228499133
    ReportType=2
    Consent=1
    UploadTime=131341650789424385
    ReportIdentifier=f81b2758-0a7b-11e7-9c99-7085c233cfea
    IntegratorReportIdentifier=078d780f-3e9e-4a96-91a1-9ad0383cc979
    NsAppName=msvsmon.exe
    AppSessionGuid=00001388-0001-0009-5343-2550889ed201
    TargetAppId=W:0006435695e91ead051be75e120821ac54e100000904!000093e44751e2ac832448c99bab7136e6fe341b74f6!msvsmon.exe
    TargetAppVer=2016//07//18:02:46:18!4cc8a6!msvsmon.exe
    BootId=4294967295
    Response.type=4
    Sig[0].Name=Application Name
    Sig[0].Value=msvsmon.exe
    Sig[1].Name=Application Version
    Sig[1].Value=14.0.25424.0
    Sig[2].Name=Application Timestamp
    Sig[2].Value=578c42fa
    Sig[3].Name=Fault Module Name
    Sig[3].Value=VSDebugEng.dll
    Sig[4].Name=Fault Module Version
    Sig[4].Value=14.0.25424.0
    Sig[5].Name=Fault Module Timestamp
    Sig[5].Value=578c3def
    Sig[6].Name=Exception Code
    Sig[6].Value=c0000005
    Sig[7].Name=Exception Offset
    Sig[7].Value=00000000000714a6
    DynamicSig[1].Name=OS Version
    DynamicSig[1].Value=10.0.14393.2.0.0.256.125
    DynamicSig[2].Name=Locale ID
    DynamicSig[2].Value=1033
    DynamicSig[22].Name=Additional Information 1
    DynamicSig[22].Value=aad4
    DynamicSig[23].Name=Additional Information 2
    DynamicSig[23].Value=aad47d0c2031c61bcbbd7154ccbf7338
    DynamicSig[24].Name=Additional Information 3
    DynamicSig[24].Value=6cf1
    DynamicSig[25].Name=Additional Information 4
    DynamicSig[25].Value=6cf1090444b35624af2fad0119d11d60
    UI[2]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
    UI[3]=Visual Studio 2015 Remote Debugger has stopped working
    UI[4]=Windows can check online for a solution to the problem.
    UI[5]=Check online for a solution and close the program
    UI[6]=Check online for a solution later and close the program
    UI[7]=Close the program
    LoadedModule[0]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
    LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
    LoadedModule[2]=C:\Windows\System32\KERNEL32.DLL
    LoadedModule[3]=C:\Windows\System32\KERNELBASE.dll
    LoadedModule[4]=C:\Windows\System32\ADVAPI32.dll
    LoadedModule[5]=C:\Windows\System32\msvcrt.dll
    LoadedModule[6]=C:\Windows\System32\sechost.dll
    LoadedModule[7]=C:\Windows\System32\RPCRT4.dll
    LoadedModule[8]=C:\Windows\System32\USER32.dll
    LoadedModule[9]=C:\Windows\System32\win32u.dll
    LoadedModule[10]=C:\Windows\System32\GDI32.dll
    LoadedModule[11]=C:\Windows\System32\gdi32full.dll
    LoadedModule[12]=C:\Windows\System32\ole32.dll
    LoadedModule[13]=C:\Windows\System32\combase.dll
    LoadedModule[14]=C:\Windows\System32\ucrtbase.dll
    LoadedModule[15]=C:\Windows\System32\bcryptPrimitives.dll
    LoadedModule[16]=C:\Windows\System32\OLEAUT32.dll
    LoadedModule[17]=C:\Windows\System32\WS2_32.dll
    LoadedModule[18]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.14393.0_none_2d0f50fcbdb171b8\COMCTL32.dll
    LoadedModule[19]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\VSDebugEng.dll
    LoadedModule[20]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.14393.0_none_acd6c01ad1498de0\gdiplus.dll
    LoadedModule[21]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\VCRUNTIME140.dll
    LoadedModule[22]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\MSVCP140.dll
    LoadedModule[23]=C:\Windows\System32\IMM32.DLL
    LoadedModule[24]=C:\Windows\System32\kernel.appcore.dll
    LoadedModule[25]=C:\Windows\SYSTEM32\webservices.dll
    LoadedModule[26]=C:\Windows\system32\mswsock.dll
    LoadedModule[27]=C:\Windows\SYSTEM32\SSPICLI.DLL
    LoadedModule[28]=C:\Windows\SYSTEM32\Secur32.dll
    LoadedModule[29]=C:\Windows\system32\msv1_0.DLL
    LoadedModule[30]=C:\Windows\SYSTEM32\bcrypt.dll
    LoadedModule[31]=C:\Windows\SYSTEM32\NtlmShared.dll
    LoadedModule[32]=C:\Windows\SYSTEM32\cryptdll.dll
    LoadedModule[33]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\vsdebugeng.impl.DLL
    LoadedModule[34]=C:\Windows\System32\PSAPI.DLL
    LoadedModule[35]=C:\Windows\System32\SHLWAPI.dll
    LoadedModule[36]=C:\Windows\System32\SHELL32.dll
    LoadedModule[37]=C:\Windows\System32\cfgmgr32.dll
    LoadedModule[38]=C:\Windows\SYSTEM32\mscoree.dll
    LoadedModule[39]=C:\Windows\System32\windows.storage.dll
    LoadedModule[40]=C:\Windows\System32\powrprof.dll
    LoadedModule[41]=C:\Windows\System32\shcore.dll
    LoadedModule[42]=C:\Windows\System32\profapi.dll
    LoadedModule[43]=C:\Windows\System32\clbcatq.dll
    LoadedModule[44]=C:\Windows\System32\twinapi.appcore.dll
    LoadedModule[45]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscoreei.dll
    LoadedModule[46]=C:\Windows\SYSTEM32\VERSION.dll
    LoadedModule[47]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscordbi.dll
    LoadedModule[48]=C:\Windows\SYSTEM32\WTSAPI32.dll
    LoadedModule[49]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\DiagnosticsHub.StandardCollector.Bridge.dll
    LoadedModule[50]=C:\Windows\System32\mintdh.dll
    LoadedModule[51]=C:\Program Files\Microsoft Visual Studio 14.0\Team Tools\DiagnosticsHub\Collector\amd64\DiagnosticsHub.StandardCollector.Proxy.dll
    LoadedModule[52]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\GpuEnvSetup.dll
    LoadedModule[53]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\VSGraphicsCaptureEngine.dll
    LoadedModule[54]=C:\Windows\system32\apphelp.dll
    LoadedModule[55]=C:\Program Files\Common Files\Microsoft Shared\VS7Debug\csm.dll
    LoadedModule[56]=C:\Windows\SYSTEM32\CRYPTBASE.DLL
    LoadedModule[57]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\debuggerproxy.dll
    LoadedModule[58]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\vsdebugeng.xaml.dll
    LoadedModule[59]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\WpfBootstrap.dll
    LoadedModule[60]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscordacwks.dll
    LoadedModule[61]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
    LoadedModule[62]=C:\Windows\SYSTEM32\MSVCR120_CLR0400.dll
    LoadedModule[63]=C:\Windows\assembly\NativeImages_v4.0.30319_64\mscorlib\e96b4590c579d08edc2e60cc3e5ae997\mscorlib.ni.dll
    LoadedModule[64]=C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clrjit.dll
    LoadedModule[65]=C:\Windows\assembly\NativeImages_v4.0.30319_64\System\ee1c3ea3e0049df6d53b35e21c2247e4\System.ni.dll
    LoadedModule[66]=C:\Windows\SYSTEM32\CRYPTSP.dll
    LoadedModule[67]=C:\Windows\system32\rsaenh.dll
    LoadedModule[68]=C:\Windows\SYSTEM32\ntmarta.dll
    LoadedModule[69]=C:\Windows\SYSTEM32\faultrep.dll
    LoadedModule[70]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\dbghelp.dll
    LoadedModule[71]=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\dbgcore.DLL
    State[0].Key=Transport.DoneStage1
    State[0].Value=1
    FriendlyEventName=Stopped working
    ConsentKey=APPCRASH
    AppName=Visual Studio 2015 Remote Debugger
    AppPath=C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x64\msvsmon.exe
    NsPartner=windows
    NsGroup=windows8
    ApplicationIdentity=5AFF5F5A62DAD51C750B19F61DE369E6
    MetadataHash=-1887564975


    • Edited by KernelCoder2 Friday, March 17, 2017 11:05 PM added screenshot
    Friday, March 17, 2017 12:51 AM

Answers

  • I opened a support case with Microsoft.  This is now fixed in the latest version of VS 2017.  I downloaded the new remote tools and new visual studio 2017 updates and it works.
    • Proposed as answer by Pavel A Wednesday, May 3, 2017 6:23 PM
    • Marked as answer by KernelCoder2 Friday, May 5, 2017 11:51 PM
    Wednesday, May 3, 2017 4:20 PM

All replies

  • Is this question in the wrong forum?  Should it be in Visual Studio?
    Monday, March 20, 2017 9:50 PM
  • I have the same problem with remote debug on apollo lake.

    Remote debug on sky lake or kaby lake works as expected, but on apollo lake I can't debug, and can't attach to process too.

    How fix it?

    Friday, April 28, 2017 5:57 AM
  • Can you list some of the things you have tried?  We ahve repeated this on four systems with four seperate engineers.  No success.  We have also tried VS 2017.
    Friday, April 28, 2017 9:47 PM
  • Unfortunately, I can't list a lot of things. =(

    I am using Win10rs2 x64 on local and remote hosts, latest Visual Studio 2015, x64 debugger.

    And I'm also tried several systems and all of them not working.

    Saturday, April 29, 2017 7:26 AM
  • I'm also made such thread in the Visual Studio Diagnostics forum.
    Saturday, April 29, 2017 7:46 AM
  • I opened a support case with Microsoft.  This is now fixed in the latest version of VS 2017.  I downloaded the new remote tools and new visual studio 2017 updates and it works.
    • Proposed as answer by Pavel A Wednesday, May 3, 2017 6:23 PM
    • Marked as answer by KernelCoder2 Friday, May 5, 2017 11:51 PM
    Wednesday, May 3, 2017 4:20 PM