H170A-X1/3.1 boots to BIOS sometimes

I think it's safe for me to officially close my "case". WOL works as expected and no more cold boots into BIOS.
Fast boot enabled was the cause. If Fast Boot is disabled (default setting) the cold boot effect vanishes.
Thanks for all your patience and help!

[Update]
A summary how to enable WOL (Wake on LAN)
BIOS:
Enable Wake PCIe devices (default disabled)
Disable Fast Boot (default disabled)
Disable Deep Sleep (default disabled)

Win 10:
Install Intel NIC driver, settings:
1) Respond to ARP requests... -> enabled
2) Respond to NS requests.... -> enabled
3) Energy Efficient Ethernet -> disabled
4) Reduce Link Speed... -> disabled
5) Wake on Magic Packet -> enabled
6) Wake on Pattern Match -> disabled
7) Wake on Magic Packet from power off state -> enabled
8) Wake on Link Settings -> Disabled

Disable Fast Boot in Windows power options (default enabled)!


Edited by cybermcm - 13 Sep 2016 at 2:02pm

lindend wrote: cybermcm wrote: Off-topic: Neither my gmail or outlook.com address is able to get mails from this forum (e.g. replies to this thread). Am I alone with this problem? I don't get notifications either.

Sux doesn't it. It's being looked into.

Imagine keeping track of the threads us Mods post to ........... sigh.

Hopefully to be remedied. Soon I hope.

cybermcm wrote: I'll try to test further but it seems that you got the right idea! Since the moment I disabled Fast Boot I never experienced a cold boot into BIOS. I want to wait a few days longer to close my problem because I didn't had much time lately to do real testing.

Are you indicating that if you disable the UEFI fast boot, you don't see this issue?  I've never enabled UEFI fast boot so that isn't the source of my problem.  That being said, next boot, I will very that its disabled (default state).

cybermcm wrote: Off-topic: Neither my gmail or outlook.com address is able to get mails from this forum (e.g. replies to this thread). Am I alone with this problem?

I don't get notifications either.


Edited by lindend - 07 Sep 2016 at 11:20am

cybermcm, I finally got my H110 chipset PC (the new DeskMini 110W) to start into the UEFI after a power reset.

You know the configuration, Wake on LAN enabled in the UEFI and in the Intel network driver. Yes I did not have Reduce Link Speed checked. I had Windows 10 fast startup unchecked, and cold booted a few times to be sure it was not active. I had Fast Boot set to Ultra Fast, the only Fast Boot setting I had available in the UEFI of this board, the H110M-STX, since I have a UEFI booting Windows 10 installation, installed with CSM disabled.

But what was it, apparently, that caused the cold boot into the UEFI after a power reset?

Something I forgot to ask you about, but tried it anyway. The Deep Sleep option in the UEFI.

Deep Sleep is set to Disabled by default. Frankly, I don't know what power state the board is in when Deep Sleep is Disabled.

I figured you might have set Deep Sleep to S5, in order to get WOL working. BTW, you are correct about Windows fast startup being required to be not enabled (unchecked) in order for WOL to work, that is a known requirement given what I read about it, in multiple places.

So with Deep Sleep set to S5, and the rest of the configuration above, I experienced the cold boot into the UEFI.

I haven't tried to see if it will do it again, and that was NOT on a WOL event. I actually forgot I had that PC ready to test this, and started it up since it has a UEFI update that I wanted to apply.

Also, to be very clear, that was after I had done a power reset on that PC, which did NOT start into the UEFI when I applied power to the PC again. I happened when I powered the PC on manually. Regardless, I think it may be significant in this situation. I wanted to get this out to you ASAP.

The question that remains is, what did you have Deep Sleep set to in your UEFI?


Edited by parsec - 05 Sep 2016 at 9:21am