SSMS 18.12.1 crashing intermittently - ssms

A number of us at my job have had issues with SSMS restarting periodically throughout the day. This has happened across a number of SSMS versions and over VPN connections as well as on PCs on the local network. This morning is particularly bad - it's happening about about 20 minute intervals - 0947, 0924, 0851. Some days are worse than others.
What typically happens is that SSMS will be sitting there idle and - just restart. This isn't in response to a long query being executed or any obvious user activity. No error message gets displayed and SSMS typically restarts.
I have a suspicion that this is due to Crowdstrike being run in our environment but have had a challenge pinning this down with complete certainty.
It's worth mentioning that I've reinstalled various versions, multiple times and have done things like delete all references to SSMS in the registry in an attempt to get a clean build. The fact that this has happened across multiple machines and multiple accounts makes me think this isn't down to just a dodgy install.
It's also worth mentioning that my machine is HP Laptop (AMD Ryzen 5 Pro 5650) with 15.3GB of RAM, only 11GB of which area currently in use.
Has anybody else come across this?
`
The Windows Error Reporting log entry is as follows: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
We get an Application Error in the Event Viewer as follows
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 Runtime Error from Event Viewer
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)
**The referenced .WER file's contents:**
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
We're not really "doing" anything - SSMS is simply sitting idle.

Related

In Windows 7, a process started with CreateProcessAsUser by a windows service with a local system account crashes

In Windows 7, a process started with CreateProcessAsUser by a windows service with a local system account crashes, but the same process started manually runs fine. The CreateProcessAsUser functionality is in a separate COM component [64 bit C++ dll], and the windows service [dot net 4.6.1] has platform target [Any CPU]. The process does not write anything to the event log either, suggesting that no code is executed, and it crashes immediately. This code works perfectly in windows 10.
I tried to attach to the process but it ends too soon to do anything. I do get a message "Module not found" , suggesting that it doesnt find a library. But I cant figure out which one. I gave it all the libraries it needs, which can be seen by the fact that the program runs ok when started manually from the same folder. I also tried to specify the startup folder in the function CreateProcessAsUser, but there was no difference, but I think it starts in the correct folder by default [where it is located]
I found the following link on SO
Why is this process crashing as soon as it is launched?
But it did not help either. ProcMon does not show where a module was not found [It says PATH NOT FOUND if I remove a known module]
The process exit status is -1066598274
and the stack trace is
0 ntoskrnl.exe RtlNtStatusToDosError + 0x1086 0xfffff8000712f206 C:\Windows\system32\ntoskrnl.exe
1 ntoskrnl.exe RtlCopySidAndAttributesArray + 0x1789 0xfffff8000714b0d9 C:\Windows\system32\ntoskrnl.exe
2 ntoskrnl.exe RtlNtStatusToDosError + 0x1538 0xfffff8000712f6b8 C:\Windows\system32\ntoskrnl.exe
3 ntoskrnl.exe KeSynchronizeExecution + 0x3a23 0xfffff80006e75e53 C:\Windows\system32\ntoskrnl.exe
The event viewer shows the following information
Faulting application name: BizBrainAgentPluginHost.exe, version: 1.0.0.0, time stamp: 0x5b88084d
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b8479b
Exception code: 0xc06d007e
Fault offset: 0x0000000000009e5d
Faulting process id: 0x484
Faulting application start time: 0x01d440746491e037
Faulting application path: C:\Program Files\Avinashi Ventures Pvt Ltd\myTallyApp Agent\BizBrainAgentPluginHost.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: a2f39c97-ac67-11e8-94f1-0023ae9747d0
Thanks

System.Runtime.InteropServices.COMException | vb.net

I know this question has been answered many times but I have tried all previous suggested resolution.
1.) The target CPU is x86
2.) I have registered the ocx and dll files
The application is working fine on old machines (all OS) but not on new images.
Here is the log :
Framework Version: v4.0.30319 Description: The process was terminated
due to an unhandled exception. Exception Info:
System.Runtime.InteropServices.COMException at
System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(System.Guid
ByRef, System.Object, Int32, System.Guid ByRef) at
System.Windows.Forms.AxHost.CreateWithLicense(System.String,
System.Guid) at
System.Windows.Forms.AxHost.CreateInstanceCore(System.Guid) at
System.Windows.Forms.AxHost.CreateInstance() at
System.Windows.Forms.AxHost.GetOcxCreate() at
System.Windows.Forms.AxHost.TransitionUpTo(Int32) at
System.Windows.Forms.AxHost.CreateHandle() at
System.Windows.Forms.Control.CreateControl(Boolean) at
System.Windows.Forms.Control.CreateControl(Boolean) at
System.Windows.Forms.AxHost.EndInit() at
Restaurant.frmMain.InitializeComponent() at
Restaurant.frmMain..ctor()
Exception Info: System.InvalidOperationException at
Restaurant.My.MyProject+MyForms.Create__Instance__[System.__Canon,
mscorlib, Version=4.0.0.0, Culture=neutral,
PublicKeyToken=b77a5c561934e089] at
Restaurant.frmMain.Main()
Here is how I am registering the files :
C:\Windows\Microsoft.NET\Framework\v2.0.50727\Caspol -q -machine -addgroup 1 -url file://C:/xyz/* FullTrust -name "V Drive"
regsvr32 c:\xyz\crystl32.ocx
regsvr32 c:\xyz\MSCOMCT2.OCX
regsvr32 c:\xyz\MSDATGRD.OCX
regsvr32 c:\xyz\cpeaut32.dll
regsvr32 c:\xyz\msstdfmt.dll
Crystal reports runtime engine for .NET 4 framework in installed on the system (both x86 and x64).
I had this issue once.
I ran Visual Studio as administrator.
Also make sure you know which setting your platform is for the build: AnyCPU, x86, x64
For you its x86 so try using AnyCPU!
Try debugging the issue
I read an article from Microsoft which said you can debug where this exception is occurring by:
Debug > Exceptions... and use the Find option to locate System.Runtime.InteropServices.COMException. Tick the option to break when it's thrown and then debug your application.

Visual Studio 2015 Community Crashes on Startup

I've been using VS 2015 Community Edition without any issues for the past 2 months. Then one day it decided to crash (I wasn't doing anything when it crashed). After I tried starting it up again, it only gets to the home-page screen then crashes. No project is being opened, it crashes on its own.
Things I tried with no success:
Repairing the install.
Uninstalling then Reinstalling.
Running in /safemode (still crashes in safemode!)
I don't have anything custom installed (especially after the clean install).
At this point my only hope is re-installing windows (running Windows 7), and hoping the problem goes away then. Any other ideas, things I can try?
Here's the log dump from starting VS2015 in safemode (I wanted to post the contents here, but they exceed the allowed post size):
http://wikisend.com/download/447654/vs_log.txt
I did search through the log for error tags, and found the following instances:
<entry>
<record>2196</record>
<time>2016/03/16 19:49:43.330</time>
<type>Error</type>
<source>UserConnection</source>
<description>Failed to get IAccountManager from service provider.</description>
</entry>
<entry>
<record>2416</record>
<time>2016/03/16 19:49:44.273</time>
<type>Error</type>
<source>Extension Manager</source>
<description>Extension will not be loaded because an extension with the same ID &apos;Microsoft.Dev14.VsixTemplatesPackage.V2.443cca91-ec20-41e5-a165-f28e56b89650&apos; is already loaded at C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\EXTENSIONS\OZPNHXDR.G5H\...</description>
<path>C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\EXTENSIONS\NUGETIFIEDEXTENSIBILITYTEMPLATES\</path>
</entry>
<entry>
<record>2417</record>
<time>2016/03/16 19:49:44.274</time>
<type>Error</type>
<source>Extension Manager</source>
<description>Extension will not be loaded because an extension with the same ID &apos;Microsoft.VisualStudio.TeamFoundation.TeamExplorer.Extensions&apos; is already loaded at C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\EXTENSIONS\MKTRGVMI.4Y3\...</description>
<path>C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\COMMONEXTENSIONS\MICROSOFT\TEAMFOUNDATION\TEAM EXPLORER\</path>
</entry>
EDIT 1:
Following magicandre1981's advice I ran procdump, but the resulting file is 0.5 GB, so it's too much to upload. Here's a screenshot from the dump file. The exception seems to be 0xE0434352.
EDIT 2:
I looked at Event Viewer, and found the following Error related to the crash. Looks like the exception is caused by Microsoft.VisualStudio.Services.Experimentation.FlightsClient:
Application: devenv.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at Microsoft.VisualStudio.Services.Experimentation.FlightsClient+<ReadStreamFromRemoteAsync>d__20`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].MoveNext() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at Microsoft.VisualStudio.Services.Experimentation.ShippedFlightsClient+<SetRemoteFlightsAsync>d__4.MoveNext() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at Microsoft.VisualStudio.Services.Experimentation.VSExperimentationService+<<FlightDataCallback>b__33_0>d.MoveNext() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at Microsoft.VisualStudio.Services.Experimentation.VSExperimentationService+<FlightDataCallback>d__33.MoveNext() at System.Runtime.CompilerServices.AsyncMethodBuilderCore+<>c.<ThrowAsync>b__6_1(System.Object) at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
EDIT 3:
Searching for TestFlight related posts, I found the following from Microsoft (opting out of Experience Improvement Program). Looked very promising, but sadly didn't resolve my issue:
https://connect.microsoft.com/VisualStudio/feedback/details/2082049/crash-on-startup
I fixed the problem by installing Visual Studio 2015 Update 2 RC (I was running Update 1), and unchecking every single optional install feature (I just need C#/WPF). Chances are, simply installing Update 2 RC would fix the issue, but I've wasted too much time on it already to keep trying over and over again.
Here's a link to Update 2 RC:
https://www.visualstudio.com/en-us/news/vs2015-update2-vs.aspx

Visual Studio 2012 crash on startup

As soon as I open visual studio it goes unresponsive. I have looked at the event viewer, and it gives 3 errors when visual studio crashes in order:
1)
Application: WDExpress.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException
Stack:
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__1(System.Object)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
2)
Faulting application name: WDExpress.exe, version: 11.0.60315.1, time stamp: 0x5142b273
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83c8a
Exception code: 0xe0434352
Fault offset: 0x0000c41f
Faulting process id: 0x18f0
Faulting application start time: 0x01ce445978318661
Faulting application path: D:\Programs\vs\Common7\IDE\WDExpress.exe
Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
Report Id: bbf0314d-b04c-11e2-a8b8-08002700c410
3)
Fault bucket , type 0
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: wdexpress.exe
P2: 11.0.60315.1
P3: 5142b273
P4: Microsoft.VisualStudio.Shell.11.0
P5: 11.0.60315.1
P6: 514298c6
P7: 941
P8: 5b
P9: System.InvalidOperationException
P10:
Attached files:
C:\Users\Steve\AppData\Local\Temp\WER2FF6.tmp.WERInternalMetadata.xml
These files may be available here:
C:\Users\Steve\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_wdexpress.exe_b14ec39a92949f27abbb79e507ed518f9c5afcf_0abe3755
Analysis symbol:
Rechecking for solution: 0
Report Id: bbf0314d-b04c-11e2-a8b8-08002700c410
I have reinstalled at least 8 times, uninstalled using the default uninstaller. Then used revo uninstaller, manually cleaned registry keys, run .net verifier (no errors), repaired the install, tried on another account. It simply will not work. Any ideas?
P.S this is my last resort I've been looking everywhere and am unable to solve it even when others have similar problems
I've been annoyed by the symptom which seems to be exactly the same.
In my case, regsvr ieproxy.dll made the symptom fixed.
Hope this helps:
Visual Studio 2012 Crashes after installing IE9 (Faulting Module ntdll.dll)

I have a faulting dll and a fault address - how do I start analysing the error?

I have the following two error logs in the Windows Event Viewer of our IIS production server:
Source: Application Error
Category: (100)
Event ID: (1000)
Description: Faulting application w3wp.exe, version 6.0.3790.3959, faulting module mscorwks.dll, version 2.0.50727.3603, fault address 0x0001da8f.
Seconds later:
Source: .NET Runtime 2.0 Error Reporting
Category: None
Event ID: 1000
Description: Faulting application w3wp.exe, version 6.0.3790.3959, stamp 45d6968e, faulting module mscorwks.dll, version 2.0.50727.3603, stamp 4a7cd88e, debug? 0, fault address 0x0001da8f.
What can I do with these error messages? I see that I have a fault address and a dll name - are there any tools that will show me what is at this address in the dll? Would this be the correct approach to figuring out what caused the crash? I've so far not been able to replicate it.
Thanks.