ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - Z170 M-ITX gaming boot issue.
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Z170 M-ITX gaming boot issue.
 Post Reply Post Reply Page  <12
Author
Message
  Topic Search Topic Search  Topic Options Topic Options
Brad View Drop Down
Newbie
Newbie


Joined: 22 Jun 2016
Status: Offline
Points: 19 		Post Options Post Options   Thanks (1) Thanks(1)   Quote Brad Quote  Post ReplyReply Direct Link To This Post Posted: 27 Jul 2016 at 11:58pm
There are quite a few threads in the forums regarding the Z170 Gaming ITX with wake/sleep issues.  Do a search.  

All I know is that there is some sort of bug/misconfiguration in v2.0 and v2.1. Downgrading to UEFI v1.8 solved my problems.

Hopefully they are working on fixing it.  Don't hold your breath, it's been 3 months since the last (non-working) update.
Back to Top
Snipeuout View Drop Down
Newbie
Newbie


Joined: 26 Jul 2016
Status: Offline
Points: 8 		Post Options Post Options   Thanks (0) Thanks(0)   Quote Snipeuout Quote  Post ReplyReply Direct Link To This Post Posted: 28 Jul 2016 at 12:09am
Last night I did a few some restarts, shutdown/boots and sleep/wakes. So far it works 4.0.
 
This looks to be a bios issue with 2.0 and 2.1. Whatever changed between 1.8 and 2.0 has a critical bug in it. Hopefully 2.2 will come out with a fix.
 
Will keep a log and report back.
Back to Top
Snipeuout View Drop Down
Newbie
Newbie


Joined: 26 Jul 2016
Status: Offline
Points: 8 		Post Options Post Options   Thanks (0) Thanks(0)   Quote Snipeuout Quote  Post ReplyReply Direct Link To This Post Posted: 28 Jul 2016 at 12:58am
Originally posted by parsec parsec wrote:

Originally posted by gusviper gusviper wrote:

Dear Snipeuout, we have almost the same specs, and 100% the same problem.
my specs
I7-6700k
Corsair vegennce 3200 16-18-18-35 2x16gb
Corsair RM 550 PSU
Samsung M.2 500GB 850 EVO
UPS CyberPower Adaptive Sinewave CP900EPFCLCD

The 1.8 Bios version fixes the problem.
But if u want to use the latest version (2.10 ) without sleep mode problems, u have to raise from the bios settings, the CPU VCCIO Voltage from 0.95 up to 1.00 (1.00v-1.20v is safe).
Give it a try, this worked for me.But i hope Asrock support give a permanent solution.


First I want to thank you for posting this information. If it is true (sorry but I cannot verify it myself, I don't use this board. I'm not saying you are wrong or giving false information, I simply do not know) it is useful for helping others with this issue. But this situation is not necessarily a problem with the 2.10 UEFI, as I will explain.

Your post implies that the default, Auto VCCIO voltage was changed (reduced) after UEFI version 1.80, in version 2.10.

UEFI 2.10 includes an "Improve DRAM compatibility" change, so that is possible.

Is that true? Do you know what the default or Auto VCCIO voltage was with UEFI 1.80? The VCCIO voltage can be different for several reasons.

Or do you think something else is happening?

VCCIO voltage is usually increased when using DDR4 memory at over clocked speeds, or the PC won't POST/boot. That can be done manually, or is set by the memory's XMP profile.

My ASRock Z170 Extreme7+ board, used with my G.SKILL 3200 memory, sets the VCCIO voltage (and VCCSA) automatically to much higher values when the memory speed is set to 3200. That is necessary for the higher memory speed, any speed beyond 2133 is an OC. The voltages were higher than necessary, and I was able to reduce them without any problem.

Since it is difficult to know what VCCIO and VCCSA voltage is needed for every model of DDR4 memory, and for the amount of memory being used, high values for these voltages are used to insure compatibility.

Your memory seems to be at 3200, obviously an OC beyond the standard DDR4 speed of 2133.

Are you using the XMP profile to set your memory at 3200, or did you change the memory settings yourself?

It is possible that the 2.10 UEFI includes reduced automatic VCCIO (and VCCSA?) voltage values used with memory at over clocked speeds. It seems that is what has happened.

If your memory at 3200 does not work perfectly (wake from Sleep problem) with the different, reduced value for the VCCIO voltage (assuming that is happening with UEFI 2.10), you need to adjust it, which you have done.

