.dmp crashes

[5292nate]

Hey guys, I'm back again. Same crap but instead of being on the NERW route, this happens all the time, any route, no matter what I'm running. I've run RAM cleaners, and tried everything Buzz and others have recommended. I'm just at my wits end with this crap. Does anyone else have this problem?

38011786_1863510310611310_457732183906320384_n.jpg

[BoostedFridge]

Have you tried doing a file verification?

[5292nate]

Yes I have. All that did was reset every sound and other mod I've made to the game.

[gtrtroger]

Too many workshop scenarios...... unsubscribe from all of them, clean up any that don’t get removed automatically (this does happen a lot) with RWTools, then restart the game. Should be ok. You can resubscribe to the scenarios as you need too later...nothing lost.

[NS349]

yeah had that problem for a while and still get it from time to time, I can say I've done everything from a clean install to not many dlc, then thorugh the years I've had many routes and third party assets etc.. and its hard to figure out what exactly is causing it, but just from my experience I noticed I get this .dmp crash when I have other tabs running like chrome or firefox. So I try to just only have TS running and nothing else, main reason because TS is so large and needs the memory and space to run with that said, I have a very decent rig, but I feel its just how the game engine is and not like other games where you can multi-task and do other things. Also, I have noticed I have this problem with third-party routes and some on DLC like Marias Pass and Cajon Pass. If you also ever edit a route or scenario and use other assets from other dlc or third-party things can cause this issue.

[5292nate]

I unsubscribed from every workshop scenario and same deal. I just don't get it.

[buzz456]

Have you run the system check to make sure your RAM is all working?

[trev123]

Lowering your graphics settings can sometimes fix this issue.

[peterhayes]

IMO This has nothing to do with Physical RAM and you can verify the game files until the cows come home and that won’t fix anything.
I think that you produce quite a few mods to TS (reskins etc?) and possibly one of your "enhancements", as TS starts or runs, corrupts the VAS, and causes TS to crash.
If it was anything to do with RAM (memory) then Windows would crash with a BSOD!!
Somewhere in your system you have a “corrupt” file(s) that is causing the crash. Probably something that creates a serious invalid page fault.
Open “View Reliability History” in Windows - click on the white cross in the red circle at the time of the crash. Is there a critical error for railworks.exe OR for windows (eg explorer), or a kernel error?
Click on view technical details.
What does it say for the following (if present)

Faulting application name:
Faulting module name:
Exception code:
Fault offset:
Faulting process id:
Faulting application path:
Faulting module path:
Report Id:
Faulting package full name:
Faulting package-relative application ID:
Look at several - Are all the crash details the same for each dmp file created?

Diagnostics Optional
Have you run basic windows diagnostics: GOOGLE all
sfc /scannow
dxdiag
chkdsk /f/v/x

How much FREE space on your TS2018 install?
Is TS2018 installed in C:\Program Files (x86)
Antivirus\Malware\Firewall set to exclude Railworks.exe and Steam.exe?
Is UAC turned on? if yes try turning it off temporarily - Google User Account Control.

My solution (drastic last resort):
Copy the Assets and Content folders and keep in a safe place.
Delete the railworks folder.
Open steam and reinstall TS.
Also copy this pristine install to a safe place, it can be used to restore TS if you get a crash adding the saved files (below).
Now add the SAVED Assets and or Content folder (say 10 at a time) until you get a dmp file.
You can then easily find the offending asset/route that is causing the crash.
It will not be easy to fix this error.

pH

[Chacal]

If you haven't done this already, run TS with Logmate.

[jalsina]

If you haven't done this already, run TS with Logmate.

And take a look (in the logmate) for anything related with files located in the Content folder root.