SSMS 18.12.1间歇性崩溃求助：空闲时自动重启问题排查

问题现象 #

• 多名员工遭遇SSMS周期性自动重启，覆盖多个SSMS版本，VPN/本地网络环境均会发生
• 今日故障加剧，约每20分钟重启一次（记录时间：09:47、09:24、08:51），无固定规律，部分时段更频繁
• 触发场景：SSMS处于空闲状态时突然重启，非长查询或用户操作导致，无错误提示，重启后暂时恢复正常
• 环境排除：已尝试重装不同版本SSMS、清理SSMS相关注册表项，问题依旧；多台设备、多个账号均出现故障，排除单设备/账号异常
• 设备信息：HP Laptop（AMD Ryzen 5 Pro 5650），内存15.3GB，当前仅占用11GB
• 怀疑方向：环境中运行的Crowdstrike可能存在干扰，但未确认

错误日志信息 #

Windows错误报告日志 #

Fault bucket 1344123028005871426, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Ssms.exe
P2: 2019.150.18424.0
P3: 62b10e6f
P4: PresentationCore
P5: 4.8.4579.0
P6: 631946f9
P7: 4834
P8: 0
P9: System.OutOfMemoryException
P10:

Attached files:
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER6C88.tmp.mdmp
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7265.tmp.WERInternalMetadata.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7285.tmp.xml
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER7283.tmp.csv
\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER72E2.tmp.txt

These files may be available here:
\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Ssms.exe_43575f69ad1e116788ab6f8aefadf1dd8e3c827e_ec2160f4_4616dc68-1cbc-47cd-aa89-c03e560e8927

Analysis symbol:
Rechecking for solution: 0
Report Id: e2d6335c-1bf1-4113-bbb2-fcc29a8aafee
Report Status: 268435456
Hashed bucket: 6dbc69c42400d68b52a748c5c2b65f42
Cab Guid: 0

事件查看器中的应用程序错误 #

Faulting application name: Ssms.exe, version: 2019.150.18424.0, time stamp: 0x62b10e6f
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2251, time stamp: 0x0d929ca0
Exception code: 0xe0434352
Fault offset: 0x0012e062
Faulting process id: 0xe918
Faulting application start time: 0x01d90fdbb55ea3f9
Faulting application path: C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: e2d6335c-1bf1-4113-bbb2-fcc29a8aafee
Faulting package full name:
Faulting package-relative application ID:

事件查看器中的.NET运行时错误 #

Application: Ssms.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.OutOfMemoryException
at MS.Internal.PointUtil.FromPoint(System.Windows.Point)
at MS.Internal.PointUtil.ScreenToClient(System.Windows.Point, System.Windows.PresentationSource)
at System.Windows.Input.MouseDevice.GetPosition(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.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)

WER文件内容 #

