How do I fix Train Simulator Classic out of memory?
To fix the Train Simulator Classic out-of-memory error, run the 64-bit executable, leave the Windows page file enabled, close memory-heavy programs, clear the simulator cache and verify its files. If it fails only on one route or scenario, reduce scenery settings and isolate faulty or excessively heavy add-on content.
Why does Train Simulator Classic run out of memory?
Train Simulator Classic can exhaust its process address space, physical RAM, Windows virtual memory or graphics memory. Dense routes, high-resolution assets, numerous AI trains and long sessions all increase the load.
The 32-bit RailWorks.exe has a virtual address-space ceiling of roughly 4 GB, regardless of how much RAM is installed. The 64-bit RailWorks64.exe removes that low ceiling, but it cannot compensate for a disabled page file, insufficient disk space, an extreme scenario or a broken asset.
How do I clear the out-of-memory error?
- Confirm that the 64-bit simulator is running. Select the 64-bit launch option, then check the Details tab in Windows Task Manager for
RailWorks64.exe. An old desktop shortcut may still open the 32-bit executable. Do not assume that having 64-bit Windows automatically launches the 64-bit simulator. - Restart Windows and close heavy background programs. Web browsers, recording tools and other games can consume enough RAM or graphics memory to expose a marginal route. Also ensure the Windows system drive has free space for temporary files and virtual memory.
- Enable a system-managed page file. Open Windows Advanced system settings, find Performance and Virtual memory, then select automatic management or a system-managed size. Reboot after changing it. Disabling the page file is a common cause of memory errors even when Task Manager appears to show free RAM.
- Clear the simulator cache. In Train Simulator Classic, open Settings, select Tools and use Clear Cache, then allow the simulator to restart. This rebuilds cached blueprint data and is particularly useful after installing, removing or updating add-ons.
- Verify the installed files. Open Train Simulator Classic in the game client's library, choose Properties and run its installed-file verification. Back up deliberately modified default files first, because verification can replace them.
- Reduce the settings that allocate the most resources. Lower Scenery Quality and Scenery Density by one step, followed by shadows and texture-related detail if necessary. Retest the exact same scenario after each change. Our guide to balancing Train Simulator Classic graphics settings explains which reductions usually preserve the appearance of a route.
- Test a simple scenario on the same route. If a lightweight career, standard or Quick Drive scenario loads but the original does not, the scenario's player consist, static stock, AI traffic or scripts are the likely cause. If every scenario on that route fails, investigate the route and its required assets instead.
How can I identify what is using the memory?
The point at which Train Simulator Classic fails usually identifies the responsible layer. Repeatable failures are more useful diagnostically than an occasional crash after hours of play.
| Failure pattern | Most likely cause | Best next test |
|---|---|---|
| Most routes fail while loading | 32-bit mode, disabled page file or damaged core files | Confirm RailWorks64.exe, check virtual memory and verify files |
| Only one scenario fails | Heavy or faulty rolling stock, AI traffic or scenario scripting | Load another scenario on the same route |
| Every scenario on one route fails | Route scenery, a required asset or excessive route complexity | Clear the cache and test the route with lower scenery settings |
| The error appears after several consecutive runs | Memory retained during a long session | Restart the simulator and load the problem scenario first |
| The error started after adding content | Faulty, incompatible or unusually large add-on assets | Back up and temporarily isolate the newly added content |
If the message is actually a generic crash or dump-file notification rather than an explicit memory error, use our broader Train Simulator Classic crash-diagnosis checklist. Graphics drivers, overlays and damaged files can produce similar symptoms without exhausting memory.
Will installing more RAM fix it?
More RAM helps only when the 64-bit simulator and other programs are genuinely exhausting physical memory. It will not raise the address-space limit of the 32-bit executable, repair a bad scenario or fix a disabled page file.
Watch the Memory and GPU memory readings in Task Manager while loading the affected route. If system memory approaches its limit and disk activity rises sharply, additional RAM may improve both stability and loading time. On a computer with integrated graphics, the GPU also shares system memory, so high-resolution scenery can create pressure sooner.
What should I avoid when fixing the error?
- Do not disable virtual memory in an attempt to force Windows to use physical RAM.
- Do not install unofficial memory patches or replace the simulator executable.
- Do not delete the entire
AssetsorContentfolder; isolate recent add-ons and keep backups instead. - Do not return permanently to 32-bit mode just because one legacy locomotive fails in 64-bit. That points to an add-on compatibility problem, while 32-bit mode makes genuine out-of-memory failures more likely.
- Do not change several graphics settings and add-ons at once. Make one change, reload the same scenario and record whether the failure moves or disappears.