Crashing - restarts computer

[X3r0]

It seems random but it does it on all save files. If I revert to previous save, it inevitably restarts the computer around the same time as before when loading to that save. I'm effectively locked out of my save files because they always crash soon after loading. I'm unable to find any dump files in the X4 directory so I couldn't share any reports. Started a few weeks ago, Was a bit better when 7.0 dropped, now it's back at it. I tried resetting game settings, uninstalling/reinstalling game, tried uninstalling/disabling 3rd party software so the computer runs bare minimum. Computer is otherwise stable and there don't seem to be any stability issues when running stress tests.

System specs:
CPU: Ryzen 7950X
Motherboard: MSI MAG X670E TOMAHAWK WIFI motherboard AMD X670 Socket AM5 ATX BIOS version 1.40
RAM: 64GB (2X32) G.SKILL Ripjaws S5 Series (Intel XMP 3.0) DDR5 RAM 64GB (2x32GB) 5600MT/s CL36-36-36-89 1.25V
GPU: Acer Predator BiFrost A770 16GB, latest driver.
Storage: PNY CS3030 2 TB M.2 SSD

Edition Windows 10 Home
Version 22H2
Installed on ‎1/‎1/‎2022
OS build 19045.4529
Experience Windows Feature Experience Pack 1000.19058.1000.0

[Alan Phipps]

System restarts cannot be directly caused by the game code but are likely to be underlying device driver or (less likely after successful stress testing) hardware issues that the game loading may be exposing.

Please see the information we need, especially a link to your uploaded DxDiag with its system & driver information and included Windows Error Reporting, as then we would be far better placed to advise you effectively.

[X3r0]

Here's a link to my DxDiag, file is available to anyone with link so should be accessible immediately.
https://drive.google.com/file/d/1_d4kDv ... sp=sharing

[Alan Phipps]

You seem to be having a lot of MemDiagV1 issues which are app-handling memory issues detected by the Windows RADAR system.

I would initially try addressing 3 areas:
1. Run the Windows Memory Diagnostic Tool.
2. Configure your system virtual memory in case yours is still set to factory default after more memory or drives were added.
3. Run the System Maintenance Troubleshooter.

On the driver side, yours seem OK and up to date although I don't know much about Intel(R) Arc(TM) A770 Graphics and its drivers. (See here for another view.)

I would recommend disabling any of your several *sound* devices and drivers that you don't use. Go to Device Manager, Sound/Audio Devices (right-click on a device in the listing for a disable/enable pop-up). This action is entirely recoverable.

Good luck.

[X3r0]

I guess there's nothing for it... Tried all the stuff, still doing the same thing. I guess I'll have to suffer withdrawals because X4 is a hell of a drug.

[Imperial Good]

RAM: 64GB (2X32) G.SKILL Ripjaws S5 Series (Intel XMP 3.0) DDR5 RAM 64GB (2x32GB) 5600MT/s CL36-36-36-89 1.25V

5600 MT/s is technically an overclock. Try 5200 MT/s.

Use the appropriate AMD profiles, not XMP. XMP is optimised for Intel processors.

Try updating motherboard UEFI/BIOS. There were major fixes for memory training and stability.

[X3r0]

RAM: 64GB (2X32) G.SKILL Ripjaws S5 Series (Intel XMP 3.0) DDR5 RAM 64GB (2x32GB) 5600MT/s CL36-36-36-89 1.25V

5600 MT/s is technically an overclock. Try 5200 MT/s.

Use the appropriate AMD profiles, not XMP. XMP is optimised for Intel processors.

Try updating motherboard UEFI/BIOS. There were major fixes for memory training and stability.

I actually had a very long battle with memory issues when I installed my current motherboard. If I turned on XMP it would take 10-15 minutes to boot up and had constant stability issues. I turned it all off and let the motherboard configure things and it's been rocking ever since. I can try to see if I can manually downclock it without going into XPO because it'll freak the hell out.

edit: Well, it's been a very fun 4K hours that I sunk into X4, but, I'm at the end of it... I've had enough computer troubles in recent history as is, and, last time I tried troubleshooting my motherboard I may have ended up killing it, losing years worth of studio projects because it affected my backup as well... I can't any more. I'll be trying again from time to time to see if this has been identified and patched, until then, o7.

[Imperial Good]

edit: Well, it's been a very fun 4K hours that I sunk into X4, but, I'm at the end of it... I've had enough computer troubles in recent history as is, and, last time I tried troubleshooting my motherboard I may have ended up killing it, losing years worth of studio projects because it affected my backup as well... I can't any more. I'll be trying again from time to time to see if this has been identified and patched, until then, o7.

There is nothing that can be patched from a code perspective. User level applications like X4 cannot accidently make a computer restart, operating systems are designed to prevent this. It might fix itself only if the way X4 loads the system changes enough with patches that it no longer produces a workload that just happens to be unstable on your system. A correctly functioning system is as good as perfectly stable with all workload profiles.

As I mentioned, XMP is not supported by modern AMD CPUs as it is an Intel standard. XMP timings are for Intel CPUs and motherboards and will perform very poorly on AMD CPUs. For AM5 CPUs you should be using EXPO timings.

When AM5 launched, EXPO as well as memory training in general was not very well developed and had a lot of issues. These were fixed in subsequent UEFI/AGESA updates. This is where a UEFI update might help significantly with memory stability.

When first powering on an AM5 system or after changing memory settings there is apparently a long memory training period which can last several minutes. Rather than relying on a user or vendor input table of fine memory timings, the CPU should dynamically resolve these during memory training.

You could also try turning on eco mode for the CPU. This should make the CPU run more efficiently/cooler which might improve stability in some workloads.

[X3r0]

Well, I can't say it's fixed but I did just put in more gameplay than I have in a few days (about 5 minuts)... I finally did the thing and updated bios. That one was the last thing I would do considering what it did to my previous motherboard, but I guess this time it worked?...

Oh, and I already had my CPU underclocked because it's a 7950X, anyone who runs it at stock settings is a glutton for punishment via fan noise and hot room. XD

EDIT: I would say it's resolved. I have had very stable gameplay for a few hours now. Apparently, the new BIOS version had something to do with Memory Training and it's actually working now with A-XMP.