3 ms·
Fun fact: A friend has a first-gen Ryzen with 8 cores (16 hyperthreads), and wondered why Civilization V was always crashing on his system. Turns out that Civ V
by majewsky 8y ago
Fun fact: A friend has a first-gen Ryzen with 8 cores (16 hyperthreads), and wondered why Civilization V was always crashing on his system. Turns out that Civ V runs into weird race conditions with that many threads. When he pinned the game to 8 or less hyperthreads, it started working properly.
- ethbro 8y agoWriting code on top of legacy single threaded frameworks / content interfaces, under an insane holiday release deadline, while trying to enable multithreading... is pretty much my definition of hell. I feel bad for the poor programmers who got that job.
- paulmd 8y agoDoubtful. Nobody's reporting issues with 5960Xs, and if it were really a race condition then you would occasionally get crashes even in 4- and 6-core processors. Civ5 is one of the games that can trigger Ryzen segfaults, guessing he has a faulty chip. He should run kill-ryzen and see if his chip is stable. Note that contrary to popular belief, the segfault bug does not "only" affect Linux or compiling workloads (it's a litho fault - these workloads just happen to trigger it) and there is no "safe" date range of first-gen Ryzen chips. Newer chips are more likely to work properly, but a smaller number are still faulty - even some RMA chips, since AMD stopped testing them after a few months. I went through the AMD support thread and pulled out some examples: https://news.ycombinator.com/item?id=17074355 https://news.ycombinator.com/item?id=17074355 Looking through the latest posts in the AMD community thread, at least one user is reporting this even on a second-hand processor, although that's not really enough to make a definitive statement.