1.0) BIOS Type: LZMA BCJ Version: F5 For: BIOS File size: 1.67 Mb Count views: 2611
CPU Z GIGABYTE DRIVER
1.0) Intel INF installation driver Type: LZMA BCJ SELF-EXTRACTING Version: 9.2.0.1030 For: Windows XP, Windows Vista, Windows 7, Windows 7 64-bit, Windows Vista 64-bit, Windows XP 64-bit File size: 2.43 Mb Count views: 2611 Count downloads: 2 1.0) BIOS Type: LZMA BCJ Version: F2 For: BIOS File size: 1.58 Mb Count views: 2672 1.0) Creative Audio driver Type: LZMA BCJ SELF-EXTRACTING Version: 6.0.01.1327 For: Windows XP, Windows Vista, Windows 7, Windows 7 64-bit, Windows Vista 64-bit, Windows XP 64-bit File size: 203.94 Mb Count views: 2685 Count downloads: 11 1.0) 3TB+ Unlock Preinstall driver Type: LZMA BCJ Version: B11.0223.2 For: Windows XP, Windows XP 64-bit File size: 145 Kb Count views: 2703 Count downloads: 2 1.0) 3TB+ unlock driver Type: LZMA BCJ Version: B12.1102.01 For: Windows XP, Windows Vista, Windows 7, Windows 7 64-bit, Windows Vista 64-bit, Windows XP 64-bit File size: 6.21 Mb Count views: 2714 1.0) Creative SB X-Fi driver Type: LZMA BCJ Version: 1.0 For: Windows Vista, Windows 7, Windows 7 64-bit, Windows Vista 64-bit File size: 69.49 Mb Count views: 2887 Count downloads: 7
CPU Z GIGABYTE WINDOWS 8
1.0) G1-Killer™ CPU-Z driver Type: LZMA BCJ Version: 1.61.3 For: Windows XP, Windows Vista, Windows 7, Windows 7 64-bit, Windows Vista 64-bit, Windows XP 64-bit, Windows 8, Windows 10, Windows 8 64-bit File size: 2.45 Mb Count views: 3068 Count downloads: 4 If Gigabyte's overclock ends up having been a PR stunt, it'll not only hurt the company's credibility, but also tarnish HiCookie's (who is one of the more respected personalities in the extreme overclocking scene) reputation.Popular Motherboards Gigabyte G1.Sniper 2 (rev.
Admittedly, Intel probably won't waste further resources just to fix a bug to provide a level playing field for overclockers. The CPU-Z team has its hands tied, and therefore, only Intel can solve the problem through either a new hardware stepping or another microcode patch. 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.
CPU Z GIGABYTE UPDATE
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.