Save Dump File Error

[UPSD70ACe]

Hi & Hello well I am working on my Amtrak California Route.I am on my Laptop not on my Desktop PC.When ever I save a scenario I am getting this error.
Saved Dump File To C:\TempDump\TS2014-v38.38.dmp.So what dose that mean hope you can help soon Thanks Y'all.

[peterhayes]

UPS
AFAIK .dmp files are quite hard to read and interpret as you usually need to use Windows debugger tools (and you think the RSC editor is bad) plus they (the .dmp files) are pretty useless as we do not have access to the TS2014 source code - only RSC does.
It might be better to run Process Monitor or Process Explorer or VMMAP in the backgrounds and then analyse their logs to see what might have happened. Even here its not easy to interpret errors.

[UPSD70ACe]

Will this happen on my desktop PC.I have win 8 Icore5 2TB HD Drive.I plan to copy the Route I had edited to my TS2014 on my Dell Desktop PC?

[GSkid]

I've gotten the dump file error when the sim crashes trying to quick drive some trains I built in the consist builder. It only happens on certain routes with these consists. They used to work on them all, but something has changed. It's happened since the subsequent updates to TS2014. Not sure if the updates broke it or me reinstalling sounds packs since then did something. Cuz my consist builder trainsets were working in 2014 PRIOR to those events on all the routes instead of just some of them.

I'm just gonna delete my consist builder trainsets and start from scratch again. Maybe that will get them working on all the routes again.

Something else I've noticed with TS2014. People say their load times are quicker. I'm not sure what they are talking about. Mine have gotten SLOWER. What I mean by that is.... TS2013 in quick drive for example. If I loaded a route the first time and exited back out to the main menu and re-loaded the same route all over again.... the second load up would be MUCH QUICKER than the initial first load up of the route.

With TS2014...... my 2nd load up of the route is just as long as the first initial load up time of the route. It's almost like TS2013 cached the route correctly and TS2014 somehow isn't. Just weird!