But that does not mean the 2.10 UEFI has an issue in general. UEFI 2.10 might be setting the VCCIO voltage to low in some cases, but that will take some research to verify.

I hope you understand that when we OC our memory or CPU, we are responsible for finding and setting the necessary voltages that provide stability. That is the only solution that is realistic. What other permanent solution is possible?

Yes it is frustrating that after a UEFI update, we find an issue occurring with our PC. You found the solution, but IMO we cannot expect the UEFI used in our boards to provide automatic voltage values that work for the over clocked memory we are using. Those voltage values will not work for all memory models. ASRock does provide memory OC settings for some models of memory, for some of their boards.

If the VCCIO voltage is being set to low at 2133 memory speed, then I would agree that should be fixed.

As I said above, all of this should be verified before we come to any conclusions.
 
My 2 cents on your post. The issue occurs in Bios 2.0 and 2.1 with the ram set to JEDEC speeds of 2133. On a "Just plugged in" start I can stress test and benchmark the system at 2133 or 3200 with no stability issue using 2.0/2.1, however once I shutdown and start the PC (2133 or 3200) it goes into this failed mode where only the GPU is powered.
 
If 1.8 works fine, how can we not at least suspect that bio 2.0/2.1 are bugged? 
Back to Top
sgoemans View Drop Down
Newbie
Newbie
Avatar

Joined: 29 Jul 2016
Location: Munich
Status: Offline
Points: 2 		Post Options Post Options   Thanks (0) Thanks(0)   Quote sgoemans Quote  Post ReplyReply Direct Link To This Post Posted: 29 Jul 2016 at 4:35am
Hello, I seem to be another customer with exactly the same issue. My PC specs are also identical:

ASRock Fatal1ty Z170 Gaming/ac

I7-6700k
Corsair Vegennce 3200 16-18-18-35 2x16gb
Corsair RMi 650 PSU
Crucial CT750MX SSD
Crucial H100i v2 WaterCooling
Asus GTX1080

After upgrading my 1.50 BIOS to 2.10, I experienced the exact same symptoms as gusviper and Snipeuout. Only power cycling my PSU  brings my system back. After a shutdown or standby without power cycling the PSU, the system will light up some LEDs and a few fans start spinning, but there is no HDD activity. Also the AsRock safe boot feature (after a defined number of failed boots) doesn't kick in. POST is definitely not performed.

After I flashed back to 1.50 and loading UEFI default values, everything is back to normal.
Hopefully adjusting the VCCIO voltage helps. Nevertheless, AsRock has an issue which needs to be addressed.
Back to Top
Snipeuout View Drop Down
Newbie
Newbie


Joined: 26 Jul 2016
Status: Offline
Points: 8 		Post Options Post Options   Thanks (0) Thanks(0)   Quote Snipeuout Quote  Post ReplyReply Direct Link To This Post Posted: 29 Jul 2016 at 8:31am
Originally posted by sgoemans sgoemans wrote:

Hello, I seem to be another customer with exactly the same issue. My PC specs are also identical:

ASRock Fatal1ty Z170 Gaming/ac

I7-6700k
Corsair Vegennce 3200 16-18-18-35 2x16gb
Corsair RMi 650 PSU
Crucial CT750MX SSD
Crucial H100i v2 WaterCooling
Asus GTX1080

After upgrading my 1.50 BIOS to 2.10, I experienced the exact same symptoms as gusviper and Snipeuout. Only power cycling my PSU  brings my system back. After a shutdown or standby without power cycling the PSU, the system will light up some LEDs and a few fans start spinning, but there is no HDD activity. Also the AsRock safe boot feature (after a defined number of failed boots) doesn't kick in. POST is definitely not performed.

After I flashed back to 1.50 and loading UEFI default values, everything is back to normal.
Hopefully adjusting the VCCIO voltage helps. Nevertheless, AsRock has an issue which needs to be addressed.

 
Interesting how the issue is plaguing everyone with Vengeance 3200 memory. I wonder if this is purely a coincidence. Don't see how this memory (at JEDEC or XMP speed) would cause the system to fail to boot with 2.0/2.1.
Back to Top
ASRock_TSD View Drop Down
ASRock_Official
ASRock_Official


Joined: 20 Mar 2015
Status: Offline
Points: 8787 		Post Options Post Options   Thanks (0) Thanks(0)   Quote ASRock_TSD Quote  Post ReplyReply Direct Link To This Post Posted: 29 Jul 2016 at 11:24am
Dear Customer:
This is ASRock TSD Bryan.

