Z370 Extreme4 XMP bug

reducing helped me too get rid of mem errors

Same problem and working solution:

- Asrock Z370 Extreme4
- 2x8Gb Patriot 3200Mhz PV416G320C6K
- Intel i3-8100
- Ubuntu 17.10

Hangs up system every few hours, needs reboot. Though strangely error-less and solid in Memtest86+.

Lowering the before mentioned voltages makes it solid as a rock at XMP profile.

@Flode : you are THE man. Thanks


Edited by ppeetoom - 18 Dec 2017 at 5:41am

I just wanted to thank Flode for the solution, I had the same problem (ASRock Exterem4 Z370, Corsair Vengeance LPX 32GB 2x16GB DDR4 3200MH) - reducing the voltage works

These posts seem to confirm the issue. I say "seem" only because it is unusual for an issue to apply 100% of the time when there are hardware variables involved. The variables here are different models of memory, with differing OC speeds applied by the XMP profile.

Enabling the XMP profile causes an automatic increase in the VCCIO and VCCSA voltages. That is not caused by the XMP profile itself, but the code in the UEFI. That is a standard adjustment when over clocking memory, it normally enhances stability.

The interesting thing here is, all three users posting about this issue are using 3200 speed memory. My guess is the voltage values used for VCCIO and VCCSA when the XMP profile is enabled is simply one voltage value, regardless of the memory OC speed.

A memory OC of 3200 is not a very high memory over clock relative to Intel Z370 and Z270 boards and the Kaby Lake and Coffee Lake processor's memory controllers. Memory over clocks for Z370 and some Z270 systems of over 4000 are possible. The high VCCIO and VCCSA voltages are more appropriate for use with memory over clocks over ~3600.

The purpose of the high VCCIO and VCCSA voltages applied when the XMP profile is enabled is to insure (as much as possible) a memory OC will POST successfully. As we see with CPU over clocks, more VCore is needed, but too much is unnecessary and we reduce it to an appropriate value.

The problem is all users are not aware of the need to configure the VCCIO and VCCSA voltages with memory over clocks. The memory OC potential of the memory controller is also a factor. The compromised solution is to set them on the high side.

VCCIO and VCCSA voltages also  tend to be "sweet spot" type voltages, the optimum values need to be dialed in for the memory being used, and the OC speed. Increasing them worked with memory over clocks, but too much was not known to cause stability issues, at least with Z270 systems.

My ASRock Z270 board's UEFI also set the VCCIO and VCCSA voltages higher than was needed with my G.SKILL 3600 memory. But I did not experience any of the freezing issues described here. talos reported the same experience with his Z270 system. I am surprised that reducing those voltages caused the freezing to stop, given past experience. I'm glad that it did. It seems things have changed with the memory controllers in Coffee Lake processors.

FYI, you can check the actual applied VCCIO and VCCSA voltages in the H/W Monitoring screen in the UEFI, and in Windows with programs such as HWiNFO64. My point is the actual/resulting voltage tends to be a bit more than the value entered for either option, according to the readings. You might want to select a slightly lower value for the option, to achieve a perfect result for your memory.

Hi,

I just registered to report the same problem.
I built my new system yesterday.
i5-8600K
16GB G.Skill Flare X 14 3200 ( F4-3200C14D-16GFX )
Z370 Extreme 4
GTX 1080
Win 10

The board came with 1.10 and I flashed 1.30 immediately. Didn't know that it could be unstable, downloaded newest BIOS from official site.

After installing Win 10 and everything, I went back to the UEFI and set XMP Profile from "Auto" to "Profile 1".
After like 3-5 minutes in Windows, the system froze.
Setting it back to "Auto", which makes my expensive RAM run with 2400Mhz, and everything is stable since then.

Since my system is brand new, I didn't toy with any voltage settings in the UEFI at all.

There seems to be something wrong with 1.30 and XMP Profiles.
I didn't buy "3200-14-14-14-34" RAM to let it run at "2400-16-16-16-39".

Is is possible to roll back to an older BIOS version without any issues?
How fast will this be fixed? I have like 10 days left on my return policy.

Oh, and PS: I really like ASRock Boards. I had a P67 Pro3 and after that, for many years, a Z77 Extreme4 with which I was very satisfied. Both served my good old Sandy Bridge well for many years.
I wanted to be loyal, read some impressions of the Extreme4 and went with it.

Hopefully this can be fixed.

best regards
Doc



Edited by DocBrown - 11 Dec 2017 at 8:02am