Access violations - unnerving - B&LE

[FourEightFour]

I'm having problems with access violations on the B&LE and a few other routes. I have not played this sim in a while and I'm having a hard time trying to figure this out, advice greatly appreciated. I've tried a few different steps. I'm creating a free roam on the B&LE in 64 bit mode with UP FEF and RWA rolling stock. I can open a fresh scenario only, I can save, and I am unable to run at all. I can open it in 32 bit mode and run without problems. My computer loads & runs the sim much smoother in 64 bit mode. Where does one start in the diagnosis? I'm coming back to the sim and 64bit mode is something new to me. Thanks for your help.

[buzz456]

I'm having problems with access violations on the B&LE and a few other routes. I have not played this sim in a while and I'm having a hard time trying to figure this out, advice greatly appreciated. I've tried a few different steps. I'm creating a free roam on the B&LE in 64 bit mode with UP FEF and RWA rolling stock. I can open a fresh scenario only, I can save, and I am unable to run at all. I can open it in 32 bit mode and run without problems. My computer loads & runs the sim much smoother in 64 bit mode. Where does one start in the diagnosis? I'm coming back to the sim and 64bit mode is something new to me. Thanks for your help.

First thing I would do is verify local files. It sounds like something is missing or borked somehow. Some had some issues with the 64 bit early on but they seem to have died down. I'm using it almost all of the time with no problems.

[mrennie]

Hi Justin, great to see you're back! I'm getting access violations all the time while trying to write the scenarios for my Promontory route - sometimes it even gives me a black-screen-of-death and I have to reboot the computer. I'd been using 64-bit most of the time, but I'm also getting it happen when I try 32-bit instead. The likelihood of it happening seems to increase the more often I go in and out of the editor. I've also noticed that quite often the track I'd laid months ago has become corrupted invisibly, without me having touched it, forcing me to re-lay some pieces of track. One caveat though - when I run the hardware health checks at boot-up, it reports that there's a problem with a memory chip, so maybe sometimes I'm simply straying into the address range that contains the fault. Have you done a full diagnostic on your computer?

[savv_nz]

I've also noticed that quite often the track I'd laid months ago has become corrupted invisibly, without me having touched it, forcing me to re-lay some pieces of track. ?

I'm unable to suggest anything about the scenario editor, but over on Dovetails forums they recommend (as of October 15....) using the 32bit version for route editing because saving in 64 bit may corrupt your tracks.bin file.
https://forums.dovetailgames.com/thread ... ute.13312/

[buzz456]

One I trust you all are using the F2 key before saves. The second thing is I am using a program from Iobit that is called a performance monitor (I'm sure there is other stuff out there that does the same thing) which when you click on it it releases RAM. It is one click and I do it before every restart or save. I bet I only get the access violation every maybe 30 or more restarts. I'm sure that is a major key. I do have 16 megs of RAM but there is something going on with a cache somewhere that doesn't like this to build up. It only release between 250-500 each time but it's more or less solved my crashing problem.
By the way this little thing is part of the free version of Advanced System Care from them.

[mrennie]

One I trust you all are using the F2 key before saves. The second thing is I am using a program from Iobit that is called a performance monitor (I'm sure there is other stuff out there that does the same thing) which when you click on it it releases RAM. It is one click and I do it before every restart or save. I bet I only get the access violation every maybe 30 or more restarts. I'm sure that is a major key. I do have 16 megs of RAM but there is something going on with a cache somewhere that doesn't like this to build up. It only release between 250-500 each time but it's more or less solved my crashing problem.
By the way this little thing is part of the free version of Advanced System Care from them.

Thanks Buzz, I'll give it a go!