ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - H170A-X1/3.1 boots to BIOS sometimes
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

H170A-X1/3.1 boots to BIOS sometimes

 Post Reply Post Reply Page  123 5>
Author
Message
cybermcm View Drop Down
Newbie
Newbie


Joined: 18 Aug 2016
Status: Offline
Points: 24
Post Options Post Options   Thanks (0) Thanks(0)   Quote cybermcm Quote  Post ReplyReply Direct Link To This Post Topic: H170A-X1/3.1 boots to BIOS sometimes
    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 link for a quick solution




Edited by cybermcm - 13 Sep 2016 at 4:08am
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post 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
Back to Top
cybermcm View Drop Down
Newbie
Newbie


Joined: 18 Aug 2016
Status: Offline
Points: 24
Post Options Post Options   Thanks (0) Thanks(0)   Quote cybermcm Quote  Post ReplyReply Direct Link To This Post 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...
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post Posted: 18 Aug 2016 at 10:48pm
Being quite sure then as you are, then I'd say it's time to look elsewhere.
Back to Top
cybermcm View Drop Down
Newbie
Newbie


Joined: 18 Aug 2016
Status: Offline
Points: 24
Post Options Post Options   Thanks (0) Thanks(0)   Quote cybermcm Quote  Post ReplyReply Direct Link To This Post 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...
Back to Top
wardog View Drop Down
Moderator Group
Moderator Group


Joined: 15 Jul 2015
Status: Offline
Points: 6447
Post Options Post Options   Thanks (0) Thanks(0)   Quote wardog Quote  Post ReplyReply Direct Link To This Post 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.
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: 19 Aug 2016 at 11:57am
Originally posted by cybermcm cybermcm wrote:

@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...


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

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.


Back to Top
cybermcm View Drop Down
Newbie
Newbie


Joined: 18 Aug 2016
Status: Offline
Points: 24
Post Options Post Options   Thanks (0) Thanks(0)   Quote cybermcm Quote  Post ReplyReply Direct Link To This Post 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


Edited by cybermcm - 20 Aug 2016 at 7:35pm
Back to Top
cybermcm View Drop Down
Newbie
Newbie


Joined: 18 Aug 2016
Status: Offline
Points: 24
Post Options Post Options   Thanks (0) Thanks(0)   Quote cybermcm Quote  Post ReplyReply Direct Link To This Post 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...
Back to Top
cybermcm View Drop Down
Newbie
Newbie


Joined: 18 Aug 2016
Status: Offline
Points: 24
Post Options Post Options   Thanks (0) Thanks(0)   Quote cybermcm Quote  Post ReplyReply Direct Link To This Post 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)?
Back to Top
 Post Reply Post Reply Page  123 5>
  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.094 seconds.