[6.00 HF5] Regular crashes without error message / game closes

[Nivcore]

First of all, I apologize for the double post.
I have already created this report in the German forum.
There I received no help so far, so I wanted to try again here because of the larger community.

The game crashes more often.
No error message, the game just closes.
A connection with certain actions in the game is not producible for me.
It seems absolutely random when/at what the game closes.

The system was just reinstalled on 11.05.
So a complete reinstall of Windows 11 and formatting of all hard drives.
(Because of mainboard change)
So everything is still quite fresh.
In hundreds of hours before I had less crashes than in the days now.

6.0 HF 5 German
No modifications
Game start: Stranded

X4 DMP files from crashes
https://file.io/YNLA2yPrQefX

DxDiag & volcano info:
https://file.io/lgfLPlFaRScw

- Note: When creating the Vulkaninfo.txt the console gives an error. "WARNING [Loader Message] Code 0 windows_read_data_files_in_registry Registry lookup failed to get layer manifest files."
However, the file is still created. Is there possibly already an error here?

Savegame:
https://file.io/4BaDeM5w6drS

Attempts to resolve so far;
- The game has been checked for errors on Steam (no corrupted files).
- A reinstallation of the game via Steam
- Disabling Steam in Game Overlay
- Driver updates and reinstallation

I hope a cause can be found.
If more info/data is needed, I will of course gladly provide it.

Thanks in advance

[CBJ]

I've been through your crashdumps, and you're right: there is absolutely no pattern to them. They are all over the place, mostly in code where crashes would not be expected at all. This fairly strongly suggests a system problem. If nothing is overclocked or over/under-volted, then I would say the most likely candidate would be something like faulty memory, or possibly a power supply issue.

[Nivcore]

Hey,

first of all, thanks for the quick reply.
So I had the memory checked again over hours, no error detected. (memtest86)

The only overclock that is enabled is the XMP profile.
Could that be the reason for this crashes?
Should I disable that?

Otherwise, I don't know any more steps to narrow it down.

Thanks until here

[CBJ]

The only overclock that is enabled is the XMP profile.
Could that be the reason for this crashes?
Should I disable that?

That is very much a possibility, since the error is quite likely to be memory-related. So yes, try disabling it.

[Nivcore]

okay then I will have to try that.
Is X4 generally not compatible with XMP or is there simply a certain limit? So only a use of the base speed is recommended?
So e.g. 6000 instead of 7200 (in my case).

Thanks until here

[CBJ]

Is X4 generally not compatible with XMP or is there simply a certain limit? So only a use of the base speed is recommended?

That's an impossible question to answer. The game pushes both CPU and memory quite hard - more so than most games - so any system instability will be more likely to be exposed while playing it than in other situations. But there is no hard-and-fast "compatibility" rule we can give people. The same rule applies as with any overclocking or other system tweak: the first thing you should do when a problem shows up, regardless of what you're doing at the time, is to set it back to the default and see if that solves it.

[user1679]

I can't download the DxDiag to see what version of windows you have (says it was deleted) but sometimes the Windows Event Viewer can shed some light:

Windows 7:

Click "Start", "Run" and paste this in the box:

"C:\Windows\system32\mmc.exe" "C:\Windows\system32\eventvwr.msc" /s

Windows 8,10:

Right click the Start button, select Control Panel, select System & Security, double-click Administrative tools then double-click Event Viewer

Once that's open, expand "Windows Event Logs" and select the "Application" option. You can filter the list by right clicking "Application" and choosing "filter current log" and entering "x4.exe" as the source. Sometimes this list will show that a program crashed because of memory errors, driver errors, disk errors or something else.