Forum Discussion
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...
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:
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: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).
- This is a brand new computer, CPU is not the problem. We are seeing this on multiple machines in our company