For this issue, please update to BIOS P2.30 to try. Download link is as follow:
http://www.asrock.com/mb/Intel/Fatal1ty%20Z170%20Gaming-ITXac/?cat=Download&os=BIOS

If you have any further question, please contact us:
http://event.asrock.com/tsd.asp?ln=en

Thank you.
Yours truly,
ASRock TSD 
Back to Top
sgoemans View Drop Down
Newbie
Newbie
Avatar

Joined: 29 Jul 2016
Location: Munich
Status: Offline
Points: 2 		Post Options Post Options   Thanks (0) Thanks(0)   Quote sgoemans Quote  Post ReplyReply Direct Link To This Post Posted: 30 Jul 2016 at 12:14am
Originally posted by ASRock_TSD ASRock_TSD wrote:

Dear Customer:
This is ASRock TSD Bryan.

For this issue, please update to BIOS P2.30 to try. Download link is as follow:
http://www.asrock.com/mb/Intel/Fatal1ty%20Z170%20Gaming-ITXac/?cat=Download&os=BIOS

If you have any further question, please contact us:
http://event.asrock.com/tsd.asp?ln=en

Thank you.
Yours truly,
ASRock TSD 

Thanks for your support. Unfortunately, the new BIOS 2.30 didn't fix the issue, although I can see that VCCIO is now preset to 1.150V. If I alter the value to 1.050V, everything is fine again. Summary:
2.10 default - Not OK
2.10 VCCIO from 0.95 to 1.050 -> OK
2.30 default - Not OK
2.30 VCCIO from 1.150 to 1.050 -> OK
Please note that I always set the DRAM profile to XMP 2.0 Profile 1 before I started testing.
Back to Top
parsec View Drop Down
Moderator Group
Moderator Group
Avatar

Joined: 04 May 2015
Location: USA
Status: Offline
Points: 4996 		Post Options Post Options   Thanks (0) Thanks(0)   Quote parsec Quote  Post ReplyReply Direct Link To This Post Posted: 30 Jul 2016 at 1:30pm
Originally posted by Snipeuout Snipeuout wrote:

My 2 cents on your post. The issue occurs in Bios 2.0 and 2.1 with the ram set to JEDEC speeds of 2133. On a "Just plugged in" start I can stress test and benchmark the system at 2133 or 3200 with no stability issue using 2.0/2.1, however once I shutdown and start the PC (2133 or 3200) it goes into this failed mode where only the GPU is powered.
 
If 1.8 works fine, how can we not at least suspect that bio 2.0/2.1 are bugged? 


So now this is NOT just a wake from Sleep issue? You have it on the second cold boot after restoring power to the board? Confused

I was trying to explain the potential cause for this situation, or why it is happening, not that it is not happening. Plus I'm working from very little information. But I did see information that seemed to explain at least some of the issues. Add to that, my ASRock Z170 board with the latest UEFI version does not have any of these problems at all.

My explanation seems to be supported by this post:

Originally posted by sgoemans sgoemans wrote:

Thanks for your support. Unfortunately, the new BIOS 2.30 didn't fix the issue, although I can see that VCCIO is now preset to 1.150V. If I alter the value to 1.050V, everything is fine again. Summary:
2.10 default - Not OK
2.10 VCCIO from 0.95 to 1.050 -> OK
2.30 default - Not OK
2.30 VCCIO from 1.150 to 1.050 -> OK
Please note that I always set the DRAM profile to XMP 2.0 Profile 1 before I started testing.



If the extent of your interest in this situation is either it is "bugged" or not "bugged" for your memory model, then feel free to call it bugged.

IMO, bugged means broken under all circumstances. The cause of the failure is a voltage value that is wrong in any circumstance, like a CPU voltage set to 0.001V, for example.

I'm beginning to think ASRock  made a mistake attempting to enhance memory compatibility with UEFI updates for their Z170 boards. The new modifications are causing other problems with memory that was compatible before the updates.

Frankly, IMO the XMP profiles in some DDR4 memory are wrong, or contain bad data. XMP profiles for Skylake and X99 HEDT systems, the only ones that use DDR4 memory, are not 100% compatible, in reality. Some memory manufactures don't like that, and try to make their memory one profile fits all. Then the mother board manufactures get to deal with it... as usual.  Wacko
Back to Top
 Post Reply Post Reply Page  <12
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.04
Copyright ©2001-2021 Web Wiz Ltd.

This page was generated in 0.203 seconds.