Help apricated - Crash to desktop - hardware issue

[Lord_fenris28]

Hi all,
I am running out of ideas and could use some help in fixing. I can't play the game but would really like to try the new dlc or at least play X4 again. Since I bought my new PC 1,5 years ago, that is kind of not possible

Please reach out if you need further info, I hope I catched it all

Thanks in advance

Typical Event:
The game is either crashing to desktop while starting or some 2-5 minutes within the game after starting an old safe or any fresh start (at least budgeted, emergence, project genesis, accomplished scientist) or just being lazy in the main menu. In all scenarios I am either flying (no keyboard input) or walking (key board input) or just in the main menu

Summary of things done:
The game failed on 6.2 and now on 7.0 identically (to the naive eye)
The game is unmodded
Language German and English have been tried
No changes to the system have been made, Multiple Game integrity checks have been done, multiple reinstallations on main and second hardware drive have been tested, Drivers have been updated automatically and manually from Nvidea webpage, integrity of RAM has been tested, SFC /Scannow & dism /online /cleanup-image /restorehealth executed (for the ntdll.dll), FPS limited on 60, GPU power reduced, GPU Power Supply increased (via official software), GeForce Experience installed and deinstalled and installed again, prayers to heaven and hell have been send.


Event log (German):
Applikation error 1000
Name der fehlerhaften Anwendung: X4.exe, Version: 7.0.0.0, Zeitstempel: 0x6670206f
Name des fehlerhaften Moduls: ntdll.dll, Version: 10.0.22621.3733, Zeitstempel: 0x67ca8829
Ausnahmecode: 0xc0000374
Fehleroffset: 0x000000000010c8f9
ID des fehlerhaften Prozesses: 0x0xDB4
Startzeit der fehlerhaften Anwendung: 0x0x1DAC34BCC72C63A
Pfad der fehlerhaften Anwendung: D:\SteamLibrary\steamapps\common\X4 Foundations\X4.exe
Pfad des fehlerhaften Moduls: C:\Windows\SYSTEM32\ntdll.dll
Berichtskennung: 165960c4-a952-47d2-9ec9-9cdb4086b5db
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:


3 crash Dump files
https://www.dropbox.com/scl/fi/3jvwwrwz ... 1qg6l&dl=0
https://www.dropbox.com/scl/fi/gzqeqvcm ... w79bl&dl=0
https://www.dropbox.com/scl/fi/nqcobwdw ... mdyk6&dl=0


DxDiag
https://www.dropbox.com/scl/fi/8mx2svrq ... r09lm&dl=0

Vulkan-Info (please note that your guide did not generate an info file. This is a copy of the vulkaninfo cmd command)
https://www.dropbox.com/scl/fi/nsp2yjge ... 59rxd&dl=0

A save game cannot be provided because it crashes before I can save.

[Alan Phipps]

Stackhash issues with various apps and games are difficult to pin down exactly but some have had success by doing a clean reinstall or clean update of their graphics driver. Still, you say that you have done that (as long as it was a clean update).

[CBJ]

The first two crashes are occurring while the game is trying to compile shaders, which happens very early on. The last one is an error in a lua DLL, which is probably one where the game at least tried to reach the main menu. None of these are "normal" in the sense that they're crashes in stable third party components that we do not normally see reports about.

That suggests that either your game installation is corrupted, or you have something like a faulty memory stick that means they get corrupted once they've been loaded into memory. Given some of the other crashes that appear in your DXDiag report, my initial inclination would be that it's the more likely to be the latter, and that you probably need to run some memory verification tools and/or try taking individual memory sticks out to narrow down what's causing it.

One other possibility might be that the corruption is caused by overclocking your memory or setting too tight timings. If you've tried anything like that then try resetting everything back to normal, or even a little below normal, to see if that helps stabilise things.

[Lord_fenris28]

Hi all,
thanks for the fast reply. I might should have add that I did a clean windows installation 2 month ago, the problem also occurred before. Including the fresh clean (maybe I understand clean not correctly, that means deinstall the earlier one properly before installing the new one, right?)

The memory was tested with "windows memory diagnostic", the GPU memory, I tried to check with CPU-Z (which just give me a value, so how would I verify that part of integrity?)
Thinking about the memory being broken after loading, would that appear in a windows memory diagnostic or would that potentially stay silent? (I will try taken sticks out in my lunch break)

In regards of overclocking: I tried underclocking to 80% with a guide, which causes crashes to. However, that is not my daily business and I am not confident that I have the skill set to fix it. All settings, that I know of, are back to normal. It is however a gaming PC; I will try to find anything point into default overclocking in Bios and wherever a noop like me will find it.

Again, many thanks for the fast reply. If you can guide me to GPU Memory checks, that would help me, google always lead me to the windows test or potential shady tools

[Lord_fenris28]

Update: Meanwhile I have updated to run the game with just one memory stick. Both single RAM runs failed as usual. I have further checked all BIOS and other hidden settings for default overclocking (CPU;GPU; RAM) and they are disabled. A clean deinstallation and installation of all NVidia components did not help, neither did a clean reinstallation of the game.

Are there any other suggestions and what I can try, or do I need to accept that my PC is simple to advanced for the game and have to wait for X5?

[Lord_fenris28]

Meanwhile, the card has been checked by Nvidia as well as the shop where I biught it. The graphic card is 100% intat. Any other ideas?

[sirprosik]

I would check the power supply. If a known good power supply and still with errors then it could be the motherboard or CPU less likely.
I have personally had 10 motherboards in a row by a certain manufacturer be bad and once replaced with Intel all ran good with only the motherboard switch.

[Lord_fenris28]

Small update: It was the motherboard

[CBJ]

Thanks for reporting back, and glad to hear you've got it sorted out. Issues like this can be very hard to track down. Enjoy the game!