Is Gigabytes BIOS problematic or is there something you're missing in your understanding?

F5F Stay Refreshed Hardware Desktop Is Gigabytes BIOS problematic or is there something you're missing in your understanding?

Is Gigabytes BIOS problematic or is there something you're missing in your understanding?

Is Gigabytes BIOS problematic or is there something you're missing in your understanding?

X

xCattyx
Member

196

05-04-2017, 01:34 PM

#1

I have an 8700k in a Gigabyte Z370 XP-SLI running at 1.32 volts, turbo mode enabled, and the load line set to "High." First, regarding the voltage control menu: one option isn't listed in the manual and doesn't appear when selected—typically you can type in "turbo" or "high," but not low, med, or extreme. Why? It seems the manual doesn’t provide guidance for this specific configuration.

Next, after enabling the iGPU and booting into Windows, the system overheated immediately. CPU-Z reported the same issue. I disabled the iGPU in BIOS, then rechecked the settings—overclocking was correctly applied. When I loaded a saved profile without the iGPU, it still overheated. I tried turning the iGPU back on again, but it kept overheating. I attempted to use the same settings manually, and the problem disappeared.

X

xCattyx

05-04-2017, 01:34 PM #1

I have an 8700k in a Gigabyte Z370 XP-SLI running at 1.32 volts, turbo mode enabled, and the load line set to "High." First, regarding the voltage control menu: one option isn't listed in the manual and doesn't appear when selected—typically you can type in "turbo" or "high," but not low, med, or extreme. Why? It seems the manual doesn’t provide guidance for this specific configuration.

Next, after enabling the iGPU and booting into Windows, the system overheated immediately. CPU-Z reported the same issue. I disabled the iGPU in BIOS, then rechecked the settings—overclocking was correctly applied. When I loaded a saved profile without the iGPU, it still overheated. I tried turning the iGPU back on again, but it kept overheating. I attempted to use the same settings manually, and the problem disappeared.