I’d also have a hard time thinking it’s the Ryzen because I’d imagine there would be more reports for that. Ryzen 3000 series has a lot of different skus and I can’t imagine it would be just to thr 3900x. And I’d assume I’d see problems in other games too.
The access violation piece is what is interesting to me. I’m a programmer for a living and usually that one means a bug in my code.
Games crash when too many cores/threads are in use is nothing new. And the R9 3900X does have 24 or 32 threads.
I really don’t think that’s true. Having threads available doesn’t mean that the game has to make use of them… that’s just not how computers work.
I had a couple of crashes too. Setting vsync limit to 60hz helped for me. Maybe it’s a power issue… although my psu is fine, but does this game go bonkers with power draw or power fluctuation when fps goes over 100 and back to 50’s in some places. Just a guess.
That sounds like it might be related. I think the full screen map I see >100 FPS, so I’ll try to set vsync and see if that helps
This is exactly what I say about too many threads.
I’m going to try both now that I have some time and will report back.
I tried with all permutations of vsync and SMT and SMT is definitely the issue.
@Chessqueen, while I don’t think “too many threads” is the best way to describe the issue (because the number of threads isn’t the problem; it’s an issue with any single physical core being able to simultaneously process more than a single thread of execution), there definitely is an issue with SMT in this game on Ryzen 3xxx series CPUs at the very least. I’ve seen threads across the internet about all Ryzen generations having issues with SMT enabled including Rainbow Six Siege, Ashes of the Singularity (with dx12), and Battlefield 1 also.
It seems like this should be an issue investigated by @warhorse, even if their response is to push the issue up to Crytek to debug. My instinct from being a programmer for years is that this smells like a race condition. Access violations don’t happen just because SMT is enabled.
There is no good reason why I should have to disable SMT to run a game. I didn’t buy a CPU with 12 cores/24 threads just to game; I need all those threads to get other work done and rebooting to enable/disable SMT is a massive waste of my time.
If anyone at Warhorse is reading here, I am more than willing to help debug the issue in any way I can.
No. What you mean about SMT would just slow down the performance, but not crash a game. Too many threads are a known issue when a game crashes.
Maybe you can limit the usage of threads in the game config file?
Did you try a clean install of your GPU drivers? Is your GPU OCd? I have a GTX-1080, and if I OC it at all, it does exactly this every time, but not in any other game. Are you sure DX, VC Redist. and .NET are all up to date? Sometimes, if I reinstall windows, I forget to do this since my games are all installed on another drive, and they crash because of this, sometimes there’s an error window saying some file is missing, but sometimes not. It really sounds like an OCd GPU to me, since it always runs fine for a few minutes before crashing to desktop (in my experience with KCD, GTX-1080 and my 1800x / Crosshair Vi Hero / 64 GB RAM / Windows 10 1903 (but did this in previous versions). Basically, I decided the slight OC on a card that like most GPUs made today, OC themselves anyway… just wasn’t worth the instability, extra heat and issues like this, so I have a stock GPU profile running with this game (just upped the power slider).
We already know it’s a game bug with SMT on too many threads.
Wow. If that’s the case, maybe there’s a way to limit the thread countin the ini file. That would work fine, if possible. . and make for an easy fix for WH.
Better to optimize/tweak the game for using more threads than to limit them.
@LG25, yeah, I did do the vast majority of the steps you suggested. I didn’t have any sort of OC, so that wasn’t the problem, and I did do all the reinstalls. The only step that did help was reducing the number of threads available to the game. At first, I was doing that by disabling SMT, but that’s a massive waste of time to do every time I want to play a game. I ended up finding the “sys_streaming_CPU” option in the cfg file for the game. I tried a few different options and settled on 8 for my machine and that seems to be working for the time being.
@Chessqueen, do you have any links to other posts on here or even on other forums around the internet? I want to read what other people are experiencing if this is an actual issue with the game. If it weren’t for the fact that reducing the number of threads available to the game fixes the issue for me, I’d never believe that having too many threads available to a game could cause that game to crash. It’s just insane because just having threads available doesn’t mean a program needs to use them all. It’s an insane issue so I want to see what other people are seeing.
There was another user here who had stability issues with Ryzen 3000.
This does not mean there is something wrong with the cpu - this is the best cpu you can actually get.
But it’s a well known fact that games can have issues with too many threads. Old games crash or have sound stuttering when they don’t run on one single core and even modern games are made for 4 threads and can crash when you have too many (6 or more). Risen 3 had this bug too. It crashed on hexa core systems. But the devs fixed it in a later patch.
Could it be your BIOS? I think Jayz2cents had trouble with his 3900 and was waiting for a bios update.
BIOS is fully up-to-date. I’ve been keeping it up-to-date already, but I double checked when this issue started and I was already all set.
The only other game I seen this happen with is an old game called The Saboteur. It wouldn’t run at all with more than 4 cores. Someone made a patch that changed a hex value in the exe. It basically skipped a check and it worked. I had to disable cores in the bios before that. WH can certainly fix this.
