Jerome Roy 

Well, let me add my frustration. You moan here about something called Trados Studio. What is this? Where it is? On the moon? What was it doing?

Please do not get me wrong, but if you expect help, tell us what are you doing with which version on what kind of PC with files of a certain type stored where. Moaning does not help at all.

Hello Jerzy,

I indicated that I was using the latest version of Trados Studio, namely 2024 SR1.
On earth, on a computer, an ASUS, running Windows 11, which is up to date.

I also explained what I was trying to do.

And I also pointed out that I received virtually no messages when Studio crashed.

Unfortunately, this happens with all types of files.

Regarding my frustration: this problem already existed, especially the interaction between Studio and Multiterm, but since Studio 2024, the situation has worsened.

I'm not the type of person who “blames instead of looking for solutions", so 

Perhaps you will be able to interpret the log files I provided better than I can.

Jérôme

Jerome Roy said:

I indicated that I was using the latest version of Trados Studio, namely 2024 SR1

Unfrotunately, you did not. "All programs are up to date" could also be S2022 or anything else.

Now, have you resetted Studio to its neutral state? This means deleting certain folders, did you do that? Are you sure your Documents folder is not connected to OneDrive? In Windows 11 this can be the fact even if we do not notice this.

Unfortunately, I am only a user and not developer. Hopefully Loredana Stoia  or someone from RWS team will be able to read the logs.

In the meantime, here are some main reasons for frequent crashes of TS2024:

• User profile from previous version
• Project templates from previous version
• Outdated plugins
• Too many plugins
• Weak processor, slow memory, slow HDD

Possible solutions, if Studio has already been resetted:

• Reset user profile
• Change user profile to a default one
• Import an user profile from here: C:\Program Files (x86)\Trados\Trados Studio\Studio18\UserProfiles
  (before doing this declare a profile with other name as default)
• In Editor go to View and Reset window layout

I dearly hope you can solve your problems.

Hello,

I tried what you said. I tought reset user profile would help, and it seemed at the beginning, but unfortunately it didn't last.

No news neither from anyone who may have read the logs.

Here some new ones and a picture.

Regards

<SDLErrorDetails time="8/21/2025 11:12:10 AM">
  <ErrorMessage>Object reference not set to an instance of an object.</ErrorMessage>
  <Exception>
    <Type>System.NullReferenceException, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</Type>
    <ExceptionMessage>Object reference not set to an instance of an object.</ExceptionMessage>
    <HelpLink />
    <Source>Sdl.TranslationStudio.Editor</Source>
    <HResult>-2147467261</HResult>
    <StackTrace><![CDATA[   at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocumentViewPart.OnRemove()
   at Sdl.Desktop.Platform.AbstractDockingView.RemoveViewPart(IViewPart viewPart)
   at Sdl.TranslationStudio.Editor.EditorView.OnDocumentViewPartOperation(DocumentViewPartOperationEvent e)
   at System.Reactive.AnonymousSafeObserver`1.OnNext(T value)
   at System.Reactive.Sink`1.ForwardOnNext(TTarget value)
   at System.Reactive.IdentitySink`1.OnNext(T value)
   at System.Reactive.Sink`1.ForwardOnNext(TTarget value)
   at System.Reactive.Linq.ObservableImpl.OfType`2._.OnNext(TSource value)
   at System.Reactive.Subjects.Subject`1.OnNext(T value)
   at Sdl.Desktop.Platform.Implementation.Services.EventAggregator.Publish[TEvent](TEvent sampleEvent)
   at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocumentViewPart.OnDocumentClosed(IDocument document)
   at Sdl.TranslationStudio.Api.Editor.DocumentEventHandler.Invoke(IDocument document)
   at Sdl.TranslationStudio.Api.Editor.AbstractInternalDocument.OnClosed()
   at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.OnClosed()
   at Sdl.TranslationStudio.Api.Editor.AbstractInternalDocument.CloseImpl()
   at Sdl.TranslationStudio.Api.Editor.AbstractInternalDocument.Close(Boolean uploadFilesToLanguageCloud)
   at Sdl.TranslationStudio.Editor.TranslationEditor.TranslatableDocument.Close(Boolean uploadFilesToLanguageCloud)
   at Sdl.TranslationStudio.Editor.EditorService.<>c.<CloseAllDocuments>b__58_0(IDocument t)
   at System.Linq.Enumerable.All[TSource](IEnumerable`1 source, Func`2 predicate)
   at Sdl.TranslationStudio.Editor.EditorService.CloseAllDocuments()
   at Sdl.TranslationStudio.Editor.EditorService.Window_Closing(IStudioWindow window, CancelEventArgs e)
   at Sdl.Desktop.Platform.StudioWindowCancelEventHandler.Invoke(IStudioWindow window, CancelEventArgs cancel)
   at Sdl.Desktop.Platform.Implementation.StudioWindow.OnClosing()
   at Sdl.Desktop.Platform.Implementation.StudioWindow._form_Closing(Object sender, CancelEventArgs e)
   at System.Windows.Forms.Form.OnClosing(CancelEventArgs e)
   at System.Windows.Forms.Form.WmClose(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at Sdl.Platform.UI.StudioWindowForm.WndProc(Message& message)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)]]></StackTrace>
  </Exception>
  <Environment>
    <ProductName>Trados Studio</ProductName>
    <ProductVersion>Studio18</ProductVersion>
    <EntryAssemblyFileVersion>18.1.2.6370</EntryAssemblyFileVersion>
    <OperatingSystem>Microsoft Windows 11 Pro Insider Preview</OperatingSystem>
    <ServicePack>NULL</ServicePack>
    <OperatingSystemLanguage>1031</OperatingSystemLanguage>
    <CodePage>1252</CodePage>
    <LoggedOnUser>ARCHEON4\jerom</LoggedOnUser>
    <DotNetFrameWork>4.0.30319.42000</DotNetFrameWork>
    <ComputerName>ARCHEON4</ComputerName>
    <ConnectedToNetwork>True</ConnectedToNetwork>
    <PhysicalMemory>32896664 MB</PhysicalMemory>
  </Environment>
