ASRock.com Homepage
Forum Home Forum Home > Technical Support > Intel Motherboards
  New Posts New Posts RSS Feed - Z170M Extreme4 boot device issue
  FAQ FAQ  Forum Search Search  Events   Register Register  Login Login

Z170M Extreme4 boot device issue

 Post Reply Post Reply
Author
Message
Nunyerbusiness View Drop Down
Newbie
Newbie


Joined: 16 Jul 2016
Status: Offline
Points: 19
Post Options Post Options   Thanks (0) Thanks(0)   Quote Nunyerbusiness Quote  Post ReplyReply Direct Link To This Post Topic: Z170M Extreme4 boot device issue
    Posted: 30 Jul 2016 at 10:01pm
Guys,

I have a Toshiba RD-400 SSD in the PCIe slot. I definitely had issues before with boot corruption using the Toshiba drivers. A perfectly stable, non-overclocked system would die and report 'no OS' on reboot, but just now I had the issue again without using their drivers. I went into UEFI simple, tried to set boot device to windows boot manager (RD400), but it would refuse to boot. I went into advanced and did the same thing, BOOM >> booted no problem.

Anyone see ANY similar issues with other PCIe or m.2 drives?  I don't know if it was solved by mucking around in UEFI or it's drive hiccups.  I noticed it did happen immediately after I booted a USB to check my recovery was OK or not.  This fact makes it even stranger.

ANY help or ideas to troubleshoot is greatly appreciated!

(ps. that RD400 is a screamer)
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: 30 Jul 2016 at 10:32pm
Boot record hosed?

cmd > "bootrec /?" (sans quotation marks for help with bootrec)


Another is possibly clearing, not resetting, the MBs BIOS.
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: 30 Jul 2016 at 10:54pm
Originally posted by Nunyerbusiness Nunyerbusiness wrote:

Guys,

I have a Toshiba RD-400 SSD in the PCIe slot. I definitely had issues before with boot corruption using the Toshiba drivers. A perfectly stable, non-overclocked system would die and report 'no OS' on reboot, but just now I had the issue again without using their drivers. I went into UEFI simple, tried to set boot device to windows boot manager (RD400), but it would refuse to boot. I went into advanced and did the same thing, BOOM >> booted no problem.

Anyone see ANY similar issues with other PCIe or m.2 drives?  I don't know if it was solved by mucking around in UEFI or it's drive hiccups.  I noticed it did happen immediately after I booted a USB to check my recovery was OK or not.  This fact makes it even stranger.

ANY help or ideas to troubleshoot is greatly appreciated!

(ps. that RD400 is a screamer)


What Windows version are you using?

I imagine you must have either CSM disabled, or the CSM option, Launch Storage OpROM Policy set to UEFI only, since you are using an NVMe SSD as the OS drive.

I have never used the Easy UEFI mode, but I wonder if the settings I mentioned above are preserved in Easy mode? Is the CSM option even available in Easy mode?

If you cleared the UEFI at any point, the CSM setting would be reset to its default, which normally will not allow you to boot from an NVMe SSD. I think ASRock may be setting CSM automatically now when a NMVe M.2 SSD is being used, but that may only be in Advanced mode.

If your OS boots from that SSD without running any type of repair on it, then there was no corruption of the boot record. The problem was simply the CSM option setting, apparently.


Back to Top
Nunyerbusiness View Drop Down
Newbie
Newbie


Joined: 16 Jul 2016
Status: Offline
Points: 19
Post Options Post Options   Thanks (0) Thanks(0)   Quote Nunyerbusiness Quote  Post ReplyReply Direct Link To This Post Posted: 19 Aug 2016 at 9:17pm
^^ I'll check it again, but like I said this should NOT be happening in easy UEFI as it's confusing a LOT of poeple!
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 10:14pm
Originally posted by Nunyerbusiness Nunyerbusiness wrote:

^^ I'll check it again, but like I said this should NOT be happening in easy UEFI as it's confusing a LOT of poeple!


Easy Mode could also be called Simple Mode. What should be happening with a UEFI/BIOS setting depends upon many factors, and any time a computer program (a UEFI/BIOS is a program) uses a default value for an option with specialized hardware (a PCIe NVMe SSD used as the OS drive), it will work for some users, but not others. One user's "should" is not everyone's "should".

If you use Easy Mode, certain settings (decisions) are made for you. That is part of why it is "easy". A PCIe NVMe SSD used as the OS drive is a very new thing. They have only been available for at most one year. SATA drives, which are far more common and have been in use for many years, don't need to be configured like NVMe SSDs do. So when choosing a default, automatic setting for a UEFI/BIOS option, the setting that is most commonly used will always be the choice.

NVMe is a completely new protocol, and different than SATA. It uses its own, different drivers than SATA. There are some new things to learn about NVMe SSDs used as OS drives. For some reason, mother board manufactures have become responsible for educating users about using their PCIe NVMe SSDs that are manufactured and sold by other companies. Pinch

Where is the evidence that Easy Mode is confusing a lot of people? I haven't seen complaints about it in this forum?
Back to Top
 Post Reply Post Reply
  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.109 seconds.