This pretty much agrees with what I put in the OP. Both Intel and mobo vendors know exactly what the cause is but they're hoping the issue issue blows over rather than confronting it. They won't dare do anything that risks lowering benchmarks or a class action lawsuit.
Nothing new here, Intel does this every time AMD starts beating them. Industrial water cooler @ Computex, Prescott throttling @ stock, faulty 1.13 GHz P3 recall because it couldn't compile the Linux kernel.
Heck, E-cores are nothing more than Cinebench accelerators specifically designed to win benchmarks because Intel can't compete with real cores. To hell with the people trying to actually use the chips for real work and finding all sorts of scheduling problems with the async design.
The solution? An "Intel accelerator utility" that disables them. You know, for all those other times when you aren't constantly looping Cinebench.
First reported in February, here we are in April, Intel still "investigating". How come a $161 billion corporation has so much trouble figuring this out when according to some people in this very thread, they've solved it? Just point Papa Gelsinger over here and things should be sorted quickly, amirite?
Last edited: