Phoenix Point completely unplayable after Ancients DLC downloaded, and newest update installed - Stack trace/Crash supplied

The game refuses to function properly now that I have enabled the new Ancients DLC. It has crashed 4 times now in 15 minutes of gameplay. All in the first Jericho mission where the soldiers go crazy. I have to save after every single move to get through this…

Where are PP crash logs stored so I can provide the related crash logs?

Just use F12 it should upload all relevant logs and such.

What does that mean, exactly? Press F12 during the crash? After the crash?

Also, since it may be relevant, I have:
Ryzen 3900x
RTX 2080 ti
Gigabyte Auros x570 Master

I found the log in APPDATA. Here is the error:

========== OUTPUTTING STACK TRACE ==================

RtlLookupFunctionEntry returned NULL function. Aborting stack walk.
0x00007FFE978C40EB (UnityPlayer) UnityMain
0x00007FFE978C3BFA (UnityPlayer) UnityMain
ERROR: SymGetSymFromAddr64, GetLastError: ‘Attempt to access invalid address.’ (Address: 00007FFE96F70FE3)
0x00007FFE96F70FE3 (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: ‘Attempt to access invalid address.’ (Address: 00007FFE96F5F1C2)
0x00007FFE96F5F1C2 (UnityPlayer) (function-name not available)
0x00007FFE978B2CF8 (UnityPlayer) UnityMain
ERROR: SymGetSymFromAddr64, GetLastError: ‘Attempt to access invalid address.’ (Address: 00007FFE9704DF5C)
0x00007FFE9704DF5C (UnityPlayer) (function-name not available)
ERROR: SymGetSymFromAddr64, GetLastError: ‘Attempt to access invalid address.’ (Address: 00007FFE9704CF8D)
0x00007FFE9704CF8D (UnityPlayer) (function-name not available)
0x00007FFF09E25C1D (USER32) CallWindowProcW
0x00007FFF09E257EC (USER32) DispatchMessageW
0x00007FFF09E31F83 (USER32) IsWindowVisible
0x00007FFF0ACBFDE4 (ntdll) KiUserCallbackDispatcher
0x00007FFF07EC10C4 (win32u) NtUserPeekMessage
0x00007FFF09E294F2 (USER32) PeekMessageW
0x00007FFF09E29AE9 (USER32) PeekMessageA
0x00007FFEDC65F3F3 (atcuf64) AtcQueryRegion
ERROR: SymGetSymFromAddr64, GetLastError: ‘Attempt to access invalid address.’ (Address: 00007FFEDC63588B)
0x00007FFEDC63588B (atcuf64) (function-name not available)

========== END OF STACKTRACE ===========

A crash has been intercepted by the crash handler. For call stack and other details, see the latest crash report generated in:

  • C:/Users/Asyranok/AppData/Local/Temp/Snapshot Games Inc/Phoenix Point/Crashes

I cannot play for more than 5 minutes without encountering this. It doesn’t matter what mission I play. I have now tried several.

As a result, the game is unplayable. Please let me know what other information I can provide you to get working on a hotfix. This may be limited to high end hardware, for all I know. But it is absolutely a blocker from playing the game. I very recently, with absolutely no changes, played previous versions of the game before the newest update and newest DLC with no issues.

Still, I am going to underclock my Gfx card to see if that helps.

Edit: Underclocking my GFX card well below (~250mhz core, -1000k clock) the factory speed has already made it far more stable. I needed to do this to make OuterWorlds more stable too. But it seems to be working.

The crash log is located in a different location than the player and output files. C:/Users/[USERNAME]/AppData/Local/Temp/Snapshot Games Inc/Phoenix Point/Crashes[timestamp]

Your config is too fast for this game. Take out something and try again. :slight_smile:

Here are Github gists of the error files. The crash.dmp file is some sort of proprietary file, and would be rendered useless/corrupted in a gist. I’d need to attach it directly to this post, but I don’t see a file upload option. Here are the two log files along with the dump:

Error Log:
Player Log:

Underclocking to around 1600mhz has made it 100% stable so far. It was originally at 1800mhz core clock, The base clock for the base 2080ti is 1550mhz, but for this version of the 2080ti, it is a 1650mhz out of the box clock. So I met it midway between the two clock speeds. I also had to do this for Outer Worlds. It would crash every 5 minutes as well. Underclocking got it to crashing every 40 or so minutes. That game was far less stable on launch than this.