H170A-X1/3.1 boots to BIOS sometimes
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=3270
Printed Date: 20 Jul 2025 at 3:18pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: H170A-X1/3.1 boots to BIOS sometimes
Posted By: cybermcm
Subject: H170A-X1/3.1 boots to BIOS sometimes
Date Posted: 18 Aug 2016 at 1:28pm
|
Hi, I've an annoying problem with my new H170A-X1/3.1 (BIOS 1.90). The MB sometimes (not always) boots straight into BIOS after a power reset (no power -> power on -> straight into BIOS). There is no real error messages, the BIOS settings are correct. I already did change the MB because I thought that my first one was a faulty one but it is the same with the new one. I did change a few BIOS settings, I'm guessing it has something to do with the WOL (wake on lan) function. WOL is working (as it should). Any clues? My system: i5-6500 Samsung SSD 850 Evo 500GB Toshiba X300 6TB be quiet! Straight Power 10-CM 500W KINGSTON DDR4 32GB 2133MHz Non-ECC CL15 DIMM (Kit of 2) UPDATE: There was a solution to my problem, please follow this http://forum.asrock.com/forum_posts.asp?TID=3270&PID=16742&SID=2137245fza9631432d3f8f26f1d9e1654282407&title=h170ax1-31-boots-to-bios-sometimes#16742" rel="nofollow - link for a quick solution |
Replies:
Posted By: wardog
Date Posted: 18 Aug 2016 at 1:48pm
|
What is the model of memory you have? Does Kingston verify it compatible wit the motherboard? http://www.kingston.com/us/memory/search/options |
Posted By: cybermcm
Date Posted: 18 Aug 2016 at 7:50pm
|
@wardog: my RAM: KVR21N15D8, my MB is not listed on the Kingston page but this is a standard RAM module, no OC, so I'm quite sure that this is not related to the RAM modules... |
Posted By: wardog
Date Posted: 18 Aug 2016 at 10:48pm
|
Being quite sure then as you are, then I'd say it's time to look elsewhere. |
Posted By: cybermcm
Date Posted: 18 Aug 2016 at 11:28pm
|
any ideas where to look? I never owned a Asrock board before, is it useful to create an official bug report anywhere since I'm quite sure that this can only be solved by an update? The problem will be that it is hard to convince anyone at Asrock since it is not really reproduce-able (but I have found topics here with the same problem) but it happens... |
Posted By: wardog
Date Posted: 19 Aug 2016 at 10:20am
|
Honestly, and I'm NOT trying to sway you, IMHO seeings your on the second MB and experiencing the same issue, that to me anyways would make me look elsewhere beyond the motherboard at other components. Have you done an out of the case build? I'd say that's the next thing I'd do here. |
Posted By: parsec
Date Posted: 19 Aug 2016 at 11:57am
While there are only two platforms that support DDR4 memory currently, X99 and Intel 100 series chipset boards, we have learned over time that these two platforms have different SPD and XMP memory profile settings, and are not 100% compatible. They usually need to have some of the memory settings manually adjusted, VCCSA and VCCIO in particular. Your's is the second model of Kingston memory I've checked today that has its compatibility list link removed: http://www.kingston.com/us/memory/search/?partid=kvr21n15d8k2/32" rel="nofollow - http://www.kingston.com/us/memory/search/?partid=kvr21n15d8k2/32 Your board's Memory Support list does include your Kingston memory model, although the model number you gave cut off the capacity. Your memory is the Double Sided (DS) type. That type of memory should be used in the A1 and B1 slots. No idea if you use them or not. When an ASRock board starts into the UEFI, that means it thinks a UEFI setting is wrong. Or, the Boot Failure Guard feature has detected a failed boot, and restarts the board into the UEFI to "fix" settings, normally a bad CPU or memory OC. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
cybermcm wrote:Posted By: cybermcm
Date Posted: 20 Aug 2016 at 3:59am
|
@parsec: The whole RAM model number is "KVR21N15D8K2/32" like you expected. RAM place: According to the manual I placed it in A2 and B2, there is no explanation that it should be placed in A1 and B1? "Boot Failure Guard" was disabled. Next steps from my side: 1) I'll revert back to BIOS default settings and keep an eye on it if it happens again (my guess is still a BIOS bug, maybe the WOL function) 2) I'll change the RAM slots if necessary to A1 and B1 but I'm not sure because manual says otherwise? 3) changing the RAM parameter. If I've no intention to do OC at all, is it useful to alter the parameters? Where can I find the right VCCSA and VCCIO parameter? 4) is there a "log" where I can find the reason why my MB boots into BIOS? old POST codes aren't available as far as I know |
Posted By: cybermcm
Date Posted: 23 Aug 2016 at 4:49am
|
update: I did switch back to default UEFI settings and there was no boot to BIOS since this action. I'll continue to monitor this and then try to set my desired BIOS settings step by step. I'm still guessing that this is somehow connected to an UEFI setting... |
Posted By: cybermcm
Date Posted: 24 Aug 2016 at 9:20pm
|
update #2: I think I figured it out. The problem relates to the "wake on LAN" function. BIOS: Wake on LAN enabled (UEFI default -> disabled) OS (Windows): Original Intel NIC driver -> Wake on LAN enabled from power off What happens? After powerloss -> power on (without pressing the power button) -> PC starts for about 3 seconds (I'm guessing to initialize the WOL function) -> Power button -> PC boots to BIOS (probably "thinking" that the first boot process was interrupted) BIOS: Safe guard is off -> I'm thinking that this is indeed a BIOS bug Can anyone confirm this behavior with this board (or even another Asrock board)? |
Posted By: parsec
Date Posted: 24 Aug 2016 at 11:45pm
For some reason, your board's Memory Support list does not include several Note entries at the top that we usually find in those lists of other ASRock boards. There is no reason I'm aware of why your board should be different regarding memory than and other ASRock board. I assume the missing notes, which are basically identical between board models, might be a mistake. Your board's manual also does not include this information, so you haven't overlooked anything. I found that several other H170 boards do not include any Notes in their Memory Support lists. We can see that some of the Notes provide basic information about the list such as what 'V' and "2PCS" means, which should be included IMO. These are the Notes from another ASRock H170 board: Note1: Dual Channel: V = supports 2 modules and 4 modules Note2: 2PCS = tested successfully with 2 modules Note3: For 2pcs (DS), please use A1 and B1 slot. Note4: The O.C. mode is not guaranteed. It depends on whole system configuration and other parameters. Note5: For system stability, use more efficient memory cooling system to support a full memory load (4 DIMMs) when overclocking. Note6: The system needs discrete VGA card to support DDR4-2133+ Note3 explains the use of the A1 and B1 memory slots when using Double Sided (DS) memory. That information is included in all ASRock, Intel 100 series chipset boards (such as your H170 chipset board) that have four memory slots. While it is not absolutely wrong to use the A2 and B2 slots with two pieces of double sided memory, it is considered optimal to use the A1 and B1 slots in that situation. Unless there is some reason you cannot put your memory in the A1 and B1 slots, such as clearance issues with your CPU cooler, you should put them in the A1 and B1 slots. If you do that, clear the UEFI/CMOS at the same time. If you use any non-default UEFI options, save them in a profile before you clear the UEFI, so you can restore them easily. There is no log that records why the board started into the UEFI/BIOS. If a board can start into the UEFI/BIOS, POST has passed successfully. In the UEFI, OC Tweaker screen, the Voltage Configuration screen has the VCCSA Voltage option. Your board does not seem to have a VCCIO option, since it is not the type that can over clock memory. The correct VCCSA value should be programmed into your memory's SPD and XMP data. Using the Auto setting should also provide an appropriate value for VCCSA. I mentioned this earlier as a potential fix IF you were having an issue with your memory, which was unknown at the time, and still not known to be related to your issue.
The Wake on Lan, or Wake on Magic Packet from power off state option, with the Intel network driver installed on my ASRock Z170 board, that uses the same Intel I219-V network chip as your board does, includes this information in the Device Manager Properties, when this option is selected: Allows the adapter to wake an Advanced Power Management (APM) enabled system from a power-off (S5) state. ACPI systems can wake from an S5 state if the system's BIOS supports it. Notice it can wake the PC from an S5 "power-off" state. The ACPI S5 state is a Windows/OS shutdown state. It is not a power loss from the PSU to a power on of the PSU. A description of the S5 ACPI state:G2 (S5), Soft Off: G2/S5 is almost the same as G3 Mechanical Off, except that the power supply unit (PSU) still supplies power, at a minimum, to the power button to allow return to S0. A full reboot is required. No previous content is retained. Other components may remain powered so the computer can "wake" on input from the keyboard, clock, modem, LAN, or USB device. The LAN/network chip is still supplied with power when a PC is shutdown, in the S5 state. Otherwise WOL would not work. If the PSU is shut of with its power switch, or loss of AC power, nothing can be done for WOL to work. Can you describe what the circumstances of your power loss to power on situation is? Did the power loss occur when the PC was shutdown from the OS, or what?  ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: cybermcm
Date Posted: 25 Aug 2016 at 4:33am
|
@parsec: Thank you for your detailed information. I'll try to put my RAM into A1 and B1 but I don't think that it will change something. WOL: I normally shut down my PC in the evening and it is also connected to a plugbar with a mechanical switch which I also shut down (so PC and PSU is complete without power). If I switch on the plugbar (in the morning) my PC starts for about 3 seconds (so Power On screen is visible and POST checks are running on the bottom right) I think this is necessary to get WOL working (which is explained in your post). After that PC is off again but I'm able to wake it from a remote location with the issue that on next boot the PC jumps into BIOS (which makes the WOL function useless from a remote location). |
Posted By: lindend
Date Posted: 25 Aug 2016 at 10:06am
|
Different motherboard but very similar symptoms. Z170 OC Formula motherboard boots into UEFI setup when AC power is restored, but not when I press the power button when the device is off but A/C power is present. This problem started happening a week or so ago, and it was around the time I started to try to get Wake on LAN to work. I first enabled the "Boot from Onboard LAN". When that didn't work, I restored the default setting, but ever since, I've been stuck in this state. I currently have the "PCIE Devices Power On" setting enabled but I enabled this after the boot into UEFI Setup started happening. I think you're on to something here, UEFI Setup bug w/WoL settings, but unclear the exact sequence to get into this state or if its tied to the A/C Power On Setting too. Edit: pretty sure this isn't a failed boot issue. I had problems with the XMP Profile setting when I had RAM in the A1 and B1 slots. Moved them to the A2 and B2 slots as described in the manual and the XMP Profile instabilities and failed boot issues went away. RAM is CORSAIR Vengeance LPX 32GB (2 x 16GB) CMK32GX4M2B3200C16 Edit #2: Doesn't boot into UEFI when I do Wake on LAN either. Only when A/C power is restored and the UEFI setting to power up when A/C power is restored is enabled. |
Posted By: cybermcm
Date Posted: 25 Aug 2016 at 1:47pm
|
@lindend: It happens after the first boot when AC power is restored (with "PCIE Devices Power On" enabled). It doesn't matter if you have A/C Power On settings configured. Of course after a power loss the first boot goes into BIOS. After a power loss if the power returns to the PSU is your PC starting for a few seconds? |
Posted By: lindend
Date Posted: 25 Aug 2016 at 7:20pm
|
No, the behavior appears identical for the A/C power loss boot and pressing the power button or doing a Wake on LAN. Just in case it was the failed boot issue, I increased the number of failed boot attempts to 6 before going into Setup and that didn't alter anything. I see the logo for 1-2 seconds, then it enters setup on a cold boot. |
Posted By: wardog
Date Posted: 25 Aug 2016 at 8:15pm
|
Anyone here stop and consider this might be caused by an unstable overclock? That would explain away a lot of what I just read here in two pages. |
Posted By: cybermcm
Date Posted: 26 Aug 2016 at 12:25am
|
@wardog: No, I'm doing absolutely no overclocking. Every OC parameter in BIOS is set to AUTO or Default. My RAM is a non OC RAM. This is a bug. @lindend: Sorry, I wasn't clear enough. It happens like you described. What I meant was that the BIOS option "A/C Power On" option has no effect on this bug. |
Posted By: cybermcm
Date Posted: 26 Aug 2016 at 4:21am
|
I opened an official support incident on the Asrock page. I'll post an update as soon as I get an answer |
Posted By: lindend
Date Posted: 26 Aug 2016 at 7:01am
|
I've not overclocked anything yet. Wanted to have a stable system first. |
Posted By: cybermcm
Date Posted: 27 Aug 2016 at 6:32pm
|
@lindend: I didn't get an answer to my bug report. Can you try to create an incident on the Asrock page? |
Posted By: cybermcm
Date Posted: 29 Aug 2016 at 5:49pm
|
I got an answer from Asrock: it is hardware limitation. The only thing you can do is to let the system boot up and shut down after cutting AC power off. This is weird. If that is an normal behavior all boards will have the same bug?!? Anyone want to try to open another case? |
Posted By: rrck
Date Posted: 02 Sep 2016 at 12:41am
|
Same here, with a H170M Pro. Booting to "logo screen" after external power is restored, despite selecting "POWER OFF" in BIOS. I've never seen such harebrained behavior before. But where can I open a bug report? Do you have a link for me? |
Posted By: cybermcm
Date Posted: 02 Sep 2016 at 3:46am
|
sure, I used this one: http://event.asrock.com/tsd.asp There is still no solution. We have to convince Asrock to look into it. This is a bug... |
Posted By: parsec
Date Posted: 02 Sep 2016 at 8:08am
The Restore on AC/Power Loss option's purpose is not meant to apply in the situation that is being discussed here. Your situation occurs after the PC is shutdown and the PSU is either switched off or removed from AC power, right? This is the description of this option in my ASRock 170 board's manual: Restore on AC/Power Loss Select the power state after a power failure. If [Power Off] is selected, the power will remain off when the power recovers. If [Power On] is selected, the system will start to boot up when the power recovers. Note the use of the words restore and failure. The purpose of this option is to either start or not start the PC after a power failure (once power is restored) when the PC was on and the OS was booted and is running. Turning off the PSU manually or removing AC power to the PSU, with the PC shutdown, is not a power failure situation. If the PC is shutdown, what needs to be restored if the PSU is turned off and then turned on again? This option allows the user to configure whether or not a running PC will start again or not, when AC power is lost during a storm, for example. That is a power failure. I agree that if every time I shutdown my PCs to work on them, and turn off and unplug the PSU, and upon connecting the PSU to AC power and turning it on again, it would immediately start and either go into the UEFI or boot, or even start for a few seconds and then shut off, is not a normal situation, or at least one that I have experienced in the past. But I don't have WOL enabled. I have several ASRock boards, and none of them start when I turn on the PSU after a shutdown, or otherwise. My only point here is, the Restore on AC/Power Loss option is not meant to control what you are experiencing. WOL seems to be the cause. The answer from support is saying apparently that some type of initialization or setup is being done when the PSU is turned on (supplying power to the board) and WOL is enabled. I don't know if that is true or not. But some of you feel that is absolutely impossible? Do all of you use Windows 10? Windows 10 has caused network issues of all kinds. Intel network driver features like NIC teaming is broken with Windows 10 from the beginning, and has still not been fixed. This is just a thought, I'm not saying Windows 10 is the problem. I'll need to try this myself with WOL enabled. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: rrck
Date Posted: 02 Sep 2016 at 2:04pm
I know what it's meant for, and it's a useful and required option. All I'm saying is that if that option is DISABLED, the PC should not behave the way it does. It should stay switched off completely, not start and shut down after a few seconds. And it's got nothing to do with WOL; I've disabled all Wakes that I could find. |
Posted By: rrck
Date Posted: 02 Sep 2016 at 2:05pm
Thanks, I'll open another one. (Besides, I had an ASRock board before, and that one wasn't so stupid.) |
Posted By: cybermcm
Date Posted: 02 Sep 2016 at 3:34pm
|
Thanks four your answers. I don't want to mix up things so I'll clarify my case: I'm not using the "Restore on AC/Power Loss" option, this is still set to off in my case (default value). If you enable wake on lan then the board is powered for a few seconds to initialize the WOL function, which is an expected and desired function. My problem is that after that the first boot goes into BIOS and this can only be a bug and never be a desired configuration (it would also happen after a power loss)! And yes I'm working with Win10 64bit but I don't think that this has something to do with it. |
Posted By: parsec
Date Posted: 02 Sep 2016 at 9:31pm
Well, I tried to explain that option, if you refuse to accept it is not related to your situation, that is your choice. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: parsec
Date Posted: 02 Sep 2016 at 9:54pm
I understand that the issue is not related to the Restore on AC/Power Loss, I said that in my previous post. I also said I understand what your problem is, and I never said it did not exist, or is not an issue. As I tried to emphasize in my previous post, the ONLY point I was making was the Restore on AC/Power Loss option will not change the behavior you are experiencing. Sorry to keep repeating this, but it seems like no one actually reads it. I am done with that.Yes, starting into the UEFI/BIOS when power is restored is a problem, I agree for all the reasons you listed. That is obvious. This is the one and only issue that needs to be fixed and figured out here. My first test on a new ASRock H110 chipset system I have also confirms that when power is removed and then restored, the PC will start for a moment and then turn off when WOL is enabled in the UEFI. But that system did not start into the UEFI/BIOS. I need to try some configurations of the Intel network driver settings in Device Manager to see if this PC will do what yours does. I also will do that on my ASRock Z170 PC. Are we (you and I) on the same page now? We should be, I just want you to know that. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: cybermcm
Date Posted: 02 Sep 2016 at 11:02pm
We are ;-) I just want to make sure that the "real" problem is discussed further. Please check your Windows NIC settings, there should be an option "Wake on Magic Packet from power off state" which has to be enabled. Without this option WOL isn't working (which is a normal behavior). Another Point in Win10: You have to clear "Turn on fast startup" in Power options -> System settings to get WOL working (at least I had to do this) Is WOL working with your configuration? |
Posted By: lindend
Date Posted: 03 Sep 2016 at 5:15am
|
I actually built two machines with the Z170 OC Formula motherboard. Both machines are identical and have identical UEFI settings. One boots into UEFI, the other doesn't. One works with WoL, the other doesn't. The one where I can't get WoL to work also doesn't boot into UEFI from a cold boot. I've disabled Fast boot on both in Win10. They have the same revision of Intel drivers loaded (12.15.22.6). The machine where WoL doesn't work will wake up the device with a magic packet in hibernate mode, just not from a cold boot. To enable WoL in UEFI, I enabled the option in ACPI settings (PCIE Devices Power On). Is this the correct option? |
Posted By: parsec
Date Posted: 03 Sep 2016 at 8:58am
Good, and I also want to discuss your issue. I tested this on my Z170 Extreme7+ board. My board's UEFI also uses the PCIE Devices Power On option to enable WOL, which I set to Enabled. I did not have the Boot From Onboard LAN option enabled, it was disabled. This board has the same Intel I219-V chip as yours, which is really a "PHY Layer" chip used to work with the MAC networking capabilities of the board's chipset, the Z170 in my board, and the H170 in yours. My board also has an I211-AT chip, that provides the PHY and MAC support on one chip. The I219-V is the one connected to my router. I had all three WOL options checked in the Power Management tab of the I219-V's Properties. I also had all of the Power Saver Options checked. BTW, I have the Intel 21.0 network driver installed, directly from Intel: http://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=83418" rel="nofollow - http://downloadcenter.intel.com/download/25016/Intel-Network-Adapter-Driver-for-Windows-10?product=83418 I had Windows Fast startup checked during this test, I was not aware of that being possibly a problem with WOL. With this configuration, I shutdown Windows 10, turned off the PSU with its switch, and pulled the AC cord out of the PSU. I let the PC sit like that for at least an hour. I then connected the AC cord to the PSU, and turned it on. The PC immediately started for a few seconds, but then shut off and stayed that way. That does not happen when PCIE Devices Power On is disabled, the PC does nothing when power is restored to the board. I later turned on the PC with the case power switch, and it booted into Windows 10 normally. So trying this all of one time so far, I did not get the start up into the UEFI UI behavior that you are getting on this Z170 board. I have not tested WOL on this PC yet. You said in your first post that the startup into the UEFI after a power reset only happens sometimes? So it seemingly randomly does this? I'm not implying you don't have a problem, just that a random one is more difficult to diagnose. I'll try this test again on the H110 chipset PC, which also uses the I219-V chip. I did not have WOL enabled in the I219V Properties when I tested the power reset. I could also try this test on my ASRock X99 board PC, which has Windows 10. Anything else I can try for you? At least a few power restores on the Z170 board? You post about the response from ASRock support seemed to say that you thought ASRock support said it is normal for the board to start into the UEFI with WOL enabled after a power restore. I say that since you have said the momentary start up and then shut off on a power restore is normal when WOL is enabled. I believe that is what ASRock support said. I just want to clarify what you said about that. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: cybermcm
Date Posted: 03 Sep 2016 at 6:48pm
Have you checked the NIC settings? There is a setting "Wake on magic packet from power off state"? My board boots into UEFI only if WOL is working, so it is the same as you described. Does your board always boots into UEFI after power loss of the PSU or only sometimes? In my case it is often but not always.
Thats the correct option. Make sure that you haven't enabled "deep sleep" because then WOL isn't working (at least for me) |
Posted By: cybermcm
Date Posted: 03 Sep 2016 at 7:10pm
First of all, thanks for the time you spend looking into this! My NIC options, we have the same driver version (just to be sure): 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 It would be really interesting if your WOL really works. This misbehavior only occurs if WOL is working, at least for me. It makes no difference if I wake up my PC with the power button or with WOL.
Correct, it is often the case (with PSU power down) but not always.
If you test with a H110 chipset please enable WOL. It doesn't occur if WOL is disabled. Power restores with Z170? It would be great if you can try it a few times (and check if WOL is actually working). It happens about 2 out of 3 times with my board.
About Asrock support. The answer to the described issue was "it is hardware limitation. The only thing you can do is to let the system boot up and shut down after cutting AC power off." So basically they say, it is a feature, not a bug. If this is the case it is really disappointing. |
Posted By: parsec
Date Posted: 04 Sep 2016 at 1:12am
|
cybermcm, as you know, my NIC options were not the same as yours, but I can change them to match yours, that's easy. Part of my purpose as a moderator is to work with ASRock users when they have issues. Which means actually trying to reproduce their issues if possible. So thanks for appreciating that! To be on the "same page" again, what is your procedure or method for producing/having a WOL event on your PC? About the statement from ASRock support you received, which is: "it is hardware limitation. The only thing you can do is to let the system boot up and shut down after cutting AC power off." IMO, this is only referring to the momentary start up and shutdown of the PC when power is restored and WOL is enabled. At least I hope it is. That behavior is neither a feature or a bug, simply what is required for WOL to become working after a power reset. Support called it a limitation. I can see why you could think otherwise, given the "... system boot up and shutdown..." part of the statement. I think the statement from support is not addressing the situation of the startup into the UEFI. You referred to that as a feature, which I cannot see as being correct, or what support said in that statement. In both cases, where the PC starts to initialize WOL and then turns off, or starts into the UEFI UI, when power is restored (the issue), is neither a boot up or shutdown situation. I tend to be very specific and exact about terminology. For example, "booting up" is the loading of the OS, which is the final part of a PC's startup procedure. The first part is POST, which includes initialization of certain things. Does the WOL initialization operation when power is restored include a full POST? It seemed too short for that IMO, but it could make sense to do so. I'm not dismissing this as normal behavior, it seems to be a bug, but is not a feature, that is all I'm saying. Why this happens sometimes is the question in general. Meaning you and I may never know exactly why, if it is a UEFI/BIOS bug. I meant to ask you about this, do you use any of the Fast Boot option settings in the UEFI, besides Disabled? Fast Boot is actually a "fast POST", which I imagine has the potential to have side affects, not that I've ever seen any, but that does not mean they cannot exist. EDIT: Where is the Reduce Link Speed setting you listed? I don't see that on the Power Management tab, or any others. ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: cybermcm
Date Posted: 04 Sep 2016 at 4:54am
I'm using my router to produce a WOL packet. I mainly use it if I'm at work and need data from my PC at home. Over the last days I tried to keep the PSU with power, config not changed, WOL working. I never experienced a boot into BIOS. Today I switched back to my "old" procedure, shutting power down (also PSU) and then did a normal power on (with the power on switch). First try, directly into BIOS again :-(
"feature" -> this was meant to be sarcastic ;-)
I think that on initialization after power loss -> power on the post process can't finish. The "warm up" is to short for that. I can still see the post numbers in the bottom right corner until the PC shuts down again.
This is a very good point. I forgot that I had set this option to "fast". I'll try to set it to disabled and will monitor the outcome
Reduce Link Speed: Power Management tab -> Power Saver Options -> 4th option (scroll down, only the first 3 are shown) |
Posted By: lindend
Date Posted: 05 Sep 2016 at 3:12am
|
I meant to ask you about this, do you use any of the Fast Boot option settings in the UEFI I'm not using Fast boot and have never enabled it. |
Posted By: parsec
Date Posted: 05 Sep 2016 at 9: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? ------------- http://valid.x86.fr/48rujh" rel="nofollow">
|
Posted By: cybermcm
Date Posted: 07 Sep 2016 at 4:11am
Sorry for the delayed answer, I wasn't @home for a few days. Deep Sleep: I never touched this option, so it is still set to disabled (WOL working). 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. 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? |
Posted By: lindend
Date Posted: 07 Sep 2016 at 11:04am
I don't get notifications either. |
Posted By: lindend
Date Posted: 07 Sep 2016 at 11:13am
The Windows driver settings are identical between machines and both have the option to only allow a magic packet to wake up the computer. I have noticed that maybe 20% of the time, it boots normally from a cold boot. Haven't figured out a pattern yet. Is that roughly the percentage you're seeing?
Like you, I haven't touched the Deep Sleep setting. Wonder if that has something to do with this issue? System in an unknown, undefined state via the default? |
Posted By: lindend
Date Posted: 07 Sep 2016 at 11:24am
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). |
Posted By: cybermcm
Date Posted: 07 Sep 2016 at 5:13pm
Correct, after setting Fast boot to disabled I never experienced a cold boot to BIOS. But I'm still testing, didn't had much time lately... |
Posted By: wardog
Date Posted: 07 Sep 2016 at 5:13pm
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. |
Posted By: cybermcm
Date Posted: 08 Sep 2016 at 4:17pm
Another idea: Please try to reset UEFI back to default settings and enable only the WOL function (PCIE devices). Don't change anything else if possible and then try again... |
Posted By: cybermcm
Date Posted: 12 Sep 2016 at 10:23pm
|
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)! |
Posted By: wardog
Date Posted: 13 Sep 2016 at 12:24am
|
Thank YOU for posting what you discovered. |