I've started getting repeatble Unreal Engine crashes with NY-Trenton, specifically the Sunny Side Up scenario as I'm coming through the tunnel on the approach to New York Penn station. Has anybody else encountered this? I'm running NVIDIA GeForce 536.99 - the latest drivers. I've also verified all the files via Steam. Any advice much appreciated!
This is the text: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000050 TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping TS2Prototype_Win64_Shipping kernel32 ntdll I do have some mods installed, but they are enhancement packs for other routes. The only thing I can think of is that I updated the GPU drivers this afternoon. Maybe I should roll back and see it that helps? I would note that I also get this same issue on the Bakerloo Line (mainly 1938 stock) and I was getting that with no mods installed at all - but on that route it was always when underground, but wasn't repeatable, but would happen maybe 1 in 5 service runs.
I can't find any meaningful explanations for that error code online, at least insofar as it could relate to TSW. I found a similar error message for Overwatch 2, and completed checks suggested there such as disk scans, etc.
Just got this same crash on Bakerloo again today. Has anybody any idea what causes an "EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000050" error?
I've now completely reset the game back to the original engine.ini and removed all mods, plus verified all files. Still getting an Unreal Engine crash when going through the tunnel into New York Penn. I'll submit this as a properr bug report now, and just avoid this broken route.
i had that crash too for me it was engine.ini or godmode save (depends on what you are using) s.ForceGCAfterLevelStreamedOut=0 when i removed that line it did not crash have not any crashes on other routes so far with the line in it
It´s a memory error and it´s solved by increasing virtual memory pagefile size in Windows, as usual, even if game does not use more than 10GB RAM and VRAM normally. Pagefile of 16GB or auto should be enough. It happens also at SEH route tunnels. There was a major Windows 11 update few days ago (I started to see the error then) and today we had another update (23H2) so prepare for exotic results during the following days. Cheers
Since you asked. On a technical level, the CPU is trying to read memory from an address (0x50) which is not accessible. There's a load of things that can go wrong in code that would lead to this kind of error. The error message alone really does not tell me much The stack trace below the error message would help an expert locate the problem, but the entries are unfortunately truncated, they all have the same name. So without any understanding of the engine - not much to say.
it is not he pagefile setting at least not for me also not the ini settings tried several runs on the Sunny Side Up scenario for me on Sunny Side Up if i went real fast to destination it always crashed no matter what even without the line s.ForceGCAfterLevelStreamedOut=0 if i went with the normal speeds and atc speeds no crash hopefully once it get patched that bug will be gone
