I keep getting the following error in TSW4: " Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000000 " (Also see image below). However, the error only occurs when attempting to run ANY scenario with ANY Loco in: 1, ECML Peterborough to Doncaster (Full timetable). (But the error does not occur when selecting the "Reduced" timetable option). 2. Southeastern High Speed: I am unable to run any option on this route without the error occurring as soon as I try to run a selected option. I can confirm that I have the latest version of all my drivers installed; and my BIOS is fully updated. I get the error as described whether I run the game in DX11 or DX12; whether or not I enable a page file; and whether I run the game with the original Engini.ini file or with JetWash and/or @gelaxo enhancements. The error also occurs irrespective of whether or not I run my PC boosted or not. Inttegrity of game files has been verified. What is strange in my case, is that I can run all the other scenarios of my DLC without any problems at all (and I own almost all of the TSW 4 and TSW4-compatible DLC). I have seen that this same error has been encountered and reported by other users under widely differing circumstances and with widely differing hardware, but I have never seen a formal explanation as to the cause, or a solution. (Not even via "Google"). Despite selecting the option to "Send" the error report every time it is offered, there appears to be no follow up anywhere. I would really appreciate advice as to how to address this issue. (Details of my Windows 11 rig are as below) (Reason for editing: corrected typos)
Did you happen to tamper with your pagefile settings? Try going with the default setting which is to allow the system to automatically set the pagefile size. Because my first guess would be that the game is trying to access memory it can't get access to, and things like this tend to happen when you play around with your pagefile too much (you set a custom size, disable it entirely, etc).
JetWash: Yes. But I rolled back to check, and the issue remains. It seems strange that the issue is absent for more than 95% of my DLC. I have a feeling that my system somehow does not like certain layers. Could this be the case?
Xander1986: Yes. But I have reverted to a "no mods" state to check, and the issue is present in that state as well. It seems strange that the issue is absent for more than 95% of my DLC. I have a feeling that my system somehow does not like certain layers. Could this be the case?
Dinosbacsi : Yes I did, but I have also tried with standard Windows 11 default settings and the issue is still present. It seems strange that the issue is absent for more than 95% of my DLC. I have a feeling that my system somehow does not like certain layers. Could this be the case?
Do you have an overclock or under-volt (or both) on your GPU? TSW4 seems particularly sensitive to both, more than previous versions. Failing that, I would suggest running mem test and see if that throws anything up. I suspect that the routes that are crashing are pushing your PC further than it can take. Do you have very high graphics settings?
That is odd. It’s certainly pointing towards some sort of memory issue I’d say, although I’ve no idea what.
It seems I have solved the problem: I removed ONLY the .pak files created by bescot that I had previously installed. PLEASE NOTE: I am not in any way criticising his work, since all of those files previously significantly improved my gameplay, as intended. Somehow (and I am still trying to find out specifically what), one or more of his files seems to have caused a conflict in RAM (as suspected by JetWash ). In any event, I can now run any and all of my DLC using virtual all of JetWash Ultra settings, with my PC overclocked, and in 4k. fps remains above 40, but is 50-plus in most scenarios. Over the next few days, I will attempt to identify which specific file(s) is involved. Many thanks to JetWash , Dinosbacsi and Xander1986 for you willingness to assist me. Much appreciated!
No problem mods could be result in problems If they are outdated. So check time by time your'e mods and what you have installed.
Which of Bescot’s mods are you talking about? If it’s anything related to SEHS then he definitely hasn’t updated them to work with TSW4, and that will be the cause of your crash. On TSC only mods that show up when you tick TSW4 (of which there are only 3 pages) are compatible. It’s more than likely anything else will cause your game to crash.
