On the full nerd podcast Wendell discusses how many of the servers were running 5600MTs often a single stick which he says Intel officially states should work. And that either dropping the multiplier or downclocking to 5200MTs would make the errors go away.
He also talks about with Linux it would just say the core is malfunctioning and that it is being turned off. Then it will limp along.But sometimes it'll kernel panic and sometimes it's so bad the bios resets. On the Asus W680 it deals with it by dropping the speed to 3600MTs and since it's DC they have to go somewhere else to handle the problem that board has and it's frustrating. This goes back to January, and he did not have that access,so he'd have to wait sometimes days for others to deal with it. Asus, ASRock, and Super Micro all handle things differently, but it's a coin toss which board will have failures with Raptor. And that within his 168hr window half would error. Out of the sample size of 2800.
The host says his first one had a bad IMC, the replacement was the one he had random crashes in games. Including the EAC ban in fortnite. He'd get blackscreen crashes with nothing in the fortnite log. It was also a permban which had he not known people there would have been the end of his account. Wendell said another dev he shared data with said they would be rolling back a bunch of bans on raptor users. Host said even with x52 multi the system was janky with stuff like WHEA errors.
Wendell said with games it would often point to memory issues, but in Linux he wrote a program that ran in cache and never touched memory and he was still seeing huge failure rates.
His conclusion was turning off e-cores rarely helped, and the solution was limiting multiplier and running memory speed "dog slow". At x53 and DDR4 level speeds the 12900K with 6400Mts should ROFLstomp raptor. That damned certain isn't what gamers paid for.