Forum Discussion

Tracer1808's avatar
Tracer1808
Copper Contributor
Jun 23, 2024

SSMS 20.1 constantly crashing (suspecting .NET issue)

I cannot make SSMS to work. After installing SSMS 20.1 (or any other version) it constantly crashes. I get various errors such as:

  • Cannot create the window
  • Exception has been thrown by the target of an invocation
  • JIT compiler encountered an internal limitation
  • Crashing after the splash screen without any error message
  • Losing profile data
  • Crashing after login
  • Crashing after various operations (SELECT TOP 1000 from the context menu etc., when starting various dialogs etc.)

Examining the event viewer I suspect a .NET issue. Some examples:

Faulting application name: Ssms.exe, version: 20.1.10.0, time stamp: 0x660d7b89
Faulting module name: clrjit.dll, version: 4.8.9241.0, time stamp: 0x6604a357
Exception code: 0xc0000005
Fault offset: 0x00004964
Faulting process id: 0x3b28
Faulting application start time: 0x01dac5542e795318
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server Management Studio 20\Common7\IDE\Ssms.exe
Faulting module path: **C:\Windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll**
Report Id: 9cf7bd0e-2bdc-48f9-ac31-575919dab13a
Faulting package full name: 
Faulting package-relative application ID: 
Application: Ssms.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at System.Windows.Media.Visual.GetDpi()
   at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size)
   at System.Windows.UIElement.Measure(System.Windows.Size)
   at System.Windows.Interop.HwndSource.SetLayoutSize()
   at System.Windows.Interop.HwndSource.set_RootVisualInternal(System.Windows.Media.Visual)
   at System.Windows.Interop.HwndSource.set_RootVisual(System.Windows.Media.Visual)
   at System.Windows.Window.SetRootVisual()
   at System.Windows.Window.SetRootVisualAndUpdateSTC()
   at System.Windows.Window.SafeCreateWindowDuringShow()
   at System.Windows.Window.ShowHelper(System.Object)
   at System.Windows.Window.Show()
   at Microsoft.VisualStudio.PlatformUI.WpfHostPrivate+UIWPFElementContainer.ShowWindow()

I also noticed that if I am unsuccessful the first time I try to run SSMS, then I'm doomed until I restart and try again.

I already tried the following:

  • I reinstalled my PC few times. Tried both with Windows 10 and Windows 11 fully updated, but still no luck when it comes to running SSMS correctly.
  • I tried .NET Framework repair tool. No luck.
  • I tried repairing SSMS. No luck.
  • I tried uninstalling and installing .NET (Windows features On/Off). No luck. On a manual installation it says a current/newer version is already installed.

Everything was fine until few months ago. Then SSMS started crashing. I suspect some Windows update may have caused this because now it doesn't work even on a freshly installed and updated PC.

 

Any solution?

 
sql server management studio
ssms
  • markmoore505's avatar
    markmoore505
    Copper Contributor
    Jul 24, 2024

    Tracer1808 

     

    I have been having this issue a lot lately.

    Faulting application name: Ssms.exe, version: 20.2.30.0, time stamp: 0x66893cc8
Faulting module name: clr.dll, version: 4.8.9256.0, time stamp: 0x665a83c0
Exception code: 0xc00000fd
Fault offset: 0x0002efa0
Faulting process id: 0x0x63DC
Faulting application start time: 0x0x1DADDF043475F82
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server Management Studio 20\Common7\IDE\Ssms.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: 13822468-051f-402e-a8f6-30675df0ecac
Faulting package full name: 
Faulting package-relative application ID:

     

     

     

     

     

    • markmoore505's avatar
      markmoore505
      Copper Contributor
      Sep 06, 2024

      Still no response from anyone on this. Here we are a few months later, a new version of VS and still having the same issues

       

      Faulting application name: Ssms.exe, version: 20.2.30.0, time stamp: 0x66893cc8
Faulting module name: clr.dll, version: 4.8.9261.0, time stamp: 0x667a1900
Exception code: 0xc00000fd
Fault offset: 0x0045942a
Faulting process id: 0x0x999C
Faulting application start time: 0x0x1DB0049FB1387AD
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server Management Studio 20\Common7\IDE\Ssms.exe
Faulting module path: C:\Windows\Microsoft.NET\Framework\v4.0.30319\clr.dll
Report Id: 72476ceb-c823-4371-8293-beb9d0a0ddee
Faulting package full name: 
Faulting package-relative application ID:
      • Tracer1808's avatar
        Tracer1808
        Copper Contributor
        Sep 06, 2024

        markmoore505 Hi,

        I have resolved my issue after CPU replacement. I have Intel 13900KF, and considering the overvoltage issue that was destroying Intel CPUs it seams my CPU was damaged over time and started crashing SSMS and later some other apps as well. So, if you have 13th or 14th gen Intel CPU, this might be the problem and you should replace the CPU (hopefully is under warranty).