Crashes to desktop

Discussion in 'Misc' started by stijndp, Dec 27, 2020.

  1. stijndp

    stijndp Villager

    Joined:
    Jun 24, 2018
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Hey.

    Played AoEO from Alpha until shutdown. Then later intermediately tested the fan projects trying to revive the game. In 2018 started playing Celeste but somewhere along the line I started getting CTDs. Didn't find a solution and picked up other games.
    Now I'm on a different system and trying to get back in the game but somehow I'm still getting the same CTDs.

    Symptoms:
    - First place I get CTDs is while switching regions. I can switch around but after playing for a random amount of time and then switching map right at the end of loading, the client CTDs. The sound keeps working on the loading screen until the crash so I can hear that I "arrive" in the region but right at the end I get the CTD. I can hear that bell chime just before the CTD.
    - Second place and much more annoying CTDs are during missions. I can play for 15-60 minutes but somewhere the client will just disappear. It's not a consistent action in the game that it happens on. The only consistency in the inconsistency is that the more units, the faster the CTD will come. For example I can play multiple quests with low unit count in the mission before it crashes but if I play a 4vs4 skirmish, it'll crash around 15 min playtime when a few 100 units are on the map.
    - Third problem doesn't give CTDs but maybe it might be related and could help in the diagnose. In the game after a short while art assets randomly stop loading or displaying correctly.
    It happens with loading screens where the loading screen will be completely white but text and progress bars are still there. It's also not all loading screens at once. Some will become white while other loading screens just keep displaying. And the next time I get the same loading screen, it might be there or one that was showing previously is now white.
    And I get the same in UI dialogues where the background of the dialogue is completely white but everything else like text or buttons keep showing. And just like with the loading screens; when it happens to some, some others don't have it.
    I added a screenshot of a failing UI dialogue and also loading screen in the link I provided below.

    Things I tried:
    - Updating drivers etc
    - Enable/disable SLI
    - Full screen/Windowed mode
    - Tried both the install I have from Steam and a standalone install
    - Tried game scans
    - Tried deleting everything and reinstalling
    - Tried the extra installs mentioned on the install page

    I made a collection of things that can maybe help a diagnostics. They're all at https://www.dropbox.com/sh/hoqomlzckctec0n/AACbVYbVSVT1HVNZa99YcChHa?dl=0
    Logs from the client folder. Logs from Windows event viewer. Dxdiag and aida64 report for software and hardware config and also a 40 minute pingplotter while playing the game and having a CTD at the end. And some screenshots of the assets problem.
    I can't manage to create a dump. When I try to enable diagnostics mode, the first time on fresh install the game adds the procdump executables but whatever I try, no dumps get created in the documents folder on crash. If the diagnostics mode is native to the client I understand why the exception wouldn't be caught because it's a hard exit with fault 0 but if the launcher is meant to monitor, something is going wrong there.

    Maybe an interesting thing I can add is when I get a CTD while playing missions, the faulting application is spartan.exe and the faulting module is spartan.exe. When I get a CTD on the loading screen when switching regions, the faulting application is still spartan.exe but then the faulting module is d3dx9_40.dll.
    Other than that I don't manage to find much in there that I can do anything with.

    The problem stumps me.
    Assets not loading could suggest game files are wrong. But they don't always fail and I've done so many game scan and complete reinstalls already.
    The CTDs happening at a random time but the more memory used, the faster they happen indicate memory bugs. But then every player should be getting those. And if they were oom exceptions, .NET would catch them instead of giving a CTD.
    It doesn't appear to be network because ping and packet loss is stable.
    The problems are also isolated to Celeste. Games with bugs I'll encounter bugs but I mean that in general, among hundreds of other games, I don't have any that show similar problems. If other games or software did, it would make it more likely that hardware or drivers would be the main candidates as the cause. Other games from 30 years ago to today work fine so it's not a general system problem. And no other Microsoft games from the era or that used to have GFWL have problems so it's not that there are certain API calls or libs they used that are failing.
    And the problem has carried over from my old 3930K based system with Win7 to my 3950X based system with a fresh Win10.

    Hope someone has an idea what is happening.
    Been programming .NET for over 15 years so if needed you can talk me through more advanced debugging if it would help. Or if there are other simple things to try that I've undoubtly overlooked.
     
  2. Loading...


  3. Kevsoft

    Kevsoft XLiveless Dev
    Staff Member Administrator

    Joined:
    Oct 24, 2017
    Messages:
    244
    Likes Received:
    188
    Trophy Points:
    43
    The only thing I was able to read out of this data that all these crashes either directly or indirectly have to do with the render system. Other than that I was not able to find the cause of these crashes.
     
  4. stijndp

    stijndp Villager

    Joined:
    Jun 24, 2018
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    Thanks for looking.

    With the lack of a dump working, I attached the debugger trying to get more info.
    It's at https://www.dropbox.com/s/fzyh1x146607gcs/Debug.txt?dl=0

    The log until line 183 is from the startup screen logging in, loading and playing a mission.

    Then things hit the fan. This is by spartan itself just before the debugger breaks.
    (53f0.149c): C++ EH exception - code e06d7363 (first chance)
    (53f0.149c): C++ EH exception - code e06d7363 (!!! second chance !!!)
    eax=012fd300 ebx=1fec75c4 ecx=00000003 edx=00000000 esi=00a9b048 edi=134f8200
    eip=760ca892 esp=012fd300 ebp=012fd35c iopl=0 nv up ei pl nz ac pe nc
    cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00200216
    KERNELBASE!RaiseException+0x62:
    760ca892 8b4c2454 mov ecx,dword ptr [esp+54h] ss:002b:012fd354=27288a65
    0:000> g​

    Then I try to force to continue it.
    WARNING: Continuing a non-continuable exception
    (53f0.149c): Break instruction exception - code 80000003 (first chance)
    eax=012fd300 ebx=1fec75c4 ecx=26075965 edx=00000000 esi=00a9b048 edi=134f8200
    eip=00817c37 esp=012fd3a4 ebp=012fd3b0 iopl=0 nv up ei pl zr na pe nc
    cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00200246
    Spartan!clrRuntimeIsConfigDefined+0x1723e7:
    00817c37 cc int 3
    0:000> g​

    And upon more defibrillator shocks it just keeps repeating.
    (53f0.149c): Access violation - code c0000005 (first chance)
    First chance exceptions are reported before any exception handling.
    This exception may be expected and handled.
    eax=0093bdb4 ebx=1fec75c4 ecx=9acc1768 edx=00000009 esi=00a9b048 edi=134f8200
    eip=00923ba8 esp=012fd3a8 ebp=012fd3b0 iopl=0 nv up ei pl nz na po nc
    cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210202
    Spartan!clrRuntimeIsConfigDefined+0x27e358:
    00923ba8 8f ???
    0:000> g
    (53f0.149c): Access violation - code c0000005 (!!! second chance !!!)
    eax=0093bdb4 ebx=1fec75c4 ecx=9acc1768 edx=00000009 esi=00a9b048 edi=134f8200
    eip=00923ba8 esp=012fd3a8 ebp=012fd3b0 iopl=0 nv up ei pl nz na po nc
    cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00210202
    Spartan!clrRuntimeIsConfigDefined+0x27e358:
    00923ba8 8f ???
    0:000> g​

    When I then let the patient go with an exception not handled, it's last breath before spartan.exe crashes itself.
    eax=00000000 ebx=0489fa7c ecx=00000000 edx=00000000 esi=00000000 edi=00000000
    eip=771f198c esp=0489f9a4 ebp=0489f9f8 iopl=0 nv up ei pl nz na po nc
    cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000202
    ntdll!NtQuerySystemInformation+0xc:
    771f198c c21000 ret 10h​

    Got assembly readers on the team? :)
     
  5. Luciano

    Luciano Administrator
    Staff Member Administrator

    Joined:
    Oct 23, 2017
    Messages:
    11
    Likes Received:
    4
    Trophy Points:
    3
    what's the clock speed on your RAM?
    what is your motherboard's model?
    when you did the reinstall - did steam install directx runtimes?
     
  6. Provin915

    Provin915 Long Swordsman

    Joined:
    Apr 21, 2020
    Messages:
    22
    Likes Received:
    5
    Trophy Points:
    3
    I've recently had a couple of crashes too. Especially, during the winter leg event quests.. Mostly, random spartan errors. Will try to ss and post next time I get one.
     
  7. stijndp

    stijndp Villager

    Joined:
    Jun 24, 2018
    Messages:
    3
    Likes Received:
    0
    Trophy Points:
    1
    On the 3930K it was DDR3-1600 10-10-10-30.
    On the the 3950X https://www.dropbox.com/s/iplw55pvksbh145/3950X_memory.jpg

    Motherboard Asus Crosshair VIII Hero Wifi.
    Crashes happen with both Realtek audio and separate BT headphones. Also uninstalled Sonic Studio 3 from Realtek while trying to run the game with as few 3rd party DLLs as possible.

    Steam went through the Prerequisites folder like usually. On reinstall it didn't install anything since it has the latest Dx and all C++ redists. GFWL it keeps repeating since the GFWL installer can't find the files anymore.
    I also downloaded the standalone setup from Ms and as expected it had nothing to install for DirectX.
     

    Attached Files:

  8. Luciano

    Luciano Administrator
    Staff Member Administrator

    Joined:
    Oct 23, 2017
    Messages:
    11
    Likes Received:
    4
    Trophy Points:
    3
    Kev will be adding more client side logging with an upcoming patch. I hope you can try again once we release it so we can try and clear this up.
     
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice