Crashing when saving

[IVIR Alaska]

6.20 English
this is without mods. however tried with mods as well and issue persists regardless.
Tarren cadet
Frequently when I save the game I will get a crash of the game. it does not matter if it is a manual save or an auto save.
No relevant changes. i dont do changes to games other than mods which i did not do in this case.
https://drive.google.com/file/d/1Kt-lDF ... sp=sharing
https://drive.google.com/file/d/1fnW_00 ... sp=sharing

[Alan Phipps]

Your DxDiag shows multiple sound devices and their drivers operating all at the same time. It may be useful to disable the devices and drivers you do not use in Device Manager, Sound/Audio Devices.

The Windows Error Reporting shows no direct X4 exe crashes, but does show LivekernelEvents & BlueScreens and one XML Core AppCrash. Those are nearly always due to hardware or driver issues. I hope that something here helps.

[IVIR Alaska]

Your DxDiag shows multiple sound devices and their drivers operating all at the same time. It may be useful to disable the devices and drivers you do not use in Device Manager, Sound/Audio Devices.

The Windows Error Reporting shows no direct X4 exe crashes, but does show LivekernelEvents & BlueScreens and one XML Core AppCrash. Those are nearly always due to hardware or driver issues. I hope that something here helps.

so do you believe the multiple sound devices and drives could be the cause?

[Alan Phipps]

I believe that the most likely cause could be an unhappy driver somewhere and so reducing the number of 'suspects' is probably a good idea. Some of your sound drivers are not that recent (eg Razer and THX).

The next thing to check might be your memory and drive stability using Windows built in RAM and drive checking facilities.

If your Samsung SSDs support Magician and/or Rapid modes then I would suggest not using those modes with X4.

[IVIR Alaska]

I believe that the most likely cause could be an unhappy driver somewhere and so reducing the number of 'suspects' is probably a good idea. Some of your sound drivers are not that recent (eg Razer and THX).

The next thing to check might be your memory and drive stability using Windows built in RAM and drive checking facilities.

If your Samsung SSDs support Magician and/or Rapid modes then I would suggest not using those modes with X4.

I disabled the other sound devices/drives and the crashes still occur. im not sure how to check memory or drive stability. i do have samsung magician the program that i use to scan my drive but that says it is healthy. the pop up i get is X4 has stopped working.

[IVIR Alaska]

https://drive.google.com/file/d/1Kt-lDF ... sp=sharing

also it keeps creating dmp files whenever the game crashes, is there still nothing in it that gives a clue as to the cause?

[IVIR Alaska]

possible work around. i noticed it doesnt seem to crash when i save into a new save slot. so what ive been doing is using the first 5 save slots then once ive saved on spot 5, i delete slot 1 and will use slot 1, now empty, for my next save. when i save on slot 1 i delete slot 2 to ready slot 2 for next save. so far it hasnt crashed in a long while. will keep playing to see if it crashes but looking like a good solution.

[IVIR Alaska]

possible work around. i noticed it doesnt seem to crash when i save into a new save slot. so what ive been doing is using the first 5 save slots then once ive saved on spot 5, i delete slot 1 and will use slot 1, now empty, for my next save. when i save on slot 1 i delete slot 2 to ready slot 2 for next save. so far it hasnt crashed in a long while. will keep playing to see if it crashes but looking like a good solution.

whelp, still crashes

[Alan Phipps]

X4 and Samsung Magician/Rapid have never got on well; that is why it is even mentioned in the frequent/known issues Sticky. The caching it uses may interfere with the save/load in some unexpected way.

It would need a dev to read the dump files properly - sorry.

[chew-ie]

Can only contribute the exception analysis made by WinDbg for file X4_620_2024_04_08_17_33_01.dmp as it points to a heap corruption. Might be no easy way out here...

Spoiler

Show

*** WARNING: Unable to verify timestamp for X4.exe
DEBUG_FLR_EXCEPTION_CODE(c0000374) and the ".exr -1" ExceptionCode(c0000005) don't match

