Home Dashboard Directory Help
Search

SSMS 2012 SP1 Crashes after locking & unlocking workstation by RichLawley


Status: 

Closed


2
0
Sign in
to vote
Type: Bug
ID: 773511
Opened: 12/5/2012 2:11:16 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

Last week I updated SQL Server 2012 SP1. At the same time I also updated Visual Studio 2012 to Update 1, so I have no idea if the two are related. Now, I have a consistently reproducible problem whereby SQL Server Management Studio 2012 crashes every time I lock and unlock my workstation. This happens on two separate workstations, but both have similar software installed on them. The crash occurs in wpfgfx_v0400.dll by the looks of things.

The crash occurs on the main window. If I open SSMS and leave it on the "Connect to Server" dialog, I can lock and unlock the workstation, but the crash will only happen once the dialog is dismissed. It also appears to be related to mouse events - if I unlock the workstation with the mouse away from the window, I can move the mouse over the background areas of the window with no problem, but as soon as I touch a UI element that reacts to hover, the crash occurs. If I left a query window open and active, it crashes immediately on unlock, even with the mouse away.

Most of the time I'd been noticing VS automatically restart itself (which implies the crash happens when the workstation is locked, as it had already restarted by the time I returned to my desk).

Fault bucket 3280890008, type 1
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: Ssms.exe
P2: 2011.110.3000.0
P3: 5081c1cd
P4: wpfgfx_v0400.dll
P5: 4.0.30319.17929
P6: 4ffa7c81
P7: c0000005
P8: 000204c7
P9:
P10:

I managed to attach a VS debugger to get some stack frame information if that's any help:

>    wpfgfx_v0400.dll!CDisplaySet::ReadDisplayModes() + 0x17 bytes    
    wpfgfx_v0400.dll!CDisplaySet::Init() + 0x5a bytes    
    wpfgfx_v0400.dll!CDisplayManager::CreateNewDisplaySet() + 0x40 bytes    
    wpfgfx_v0400.dll!CDisplayManager::DangerousGetLatestDisplaySet() + 0x3ebd bytes    
    wpfgfx_v0400.dll!CDisplaySet::DangerousHasDisplayStateChanged() + 0x72835 bytes    
    wpfgfx_v0400.dll!CMILFactory::UpdateDisplayState() + 0x34 bytes    
    wpfgfx_v0400.dll!CComposition::ProcessComposition() + 0x2c bytes    
    wpfgfx_v0400.dll!CComposition::Compose() + 0x42 bytes    
    wpfgfx_v0400.dll!CPartitionThread::RenderPartition() + 0x1b bytes    
    wpfgfx_v0400.dll!CPartitionThread::Run() + 0x2d bytes    
    wpfgfx_v0400.dll!CPartitionThread::ThreadMain() + 0x1c bytes    
    kernel32.dll!76cd33aa()     
    [Frames below may be incorrect and/or missing, no symbols loaded for kernel32.dll]    
    ntdll.dll!779e9ef2()     
    ntdll.dll!779e9ec5()     

Component version Info copied from SSMS:

Microsoft SQL Server Management Studio                        11.0.3000.0
Microsoft Data Access Components (MDAC)                        6.1.7601.17514
Microsoft MSXML                        3.0 6.0
Microsoft Internet Explorer                        9.10.9200.16438
Microsoft .NET Framework                        4.0.30319.17929
Operating System                        6.1.7601
Details
Sign in to post a comment.
Posted by Microsoft on 2/7/2013 at 9:43 PM
Hi!, thanks for writing in to Microsoft.

We took a look at this bug recently and we are not able to reproduce it in SSMS 2012 RTM and are closing it as ‘no repro’. We recommend you try this scenario again on a clean installation of SSMS 2012.

Another suggestion is to turn off "Use hardware graphics acceleration..." in "Tools...Options" in SSMS 2012 and let us know if you still have this problem.

Regards,
Sanjay Nagamangalam, SQL Server Manageability
Posted by RichLawley on 12/10/2012 at 3:06 AM
Further information:

Both of my affected systems are fully up-to-date according to Microsoft Update. They are completely different hardware - one has an ATI 5850, the other an NVidia GT520, and both have up-to-date stable graphics drivers. I uninstalled SP1 from SQL 2012 but the crash still occurs.
Posted by FryGuy1013 on 12/6/2012 at 5:16 PM
This happens for me suddenly as well with the same stack trace in my WPF apps. I did a create new WPF application in visual studio 2010 with no changes to the template, and can reproduce it with the same steps (ctrl-alt-delete, cancel, then click on the application).
Sign in to post a workaround.
File Name Submitted By Submitted On File Size  
ssms-dump.zip (restricted) 12/10/2012 -