Railworks America

I have a problem that I couldn't run my program of Train Simulator 2020 because of the error message with the title -- " OUT OF MEMORY " Did anyone else have the same experience as I have? I did sent my ticket with two files -- Crash Log and DXDIAG to DoveTail Games Support team this morning and have not heard from them yet. I know their time is evening now with the time of 6:35 P.M. BST and their office hours are 8 a.m. till 4 p.m. through the week. Now I wonder if I go ahead to uninstall the program of Train Simulator and reinstall them again to see if that will work. Or waste my time to do this with uninstall then reinstall them. Yes I have back up all of my Content Folder and Assets Folder to my Lexar USB flash drive which I have is 256GB NTFS. I do the backup every week on Sunday to make sure that everything is there with the files in both folders. So now what is your suggestion about this to reinstall or wait for DoveTail Support sometime tomorrow? And here is the error message below:

RailWorks

Saved log to . . . . . .

F:\Steam\steamapps\common\RailWorks\Temp Dump\

Exception Code: 0xC0000005

Exception Info: OUT OF MEMORY

The system is unable to run this scenario on the current configuration, we suggest either lowering the graphical settings or attempting to run the game in the 64 bit version, if fails to resolve the issue please contact our Customer Support Team at https://dovetailgames.kayako.com

I wonder if something to do with Windows 10 which I have is Windows 10 Professional 64-version. Because I see the Exception Code above and normally Microsoft have these error codes.

Let me know about this.

Thank you,

John

I’ve been getting the same. No idea why, thought it might be my RAM but no.

There are many post on this topic, I suggest troubleshooting. Its been diffrent for everyone, but all I can say is I only get this issue running in 32-bit mode but not 64-bit, my solution? just playing it in 64-bit.

I am mostly using 32 bit, for editing and route building.

I did try with 32 version and still the same with error message -- " OUT OF MEMORY " I wonder if something to do with the latest windows update last Tuesday because before Tuesday I can run 64 version with Train Simulator 2020 also 32 version too. Did you see the error code of Microsoft that I post on my first message. Guess that I will have to google to see what is with Microsoft error code.

John

This is an error that is unrelated to the amount of RAM installed, memory leaks, etc. What has happened is that a badly scripted software app eg WS Scenario/Route has tried to write to an address in the RAM that is protected, unavailable or simply does not exist. This can also happen in the editor in 64-bit mode. Using another example, now that TS2020 64-bit can access up to 8 TERABytes of VAS, the current coding may be unable to find, in some instances, the memory address needed by the working set. This creates an Invalid Page Fault and TS terminates with a 0xC0000005 error. Possibly incorrectly displayed as "out of Memory" by DTG in TS, but perhaps that's the only option Windows allows.

In TS 2019 and/or TS 2010 once the OS/VAS has loaded a scenario into the working set of the RAM (approx 4.5Gb on average) this does not vary by much more than 5/6% in addresses accessed, even in the longest scenarios. I have left TS2020 running a scenario overnight on pause, and RAM allocation was constant with very little variation. Even an 8 hour JT Western Mainlines scenario saw only minor variations in the % RAM addressed. Monitored dynamically with Pulseway app on an iPad.

Unfortunately, this is an idiosyncratic error peculiar to an individual PC - there are between 80,000 to 800,000 registered TS2020 users (I'm not sure which figure is correct) but can you imagine the number of posts on websites such as this, if it were a universal error?

I have never seen an "Access Violation", OOM, error when running DTG, RSC, JT, AP, DPS, TaD, UKTS, etc, etc DLC, but have many times when automatically loading a WS scenario, go figure.
pH

Anyway I think that the best for me is to wait and see what does the team of DoveTail Support have to say about this tomorrow through my ticket at dovetailgames.kayako.com. Hope they have an answer for this because they asked me to send DXDIAG log also crash report log too. My other simulators are working with no problem like Run-8 Simulator, Microsoft Train Simulator and Open Rails too. Just the program of DoveTail's Train Simulator 2020 that I have a problem with.

Thank you again,

John

I will be interested to see what they say even though I have only seen this very rarely. It was suggested that one of the work arounds is that there are some issues running 32 bit scenarios in 64 bit. they said to open TS in 64 bit and clone the scenario thereby making it a 64 bit. Running that one seemed to eliminate the problem. That doesn't help you much if you can't get the program started. Most folks are solving this by running the file verification and the starting issue goes away.

I’m placing my bet on a corrupt Workshop scenario.....

I have found this on my desktop after playing TS2020 with no effects on the game. From what I have found on the internet this is a Windows problem even as far back as Windows 7 if you read my Tomshardware link above and don't really think DTG can do anything about it as Peter has said there are hundreds/thousands of different computer setups. As far as I can tell by reading different forums this is only affecting a small percentage of TS users. It hasn't affected TS for me yet.

now is it just scenarios or the route it self of WS routes? just to clarify.

I couldn't tell if the problem is with routes or scenarios. I am not sure 100 percent with this. And I was thinking that I will remove all the routes out and leave few routes to see if the program of Train Simulator can run or not.

John

Trev123 -- one of the program is very old and I don't see how we can run this. That's MemTest86 and I don't know if that is wise to run because that program was designed for x86. I will run if you think that will fix the problem.

Thank you again,

John

Have you run a verify?