Sadly, it's not an algorithm that the team can slip into CPU-Z since Windows crashes are reported to Microsoft's telemetry, and Windows Defender can put CPU-Z on the blacklist for that.
If the PLL isn't locked down, the processor will go into a hard-lock instantly. This isn't something that happens out of the blue, either. While the check is enabled, the processor is clocked at a lower ratio then the value reported. The hypothetical workaround consists of altering the CPU ratio and subsequently upgrading the microcode to enable "FLL_OC_MODE" during boot. Even if the result looks legit, Doc TB can think of a way how you could bypass Intel's fix if you were to have access to the BIOS source code, which many overclockers that work with motherboard vendors do. It seems to tick all the boxes, but the fact that the overclocker didn't submit the result to HWBot looks pretty suspicious. HiCookie, Gigabyte's in-house overclocker, validated the 8 GHz overclock on November 3 utilizing CPU-Z 1.98, which already has the "FLL_OC_MODE" implementation. It certainly raised a red flag when Gigabyte started promoting its 8 GHz overclock on social media and in a press release. As a matter of fact, many processors struggle to get to 7.5 GHz, and overclockers were one-upping each other by a few MHz at best. Apparently, 7 GHz on all cores is possible, however, the ceiling for single-core overclocks ranges from 7.5 GHz to 7.6 GHz. In addition, Doc TB put multiple checks in place with CPU-Z Validator, including microcode version, core throttling, "FLL_OC_MODE" register checking to nullify the submissions that exploited the bug.ĭoc TB has since provided some statistics on Alder Lake overclocking. The CPU-Z team implemented "FLL_OC_MODE" in CPU-Z 1.98. The solution consists of a new microcode update (0x12) through the addition of the HW register called "FLL_OC_MODE." Once enabled and properly configured, the internal CPU ensures that the PLL is appropriately locked with ratios above 63. Even though the problem wasn't meaningful for mainstream users, Intel worked up a fix, anyway.
0 kommentar(er)
