Atomic Systems

Following discussions on this thread about whether portals are still unstable, and after having discovered, when using the preview feature on my broken scenario, extremely odd behaviour around the Basingstoke portal, I set up a scenario just to test the Basingstoke portal. First of all, I had one train on Reading 4 set to Basingstoke as a destination. That worked without a problem. Then, I set another train in platform 1 as a local stopping service to have its destination as Basingstoke, with the same start time. Checking the drivers list, that appeared to be fine, too.

Then, I added two trains to the Basingstoke portal: one set as stopping passenger, start time 10.00, with its destination as Reading platform 2, and one as an express passenger, start time 10.02, with its destination as Reading platform 5. The original train then shows in the driver list as "Failed". So, I removed the original train, and tried to save the scenario. When I did that, I received this error:
Immediately followed by this one:
It them promptly crashes to desktop.

jamespetts wrote:
Immediately followed by this one:

Code: Select all

The instruction at "0x020fde43" referenced memory at "0xf56f897b". The memory could not be "read".

Clock on OK to terminate the program

It them promptly crashes to desktop.

Do other Games / CPU / Memory heavy applications run okay on your system for a prolonged period of time? I ask this because that particular error can be an early warning sign that a memory stick(s) are going bad. If it's a one off then it's more likely to be the programme but if it's doing it on other applications over a period of time then the next step is to start fault finding your system. The cheapest way is a nice reformat and reinstall of your operating system, if it still does it then start pulling bits of your hardware apart.

AndyM77 wrote:Do other Games / CPU / Memory heavy applications run okay on your system for a prolonged period of time? I ask this because that particular error can be an early warning sign that a memory stick(s) are going bad. If it's a one off then it's more likely to be the programme but if it's doing it on other applications over a period of time then the next step is to start fault finding your system. The cheapest way is a nice reformat and reinstall of your operating system, if it still does it then start pulling bits of your hardware apart.

I have not been getting this error from any other programmes.