Post B6di5EH9NPQy4niQE4 by gabrielesvelto@mas.to
 (DIR) More posts by gabrielesvelto@mas.to
 (DIR) Post #B6di5E4k7XVdSJuVt2 by gabrielesvelto@mas.to
       0 likes, 1 repeats
       
       Regarding the Raptor Lake bug I received a couple of messages from confused users that had read articles on Tomshardware and Neowin. They asked about erratas and microcode updates which puzzled me, because that was part of my early investigation into the bug and we know that the failure is not caused by a known errata and microcode updates cannot fix broken CPUs. So why did they ask? As it turns out it was slop. Both articles are 100% slop full of confusing and inaccurate claims.
       
 (DIR) Post #B6di5EH9NPQy4niQE4 by gabrielesvelto@mas.to
       0 likes, 1 repeats
       
       From the looks of it editors on both websites probably fed the most prominent Raptor Lake bug we have on our tracker, as well as my social media comments, to an LLM and asked it to generate an article on the topic. The results are complete drivel that include claims like we fixed the bug (we did not), it was caused by a known errata (it was not) and was fixed by microcode (not possible, degraded hardware stays degraded). No human editors reading the sources would have made these mistakes.
       
 (DIR) Post #B6di5EVKWgmCmmLkKO by gabrielesvelto@mas.to
       1 likes, 2 repeats
       
       I haven't read either site in ages but I can confidently say that you can stop reading both Tomshardware and Neowin. If they're willing to put out this kind of slop with blatant mistakes in it you can assume the rest of their reporting is also slop, and will likely be either misleading, confusing or flat out false.
       
 (DIR) Post #B6fLDOe3HD6jHq1VTc by dhamlinmusic@dragonscave.space
       0 likes, 1 repeats
       
       @gabrielesvelto oh yeah I have been finding more and more tech "news" sites being likely AI generated slop, or just copypasta from slop sources.