[FALSO] Gigabyte exceeds 8GHz with the i9-12900K and 8300MT / s with its DDR5 memories

[FALSO] Gigabyte exceeds 8GHz with the i9-12900K and 8300MT / s with its DDR5 memories

Update: CPU-Z revealed that the record was false and marked the result as invalid on their page.

While the embargo has not yet been lifted for the new 12th Intel Core processors. Generation and Z690 motherboards, the Twitter account of Aorus Spain revealed that the overclocker of the house of Gigabyte, HiCookie, already surpassed 8GHz with the i9-12900K and the 8300MT / s in the DDR5 memories of the brand, using its motherboard for overclocking Z690 Tachyon and of course liquid nitrogen to cool the components at the lowest possible temperature.

On the CPU overclock side, HiCookie reached 8000MHz on its 8 “P” cores, while the “E” cores were disabled. For this, it required a voltage of 1.812V, which may be high to run benchmarks, but it is not bad if it is only for a frequency validation.

Read This Now:   Test - be quiet! Shadow Rock TF 2|Specs | Price

The other test shared by Gigabyte includes a validation of maximum memory frequency, where 8300MT / s were reached with C52 latency using a 16GB AORUS DDR5 module and XMP frequency of 5200 MT / s.

It will be interesting to see how these results compare to those achieved by other overclockers, and especially to see the results in different benchmarks to analyze their performance, which is more interesting than the frequency, although for this we will have to wait until tomorrow when the embargo is lifted. for these processors. We will keep you updated on the information.

What do you think about these overclocking results of the i9-12900K and the DDR5 memories obtained by HiCookie in the Gigabyte AORUS Z690 Tachyon?


Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5373

Notice: ob_end_flush(): failed to send buffer of zlib output compression (1) in /home/gamefeve/bitcoinminershashrate.com/wp-includes/functions.php on line 5373