Z170 M-ITX gaming boot issue.
Printed From: ASRock.com
Category: Technical Support
Forum Name: Intel Motherboards
Forum Description: Question about ASRock Intel Motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=3114
Printed Date: 27 Dec 2024 at 7:53am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Z170 M-ITX gaming boot issue.
Posted By: Snipeuout
Subject: Z170 M-ITX gaming boot issue.
Date Posted: 26 Jul 2016 at 10:55pm
|
New Z170 M-itx fatality gaming board has a weird boot issue. When running bios version 2.1 or 2.0, when the PC is shut down or put to sleep and then turned back on the graphics card lights up in some partial power mode where 2 of 3 of the fans spool up and the CPU fan will not spin and then no boot occurs. I then have to cycle off the PSU switch in order to boot the PC. When running 1.8 bios it so far seems to have alleviated the issue, however I'm curious to know if this is a hardware or a bio issue. Specs: I7-6700k Corsair vegennce 3200 16-18-18-35 2x16gb Evga 650watt GQ PSU ASUS 1080 Strix Samsung M.2 500GB 850 EVO System stress tests ok and benchmarks well. |
Replies:
Posted By: parsec
Date Posted: 26 Jul 2016 at 11:23pm
Just to be sure, you have the Fatal1ty Z170 Gaming-ITX/ac board? There aren't and Fatal1ty Z170M boards, and the UEFI versions you mentioned match this board: http://www.asrock.com/mb/Intel/Fatal1ty%20Z170%20Gaming-ITXac/" rel="nofollow - http://www.asrock.com/mb/Intel/Fatal1ty%20Z170%20Gaming-ITXac/ It seems you have this issue with the 2.00 or 2.10 UEFI versions, but if you change back to the 1.80 UEFI version, you don't have the issue anymore? What CPU cooler are you using? What version of Windows, or other OS are you using? Wake from Sleep issues are common, and can be difficult to fix, but you have the same problem when doing a cold boot after a standard shutdown, correct? ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Snipeuout wrote:Posted By: Snipeuout
Date Posted: 27 Jul 2016 at 1:42am
|
-It is the Fatali1ty Z170 itx gaming mobo. -Windows 10 64-bit Home. -Cooler is BIG Shuriken 2 Rev. B This issue occurs both on a cold start after a shutdown and wake from sleep. The PC only booted if power has been completely removed from the mobo. So far with bio version 1.8 this morning before work, I was able to sleep/wake and shutdown/cold start the PC. I think it may be the bio, but I want to be sure I have a health mobo. The board came with 1.6 and I think it worked fine for a reboot or two after I installed Windows for the first time. Of course immediately flashed to the latest bio and I'm not 100% it's bios or not because of that. |
Posted By: wardog
Date Posted: 27 Jul 2016 at 2:46am
|
I find it hard, very hard, to believe this could be BIOS related. That two of the three STRIXs fans, its LEDs, and the CPU fan are affected, well, to me that's seemingly a power issue. OP, have you preformed an out of the case minimal build? ""The PC only booted if power has been completely removed from the mobo."" If that is literal, what happens when power is separated from only the wall outlet and the PSU cable |
Posted By: wardog
Date Posted: 27 Jul 2016 at 2:47am
|
OP, do you power this from the wall, or from a power strip? |
Posted By: Snipeuout
Date Posted: 27 Jul 2016 at 6:57am
|
To
be as specific as possible, I cycle the switch on the PSU to resolve the issue. That is the only way
to resolve the issue, pulling the plug would probably work the same. I did not bench test (min build). However all I have is a MOBO, CPU, COOLER, RAM, M.2 HD, VGA Card and PSU all inside a case.
Actually
it is plugged into a power strip. Why would that matter thou? Why would it work
from a "just plugged in" cold boot but not a shutdown/boot cycle? Either
way, I'm going to flash back to 2.1 and plug it directly into the wall and see
if the issue still exists. Its a very conditional
issue that only occurs after a sleep/shutdown after the first boot. Rebooting/restarting works
fine, anytime, all the time. To be as specifics as I can during the failure
mode here is what happens. Only two of the GPU fans spin and stay on, and the LED
lighting on the card stays whiteish/baby blue. Normally all 3 fans spins for a
second and turn off and the LEDS glow orange. That?™s it, that?™s all the happens.
No CPU fan, no displays, no case fans. As soon as I cycle off (and keep it off for a few seconds) the PSU switch it
boots fine after. It?™s almost like when the boot circuit is triggered after the system was command to shutdown/sleep the system just
turns on the GPU partially. Maybe the NB, CPU and RAM are powered but I have no
way of knowing. It?™s
super strange. My gut tells me it?™s a bug in the BIOs. The error is so easily
repeatable. Could this be a power supply, mobo power issues or a bio bug? |
Posted By: wardog
Date Posted: 27 Jul 2016 at 10:02am
|
You seem to be stuck on it being something other than power related so I'll duck out now. Good luck. Really, good luck. |
Posted By: parsec
Date Posted: 27 Jul 2016 at 1:49pm
You can test if the BIOS versions make a difference, as you suspect. When doing that, I would suggest changing to 1.80, which you said works normally, right? If so, use 1.80 for at least two days, a week would be better. You said you were concerned about a potential problem with the board. IMO, letting it run with 1.80 for a week, and logging your results even just once a day (ie Day 1: Ok, woke from Sleep twice, shutdown and restarted once fine) will help you know if it is the board, and if 1.80 does not have the problem. If you complete a week on 1.80 without incident, then move on to 2.00 If you start getting the issue again, which will be obvious after a week without it, make note of that in your log. I would possibly see if 2.00 failed twice for you, but once is probably enough. At that point, you could decide to go back to 1.80, or try 2.10. Unless you are getting some great new feature with 2.00 or 2.10 (which I doubt), stay with 1.80 until a new version beyond 2.10 appears. They you can decide if you want to test it. Did you ever check the Windows Event log when 2.00 or 2.10 failed to wake from Sleep? I know you are not sure if the PC actually woke from Sleep, and only the video card failed to wake, but I have had that happen to me on an older, completely different system. I had entries in the Event log regarding the wake from Sleep error related to my video card and PSU. You have yet to determine if any exist in your Event log. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: gusviper
Date Posted: 27 Jul 2016 at 4:16pm
|
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.
|
Posted By: parsec
Date Posted: 27 Jul 2016 at 11:00pm
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. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: Brad
Date 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. |
Posted By: Snipeuout
Date 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.
|
Posted By: Snipeuout
Date Posted: 28 Jul 2016 at 12:58am
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?
|
Posted By: sgoemans
Date 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/acI7-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. |
Posted By: Snipeuout
Date Posted: 29 Jul 2016 at 8:31am
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.
|
Posted By: ASRock_TSD
Date 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 |
Posted By: sgoemans
Date Posted: 30 Jul 2016 at 12:14am
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. |
Posted By: parsec
Date Posted: 30 Jul 2016 at 1:30pm
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?  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:
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.  ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|