[5.10 HF3] Game Typically Freezes when running SETA while not playing

[Duncaroos]

• Version: 5.10 HF3

• Language: English

• Mods: No - Vanillla

• Game Start: Stranded

• Game Service: Steam

• System Specs: See Signature

During off-time, I have the player sit in the Player Office in the PHQ. I open the map and turn on SETA, upon which I leave the game running overnight. I consistently get back to the game being frozen about 30-2hr from the time I left.

In this link you'll have my latest save, as well as a word file that contains the 'Analyze Wait Chain' through Task Manager of X4.exe....not sure what use it is, but it is telling me that although X4 is running...it's deadlocked. I am not sure how to read this wait chain window...maybe Devs have an idea. I forgot to run the DxDiag report when it froze (when I tried to use the Task Manager 'Debug' mode on X4.exe the game crashed); I am doing the SETA AFK again tonight so I'll have another opportunity to grab it. For Windows Power Settings (see other Word file in link), the hard drive disk does not turn off (I have it set = 0 minutes (i.e. never)), Min Processor State = 1%, Max Processor State = 100%, and most power saving options are 'Off' or set to 'Max Performance'. The monitor does turn off after 15min, but I am not sure how much bearing it has.

I Tried to run vulkaninfo I get the following error: "WARNING: [Loader Message] Code 0 : ReadDataFilesInRegistry: Registry lookup failed to get layer manifest files." ....no idea what that means!

I'll definitely run the DXDiag once the game freezes up again.

[Duncaroos]

I uploaded the DXDiag report to the link. The game froze pretty much after I went AFK for the night...something I noticed, not sure if it has any bearing / out of context:

+++ WER8 +++:
Fault bucket 1725714932784606904, type 5
Event Name: RADAR_PRE_LEAK_64
Response: Not available
Cab Id: 0

Problem signature:
P1: X4.exe
P2: 5.10.0.0
P3: 10.0.19043.2.0.0

**Edit: I also asked Task Manager to create a DMP file...I'm uploading it to the link as well but says it'll be ~1.5 hr (so say 2hr from now it will be there).

[CBJ]

Could the timing of when this happens coincide with your PC switching into power-saving mode and disabling display output?

[Duncaroos]

Could the timing of when this happens coincide with your PC switching into power-saving mode and disabling display output?

It could possibly be...but I'm not sure what I can change in power settings to avoid a power save mode. I've basically set everything to max performance.

Is there something you noticed in the power settings that needed to be changed to avoid more power saving modes? Sorry if it was hidden in my wall of text, but I have a power options/settings Word file to show my current settings.

I'll try setting the display to never turn off.

[CBJ]

The question was simply to try to establish whether there was some specific event that triggers the freeze. The first thing that came to mind when I read your report was that the only obvious difference between running SETA while you are present and running it when you leave the PC, is that the PC might go into a power saving mode which could result in the graphics driver changing something that the game wasn't expecting to change or, even if only very briefly, not responding to the game quickly enough.

[Imperial Good]

I Tried to run vulkaninfo I get the following error: "WARNING: [Loader Message] Code 0 : ReadDataFilesInRegistry: Registry lookup failed to get layer manifest files." ....no idea what that means!

At the very least something is wrong with your vulkan install. It seems to work enough that you can play X4 but it should not be throwing errors like that. Try clean installing the graphic drivers. Might be worth using the third party tool display driver uninstaller to remove the existing ones when not connected to the internet and then installing the latest from an offline installer before connecting back.

[Duncaroos]

Ya I was thinking of that too....let me try reinstalling graphic drivers first and I'll try again!

[Duncaroos]

OK so here's what I've done so far, in order of what was done and tested to see if freezing still took place:

1. Check HDD Space
   - My main disk space for saving was pretty much 0 because I lately got a lot of huge files recently. I thought this might impact paging files.
   - FREEZE still took place ~15min after quicksaving and leaving
   ...
2. Update NVidia Driver from v471.68 -> v516.59 (odd that NVidia Control Panel didn't tell me this was available.....)
   - No Change, FREEZE still after 15-20min
   ...
3. Set NVidia Control Panel to "Prefer Maximum Performance" for 'Power Management Settings'
   - No Change, FREEZE still after 15-20min
   ...
4. Set 'Turn off Display after.." to >1hr
   - No Change, FREEZE still after 15-20min

I'm at a loss. I'm going to try not being in SETA and then try just being in the ship and SETA'ing. I remember doing this before successfully in a previous version, so I'm a bit stumped why I am having trouble now .

[Imperial Good]

You still need to provide the requested information. Such as directx and vulkan listings.

SETA will likely load your CPU pretty hard. Make sure CPU temperatures remain reasonable. Even if the CPU is correctly thermal throttling it might be less stable due to binning.

[Duncaroos]

Oh sorry, in my rush to post I didn't upload my vulkaninfo. I added it to the original link - updated driver at least fixed the report running.

The DxDiag was already there in the beginning - let me know if there is another debug report to provide?

Max CPU temp from last AFK run was 56 degC, which isn't that high (at least I think).

[Imperial Good]

Possibly unstable CPU/Memory? A memory error under strain could explain the random deadlock, especially given that SETA will be hammering both the CPU and memory very hard all the time. Updating UEFI (BIOS) and lowering memory transfer speed can help with this but care must be taken to update to a versions that still supports your CPU.

Your C drive has very little free space. If the swap file (page file) is placed on this drive then memory spikes could potentially cause an out of memory error that affects system stability. Like wise if any temp files are used and the drive cannot back them it may also cause an out of memory error or otherwise general instability.

[Duncaroos]

From the run I just did around Aug 4th at 0:30 AM EST, I had the following:

• +20GB Free space on C:\
  .
• Max Physical Memory Usage = 71.5% (Min: 4616MB, Max: 11690MB, Avg: 10288MB)
• Max Virtual Memory Load = 58.7% (Min: 6885MB, Max: 18246MB, Avg: 16532MB)
• Max Page File Usage = 1%
  .
• Total CPU Max Usage = 87.9%
• Max GPU Memory Usage = 53.9%
  .
• Max System Temps = 32°C
• Max Avg L3 Temps = 48.8°C
• Max CPU Temp = 55.8°C
• Max Avg Core Temps = 50.4°C
• Max VR MOS Temp = 42°C
• Max PCH Temp = 40°C
• Max GPU Temp = 57.5°C
• Max GPU Hotspot Temp = 68.5°C

This seems very adequate given its a CPU heavy game.

Windows Event Manager isn't showing any warnings/errors. If I was having memory issues, wouldn't I be getting some kind of Windows Error? Or, I would have system-wide issues with running the PC, however it is all localized to X4.

Drives were all run through a chkdsk and returned no faults. Updated BIOS to latest stable version. Ran memtest86 and had 4 cycles done without error.

____

Side note. I only got freezing in the sector of my PHQ which is basically a mega station for Commonwealth Wharfs, and L/XL fab bays (x2, x3, x1, respectively). I truly think it's no longer a hardware issue but perhaps just the mega complex is causing a freeze up when in sector. Is this something that Devs would like to investigate more? I uploaded my latest save (save_005.xml.gz) with the PHQ now in Eighteen Billion - still have the same problem.