F8 out nowI wait thanks for the new updated bios , maybe they re-name it F8
The reply i got from gigabyte tech support was
Hello,
CMK16GX4M2B3200C16(DS) is not listed in our QVL because it is not exactly the same as CMK64GX4M8B3200C16(SS).
AX370-Gaming is a 6-layer motherboard. Definitely, hardware layout (e.g PCB layer) plays a role in overclock but it’s not the only factor.
For DDR XMP performance on AM4 platform, it is more related to AMD AGESA code (APL code) support and CPU capability.
Also just tried the Hyper X its 2400 stock and wont boot to 3200 at all on xmp, tried F6 and F7, just boot loop over and over. and this is on the qvl!
Could well be, but the article mentioned K5 and K7, best to rid rid to be on the safe side anywayWell they also pulled the F7 from the gaming 5 ,so i guess it also can effect that board also?
Wow! good job you were keeping an eye on it, hopefully you wouldnt have permanently damaged it as you caught it quickThis over-volting bug happened to me with a gigabyte gaming 5 and a 1700 cpu.. I flashed the F7 bios then went straight in and re-applied my overclock with a 0.025v offset and saved and exited. When the system was booting it was obvious from the fan noise that something was odd, so as soon as I was at the desktop I loaded cpu-z and was horrified to see the core voltage at 1.7V! So I pressed the power button for 5 seconds to shut down the machine as fast as possible, reset the bios to defaults and it was fine - I didn't try re-applying the overclock again just in case it happened again and also kept it on the F7 bios as I didn't know better.
I only saw the news today that it was a bug and not something that I had done erroneously, I do still wonder what, if any, damage I've done to the CPU long term. I've flashed the F8 bios now and re-applied my overclock successfully and all seems well, I want this machine to last 4-5 years at least and it'll be a pain if that 20s over-volting kills this CPU in the future..
of all the problems I've had I can thankfully say that hasn't been one of them. has it always been like that for you or is it a recent occurrence?Hi,
Has anybody else had the boot screen freeze issue?
The Aorus logo pops up when I boot my system (I am running a Gaming 5 mobo and a 1700 @ 3.9) and the system will freeze once the Aorus logo pops up.
If I hit reset the system will boot fine and I will be able to get into windows 10. Benching and gaming also work fine and sometimes the system will occasionally boot successfully.
The mobo error code during the splash screen freeze will read '0d'. The only puzzling thing is that the system runs perfectly save for the boot freeze. The overclock is cinebench/Prime stable so I am unsure what the issue is.
Thanks in advance.