Atomic Systems

Yeah well, the update and changes I have made have made no difference! Windows is still losing focus when that host runs and TS still minimises, the only way to stop it from affecting TS is to disable it with unlocker whilst playing TS...

Press Windows+R to open the “Run” box. Type “cmd” into the box and then press Ctrl+Shift+Enter to run the command as an administrator.

Thanks.

Once again could those that are experiencing these scenario access violations to try disabling shell experience host and then run the troublesome scenario to check that it isn't this process that may be causing the error? I use unlocker https://www.iobit.com/en/iobit-unlocker.php to rename the .exe.

smarty2 wrote: I use unlocker https://www.iobit.com/en/iobit-unlocker.php to rename the .exe.

Disabling what is a pretty much essential Windows service is not the answer Martin---

‘Can I disable the Windows Shell Experience Host process?’

You can’t, and you shouldn’t. Disabling Windows Shell Experience Host will prevent you from getting the necessary visuals in Windows 10. Even if you try to end the process, your OS will start it automatically in a while. As such, if Windows Shell Experience Host eats up your RAM and CPU every now and then, your best bet is to troubleshoot the issue.

(https://www.auslogics.com/en/articles/w ... indows-10/)

smarty2 wrote:I have killed Cortana and buried her.

How? Once again, a system file/process so doing that incorrectly can/will have serious consequences.

By using unlocker to rename searchui.exe, only a little inconvenient for the start and run options plus shutting down, which a ctrl alt delete sorts out once. As for that blasted shell host, running the sfc command seems to have worked?

As for disabling shell host whilst running TS was simple using unlocker, had no significant problems disabling it. And it was easy to re-enable it after.

smarty2 wrote:As for that blasted shell host, running the sfc command seems to have worked

smarty2 wrote:Yeah well, the update and changes I have made have made no difference

….so rather than take the logical, and suggested, steps you decided to hack into the OS and then go back to what should have been a primary course of action?

I have just read some interesting info here on the Railworks forum about "Access Violation". Also on page 12 there is a list of files by Budge4 that were in a TS2019 update v65.7. I don't appear to have received this update. Does anybody else have tis update?

http://railworks.freeforums.net/thread/ ... de?page=11

Mike.

gptech wrote:

smarty2 wrote:As for that blasted shell host, running the sfc command seems to have worked

smarty2 wrote:Yeah well, the update and changes I have made have made no difference

….so rather than take the logical, and suggested, steps you decided to hack into the OS and then go back to what should have been a primary course of action?

Hey hang on a minute there Gary, you swapped those comments round in order to suit your argument! Swap em round and it all fits as it actually occurred.

Naughty lad!!!

Had my first crash with TX2019, everything has run fine so far even the demanding routes that always crashed under TS2018, but I always had problems with the GEML route London to Norwich could never complete the full run without saving and reloading and one scenario I started crashed and would not reload, thought it would work under 64bit, but no still does not work, then I decided I would try another scenario that I made but again crashed a couple miles north of Ilford, will give my last scenario a try if this fails, thinking of deleting the route, no point having it if I can drive Norwich to London, might as well stay with default Ipswich version unless I keep it just for Norwich to Ipswich.

I completed the full Glasgow to Preston run with the merged WCML north, WCML Shap and Glasgow Edinburgh update with lots of different AI and it worked perfectly, even I did as I don't normally do such a long run all at once.

david1 wrote:Had my first crash with TX2019, everything has run fine so far even the demanding routes that always crashed under TS2018, but I always had problems with the GEML route London to Norwich could never complete the full run without saving and reloading and one scenario I started crashed and would not reload, thought it would work under 64bit, but no still does not work, then I decided I would try another scenario that I made but again crashed a couple miles north of Ilford, will give my last scenario a try if this fails, thinking of deleting the route, no point having it if I can drive Norwich to London, might as well stay with default Ipswich version unless I keep it just for Norwich to Ipswich.

I completed the full Glasgow to Preston run with the merged WCML north, WCML Shap and Glasgow Edinburgh update with lots of different AI and it worked perfectly, even I did as I don't normally do such a long run all at once.

I suspect that the 64 bit version has only eliminated the crashes caused by the 32 bit memory limit, and we are still left with all the other errors that crash the programme. At least the crash reports are now being sent - to somewhere - so with a bit of luck someone at DTG will be analysing them to find out what the causes of these crashes are.

Smarty
Did you try to use the Command Prompt (Admin) from the right-click Start menu. You need to get sfc /scannow working which may fix this issue. You could also try the "DISM" commands as they may help! https://www.windowscentral.com/how-use- ... s-10-image.
Wan'y Cortana the 4th (unacknowledged) wise person?
pH

alanch wrote: I suspect that the 64 bit version has only eliminated the crashes caused by the 32 bit memory limit, and we are still left with all the other errors that crash the programme. At least the crash reports are now being sent - to somewhere - so with a bit of luck someone at DTG will be analysing them to find out what the causes of these crashes are.

Hi Alan,

As virtually every time I close TS2019 after running a modified scenario, I get the message that a crash report has been sent, I doubt if many of them are being investigated as I assume they must have received millions by now

One does wonder why this had not been reported by their beta testers though? Or if it has, then why was the 64 bit version released when it was? Always the problem when you announce a release date and have to abide by it...

Mike

mikesimpson wrote:Hi Alan,

As virtually every time I close TS2019 after running a modified scenario, I get the message that a crash report has been sent, I doubt if many of them are being investigated as I assume they must have received millions by now

One does wonder why this had not been reported by their beta testers though? Or if it has, then why was the 64 bit version released when it was? Always the problem when you announce a release date and have to abide by it...

Mike

Hi Mike - I've only had three crashes so far, and I've been exclusively running scenarios that either crashed or woldn't even start before. Most are running through to the end often with saves, pauses, overnight rests, etc., while one crashed out to the desktop after an hour and one crashed after the scenario ended - I'm pleased that it is working so well now.

Has anyone else tried the modified scenarios your computer is crashing TS on? Are you running them straight from the editor, or from the main menu?

smarty2 wrote:you swapped those comments round in order to suit your argument!

So we'll read them in chronological order...

smarty2 wrote:Yeah well, the update and changes I have made have made no difference!

...so as the advice you'd been given was to run sfc, the first concern would be to get you able to run that command, not shooting off on a tangent.
Eventually it seems you got it working, with apparent success...

smarty2 wrote:As for that blasted shell host, running the sfc command seems to have worked

That still fits my argument Martin; getting sfc working (and be honest, it's because of your actions that it wouldn't) is/was paramount.
Focus Assist won't help you with a service consuming resources, it only suppresses notifications.
I'll second Peter's comments regarding DISM if the problem rears it's head again---it's possible that you've corrupted the in-built OS image so any repair from that would only be putting the problem back in.

Martin, which bit of Cortana makes you want/need to get rid of it?