Visual studio XAML designer crashes when DL docking station is connected

[Pysco68]

Hello,

I'm facing a weird issue with Microsoft Visual Studio's XAML Designer crashing under certain circumstances.

Here are the conditions:
- DisplayLink Docking Station connected
- Opening XAML Designer in VS 2015 (with all updates) Windows UAP/UWP Project (empty project)

When I disconnect the docking station all comes back to normal. When I then reconnect the docking station the designer keeps working until it is reloaded.

I'll upload the files from the support tool and the event log errors I get in a minute.

[Pysco68]

Error 1:

Application: XDesProc.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at Windows.UI.Xaml.DependencyObject.SetValue(Windows. UI.Xaml.DependencyProperty, System.Object)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.InstanceBuilders.FrameworkElementInstanceBuil der.OnInitialized(Microsoft.VisualStudio.DesignToo ls.Platform.InstanceBuilders.IInstanceBuilderConte xt, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, System.Object)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.Initialize(Mic rosoft.VisualStudio.DesignTools.Platform.InstanceB uilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.InitializeInstance(Micr osoft.VisualStudio.DesignTools.Platform.InstanceBu ilders.IInstanceBuilder, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.InstantiateChi ldren(Microsoft.VisualStudio.DesignTools.Platform. InstanceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentCompositeNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.Initialize(Mic rosoft.VisualStudio.DesignTools.Platform.InstanceB uilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.InitializeInstance(Micr osoft.VisualStudio.DesignTools.Platform.InstanceBu ilders.IInstanceBuilder, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.Instantiate(Microsoft.V isualStudio.DesignTools.Platform.InstanceBuilders. ViewNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.UpdateProperty OrChildValue(Microsoft.VisualStudio.DesignTools.Pl atform.InstanceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Int32, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNodeChangeAction, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode ByRef, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.IInstanceBuilder ByRef, Boolean ByRef)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.UpdateProperty (Microsoft.VisualStudio.DesignTools.Platform.Insta nceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.DependencyObjectInstanceBuilderBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].UpdateProperty(Microsoft.VisualStudio.DesignTools .Platform.InstanceBuilders.IInstanceBuilderContext , Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.InstanceBuilders.DependencyObjectInstanceBuil der.UpdateProperty(Microsoft.VisualStudio.DesignTo ols.Platform.InstanceBuilders.IInstanceBuilderCont ext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.InstanceBuilders.FrameworkElementInstanceBuil der.UpdateProperty(Microsoft.VisualStudio.DesignTo ols.Platform.InstanceBuilders.IInstanceBuilderCont ext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.InstantiatePro perties(Microsoft.VisualStudio.DesignTools.Platfor m.InstanceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentCompositeNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.Initialize(Mic rosoft.VisualStudio.DesignTools.Platform.InstanceB uilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.InitializeInstance(Micr osoft.VisualStudio.DesignTools.Platform.InstanceBu ilders.IInstanceBuilder, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.InstantiateChi ldren(Microsoft.VisualStudio.DesignTools.Platform. InstanceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentCompositeNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.Initialize(Mic rosoft.VisualStudio.DesignTools.Platform.InstanceB uilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.InitializeInstance(Micr osoft.VisualStudio.DesignTools.Platform.InstanceBu ilders.IInstanceBuilder, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.Instantiate(Microsoft.V isualStudio.DesignTools.Platform.InstanceBuilders. ViewNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.UpdateProperty OrChildValue(Microsoft.VisualStudio.DesignTools.Pl atform.InstanceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Int32, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNodeChangeAction, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode ByRef, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.IInstanceBuilder ByRef, Boolean ByRef)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.UpdateProperty (Microsoft.VisualStudio.DesignTools.Platform.Insta nceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.DependencyObjectInstanceBuilderBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].UpdateProperty(Microsoft.VisualStudio.DesignTools .Platform.InstanceBuilders.IInstanceBuilderContext , Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.InstanceBuilders.DependencyObjectInstanceBuil der.UpdateProperty(Microsoft.VisualStudio.DesignTo ols.Platform.InstanceBuilders.IInstanceBuilderCont ext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.InstanceBuilders.FrameworkElementInstanceBuil der.UpdateProperty(Microsoft.VisualStudio.DesignTo ols.Platform.InstanceBuilders.IInstanceBuilderCont ext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.InstantiatePro perties(Microsoft.VisualStudio.DesignTools.Platfor m.InstanceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentCompositeNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.Initialize(Mic rosoft.VisualStudio.DesignTools.Platform.InstanceB uilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.InitializeInstance(Micr osoft.VisualStudio.DesignTools.Platform.InstanceBu ilders.IInstanceBuilder, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)

*SNIP (too long)*

[Pysco68]

at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.UpdateProperty (Microsoft.VisualStudio.DesignTools.Platform.Insta nceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.DependencyObjectInstanceBuilderBase`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].UpdateProperty(Microsoft.VisualStudio.DesignTools .Platform.InstanceBuilders.IInstanceBuilderContext , Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.InstanceBuilders.DependencyObjectInstanceBuil der.UpdateProperty(Microsoft.VisualStudio.DesignTo ols.Platform.InstanceBuilders.IInstanceBuilderCont ext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.InstanceBuilders.FrameworkElementInstanceBuil der.UpdateProperty(Microsoft.VisualStudio.DesignTo ols.Platform.InstanceBuilders.IInstanceBuilderCont ext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.InstanceBuilders.UserControlInstanceBuilder.U pdateProperty(Microsoft.VisualStudio.DesignTools.P latform.InstanceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.InstanceBuilders.PageInstanceBuilder.UpdatePr operty(Microsoft.VisualStudio.DesignTools.Platform .InstanceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Metadata .IProperty, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.InstantiatePro perties(Microsoft.VisualStudio.DesignTools.Platfor m.InstanceBuilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentCompositeNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.Initialize(Mic rosoft.VisualStudio.DesignTools.Platform.InstanceB uilders.IInstanceBuilderContext, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.InitializeInstance(Micr osoft.VisualStudio.DesignTools.Platform.InstanceBu ilders.IInstanceBuilder, Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNode, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.Instantiate(Microsoft.V isualStudio.DesignTools.Platform.InstanceBuilders. ViewNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.UpdateInternal(Microsof t.VisualStudio.DesignTools.Platform.InstanceBuilde rs.ViewNode)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.UpdateCore(Microsoft.Vi sualStudio.DesignTools.Platform.InstanceBuilders.I AttachViewRoot, Boolean, Boolean)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.UpdateInstances(Microso ft.VisualStudio.DesignTools.Platform.InstanceBuild ers.IAttachViewRoot, System.Collections.Generic.IList`1<Microsoft.VisualStudio.DesignTools.Markup.Document Model.DocumentNode>, System.Threading.CancellationToken)
at Microsoft.VisualStudio.DesignTools.XamlDesigner.Vi ews.XamlSceneView.UpdateInstancesInternal()
at Microsoft.VisualStudio.DesignTools.XamlDesigner.Vi ews.XamlSceneView.UpdateInternal(Boolean, Boolean)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.Views.WindowsXamlSceneView.UpdateInternal(Boo lean, Boolean)
at Microsoft.VisualStudio.DesignTools.XamlDesigner.Vi ews.XamlSceneView.ProcessPostponedUpdateInternal()
at Microsoft.VisualStudio.DesignTools.XamlDesigner.Vi ews.XamlSceneView.ProcessPostponedUpdate(Boolean)
at Microsoft.VisualStudio.DesignTools.XamlDesigner.Vi ews.XamlSceneView.EnsureActiveViewUpdated()
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.Views.WindowsXamlSceneView.EnsureActiveViewUp datedHelper()
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.Views.WindowsXamlSceneView.EnsureActiveViewUp dated()
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.Views.WindowsXamlSceneView.ArtboardLoaded(Sys tem.Object, System.Windows.RoutedEventArgs)
at System.Windows.RoutedEventHandlerInfo.InvokeHandle r(System.Object, System.Windows.RoutedEventArgs)
at System.Windows.EventRoute.InvokeHandlersImpl(Syste m.Object, System.Windows.RoutedEventArgs, Boolean)
at System.Windows.UIElement.RaiseEventImpl(System.Win dows.DependencyObject, System.Windows.RoutedEventArgs)
at System.Windows.UIElement.RaiseEvent(System.Windows .RoutedEventArgs)
at System.Windows.BroadcastEventHelper.BroadcastEvent (System.Windows.DependencyObject, System.Windows.RoutedEvent)
at System.Windows.BroadcastEventHelper.BroadcastLoade dEvent(System.Object)
at MS.Internal.LoadedOrUnloadedOperation.DoWork()
at System.Windows.Media.MediaContext.FireLoadedPendin gCallbacks()
at System.Windows.Media.MediaContext.FireInvokeOnRend erCallbacks()
at System.Windows.Media.MediaContext.RenderMessageHan dlerCore(System.Object)
at System.Windows.Media.MediaContext.RenderMessageHan dler(System.Object)
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatch When(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.Invok eImpl()
at System.Windows.Threading.DispatcherOperation.Invok eInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at MS.Internal.CulturePreservingExecutionContext.Run( MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invok e()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(In tPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation( System.Object)
at System.Windows.Threading.ExceptionWrapper.Internal RealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatch When(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeIm pl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(Syste m.Windows.Interop.MSG ByRef)
at System.Windows.Threading.Dispatcher.PushFrameImpl( System.Windows.Threading.DispatcherFrame)
at System.Windows.Threading.Dispatcher.PushFrame(Syst em.Windows.Threading.DispatcherFrame)
at System.Windows.Application.RunDispatcher(System.Ob ject)
at System.Windows.Application.RunInternal(System.Wind ows.Window)
at System.Windows.Application.Run(System.Windows.Wind ow)
at Microsoft.VisualStudio.DesignTools.DesignerContrac t.Isolation.DesignerProcess.RunApplication()
at Microsoft.VisualStudio.DesignTools.DesignerContrac t.Isolation.DesignerProcess+DesignProcessViewProvi der.AppContainerDesignerProcessRun(System.String[])
at Microsoft.VisualStudio.DesignTools.DesignerContrac t.Isolation.DesignerProcess+DesignProcessViewProvi der+<>c__DisplayClass3_0.<applicationView_Activated>b__0()
at System.Threading.ThreadHelper.ThreadStart_Context( System.Object)
at System.Threading.ExecutionContext.RunInternal(Syst em.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()

[Pysco68]

Name der fehlerhaften Anwendung: XDesProc.exe, Version: 14.0.25420.1, Zeitstempel: 0x576859a4
Name des fehlerhaften Moduls: Windows.UI.Xaml.dll, Version: 10.0.14393.82, Zeitstempel: 0x57a55c76
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00403f45
ID des fehlerhaften Prozesses: 0x3374
Startzeit der fehlerhaften Anwendung: 0x01d201102012e2b8
Pfad der fehlerhaften Anwendung: C:\Users\yannic\AppData\Local\Microsoft\VisualStud io\14.0\Designer\ShadowCache\hvkx1pct.x25\ittqhglt .4w3\XDesProc.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\SYSTEM32\Windows.UI.Xaml.dll
Berichtskennung: 6600e69e-a079-479d-ba92-4cef7ad41daf
Vollständiger Name des fehlerhaften Pakets: 31f2d451-f06f-46c5-8649-99ce40790f21_1.0.0.0_x86_NorthAmerica_8wekyb3d8bbw e
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: Designer.App

---------------
Other indications:

Here's another guy running into the same issue: http://stackoverflow.com/questions/39166945/system-runtime-remoting-remotingexception-in-visual-studio-update-3-using-targus

The system:
- DELL XPS 13 9350
- Windows 10 Anniversary Update Full Patched
- Visual Studio 2015 Update 3
- Display Link Driver 8.0 M1 (installed after full uninstall using "customer remove tool", same errors with Windows 10 bundled driver installed before)
- Intel HD graphics 520 driver 20.19.15.4454 (most recent provided by DELL, issue persists with the latest directly from Intel)
- BIOS is up to date

[Hamurabi]

Hi!

Same problem is here.. I'm pulling my hair out.

After 1607, my computer lags, unstable, freeze sometime, WHEN I connected to my Dell D3100.

I replaced/reinstalled everything, and mostly I can accept this "preview" state, but...

I started developing a new UWP application to my company, and I CANNOT DO MY WORK when I docked. I have to design without docking station.

It's drive me crazy.

The errors exactly the same.

One more thing. If I started the XAML designer without the dock, xaml designer working fine, and connect to the dock, i can continue my work till I close the editor. After it the problem comes to live.

What a stupid upgrade. Same with 8.0 M0 and M2 DL drivers.

[Pysco68]

I am / was in the same situation where I couldn't work on my client's app (because of the dock!?!), so I went the entrepreneur's route and went buying another docking station (lucky me having the option to use a Thunderbolt3 docking station) the problems are gone for me. My conclusion: USB docks are as crappy as I was warned *sad*

Btw., if you own a Dell XPS13/15 with the TB3 port, you can fearlessly go an buy the relatively cheap HP TB3 dock (everything besides the "remote power switch" on the dock works)

Greetings from germany!

Btw. If DisplayLink wants me to try any available fix I might take the time to do so. But two days no answer is disapointing...

[Hamurabi]

I'm using a Lenovo T460P wich is a very interesing, and not a cheap model. I bought it a month ago. I don't know if it has TB port or not, but i'll check it.

But. EVERYTHING worked fine before 1607 and with DL 7.9.

Greetings from Hungary!

[AlbanRampon]

Psyco, this is a forum. You should have created a support ticket as flagged everywhere in this forum...
This issue has been reported to Microsoft under Sysdev bug 8742480. The anniversary update has a new graphics subsystem and we are using standard Windows feature now.
I don't know if being insulting is your usual way of doing business but being frustrated doesn't mean you must be unprofessional.

Microsoft does not recommend Windows 10 Anniversary Update for business and probably won't be before December.
Microsoft Current Branch for Business (CBB (https://technet.microsoft.com/en-us/itpro/windows/manage/introduction-to-windows-10-servicing?f=255&MSPPError=-2147217396)) is v1511.

I will post here if Microsoft needs more information to investigate this crash.

[ckruhs]

Same problem here!
There was no problem with the Designer before Anniversary Update.
Now I have to unplug the Dock to get the UWP XAML Designer to work.

Configuration:
- Win10 Anniversary Update (1607 OS Build 14393.0)
- VS2015 Update 3
- DELL XPS15 with Dock Dell D3100


Exception:

COMException: Error HRESULT E_FAIL has been returned from a call to a COM component.
StackTrace:
at Windows.UI.Xaml.DependencyObject.SetValue(Dependen cyProperty dp, Object value)
at Microsoft.VisualStudio.DesignTools.WindowsXamlDesi gner.InstanceBuilders.InlineInstanceBuilder.OnInit ialized(IInstanceBuilderContext context, ViewNode target, Object instance)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ClrObjectInstanceBuilder.Initialize(IIn stanceBuilderContext context, ViewNode viewNode, Boolean isNewInstance)
at Microsoft.VisualStudio.DesignTools.Platform.Instan ceBuilders.ViewNodeManager.InitializeInstance(IIns tanceBuilder builder, ViewNode viewNode, Boolean isNewInstance)

[Pysco68]

Hello Alban,

sorry for being rude, that was by no mean my intention. Regarding your advices, sadly, the downgrade route is no option for many of us, especially when clients want new anniversary update APIs used in their apps (especially the Cortana and HoloLens stuff).

I was really desperate about my dev env not working the way I expected it and lost nearly two weeks (including reinstalling the box as a last resort which did not work out) to that, which really is bad.

As I said, if you need my help I'll be happy to help you guys.

[AlbanRampon]

Good evening Pysco,

I have created the case to Microsoft and added the repro steps from the other people I had.
I'm flagging this to their graphics team in my (weekly) meeting with them tomorrow so my bug report is directed to the right team. I see it's passed the first stage and is now pending triage.

They may give me a script to gather information for them to investigate, but the detailed called stack provided may be sufficient.

Kind regards,
Alban

[ckruhs]

Hi,

the issue is also tracked at Visual Studio Connect:
https://connect.microsoft.com/VisualStudio/feedback/details/3101540

[AlbanRampon]

I've flagged this up to the Microsoft graphics team.
They don't see how this could be a DisplayLink problem and they are contacting the Visual Studio people to look into the bug I raised to them before.

[Hamurabi]

Thanks!

I hope it will be fixed before RS2.

:-)

[AlbanRampon]

Hello,
I will ask tomorrow but I would expect this to be linked to Visual Studio not dealing with this new OS feature correctly rather than the OS as otherwise all other applications would trip on the carpet the same way.

On VS Connect, MS asked for logs. I'm not sure anyone who has a reproduction has chimed in, yet, but I think it would be helpful to get this progressed.
https://connect.microsoft.com/VisualStudio/feedback/details/3101540
My ticket to the Microsoft Sysdev portal has not been looked at yet.

Kind regards,
Alban

[AlbanRampon]

Hello,
Our bug report has been handed over to the Visual Studio team. I've been told they should now have an internal reproduction of the crash to debug it.
MS graphics team did not see how DisplayLink driver could be the root cause and they explained to the VS team the change made in the new Windows 10. I understand that doesn't really help the immediate resolution of the problem, but we have assistance and interest from within MS, and that is always helpful to get a solution. DisplayLink also uses VS.
Kind regards,
Alban

[ckruhs]

Hi Alban,
Thanks for the update :-)

Best regards,
ckruhs

[AlbanRampon]

Hi everyone,

I have some news. A solution has been found and we are discussing how this can be rolled out.
Unfortunately, this is not a VS fix but an OS fix. If you could tell me how many people are affected in your organisations, this would be most helpful for me to explain why this should be serviced in build 14393 as opposed to wait until the next OS version.
I already got that DisplayLink is losing business over this as some of you have been buying the non-universal TB2 solution instead of the universal USB one...

Kind regards,
Alban

[ckruhs]

Hi Alban,

we are a Microsoft Gold Certified ISV Partner with 20+ developers.

Best regards
Carsten

[Hamurabi]

Hi!
We have only 6 developer. But it's currently stopped us to use DL things. We have to do our development with only one direct connected HDMI monitor instead of two.

[AlbanRampon]

Thank you all for the details!

Whilst this is going through, could you please try the following?
- Connect the dock and monitors as usual,
- Change the Windows Display Settings so the Primary is NOT a DisplayLink monitor (for instance the embedded panel of a laptop will do).
- Launch VS XAML.

Does VS crash in this condition?

[ckruhs]

Hi Alban,
Yes, the XAML Designer crashed with this seetings too.

ckruhs

[AlbanRampon]

There was an update on VS Connect (https://connect.microsoft.com/VisualStudio/feedback/details/3101540).
It now looks likes it's now being handled as an application issue as we first hinted.

"Posted by Mark [MSFT] on 23/09/2016 at 22:41
Thank you for reporting your issue with Visual Studio. This issue has now been fixed, and will be released with (the next update) to Visual Studio."

[AlbanRampon]

Latest update I got is that the message on VS Connect is incorrect.
This is not a VS issue but an OS issue.

In all cases MS tried, making the primary screen not an indirect display solves the issue.
Therefore, even if they are looking to address it, this is not an emergency for them and they want to make sure the change they make doesn't create collateral damage. This is under compatibility test and there is currently no delivery date.

[Hamurabi]

Thanks for the information.

In my case I continue my XAML development without DL. Pain.

But there are bigger problems with DL+8.0M2+1607. Huge lags, every time connect-disconnec-connect-disconnect DL device, my computer gets more laggy, mouse stopps, processor high. But, ONLY when it connected. looks like something fell out of sync. I have to restart several times a week for the normal performance.

[Hamurabi]

Is there any information?

[CMJ]

Latest update I got is that the message on VS Connect is incorrect.
This is not a VS issue but an OS issue.

In all cases MS tried, making the primary screen not an indirect display solves the issue.
Therefore, even if they are looking to address it....

For what it is worth, I have the exact same crash with my XPS15 and D3100 docking station. 2 external displays, 1 to the DisplayLink dock and 1 to the XPS15 HDMI output. (Lid closed on the laptop)
Making my non-displaylink display (HDMI, forced to the Nvidia graphics adapter in my case) the "Main display" solved it for me at least.

/M

[AlbanRampon]

Hello CMJ,

Yes. Because there is a relatively easy workaround, and because a lot of the surrounding code was changed causing compatibility risks, we have stopped pushing for the fix to be backported to RS1 builds.

I hope everyone agrees we don't want to take the risk of making it worse and potentially impacting wider features than "main display", accepting it as a temporary limitation until RS2 hits release stage.

Kind regards,
Alban

[Hamurabi]

Stupid design. Beta software. Untested code and upgrade. Angry customers.

"We stopped..... until RS2". Till 2017Q2???

Nice work. :-(

[AlbanRampon]

Hamurabi,

The bug that Microsoft has identified can be worked around by assigning the primary graphics card display as main display.
Would you rather risk it for the convenience of have the systray on another display? I would not and I am being transparent about it.
If you have another issue with Visual Studio XAML Designer, you might wish to direct your anger to the people who can solve it by creating a support ticket to the Visual Studio team.

Regards,
Alban