KEY_VALUES_STRING: 1

Key : AV.Fault
Value: Read

Key : Analysis.CPU.mSec
Value: 640

Key : Analysis.Elapsed.mSec
Value: 1971

Key : Analysis.IO.Other.Mb
Value: 0

Key : Analysis.IO.Read.Mb
Value: 0

Key : Analysis.IO.Write.Mb
Value: 0

Key : Analysis.Init.CPU.mSec
Value: 202

Key : Analysis.Init.Elapsed.mSec
Value: 6900

Key : Analysis.Memory.CommitPeak.Mb
Value: 100

Key : Failure.Bucket
Value: HEAP_CORRUPTION_c0000005_heap_corruption!X4.exe

Key : Failure.Hash
Value: {bc8a62ad-4e12-359a-53d7-f0c0b3608a8c}

Key : Timeline.OS.Boot.DeltaSec
Value: 100172

Key : Timeline.Process.Start.DeltaSec
Value: 630

Key : WER.OS.Branch
Value: vb_release

Key : WER.OS.Version
Value: 10.0.19041.1

Key : WER.Process.Version
Value: 9.18.944.0


FILE_IN_CAB: X4_620_2024_04_08_17_33_01.dmp

CONTEXT: (.ecxr)
rax=0000000000000008 rbx=0000022861460000 rcx=0000022861460000
rdx=890332004d2e1700 rsi=0000022861460000 rdi=0000000000000000
rip=00007ffe2b095bb6 rsp=000000c92aeff3f0 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=00007ff718860000
r11=000000c92aeff4f0 r12=0000000000000000 r13=890332004d2e1700
r14=890332004d2e16f0 r15=0000000000000003
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010246
ntdll!RtlpFreeHeapInternal+0x4a6:
00007ffe`2b095bb6 41807e0f05 cmp byte ptr [r14+0Fh],5 ds:89033200`4d2e16ff=??
Resetting default scope

EXCEPTION_RECORD: (.exr -1)
ExceptionAddress: 00007ffe2b095bb6 (ntdll!RtlpFreeHeapInternal+0x00000000000004a6)
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000000
Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

PROCESS_NAME: X4.exe

READ_ADDRESS: ffffffffffffffff

ERROR_CODE: (NTSTATUS) 0xc0000005 - Die Anweisung in 0x%p verwies auf Arbeitsspeicher bei 0x%p. Der Vorgang %s konnte im Arbeitsspeicher nicht durchgef hrt werden.

EXCEPTION_CODE_STR: c0000005

EXCEPTION_PARAMETER1: 0000000000000000

EXCEPTION_PARAMETER2: ffffffffffffffff

ADDITIONAL_DEBUG_TEXT: Enable Pageheap/AutoVerifer ; Followup set based on attribute [Is_ChosenCrashFollowupThread] from Frame:[0] on thread:[PSEUDO_THREAD]

FAULTING_THREAD: 00004550

STACK_TEXT:
00000000`00000000 00000000`00000000 heap_corruption!X4.exe+0x0


STACK_COMMAND: ** Pseudo Context ** ManagedPseudo ** Value: ffffffff ** ; kb

SYMBOL_NAME: heap_corruption!X4.exe

MODULE_NAME: heap_corruption

IMAGE_NAME: heap_corruption

FAILURE_BUCKET_ID: HEAP_CORRUPTION_c0000005_heap_corruption!X4.exe

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {bc8a62ad-4e12-359a-53d7-f0c0b3608a8c}

Followup: MachineOwner
---------

[CBJ]

I can confirm that this looks like a memory-related issue. The game does use some additional memory when saving, and the crashdump implies that that memory is corrupted. Assuming this is an unmodified game, and since other people with unmodified games are not having the same problem, that suggests that it might be a memory fault that only occurs when exceeding a certain amount of memory used. That could mean a faulty physical memory stick, or possibly excessively tight timings on the memory configured in the BIOS.