F40ph 3-c Mbta Auto Brake Crash The Game Here

Discussion in 'TSW General Discussion' started by VION, Sep 4, 2021.

  1. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    Hello,
    I play the first service mode "801" with the F40PH MTBA on the Boston to Providence route and every time I manipulate the automatic brake lever to apply braking with the mouse cursor, I get this error message TSPrototype-Win64-Shipping.exe caused violation exception in NTDLL32 or something like that; I wanted to play the second service mode "803" Boston to Providence with the same loco and manipulating the automatic brake lever to apply braking always using the mouse cursor, it's the same and I get this same error message. The game closes completely and then the error message appears. I don't have this anomaly with the ASC64 loco.
    Does anyone got this anomalie and overall how to avoid the crash?
    Sent the error message by pressing the button on the bottom of the error message by writing these infos about what I was doing before the crash happened.
    Cheers
     
  2. LWDAdnane

    LWDAdnane Well-Known Member

    Joined:
    Mar 10, 2021
    Messages:
    348
    Likes Received:
    395
    I too have these crashes, and likewise they happen as I'm braking to approach a station, specifically South San Francisco Station, I don't know if others are affected as sometimes I can't get past South San Francisco. But again, sometimes it works fine, so really no idea what's going on. It's crashed and no mods, and no changes to my engine.ini
     
  3. FeralKitty

    FeralKitty Well-Known Member

    Joined:
    May 29, 2020
    Messages:
    405
    Likes Received:
    800
    Have you tried Steam's "Verify integrity of game files?"
     
  4. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    Yes indeed that was the first step I done then tried in windowed fullscreen then fullscreen mode but no luck. I verified also my engine.ini file which were clean from any tweaks. Also done a sfc /scannow analyse and there was any corrupted system files all 100% clean. I closed totally my L GUB software from logitech running in background to set some programmable button on my G502 mouse. No more luck; the problem come from elsewhere.
    Just went to test with the launch steam option with -DX12 and bam !!! no more crash using the mouse pointer to move the F40PH MBTA auto brake lever. Very very strange as the Dev's don't support DX12 feature as stated in the thread talking about PC crash. I m very surprised to conclude the DX12 feature has some benefit while DTG and his dev's staff don't support DX12 in TSW2. I m confused now.
    So I believe to keep the -DX12 launch feature option as long as DTG don't be able to fix the problem I got if there is something to do on their side.
    Anyway thank you for your response and interest on my problem.
    Cheers
     
  5. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    Thank you to your response and report. I don't know if trying the -DX12 launch steam option has to do about solving my problem but I can confirm this crash occur on the F40PH MBTA auto brake move using the mouse pointer; I tried to use the keys on the keyboard to apply brakes and no crash; tried also using the windows virtual keyboard also no crash. On my side only the use of mouse pointer moving the auto brake lever result in a crash. the message said TS2Prototype-Win64-Shipping do access violation in memory address (and I don't remember the exact reference, it was like something 0xfffffffffff or so. sorry to don't be very accurate)
     
    • Like Like x 1
  6. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    I come back but no more luck even with the -DX12 launch steam option feature; just went to play the second time table scenario with the F40PH MBTA the line 803 and got again a crash in the same condition using the mouse pointer to move the auto brake lever.
    So the error message said the same as earlier: TS2Prototype-Win64-Shipping cause access violation reading address 0xffffffffffffffff; and bellow is mentioned kernel32 and NTDLL. I don't know where this bug come from. For now I m constraint to use either the keys on the keyboard or the windows virtual keyboard to apply train brakes. Sorry not solved on my side.
     
  7. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    To day I sent a support ticket to Kayako. wait and see now.
     
  8. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    Hello, and sorry to come back about the trouble I got. Today I I rod carefully the advertising step by step to carry on published on the troubleshoot DTG support page. And reading all the steps I went to the Pagefile.sys set up through memory system management. Going to this item on my PC, I saw that all my SSD drives where managed by Windows automatic management for all my drives and the actual amount allocated virtual memory was a bit less than the recommended reading the infos given on the memory system management window. Following the advice given on the troubleshoot DTG support page, I sat up one pagefile.sys on my system drive C:/ with a minimum and maximum (same value) of 1.5x the amount of my physical memory which is 32 Gb in dual channel taking in mind 1Mb=1024 Kb. Moreover, I sat also another pagefile.sys on my SSD drive where TSW2 is stored, with manual values of 1.5x for the minimum and 4x for the maximum values of the total physical memory on my PC. After system reboot , I tested again this time playing the Boston to Providence route launching the Line 803 time table scenario with the same loco F40PH -3C MBTA. I don't got any crash from the start to the end of it, always moving the train brake lever using the mouse pointer. At this time I can't conclude to have fixed the crash on my side but hope this setup of pagefile.sys was a solution for me. I must to do more tests but if that could help some others, allow me to share with you my self experience.
    Cheers
    Gerard
     
    Last edited: Sep 6, 2021
  9. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    Hello and sorry to come back to this phenomenon of crashing when using the mouse pointer to manipulate the train brake lever; still not solved on my side despite having applied all the advice from DTG support and applied all the steps to avoid crashes. Is anyone else experiencing the same problem. I also know that using the mouse pointer to manipulate the power wheel on the BR155 loco, also has anomalies of the mouse pointer locking up when manipulating the wheel in the descending direction of the detent values. Would TSW2 have problems with using the mouse to operate the 3D controls on the cabs?
     
  10. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    Good evening; I am coming back to these crash phenomena and I apologise. I have just tried again with the same F40PH 3-C MBTA loco but this time on Steam offline. Well, even with my LG-HUB software and several very light programs running in the background, my three screens plugged in and active plus my IR track active and having run several time table scenarios one after the other, I didn't have any game crashes even when manipulating the automatic train brake with my mouse pointer. But as soon as I switch to online mode with Steam the problem reappears. So I think I've found my workaround for crashes is to play in Steam offline mode. Once again I'm sorry to bring up this recurring problem for me but I wanted to share my experience for others who may encounter these unexplained crashes.
    Cheers
    Gerard
    PS: Steam offline and DTG online
     
    Last edited: Oct 27, 2021
    • Helpful Helpful x 1
  11. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    Good evening and back to this crash phenomenon I just had again after today's last update for Boston Sprinter; I just did a Time table scenario with the F40PH 3-C MBTA and again I had a crash while manipulating the train brake lever with the mouse pointer. So my problem is still not solved and staying in Steam offline mode did not stop the crashes. I don't know what to do with the train brakes on the F40PH 3-C by manipulating the lever with the mouse pointer. I have no problems with the other locos under the same conditions. I really don't know what to conclude from this if it's a problem related to me or if it's a problem of the particular game of the F40PH 3-C MBTA.
     
  12. Teflon490

    Teflon490 Active Member

    Joined:
    Mar 29, 2020
    Messages:
    158
    Likes Received:
    127
    If you have 32GB or RAM, disable the pagefile completely, let the system use your RAM only. Might not fix the crashing problem since it is most likely not related to pagefile in any way, but it should give you better performance if anything.
     
    • Like Like x 1
  13. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    Re-doing an sfc /scannow, it reported corrupted files and fixed them; I re-did an sfc /scannow behind and no corrupted system files. I also reset my graphics driver by putting only the one given by windows 10 update from Nvidia (I uninstalled the last nvidia driver via the uninstallation of windows 10 programs and reboot of the PC; effectively in reboot I had only a screen with a basic driver in 800x600 apparently) then windows update installed me the Nvidia driver dated 09/30/2020 in version 456.71 After I replayed a scenario on the Boston to Providence, and there was no crash under the same conditions of using the mouse pointer to manipulate the train brake lever on the F40PH 3-C MBTA. It's strange that these crashes are random because I can't know exactly where it comes from. This last test makes me think that the graphic driver was involved but I have a doubt because none of the other locos are crashing. I don't know what to do to eradicate this random problem. I'm going to try to remodel my pagefile.sys and put it back the way it was originally and see if the problem persists or doesn't happen anymore. I have to do some more tests to be sure. In any case, thank you for wanting to help me.
    PS: in the Bios settings my RAM is on X.M.P. profile may be I must to lower the frequency at the the normal jdec don't know if it would be helping.
     
    Last edited: Oct 28, 2021
  14. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    <CallStack>ntdll 0x00007ffd82e30000 + 9cdf4 KERNELBASE 0x00007ffd80630000 + 21a5e TS2Prototype-Win64-Shipping 0x0000000140000000 + 136ef90 TS2Prototype-Win64-Shipping 0x0000000140000000 + 3806dde VCRUNTIME140 0x00007ffd6cf50000 + ecd0 ntdll 0x00007ffd82e30000 + a20cf ntdll 0x00007ffd82e30000 + 51454 ntdll 0x00007ffd82e30000 + a0bfe TS2Prototype-Win64-Shipping 0x0000000140000000 + 154d4bf TS2Prototype-Win64-Shipping 0x0000000140000000 + 1544a6f TS2Prototype-Win64-Shipping 0x0000000140000000 + 153b266 TS2Prototype-Win64-Shipping 0x0000000140000000 + 154d34b TS2Prototype-Win64-Shipping 0x0000000140000000 + 1544a6f TS2Prototype-Win64-Shipping 0x0000000140000000 + 154496e TS2Prototype-Win64-Shipping 0x0000000140000000 + 13f4139 TS2Prototype-Win64-Shipping 0x0000000140000000 + 1544842 TS2Prototype-Win64-Shipping 0x0000000140000000 + 279bd6b TS2Prototype-Win64-Shipping 0x0000000140000000 + 82864e TS2Prototype-Win64-Shipping 0x0000000140000000 + 10447ce TS2Prototype-Win64-Shipping 0x0000000140000000 + 1049c26 TS2Prototype-Win64-Shipping 0x0000000140000000 + 1049d10 TS2Prototype-Win64-Shipping 0x0000000140000000 + 1049d10 TS2Prototype-Win64-Shipping 0x0000000140000000 + 1049d10 TS2Prototype-Win64-Shipping 0x0000000140000000 + 1049d10 TS2Prototype-Win64-Shipping 0x0000000140000000 + 104fc26 TS2Prototype-Win64-Shipping 0x0000000140000000 + 104a3f1 TS2Prototype-Win64-Shipping 0x0000000140000000 + 8d82b3 TS2Prototype-Win64-Shipping 0x0000000140000000 + 8d7372 TS2Prototype-Win64-Shipping 0x0000000140000000 + 1231a21 TS2Prototype-Win64-Shipping 0x0000000140000000 + 1233d9c TS2Prototype-Win64-Shipping 0x0000000140000000 + 137f627 TS2Prototype-Win64-Shipping 0x0000000140000000 + 137ab31 KERNEL32 0x00007ffd81db0000 + 17034 ntdll 0x00007ffd82e30000 + 52651</CallStack>
    <IsCrashed>true</IsCrashed>
    <Registers />
    <ThreadID>9152</ThreadID>
    <ThreadName>TaskGraphThreadHP 20</ThreadName>
    </Thread>
    What does this mean for specialists?
     
  15. Teflon490

    Teflon490 Active Member

    Joined:
    Mar 29, 2020
    Messages:
    158
    Likes Received:
    127
    XMP should be fine, leave it on XMP profile for now.
    It is far from ideal to let Windows Update install the GPU drivers for you. Better to do it yourself and properly. First download the latest drivers from Nvidia drivers download page. Then download the utility called DDU - either from its homepage wagnardsoft or from guru3d website, these are valid sites to download it from.
    Then check this tutorial on how use DDU to clean any old traces of old driver files and settings , it is easy once you understand the basics:

    .


    First disconnect your PC from internet to prevent WU download garbage drivers again, then uninstall current drivers from control panel, restart, then run DDU to perform the cleanup.
    Then you can install the latest Nvidia drivers you have downloaded previously.

    Then report back how it behaves on the clean installation of latest GPU drivers.
     
    • Helpful Helpful x 1
  16. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    Hello, so I followed and applied the instructions in the video faithfully and scrupulously; everything worked fine regarding the installation of the new graphics driver.

    I also put my pagefile.sys back as it was originally set, i.e. "Let Windows manage for all drives". My RAM is set back to X.M.P.

    Unfortunately, after several hours of testing still using the F40PH 3-C MBTA, I had the game crash again while manipulating the train brake lever back and forth while holding down the left mouse button. And now the last test I did the crash also occurred with the traction manipulator and under the same conditions of using the mouse pointer, i.e. holding the left mouse button down and moving back and forth on to make the traction manipulator move
    .
    I must also say that this also happened with the F40PH 2-CAT but only very rarely during its use maybe once or twice. And that was when using the train brake controller as well.

    Otherwise all the other locos I have used have not caused any crashes.

    So here it's back to square one with the anxiety of being able to play the F40PH 3-C MBTA and not being able to finish a session properly. It's a real shame as I'm particularly fond of this style of Loco.
     
  17. Teflon490

    Teflon490 Active Member

    Joined:
    Mar 29, 2020
    Messages:
    158
    Likes Received:
    127
    Here's a thought...I noticed you always mention the crash happens when you are using your mouse. Try to manipulate the cab controls using the keyboard, not the mouse, and see if you can get any crashes like that.
     
  18. VION

    VION Active Member

    Joined:
    Dec 8, 2016
    Messages:
    269
    Likes Received:
    90
    Yes indeed as written above, as soon as I use either the keys on keyboard or the windows visual keyboard, I don't get crashes. I already tested with my LG HUB software running in background and without for my G502 but no luck. It seems TSW2 has something to do with the use of a mouse pointer which bring some erratically behavior mixing the use of gamepad features and a simple mouse. I don't know. But the support tell me to follow this issue named :
    • Issue with mouse interaction in Train Sim World 2. Instances where the mouse cursor is seen to get stuck and the user is unable to drag the mouse.
    VoilĂ . I don't know if others get similar issue using the mouse pointer or if I'm the only one.
    Surprisingly, it happens only on this F40PH 3-C MBTA Loco and one or two time on the other F40PH 2-CAT; otherwise all of the others locos don't give any crashe using the mouse pointer to move the levers/switches/buttons.

    PS: At the moment I'm testing using my thrusmaster joystick with the Xpadder application to map my stick and some buttons and it seems to work well as the mapping refers to keyboard key presses anyway.
     
    Last edited: Oct 31, 2021

Share This Page