X4 - Fatal Error - Exit Code 1112

[- Adreiaan -]

Hi,

playing X4 on Linux (openSUSE Tumbleweed). Have also some mods (VRO, ...) installed. Works smooth for a long time but recently it crashes. This time it crashes with the following error.

A fatal error has occured and the game cannot revocer.
Exit code: 1112

pthread_mutex_unlock (&SM)

Version 6.20 - Code revision: 511811

I didn't find any information about the error. Does anybody know what is the reason and what to do about it.

Already asked in the german forum.

BR
Adreiaan

[Daemonjax]

It's an exceptional error that was caught regarding a concurrency mutex lock -- something that shouldn't really ever happen, but they thought hey I'll write this error text in just in case instead of swallowing it and continuing on in a bad state. Good practice. Often times I think: this will never happen, BUT if it does I want the program to crash rightnow with this error logged to file.

It could be a fluke memory error -- the mutex lock is stored in main memory, not in cache. Fluke memory errors happen sometimes. Cosmic rays. Or it could be a sign the system is becoming unstable -- even for things you can't measure like: temps inside the case increasing ram temps, power fluctuations affecting ram stability (power from the wall or from the psu), etc.

Does it keep happening or was a one time thing? Games crash sometimes. Save and save often.

[- Adreiaan -]

Crashes occur more or less regularly. This error has only been displayed to me once so far. I carried out a memory check a few weeks ago when the first errors occurred. There were no errors in the memory.

I haven't changed the settings for voltages etc. for years.

From the description, it sounds like a hardware problem. This would also fit with the fact that I experience similar crashes when playing under Windows.
What surprises me, however, is that I have only noticed this with X4 so far.

Is there any way to narrow down the cause of the error?

[Alan Phipps]

It *might* also be associated with a graphics driver/Vulkan issue since VulkanInfo includes this device settings check report:

VK_KHR_win32_keyed_mutex : extension revision 1

It is interesting that Exit Code 1112 is not listed in the Egosoft Exit Code Table.

[CBJ]

It's not listed because it's not an error we'd normally expect to see. Daemonjax pretty much hit the nail on the head with regard to what it means, and the most likely causes.

[InkTide]

I'm having almost the same issue (also on linux; Zorin 17 in my case, which is basically Ubuntu 22.04 LTS under the hood), with the same exact exit code (1112), except it's not happening during gameplay. It is reliably happening every single time I close the game. The reported version also appears very strange, with weird characters that change every time I get the fatal error message box (makes me think something's pointing at the wrong memory address, unless I'm misunderstanding what it means by "Version:").

I do have mods, but not VRO. I don't think they're the issue, as this happens even when closing from the main menu, and the game itself seems to work just fine - everything works except closing the game.

[CBJ]

The fact that your error happens only on exit rather than randomly like the OP means that whatever is happening for you is not the same as what they ran into. The error code just happens to be the same because it's the same Vulkan error.

I do have mods, but not VRO. I don't think they're the issue, as this happens even when closing from the main menu, and the game itself seems to work just fine - everything works except closing the game.

Sorry, but this doesn't follow. Mods can absolutely cause problems that only show up when closing the game, and indeed that is most likely the case here. If you are able to reproduce the problem with an unmodified game, then feel free to start your own thread and provide the information requested in the very first thread at the top of the forum (minus the DXDiag because you are on Linux), so that we can investigate.