Hi,
So after running memtest this weekend, it indeed detected faulty RAM. As of now, I've identified one stick out of four, but it may be the CPU / Motherboard / etc that causes it (I'll test the slot with a known-good ECC stick). The other three are ongoing longer tests in dedicated machines ...

I'm running them at their base EXPO profile, i.e. 3200MHz. They could go much farther as those are CL14 chips, so there's quite a high margin for tolerance.

Further, I fail to see how failing ram could lead to a null dereference. Invalid pointer definitely to some random, unallocated, memory area ...

Urgh sorry for the incorrect logs. I started the game to see the game version, thus uploaded the file for the new run. Here are the correct logs attached to this message. I also noticed a crash dump file in the directory, it may help you.

As for the failing hardware, I highly doubt it. This is my ...

Hi, I experienced a game crash on 1.1.104 build 62119.

For searchability in the forum: Rail::requestToOpenGates in rail.cpp did a null pointer dereference (Read at address 0000000000000000) on line 1745.

-> What did you do?
I am afraid I don't have much more to say as I was playing normally when ...