AOTS: Escalation - Ryzen 1700X CPU - DX12 benchmark crashes to desktop when SMT is on (works just fine with SMT off)

Ashes of Singularity - Escalation (v2.3 latest) - when SMT mode is enabled in the BIOS, the DX12 benchmark crashes to the desktop (after running for a bit), DX11 mode is unaffected. If I disable SMT mode on the BIOS, the DX12 benchmark completes just fine without issues.

System Configuration:

CPU: RYZEN 7 1700X
Motherboard: Asrock Taichi X370 (with V2.4 UEFI) - also happened on my Gigabyte AB350-GAMING 3.
Memory: 32GB DDR4 (2133 MT/s)
GPU: EVGA GTX1080TI (also happens on GTX1070 FE)
Driver: 384.76
OS: Windows 10 x64 (OS BUILD 15063.413) - running AMD Chipset 17.10 drivers and the Ryzen Balanced Power Plan

Steps to Reproduce:

1) Execute Ashes of Singularity - Escalation
2) In Video Settings, make sure it's using DX12 mode then Restart
3) Try running the built-in benchmark using "GPU Focus" Scenario. Make sure it says DX12 model, and that 16 logical processors are listed in the CPU section.
4) Run benchmark.

Expected Behavior:

Benchmark Completes

Actual Behavior:

Application Crashes to Desktop consistently when SMT is enabled.

Additional Observations:

Cleanly installed windows, ran Intel Burn Test, Memtest86, Prime95 stress test for 8 hours without any issues. Tried both Gigabyte AB350 Gaming 3, and my current board (after clean reinstall) but the problem keeps occurring when SMT mode is enabled.

Any ideas?

56,442 views 10 replies
Reply #1 Top

Note: tried this test 10 times - alternating between SMT on and SMT off (rebooting in between)

100% failure rate for me with SMT on running the DX12 AOTS using my Ryzen 7 1700X CPU.

Memory and CPU are not overclocked (2133 MT/s for the MEM), Temps are good under load (running Corsair H110i AIO)

Reply #2 Top

In one if the other threads a Dev confirmed the August 2.4 patch will have some dx12 stability fixes so hopefully that will fix your issue.

Reply #4 Top

Spoke too soon - problem is back.   Disabling SMT fixes it.

Reply #5 Top

Same issue here. Only way to get the game to run in dx12 is turn smt off in bios otherwise it crashes. using a ryzen 1700. Problem is then you lose the performance gains of smt...so that's not a working solution. bought the game yesterday and it already looks like i'm going to have to fork money for a different game if I want to scratch my rts itch. Shame I was kind of hyped. 

Reply #6 Top

Even with SMT disabled the GPU is most likely going to be the bottleneck so it doesn't make much difference. You could try DX11 and see how the system performs. No other RTS that I know of is going to make use of more than 2 cores.

Obviously it's annoying it crashes with SMT, so hopefully that gets fixed in the stability update which is supposed to be coming in August.

 

Reply #7 Top

This may be related to the Ryzen segv issues Linux users are running into when performing parallel compiles.    Both my Ryzen systems are affected, i'll RMA the R7-1700 and see if it fixes the issue.

 https://www.reddit.com/r/Amd/comments/6rwggi/ryzen_build_loop_compile_failures_under_linux/

Both my systems can't run the DX12 benchmark as well with SMT enabled.

Reply #8 Top

I tried the new 2.40 beta (of AOTS), even with Vulkan - the Benchmark crashes to the desktop.   It seems like I have a broken CPU (Linux GCC failures) - waiting to RMA the CPU.

Reply #9 Top

The developers created a opt-in hotfix for this issue ( version 2.41.28238 ) which works for me.   They are working with AMD to figure out why only certain Ryzen setups are affected.  

https://steamcommunity.com/app/507490/discussions/0/133261907141932644/?ctp=5