Visual Studio 17.14.13 crashes
- Dominant language
- C#
- Stars
- 7.7k
- Forks
- 1.3k
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 61
Description
_This issue has been moved from [a ticket on Developer Community](https://developercommunity.visualstudio.com/t/Visual-Studio-171413-crashes/10961404)._
---
[severity:It's more difficult to complete my work]
I get recurring crashes of Visual Studio 17.14.13 (roughly once or twice each hour).
I don't have a reliable repro. My workload is dotnet 8 C# development (net8.0-windows target). Currently test driven development switching between running Unit tests (NUnit 4.3.2 with NUnit3TestAdapter 5.0.0) and writing code.
In event viewer I have the following .Net Runtime error after each crash:
```
Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.ComponentModel.Win32Exception
at MS.Internal.PointUtil.ScreenToClient(System.Windows.Point, System.Windows.PresentationSource)
at System.Windows.Controls.PopupControlService+ConvexHull.ContainsMousePoint()
at System.Windows.Controls.PopupControlService.MouseHasLeftSafeArea()
at System.Windows.Controls.PopupControlService.OnMouseMove(System.Windows.IInputElement)
at System.Windows.Controls.PopupControlService.OnPostProcessInput(System.Object, System.Windows.Input.ProcessInputEventArgs)
at System.Windows.Input.InputManager.RaiseProcessInputEventHandlers(System.Windows.Input.ProcessInputEventHandler, System.Windows.Input.ProcessInputEventArgs)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
at System.Windows.Input.MouseDevice.Synchronize()
at System.Windows.Input.MouseDevice.PostProcessInput(System.Object, System.Windows.Input.ProcessInputEventArgs)
at System.Windows.Input.InputManager.RaiseProcessInputEventHandlers(System.Windows.Input.ProcessInputEventHandler, System.Windows.Input.ProcessInputEventArgs)
at System.Windows.Input.InputManager.ProcessStagingArea()
at System.Windows.Input.InputManager.ProcessInput(System.Windows.Input.InputEventArgs)
at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport)
at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32)
at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef)
at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, 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.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
```
and the following Application Error:
```
Faulting application name: devenv.exe, version: 17.14.36414.22, time stamp: 0x689e6317
Faulting module name: KERNELBASE.dll, version: 10.0.22621.5697, time stamp: 0x591c8970
Exception code: 0xe0434352
Fault offset: 0x00000000000600ac
Faulting process id: 0x0x8460
Faulting application start time: 0x0x1DC1E2EE8E5CF00
Faulting application path: C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 12ca991f-f7a0-490e-aaf8-b4ea03f470b4
Faulting package full name:
Faulting package-relative application ID:
```
---
### Original Comments
#### Feedback Bot on 8/9/2025, 01:35 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Contributor guide
Assessment
This issue has not been assessed yet.