The AVX offset remains active during overclocking?
The AVX offset remains active during overclocking?
Hi,
I’m using an i9 9700K and wanted to attempt an overclock. According to what I’ve read, it’s advised to adjust the AVX offset to reduce the frequency when that particular instruction is in use.
I configured the CPU frequency multiplier to hit 5Ghz and applied three AVX offsets. When I start Windows, the clock stays below 4.7Ghz. If I leave the AVX offset unset in the BIOS, the frequency reaches 5Ghz as intended and the system remains stable.
It appears that once set, the AVX offset is consistently applied. Is this normal behavior?
My build details are as follows:
PCPartPicker Part List
CPU: Intel Core i7-9700K 3.6 GHz 8-Core Processor
CPU Cooler: NZXT Kraken Z63 98.17 CFM Liquid CPU Cooler
Motherboard: Gigabyte Z390 GAMING X ATX LGA1151
Memory: Crucial Ballistix Sport LT 16 GB (2 x 8 GB) DDR4-3000 CL15
Video Card: Asus GeForce RTX 2070 SUPER 8 GB Turbo EVO
Case: Fractal Design Meshify C ATX Mid Tower Case
Power Supply: Enermax 550 W 80+ Bronze Certified Semi-modular ATX
Thanks for your assistance.
It might be related to a BIOS issue during AVX offset implementation. You could test Intel's XTU, which performs well with AVX on my Z270 at 4.7 GHz across all cores, but smaller programs like Prime95 or FFTs only reach 4.5 GHz when AVX is active. (With MCE enabled in BIOS but using the default multiplier control, and higher speeds in XTU, the system still stays between 800-1200 MHz when idle, but jumps to full clock speeds under load. During a crash or power failure, the XTU reverts to default settings, removing any post-boot BIOS changes.)
It might be related to a BIOS issue during AVX offset implementation. You could test Intel's XTU, which performs well with the AVX offset on my Z270, reaching 4.7 GHz across all cores. However, Prime95/small FFTs with AVX enabled only reach 4.5 GHz. (When MCE is active in BIOS but the default multiplier control stays, and higher speeds from XTU are limited to 800-1200 MHz during idle or light use, it jumps to full speeds when needed under load.) In crashes or power failures, the system reverts to default settings, removing any post-boot BIOS changes. (This seems like a solid approach!)