But that isnt the issue though.
I mean look at this document which some are claiming proves faulty CPUs are the cause.
RAD Game Tools' web page. RAD makes Bink Video, the Telemetry Performance Visualization System, and Oodle Data Compression - all popular video game middleware.
www.radgametools.com
We can see in the article errors are being mislabelled, e.g. the devs acknowledge a bad hash of data can cause their engine to report "out of video memory" thats a code problem. They also report they are mislabelling verification errors as a generic "unable to load shader".
The article starts of by stating hardware problems, but then goes on to confirm its bios related,
bios is software not hardware.
It also confirms they are not sure of what the problem is other than its generic system instability.
Some solutions reported by their customers include disabling XMP, reducing SVID back to spec, reducing power limits back to spec, and downclocking CPUs. The latter could work because it in effect can force the CPU back into normal operating range by the lower clock speeds, its masking a bad bios configuration.
So yes there is nothing even in this UE document that confirms any kind of faulty CPU.
This story should be putting pressure on board vendors to stop with what they doing and UE developers to improve their code, but its a let off for them if people start blaming the chips instead.