Wow, I would not make a public statement like this without narrowing down the issue and making a replication case. Given what little insight they have now, the

Wow, I would not make a public statement like this without narrowing down the issue and making a replication case. Given what little insight they have now, the crash-triggering fault could just as likely be in the peculiarities of their own code, some flaw in their build toolchain, some flaw in a runtime library, etc With all respect to the folks at this studio, this statement reads like a junior dev throwing up their arms and blaming others over a bug they can't wrap their head around. Even if they have a hunch that it's a CPU bug and can't afford to prove it, a more professional approach would be to perform the hardware change to AMD and toss out a more curious and less authoritative statement -- "Anybody else seeing more crashes on these processors? Have you figured out what from?" vs "These are broken and should be recalled".