This is why I started getting so annoyed when people kept leaping on the "ItS yOuR hArDwArE" train or keep saying "They're probably working on it!"
No, it's not, a hardware issue, and we have 0 evidence that they are working on a fix. Hell, idk why they even have EA_Illium as a "community manager" if they aren't going to, you know, manage the community. I don't get why you wouldn't have something like a bug dashboard or even a pinned thread that lists out bugs and current statuses.
I've never seen a company of this size have this little communication so shortly after launch with such severe issues. All they're doing right now is making people more mad for no reason when they could just......comment on the issues?
It makes it seem real shady and makes me think more and more that they might not actually have any fix and that it's an issue inherent to Frostbite Engine that won't ever be resolved. I'd like to hope that's wrong, but.......radio silence
I too have the DirectX error, as well as the nvldmmk event viewer errors. As soon as I close the game after it crashes I get a full system lock up, the weird part is if you look at the crash dumps in windbg it shows as an NT error code which is GPU driver communication, and ive seen other people post their crash dumps with constant mention of Denuvo token timeout strings, despite the game not having Denuvo. Very odd.
The most damning evidence is this error goes back years with the EXACT same error code in multiple frostbite engine games. So I highly doubt its hardware and if it is its certain configurations causing driver communication errors.
