I don't know, guys, but it keeps happening to me. Latest Windows 10 Insider Preview version, I tried everything. Sometimes it works for 3, 4 hours, sometimes it crashes right after 10 minutes playing. DISM, SFC, clean boot, clean GPU driver install, disable all kind of OCs on my system. I tried everything. And it, keeps, crashing. Sooner or later. So frustrating, to the point I don't want to even open the game.
It might be that the insider preview versions of Windows 10 are affecting something. But if this is the case, then the next stable update will make Ryzen users crash again. And we'll have to wait weeks to play without disabling things like SMT. Again. Guys first we had incompatibilities with AMD's AGESA causing sound to stutter/cut. Then we had crashes that have forced many users to disable things on their BIOS that makes their CPU perform worse than it should by default. And now, I assume we can expect crashes again the moment Windows 10 updates (slow ring builds, fast ring builds, next version builds, the game crashes on all of them). Has this really been look up onto? Has EA/DICE investigated the crashes people had when they were pre-1803 Windows 10 version? We clearly have a problem, and if it's not investigated because there are workarounds, or because it doesn't crash in *one specific version of Windows 10*, then, we'll inevitably suffer issues again.
An official response to these issues would be cool. Even if it's only a "we know some of you are crashing, we're investigating". All the issues we Ryzen users have been suffering were always solved via an external solution. BIOS updates, Windows updates, disabling CPU features on the BIOS. There's clearly something wrong between the Frostbite engine and the Ryzen architecture, we can't expect everything to eventually work *by chance*. You know, this problem can potentially affect Battlefield V, as the audio cutouts, for example, affected Battlefield 4 and 3 as well. That would be awful.
Anyway. I guess for now we're set, and then we'll see if another of these threads pops out again on the next version of Windows 10. Until then, It would be nice if these issues are investigated.