</SDLErrorDetails>

7002.logs.zip

Jerome Roy 

This is really strange. With an opened document please go to View menu and use Reset window layout. It seems to me, that your error is view related. So also please check the drivers in your PC, especially the graphics driver.

 Jerome Roy 

I took a look through some of your logs and the two I checked point towards the same thing... the offending local .sdltb is corrupt / internally inconsistent, or the MultiTerm runtime that Studio is calling into is mismatched for this termbase.  The native layer throws (SEH/AccessViolation) during reorganise/open, which then causes the Termbases UI to crash while trying to reflect state.  Nothing else in the logs is causative.

So, the first thing to check is that you have also upgraded MultiTerm.  In reality this shouldn't be a problem because this release of Studio completes the removal of ties that Studio had suffered with by being so dependent on MultiTerm... but I think it makes sense to be sure anyway.  So, you should have Trados Studio 2024 - 18.1.2.6370 and MultiTerm 2024 - 18.1.2.3594.

The logs are showing that the failure occurs the moment your Project Settings hit terminology, specifically this termbase:

…\Häfele 11855-2049 Studio\Termbases\Häfele_MT2019_lokal.sdltb

It could be corrupt, it might be something else such as the termbase having the ä character, or maybe the full path being on a cloud drive such as OneDrive, Google Drive, DropBox etc.  So it might be worth copying your termbase to a location like this for example and without the umlaut:

C:\TB\Haefele_MT2019_local.sdltb

I know you might say it always worked before, but please try it anyway as you never know what may be causing the issue in reality.  From the name you probably created this termbase in 2019 or thereabouts so maybe try copying it to the new location, open it in the latest version of MultiTerm and reorganise it too.

Alternatively, and for a quick fix plan, de-wire the TB from the project (to stabilise Studio):

• Close Studio.
• Back up the project’s .sdlproj.
• Edit the .sdlproj in a text editor and remove the entries under the Termbases section that reference Häfele_MT2019_lokal.sdltb.
  (If you prefer a blunt approach, rename the .sdltb so Studio can’t find it.)
• Reopen Project Settings. If it now opens cleanly, that confirms the termbase is the trigger.

So I'd have a go at these things and see how that goes?

Jerome Roy 

Side note: I think you’re on Windows 11 Pro Insider Preview.  If the TB also crashes on a clean, known-good machine, it’s the file.  If it only crashes on Insider, the OS could be amplifying a native edge case - but the evidence you have provided still points squarely at the local termbase.

Jerome Roy 

Side note: I think you’re on Windows 11 Pro Insider Preview.  If the TB also crashes on a clean, known-good machine, it’s the file.  If it only crashes on Insider, the OS could be amplifying a native edge case - but the evidence you have provided still points squarely at the local termbase.