Version=1
EventType=CLR20r3
EventTime=133155113372246876
ReportType=2
Consent=1
UploadTime=133155113388966378
ReportStatus=268435456
ReportIdentifier=4616dc68-1cbc-47cd-aa89-c03e560e8927
IntegratorReportIdentifier=e2d6335c-1bf1-4113-bbb2-fcc29a8aafee
Wow64Host=34404
Wow64Guest=332
NsAppName=Ssms.exe
OriginalFilename=SSMS.EXE
AppSessionGuid=0000e918-0001-002a-f9a3-5eb5db0fd901
TargetAppId=W:0006eb54dba05bdf3918169dc524753b6d1a00000904!0000b8c28928d48e0ba90f7f75a3bcfe48b86650103f!Ssms.exe
TargetAppVer=2022//06//21:00:18:55!b3643!Ssms.exe
BootId=4294967295
ServiceSplit=49545216
TargetAsId=14655
IsFatal=1
EtwNonCollectReason=4
Response.BucketId=6dbc69c42400d68b52a748c5c2b65f42
Response.BucketTable=5
Response.LegacyBucketId=1344123028005871426
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=Ssms.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=2019.150.18424.0
Sig[2].Name=Problem Signature 03
Sig[2].Value=62b10e6f
Sig[3].Name=Problem Signature 04
Sig[3].Value=PresentationCore
Sig[4].Name=Problem Signature 05
Sig[4].Value=4.8.4579.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=631946f9
Sig[6].Name=Problem Signature 07
Sig[6].Value=4834
Sig[7].Name=Problem Signature 08
Sig[7].Value=0
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.OutOfMemoryException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=10.0.19044.2.0.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=2beb
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=2beba6fb4680d73a8c78ca7c24ccdb46
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=fdae
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=fdae5d07ca7a3e113815289fb726fabc
UI[2]=C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe
LoadedModule[0]=C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\Ssms.exe
LoadedModule[1]=C:\WINDOWS\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\WINDOWS\System32\KERNEL32.DLL
LoadedModule[3]=C:\WINDOWS\System32\KERNELBASE.dll
LoadedModule[4]=C:\WINDOWS\System32\USER32.dll
LoadedModule[5]=C:\WINDOWS\System32\win32u.dll
LoadedModule[6]=C:\WINDOWS\SYSTEM32\MSVCP120.dll
LoadedModule[7]=C:\WINDOWS\SYSTEM32\MSVCR120.dll
LoadedModule[8]=C:\WINDOWS\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.1110_none_a8625c1886757984\COMCTL32.dll
LoadedModule[9]=C:\WINDOWS\System32\GDI32.dll
LoadedModule[10]=C:\WINDOWS\System32\gdi32full.dll
LoadedModule[11]=C:\WINDOWS\System32\msvcrt.dll
LoadedModule[12]=C:\WINDOWS\System32\msvcp_win.dll
LoadedModule[13]=C:\WINDOWS\System32\ucrtbase.dll
LoadedModule[14]=C:\WINDOWS\System32\ADVAPI32.dll
LoadedModule[15]=C:\WINDOWS\System32\sechost.dll
LoadedModule[16]=C:\WINDOWS\System32\RPCRT4.dll
LoadedModule[17]=C:\WINDOWS\System32\IMM32.DLL
LoadedModule[18]=C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\ShellExtensions\Platform\appenvstub.dll
LoadedModule[19]=C:\WINDOWS\System32\CRYPT32.dll
LoadedModule[20]=C:\WINDOWS\System32\SHELL32.dll
LoadedModule[21]=C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\VCRUNTIME140.dll
LoadedModule[22]=C:\WINDOWS\System32\ole32.dll
LoadedModule[23]=C:\WINDOWS\System32\combase.dll
LoadedModule[24]=C:\WINDOWS\System32\OLEAUT32.dll
LoadedModule[25]=C:\WINDOWS\System32\SHLWAPI.dll
LoadedModule[26]=C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\MSVCP140.dll
LoadedModule[27]=C:\WINDOWS\SYSTEM32\VERSION.dll
LoadedModule[28]=C:\WINDOWS\WinSxS\x86_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.19041.2251_none_d9513b1fe1046fc7\gdiplus.dll
LoadedModule[29]=C:\WINDOWS\SYSTEM32\mscoree.dll
LoadedModule[30]=C:\WINDOWS\System32\ScriptControl32_16207.dll
LoadedModule[31]=C:\WINDOWS\System32\bcrypt.dll
LoadedModule[32]=C:\WINDOWS\System32\bcryptPrimitives.dll
LoadedModule[33]=C:\WINDOWS\System32\SHCORE.DLL
LoadedModule[34]=C:\WINDOWS\SYSTEM32\windows.storage.dll
LoadedModule[35]=C:\WINDOWS\SYSTEM32\Wldp.dll
LoadedModule[36]=C:\WINDOWS\SYSTEM32\kernel.appcore.dll
LoadedModule[37]=C:\WINDOWS\system32\uxtheme.dll
LoadedModule[38]=C:\WINDOWS\System32\clbcatq.dll
LoadedModule[39]=C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
LoadedModule[40]=C:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\msenv.dll
LoadedModule[41]=C:\WINDOWS\SYSTEM32\UIAutomationCore.DLL
LoadedModule[42]=C:\WINDOWS\SYSTEM32\DWrite.dll
LoadedModule[43]=C:\WINDOWS\SYSTEM32\d3d9.dll
LoadedModule[44]=C:\WINDOWS\SYSTEM32\USP10.dll

排查建议 #

• 验证Crowdstrike干扰：在合规前提下，临时在单台测试机禁用Crowdstrike，观察重启是否停止；同时检查Crowdstrike规则，确认是否拦截SSMS或PresentationCore.dll相关进程。
• 切换64位SSMS：当前使用的是x86版本SSMS，存在2GB内存限制，即使系统内存剩余也可能触发OutOfMemoryException，尝试安装并使用64位SSMS（2019及后续版本支持），监控内存占用变化。
• 修复.NET Framework与系统文件：运行sfc /scannow和DISM /Online /Cleanup-Image /RestoreHealth命令修复系统文件；修复.NET Framework 4.8，确保PresentationCore.dll等组件正常。
• 禁用SSMS后台功能：关闭SSMS的自动刷新、IntelliSense自动完成、第三方扩展，仅保留核心功能，排查是否是后台任务导致内存泄漏。
• 捕获内存转储分析：使用DebugDiag工具捕获SSMS崩溃时的内存转储，分析是否存在内存泄漏点；或用Process Monitor跟踪SSMS的内存分配情况。
• 排查其他进程注入：除Crowdstrike外，检查其他安全软件、桌面增强工具是否存在进程注入行为，逐一禁用排查。

内容的提问来源于stack exchange，提问作者PiperKeith