Matthias Burbank 

What if you copy the the segments above / below the point where it crashes into a new document.
Does this crash also?

What is the health of your TM like?
Do you have warning signs or messages show up at any point?

I assume you are aware of these articles : https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0034935 and https://gateway.rws.com/csm?id=kb_article_view&sysparm_article=KB0037519

You are welcome to send us your Files if you want us to take a closer look 

Have a good day

Lyds

When I copy the segment to another file, Trados still crashes.

I have checked the TM for any error/warnings, but there are none. And the TM is updated.

The file I'm translating is an XML file. Might there be a problem with the tags?

Matthias Burbank what you are describing are my sort of fun things to troubleshoot

In my experience when their is a single string that causes Studio to crash I would be looking at each character in isolation, followed by context of segment.
At the moment I have no understanding of what the string comprises of - special characters, tags or indeed conflict between segmentation rules / file parser rules.

Are you able to share an example file so we can take a closer look at it.

Lyds 

  In the meantime, I had the time to check the cause of the crashes. The crash is caused when I work with a term base that is located on one of our local servers. When I copy the term base to my local machine, no crashes happen at all.

In conclusion, it has nothing to do with faulty term entries, special characters etc.

Is it possible that Trados is having trouble with the connection to files on local servers, i.e. reading and writing them? That is the only explanation I have. Is there some kind of hotfix for this? We depend on working with files on server directories.

  In the meantime, I had the time to check the cause of the crashes. The crash is caused when I work with a term base that is located on one of our local servers. When I copy the term base to my local machine, no crashes happen at all.

In conclusion, it has nothing to do with faulty term entries, special characters etc.

Is it possible that Trados is having trouble with the connection to files on local servers, i.e. reading and writing them? That is the only explanation I have. Is there some kind of hotfix for this? We depend on working with files on server directories.