SystemSetting.exe Crash when click `Printer and Scanner`

[mingkuang-Chuyu]

OS: 10.0.22631.2861 x64
UWPSpy : 1.3.0.0

Recording file: Recording-SystemSettingCrash.zip

thanks

[m417z]

I can reproduce it.

Stowed exception stack trace

0:004> !pde.dse
Stowed Exception Array @ 0x000001a37a707b60

Stowed Exception #1 @ 0x000001a37ea19088
	0x80070057 (FACILITY_WIN32 - Win32 Undecorated Error Codes): E_INVALIDARG - One or more arguments are not valid

	Stack	 : 0x1a37ea18070
		7ff80196a872 Windows_UI_Xaml!CDependencyObject::SetEffectiveValue+0x1d82
		7ff801a952a2 Windows_UI_Xaml!CDependencyObject::UpdateEffectiveValue+0x232
		7ff801a94632 Windows_UI_Xaml!CUIElement::SetValue+0x272
		7ff801a92b5c Windows_UI_Xaml!CFrameworkElement::SetValue+0xac
		7ff801a91a13 Windows_UI_Xaml!CBorder::SetValue+0x43
		7ff801a50db3 Windows_UI_Xaml!DirectUI::DependencyObject::SetValueCore+0x44b
		7ff8019135bc Windows_UI_Xaml!DirectUI::DependencyObject::SetValueExpression+0x3f8
		7ff801b790fc Windows_UI_Xaml!DirectUI::TemplateBindingExpression::SetTemplateBinding+0x188
		7ff801b77d16 Windows_UI_Xaml!CControl::SubscribeToPropertyChanges+0x266
		7ff8019cb1ca Windows_UI_Xaml!CFrameworkElement::SetTemplateBinding+0x7a
		7ff801b00674 Windows_UI_Xaml!BinaryFormatObjectWriter::SetTemplateBindingOnCurrentInstance+0x1cc
		7ff8019f6ad8 Windows_UI_Xaml!BinaryFormatObjectWriter::WriteNode+0x1788
		7ff8019f484f Windows_UI_Xaml!CTemplateContent::LoadXbfVersion2+0x177
		7ff801bcaa6f Windows_UI_Xaml!CFrameworkTemplate::LoadContent+0x3ef
		7ff801c8beda Windows_UI_Xaml!CControlTemplate::LoadContent+0x9a
		7ff8019378a2 Windows_UI_Xaml!CFrameworkElement::ApplyTemplate+0x112
		7ff801a99424 Windows_UI_Xaml!CFrameworkElement::InvokeApplyTemplate+0x180
		7ff801fc9b1e Windows_UI_Xaml!CFrameworkElement::MeasureCore+0xde
		7ff801a9bb05 Windows_UI_Xaml!CUIElement::MeasureInternal+0x1c1
		7ff80192d97b Windows_UI_Xaml!CUIElement::Measure+0x37b
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff80192dac4 Windows_UI_Xaml!CUIElement::Measure+0x4c4
		7ff801a9db70 Windows_UI_Xaml!CLayoutManager::UpdateLayout+0x3c8
		7ff8019bb8be Windows_UI_Xaml!CCoreServices::NWDrawTree+0x91e
		7ff801a14419 Windows_UI_Xaml!CXcpBrowserHost::OnTick+0x199
		7ff801db0b39 Windows_UI_Xaml!CXcpDispatcher::Tick+0x129
		7ff801db0834 Windows_UI_Xaml!CXcpDispatcher::OnReentrancyProtectedWindowMessage+0x44
		7ff8019fbeee Windows_UI_Xaml!CXcpDispatcher::WindowProc+0x13e
		7ff801da63c6 Windows_UI_Xaml!CXcpDispatcher::MessageTimerCallbackStatic+0x76
		7ff805fb430d CoreMessaging!CFlat::SehSafe::Execute<<lambda_654db17c35df07198786f0867aa10de6> >+0x21
		7ff805fb356b CoreMessaging!Microsoft::CoreUI::Dispatch::TimeoutHandler::ImportAdapter$+0x6b
		7ff806003cc2 CoreMessaging!Microsoft::CoreUI::Dispatch::TimeoutManager::Callback_OnDispatch+0x102
		7ff805fb6fc4 CoreMessaging!Microsoft::CoreUI::Dispatch::Dispatcher::Callback_DispatchLoop+0x334
		7ff805fb6b5d CoreMessaging!Microsoft::CoreUI::Dispatch::EventLoop::Callback_RunCoreLoop+0x11d
		7ff805fc52bd CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::DrainCoreMessagingQueue+0x21d
		7ff805fc594d CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::OnUserDispatch+0x85
		7ff805fc55e8 CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::DoWork+0x188
		7ff805fc401b CoreMessaging!Microsoft::CoreUI::Dispatch::UserAdapter::WindowProc+0x12b
		7ff80c5ae83a user32!UserCallWinProcCheckWow+0x41a
		7ff80c5ae11c user32!DispatchClientMessage+0x9c
		7ff80c5daca3 user32!_fnDWORD+0x33
		7ff80d265f94 ntdll!KiUserCallbackDispatcherContinue+0x0
		7ff80a6b12b4 win32u!NtUserPeekMessage+0x14
		7ff80c5cc00f user32!_PeekMessage+0x3f
		7ff80c5cbf98 user32!PeekMessageW+0x168
		7ff802b70e3e Windows_UI!Windows::UI::Core::CDispatcher::ProcessMessage+0xbe
		7ff802b70b00 Windows_UI!Windows::UI::Core::CDispatcher::WaitAndProcessMessagesInternal+0xb0
		7ff802b6fe24 Windows_UI!Windows::UI::Core::CDispatcher::ProcessEvents+0x124
		7ff801f78082 Windows_UI_Xaml!CJupiterWindow::RunCoreWindowMessageLoop+0x42
		7ff801fbe5ba Windows_UI_Xaml!CJupiterControl::RunMessageLoop+0x2e
		7ff801fbe64c Windows_UI_Xaml!DirectUI::DXamlCore::RunMessageLoop+0x24
		7ff801482d45 twinapi_appcore!Windows::ApplicationModel::Core::CoreApplicationView::Run+0x35
		7ff8013f9bf7 twinapi_appcore!<lambda_42789f15e44e28e8f1176a4d3f326103>::operator()+0xa7
		7ff80c98805a SHCore!_WrapperThreadProc+0x15a
		7ff80c19e8d7 kernel32!BaseThreadInitThunk+0x17
		7ff80d19c5dc ntdll!RtlUserThreadStart+0x2c

The crash doesn't happen in/around UWPSpy code, which makes me believe that it's caused by the Windows XAML diagnostics mechanism which UWPSpy uses.