Fatal1ty Z170 Gaming-ITX/ac No display after sleep
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=2415
Printed Date: 22 Jul 2025 at 2:13pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Fatal1ty Z170 Gaming-ITX/ac No display after sleep
Posted By: dkeone
Subject: Fatal1ty Z170 Gaming-ITX/ac No display after sleep
Date Posted: 10 Apr 2016 at 4:01am
|
Hi, I built a HTPC using http://www.asrock.com/mb/Intel/Fatal1ty%20Z170%20Gaming-ITXac/" rel="nofollow - Fatal1ty Z170 Gaming-ITX/ac motherboard due to its built in hdmi 2.0 port. I have no issues getting 4k @ 60hz and everything works fine, but when i sleep the computer and wake it the tv won't turn on, the machine is running and i can remote access it. No errors in event viewer either, i've tried several of configurations in the asrock bios (updated to latest version too) , i've also tried 4 different versions of the intel 530 display driver, nothing helps.. nada.. I have to completely reboot the system to get the motherboard to send the signal to the tv again. I've googled and found various things about disabling "PLL overvoltage" but i cannot disable this in the asrock bios. Someone with some knowledge, please give me a hand, thanks! http://www.asrock.com/mb/Intel/Fatal1ty%20Z170%20Gaming-ITXac/" rel="nofollow - |
Replies:
Posted By: dkeone
Date Posted: 10 Apr 2016 at 4:02am
|
Oh i'm on OS: Windows 10. |
Posted By: dkeone
Date Posted: 12 Apr 2016 at 11:10pm
|
Turns out with bios 2.0 hdmi wakeup is completely broken... and with bios 1.8 hdmi wakeup works as long as you keep your television running but if you sleep the computer, then turn of your television, then you turn on your television and wake your htpc from sleep, no hdmi signal is being sent? what kind of team of highly incompetent monkeys are writing those bioses? I only bought this motherboard as it had hdmi 2.0 output and mini itx but man my asrock experience has been garbage so far, next time i'm sticking to asus no matter what i do, i've owned over 20 asus motherboards and i've never had these kind of issues. Terrible. |
Posted By: dkeone
Date Posted: 13 Apr 2016 at 3:21pm
|
So i down graded to 1.5 which was the version my motherboard came from and now 2 out of 3 wake up hdmi issues have been solved, but one still remain. I found a thread on another site explaining the problem:
I bolded the problem i have with bios 1.5 Can some asrock representative please respond? Is there anything you can do to solve this issue? It's clearly something you could solve with a bios update, i believe many of your costumers buying this motherboard are not looking to game with it, they are looking to a build a solid HTPC that can handle 4k@60fps without having to have a huge GPU. Thanks |
Posted By: tyeh101
Date Posted: 14 Apr 2016 at 2:54am
| I has the same issue in Windows 7 with BIOS 2.0 too. With HDMI 2.0, the screen shows a lot of vertical white lines with a big mouse pointer after sleep. With the regular HDMI port, the screen was blank. Do I have to run HDMIFeUpgrader to upgrade the firmware? The board looks great and works fine so far though it has some boot issue with picoPSU (150W) and boot normally with a regular ATX PSU. |
Posted By: tyeh101
Date Posted: 14 Apr 2016 at 8:08am
| Switched to BIOS P1.80 and everything is normal with Acer K272HUL. Don't have a 4K TV with HDMI 2.0 and no way to verify that. |
Posted By: dkeone
Date Posted: 14 Apr 2016 at 11:17am
are you sure? i have issues only if i sleep computer/tv for a long period of time, have you tried sleeping your computer for more then an hour then trying to get it to wake up? |
Posted By: ocFTW
Date Posted: 14 Apr 2016 at 11:49am
same issue here and even doing the HDMI firmware upgrade didn't fix it |
Posted By: parsec
Date Posted: 14 Apr 2016 at 2:03pm
The same team that is writing the VBIOS (familiar with that?) and graphics drivers for the 530 graphics... Intel. If you believe ASRock or Asus has anything to do with the Intel integrated graphics beyond including the latest Intel VBIOS updates in their board's UEFI/BIOS updates, and supplying an Intel graphics driver for download, then you are mistaken. So your problem with waking from Sleep and apparently losing the video output sync to the TV, which includes Windows (implementing Sleep), Intel's video drivers and VBIOS for their integrated graphics, and your 4K TV (not a PC monitor, with a new technology (4K), driven by a PC, rather than a cable TV signal or TV - type optical disk player, neither of which ever stop sending a signal to the TV except when shutoff, and have no Sleep mode), can only be blamed by you on the ASRock mother board, resulting in you saying your experience with it is garbage.  Which 20 Asus mother boards that provide a 4K video output, that you've used with your 4K TV, don't have the wake from Sleep issue? If you've followed the Intel video driver updates for their latest graphics, ranging from 510 to 580, there have been many updates and, unusual for Intel, Beta video driver releases. If you check the release notes of the latest Beta release (3/11/2016), in the Known Issues section, one of the many unresolved issues is loss of playback when resuming from S3 or S4 (Sleep and Hibernate). https://downloadmirror.intel.com/25848/eng/ReleaseNotes_GFX_15%2040%204404.pdf" rel="nofollow - https://downloadmirror.intel.com/25848/eng/ReleaseNotes_GFX_15%2040%204404.pdf New drivers or VBIOS versions are not always improvements in every way, things can break that were previously working. I also wonder how it is possible for a 4K TV to be signaled to re-sync the video signal once it is lost (Sleep) if the TV itself is not capable of detecting the loss of signal lock and trying to establish it again itself, without being power cycled. That is very basic digital signaling, which PC monitors deal with, but TVs are not built to the same standards as PC monitors. This reminds me of the Windows problem with no signal from the video card to a PC monitor upon wake from Sleep on my (sorry) Asus P67 board. Windows expected the video driver to react in a certain amount of time, and if it failed to do so, that was an error and it gave up. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: dkeone
Date Posted: 14 Apr 2016 at 2:21pm
Thank you for a good response on the subject, here's my thoughts. The TV itself i have used previously with a Intel NUC i7 and i ran 4k @60hz with sleep on that device and the tv never had any issues detecting when the nuc woke up after a day of sleeping so the TV seems fine. The Intel NUC also uses the intel built in driver (but not skylake) so i would guess it would handle those events similar to how the asrock built in intel graphics does, no? Well it does work on the nuc, it doesn't on the asrock motherboard so i'm automatically thinking asrock is to blame but it might also be the skylake intel drivers) but since i never experienced any difference running all the intel updates yet when changing bios i experienced huge difference i could only conclude that the gfx was working and asrock bios was broken. I will do more tests in the weekend, it's very time consuming to test as explained above when the TV & HTPC sleeps for more then an hour wake up signal is not being detected, doing trial and error on this obviously takes a lot of time. |
Posted By: Xaltar
Date Posted: 14 Apr 2016 at 2:43pm
|
The integrated graphics on Skylake CPUs is significantly changed over previous generations. Intel have been stepping up the iGPU portion of their CPUs for some time now and I am not surprised there are issues popping up. Skylake has been out for a while now but it has been plagued by issues from the start. That isn't uncommon when intel releases a new socket, it will take a little more time before the platform is mature and relatively problem free. On my own Skylake system I encountered a number of issues all of which were resolved for me by a microcode update (which is provided alongside a BIOS update and comes directly from intel). The fact that a microcode update was necessary to fix the problems I was having means that the original CPU microcode was the fail point. The iGPU, as Parsec noted has received numerous driver updates which can only be due to issues and bugs needing correction. I can't help but feel that Skylake was rushed to market prematurely. Despite all the problems however, Skylake is a significant step forward over previous generations and all these issues will most certainly be corrected both by intel and motherboard manufacturers soon enough. Unfortunately manufacturers can't really fix much until intel provides a proper fix, the most that can be done without a fix from intel is a workaround or hack in the BIOS that bypasses a function or disables it. Intel does not share the inner workings of their products, they provide standards that all manufacturers must adhere to in order to support their products. If you google search your problem (sleep issues on Skylake) you will see it is not restricted to any one manufacturer. Manufacturers will often use common issues like this as a selling point for their products, by using a hack/workaround in their BIOS it creates the illusion that their product/s are not effected by the issue until you look closer and note that a feature is missing or not functioning correctly. I would imagine issues like yours are being worked on, the problem seems to be that a fix for one issue breaks another, as you noted the issue was improved by changing BIOS versions. It may be of use to post your issues on intel's forums aswell. Also worth noting is that a motherboard is comprised of more than just the chipset and socket, there are numerous other componets/controllers that provide functionality. Many of these are 3rd party and have firmware of their own which needs to be provided by the respective 3rd parties. So a signal converter that provides output to the display connectors may play nice with Haswell but require an update to work properly with Skylake. In a case like this either the manufacturer of the converter can provide an update or intel can patch their microcode to make the 2 components play nice together. The relationships between components on a modern motherboard are complex and intricately connected.
------------- 
|
Posted By: dkeone
Date Posted: 14 Apr 2016 at 3:48pm
|
Interesting read, come to think of it i have been having issues when displaying the AsRock bios and i figured it was an bios issue but now i think it might actually be related to skylake and the 530 gfx. Usually when i open the bios on my Asrock z170 ITX the bios looks normal, red and similar design as the motherboard has but sometimes (maybe 3 out of 10 times) the bios looks blue, and strange artifacs like lines and weirdly displayed colors that look somewhat like 3d looks if you don't have 3d glasses on you. I will be looking to update my CPU "microcode" on my i5-6500 skylake cpu. |
Posted By: dkeone
Date Posted: 15 May 2016 at 11:29pm
|
Just wanted to update that all of my issues have been solved when i updated to BIOS 2.10 and the latest intel GFX driver released earlier this month, thanks for your hard work! Things that work now that didn't before: TV turns on 100% after sleep, even after sleeping for 24 hours. TV gets signal even if the HTPC booted while TV was not on. Running windows 10. |
Posted By: Xaltar
Date Posted: 16 May 2016 at 1:01am
Thanks for the update  -------------
|
Posted By: nullredvector
Date Posted: 10 Dec 2016 at 1:25am
|
" rel="nofollow - Is everything still working? I'm having the same 2/3 problems you were having. Im using the latest intel drivers (tried, 4542 and beta 4552) and latest BIOS (7.10). I see BIOS 2.30 has "modified S3 behavior" under release notes. I wonder if I should try that version. I'd assume, that 7.10 has those fixes as well, maybe they broke again? I'm using a Samsung KU6300 (UN40KU6300). Basically the only thing that brings the 4k@60hz signal back is hooking up to the HDMI 1.4, reinstalling the drivers and reconnecting to the HDMI 2.0 port.
|
Posted By: hiluke
Date Posted: 16 Jan 2017 at 10:05am
|
" rel="nofollow - I have just upgraded UEFI to 7.10 (from 1.80) and HDMI firmware to 1.48 (from 1.36) to solve some audio issues I had with HDMI2 4K 60Hz. However now I have noticed a few times in the last few days that the screen fails to wake after leaving the computer for a while. I have my PC set to never sleep, however if I leave it for an extended period of time, turn the TV on and try to move the mouse to wake the screen, I just get no signal. I can still remote desktop to the PC fine, just no output on the screen. I've also noticed a few times when my PC does wake the monitor that my desktop icons have been re-shuffled (like it's had to adapt to a smaller resolution). I have not noticed this with HDMI1 at all. Is there a recommended UEFI version to revert to in order to fix this problem?
|