Exception code 0xC0000005/ Exception info OUT OF MEMORY

[Carinthia]

Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll

That's often an external problem with DirectX, often in dealing with the rendering of reflections. It would be worth checking yours is fully up to date but it still could well be a problem with a specific asset.

John

[peterfhayes]

The error you have reported is a technical one in that in the editor you are trying to do something that causes TS to crash.

Exception code 0xC0000374 means STATUS_HEAP_CORRUPTION. It is the most common way to crash a C++ program. – Hans Passant Nov 14 '12 at 23:27

In other words you are trying to get Railworks something that it does not want or cannot do.

Modern computers can execute millions of instructions per second, and if one of them is erroneous, then the process could crash.

Heap corruption is a much more difficult problem to solve. The corruption can occur many millions of instructions before a crash occurs. Worse, erroneous code could alter memory that it doesn’t own, or is in use or is restricted.

https://blogs.msdn.microsoft.com/calvin ... xc0000374/
To even start to solve this type of error you need a memory dump and even then unless you are an expert coder, the error will be hard to find and fix. Then on the other hand it could resolve itself - computers are frustrating.
Basically it is a coding error from your editing that will be hard to fix, as we don't have access to the base code and you can't use a debugging tool to try and find the cause.
Sorry!
pH

[gptech]

Essentially then, we're in agreement that the error is not one caused by the core game itself--reinstalling and sticking the route back in won't fix it---but is due to a user generated change in something.

[PuffeB]

Date 30.11.12 last time that's recorded

Faulting application name: RailWorks.exe, version: 0.0.0.0, time stamp: 0x5d82130c
Faulting module name: ntdll.dll, version: 10.0.18362.387, time stamp: 0xa4208572
Exception code: 0xc0000374
Fault offset: 0x000df94d
Faulting process ID: 0x2b6c
Faulting application start time: 0x01d5a77b99b4d6db
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\RailWorks\RailWorks.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 7959beee-dabd-4df2-9c6e-98ca0981d03a
Faulting package full name:
Faulting package-relative application ID:

OUT OF MEMORY ERRORS FOR RAILWORKS
CrashRpt-Log-20191228-115230-{9851349b-8f76-4785-8f84-0d909b6be2d0 28/12/2019 11:52
CrashRpt-Log-20191228-120231-{842991a3-8293-4974-9b9e-b0aae185d01c '' 12:02
CrashRpt-Log-20191228-121633-{3ace5bdf-82f0-4ea9-9727-eed1b55eee26 '' 12:16
CrashRpt-Log-20191228-122550-{e16ad064-ab6f-4476-9364-e82f767cd5d1 '' 12:25
CrashRpt-Log-20191228-123313-{c1217e4f-479a-49f2-bdbc-3d7e51f4d9a8 '' 12:33
CrashRpt-Log-20191228-123909-{5037dc74-f44f-4228-bff5-fa5948e2a308 '' 12:39
CrashRpt-Log-20191228-131334-{d9d02f77-7b1e-421c-88be-1a695a823c5a '' 13:13
CrashRpt-Log-20191228-173755-{ee39007c-79c1-4028-ba8a-6a5a05a8522f '' 17:37
CrashRpt-Log-20191229-150224-{829cada4-d7e4-46b3-971a-27fd7c7fa274 29/12/2019 15:02
CrashRpt-Log-20191229-152354-{73c225b8-3a71-4446-9a06-4c46c1122dbb '' 15:23

Saved log to...

C:\Program Files (x86)\Steam\steamapps\common\RailWorks\TempDump\

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 quality settings or attempting to run the game in the 64-bit version, if this fails to resolve the issue please contact our Customer Support Team at https://dovetailgames.kayako.com

I would try to run the 64-bit version, RailWorks64.exe, and see if that helps.

[markpullinger]

and if you are editing stuff, it's location in program files (x86) is not ideal!

[Matthewp24]

Found out the problem with the tiles if does constantly has a problem with the error, remove the terrain and mix map, scancy and everything except for the tracks then it should reset on the tile and you don't have the out of memory error. ETC TILE +000086-000024 up and down

[tango4262]

I just want to add, ever since I have installed TS to it's own separate SSD, this problem has seemingly disappeared *touches wood*.