IMPORTANT MESSAGE: We are still experiencing some difficulties that will affect your ability work with the RWS AppStore. Our IT team is working to resolve this but for now you may not be able to download or upload apps through the RWS AppStore. We apologise for the inconvenience and will update the community when we have a resolution in place. In the meantime you can take advantage of the Private AppStore if you are using Trados Studio 2021 or 2022.

Studio randomly shuts down

I'm using Studio 2017 and it randomly just shuts itself down without any warning. Poof and it's gone.

It doesn't happen when I'm doing a certain task in particular, just whenever it fancies apparently.

Can someone tell me why this may be happening and how to rectify it if possible?

Parents Reply Children
  • Hi Spiros,

    have you checked your RAM memory f.e. using Memtest?

    Second thing - maybe it's not the right address but I'd check this. Open "Run" (use left WIN key with R on the keyboard) and type or copy&paste: eventvwr.msc and click OK. Alternatively: right-click or tap and hold the Start icon. Choose the Event Viewer.

    See the logs there. Maybe you'll find something odd of any details that will be helpful in further diagnosis. Check especially windows system logs and software and services logs. The entries are in achronological order so it should be easy to find some second after encountering the problem. I don't have English windows so the names may be not 100% accurate. Sorry about that. Maybe it's not the remedy but it's worth trying.

    More basic information about the Event Viewer:



  • This is what I could find:

    Fault bucket 2304622717258355442, type 5
    Event Name: RADAR_PRE_LEAK_WOW64
    Response: Not available
    Cab Id: 0

    Problem signature:
    P1: SDLTradosStudio.exe
    P3: 10.0.18362.2.0.0

    Attached files:

    These files may be available here:

    Analysis symbol:
    Rechecking for solution: 0
    Report Id: 9201b011-ccb1-4919-814d-877364a4fa3c
    Report Status: 268435456
    Hashed bucket: 789985c528ef76fbeffbaa26a37ad2f2
    Cab Guid: 0


    Ending a Windows Installer transaction: C:\ProgramData\Package Cache\SDL\SDLTradosStudio2019_SR1\modules\TranslationStudio15.msi. Client Process Id: 1796.


    And this is an error I get when trying to check project settings:

    <SDLErrorDetails time="5/7/2019 9:54:41 πμ">
    <ErrorMessage>Δημιουργήθηκε εξαίρεση από τον προορισμό μιας κλήσης.</ErrorMessage>
    <Type>System.Reflection.TargetInvocationException, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <StackTrace><![CDATA[ σε System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck)
    σε System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
    σε System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark)
    σε System.Activator.CreateInstance[T]()
    σε Sdl.Desktop.Platform.Settings.SettingsPageReference`1.Initialize()
    σε Sdl.Desktop.Platform.Implementation.Settings.AbstractSettingsHost.EnsurePageInitialized(ISettingsPageReference r)
    σε Sdl.Desktop.Platform.Implementation.Settings.AbstractSettingsHost.ActivateSettingsPage(String[] path)
    σε Sdl.Desktop.Platform.Implementation.Settings.AbstractSettingsHost.SetInitiallyActivePage()
    σε Sdl.Desktop.Platform.Implementation.Settings.AbstractSettingsHost.get_SettingsHostUI()
    σε Sdl.Desktop.Platform.Implementation.Settings.SettingsDialog.Dispose()
    σε Sdl.TranslationStudio.ProjectManagement.Actions.ProjectSettingsDialogHelper.Show(IProject project, IProjectManagementService service, ConfigureProjectSettingsDialogDelegate configureProjectSettingsDialog)
    σε Sdl.TranslationStudio.ProjectManagement.Actions.ProjectSettingsAction.Execute()
    σε Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.<>c__DisplayClass30_0.<ExecuteAction>b__0()
    σε Sdl.Desktop.Logger.Log.Resources(Object message, Action action)
    σε Sdl.Desktop.Platform.Implementation.CommandBars.ActionService.ExecuteAction(IAction action, ActionOrigin origin, Boolean allowToggle)
    σε Sdl.Desktop.Platform.WinForms.IgCommandBarAction.Execute()
    σε Sdl.Desktop.Platform.WinForms.IgCommandBarAction._lazyButtonTool_ToolClick(Object sender, ToolClickEventArgs e)
    σε Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick(ToolClickEventArgs e)
    σε Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.OnToolClick(ToolClickEventArgs e)
    σε Infragistics.Win.UltraWinToolbars.UltraToolbarsManager.FireEvent(ToolbarEventIds id, EventArgs e)
    σε Infragistics.Win.UltraWinToolbars.ToolBase.OnToolClick()
    σε Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.DoClickProcessing(MouseEventArgs e)
    σε Infragistics.Win.UltraWinToolbars.ButtonToolUIElement.OnMouseUp(MouseEventArgs e)
    σε Infragistics.Win.ControlUIElementBase.ProcessMouseUpHelper(Object sender, MouseEventArgs e)
    σε Infragistics.Win.ControlUIElementBase.ProcessMouseUp(Object sender, MouseEventArgs e)
    σε Infragistics.Win.Utilities.ProcessEvent(Control control, ProcessEvent eventToProcess, EventArgs e)
    σε Infragistics.Win.UltraWinToolbars.UltraToolbarsDockArea.OnMouseUp(MouseEventArgs e)
    σε System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
    σε System.Windows.Forms.Control.WndProc(Message& m)
    σε System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
    σε System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
    σε System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
    <Type>System.ArgumentNullException, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <HelpLink />
    <StackTrace><![CDATA[ σε System.Linq.Enumerable.Where[TSource](IEnumerable`1 source, Func`2 predicate)
    σε Sdl.TranslationStudio.Common.TranslationMemory.TranslationMemoriesControl..ctor()
    σε Sdl.TranslationStudio.ProjectManagement.Settings.TranslationMemoriesSettingsPageControl.InitializeComponent()
    σε Sdl.TranslationStudio.ProjectManagement.Settings.TranslationMemoriesSettingsPageControl..ctor()
    σε Sdl.TranslationStudio.ProjectManagement.Settings.TranslationMemoriesSettingsPage..ctor()]]></StackTrace>
    <ProductName>SDL Trados Studio</ProductName>
    <OperatingSystem>Microsoft Windows 10 Home</OperatingSystem>
    <PhysicalMemory>6221148 MB</PhysicalMemory>

  • Hi and 

    A reinstall of Windows didn't solve the problem for me but my frequent crashes in Studio 2019 were completely stopped by turning off Match Repair. It has to be turned off in Project Settings:

    Most of my work these days is proofreading so I don't need Match Repair. I systematically open each translated package I receive and turn Match Repair off. 

    I realise that's not a solution for translators who need Match Repair. However, I wondered if it might be a relevant factor in the search for a solution, ?

    I thought it might be useful to find out how many users say it works for them...

    All the best,

    Ali Slight smile

  • I can confirm that turning off Match Repair kept my Studio crash-free for the last 2 days. I guess we found the culprit.

  • Hi ,

    I have checked the logs and I cannot see/find any current bug logged for this exact issue, so I would absolutely recommend a support ticket if this is still ongoing (after upgrading to latest version?).

  • Hi

    A support ticket isn't enough, this is widespread. Ever since the introduction of Match Repair, it has been known by at least a few of us that turning it off stops Studio crashing. I've lost count of the amount of times I've suggested it to a user asking for help with Studio freezing/crashing and it's solved their problem.

    It needs elevating beyond investigating a single user's setup... that's why I tried to set up a survey 3 months ago, higher up in this thread.

    All the best,

    Ali Slight smile

  • Hi Steven Whale,

    I can confirm that this issue is as active as ever, even with version 1524.16.93 rendering Match repair an unusable feature. Issue stops appearing when Match repair is disabled. This was tested in 3 different machines.

  • I wonder what is being done about this. It has been over a year.

     "recommended" that a support ticket be opened. Does that mean he was expecting the users to do something? Does that mean nothing is actually being done?

    Not that it matters to me, since I don't use any of the "bells and whistles" in Studio. The software is good, but in my opinion it is too risky to use anything but the core functionality. (This bug is a good case in point.)

    But I am curious about what it takes for SDL to consider a bug important enough to fix.

    Paul has been recommending that we not use Look Ahead for years, and now it looks like Match Repair is also unusable and might remain unusable for years.

    What could SDL possibly be working on that is so critically important that major problems like this are left unresolved for years?