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
UDaManFunks
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.
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 S
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)
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