ASRock Taichi z370 fails to boot, but lets me manually boot.

Toggle sidebar Toggle sidebar
C

Carpy2

Distinguished
Nov 18, 2011
54
0
18,640
So I have a ASRock Taichi z370. I did a fresh install of windows 10 (wish I stayed with 7 now, 10 is absolute &#$!, but that's a different discussion...) onto my SSD. When I turn my computer on (or restart), it will fail to boot and come up with the failure page. I wait until it times out (10 seconds), then I have to press F11 to go into the boot manager and manually click on the drive. It shows up as Windows Boot Manager(Samsung PRO SSD blah blah), and boots just fine. This drive is in SATA_0 which ASRock recommends, and I have set it to the default boot device in the BIOS.

Anyone have a similar issue or know of a fix? It can clearly boot just fine using the drive, but it has to fail first, then have me select the drive manually. Maybe I need to "Restore" windows 10/reinstall it?

I guess it's worth to note that these SSDs are only about 2 years old, and I have been using the same drive to boot into Windows 7 with no issues. It's just once I changed to Windows 10 that this started happening. Unfortunately I changed Mobos and OS's at the same time, so I'm not sure which one is the issue.

Edit: In BIOS I can set the type of drive as SSD or HDD. I have tried setting it as both, but it's the same issue for both SSD and HDD. I have tried reflashing the BIOS with the current version, as well as a more recent beta version with no success.

Thanks!

[two posts merged]
 
Solution
J
Finally i found a solution to this on the web, some german changed the memory banks from 1-3 to 2-4 , then the booting was fixed and also the xmp settings started to work, two things in 1 blow !!
Sort by date Sort by votes
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
1. While not absolutely mandatory it's best to connect the boot drive (I'm assuming the Samsung SSD is a 2.5" model, not a M.2) to the first SATA data connector, i.e., SATA3_1.

2. You've checked the settings in the BIOS/UEFI Boot Option Priorities to ensure the SSD is correctly enumerated?

3. If the SSD has been GPT-partitioned it should be booted as a UEFI device. The Windows Boot Manager should correctly select the Samsung SSD in that case.

4. If the SSD has been MBR-partitioned, the BIOS should reflect the Samsung as Boot Option Priority #1 and NOT list the Windows Boot Manager as first in boot option priority order.

See if the above resolves the issue and let us know how it goes.

BTW, you should be able to invoke the boot menu through a press of the F11 key after you power-on the PC for the boot. You shouldn't have to wait until a "failure page" (as you refer to it) displays before accessing the boot menu via the F11 key.
 
Upvote 0 Downvote
C

Carpy2

Distinguished
Nov 18, 2011
54
0
18,640
Thanks for the reply.

1. That's what I thought. I read the manual that came with the motherboard and they said for best performance they recommend putting the boot drive in SATA3_0 (you're correct it's an SSD not a M.2).

EDIT: I tried switching my boot drive to SATA3_1 and my RAID to SATA3_2/SATA3_3, and it's the same issue.

3/4. This sounds like it's hitting on something key. It definitely is labeled as "Windows Boot Manager." After the failure page (or pressing F11, that works too), it goes to the default UEFI boot option page and there I can select the drive to boot from, and it works. I will see if for some reason I have settings in there that are trying to tell it to behave like a MBR-partitioned drive, or visa versa. I will check these things and post my results.

Thanks!
 
Upvote 0 Downvote
C

Carpy2

Distinguished
Nov 18, 2011
54
0
18,640
OK so some developments:

1. I took some screenshots of my settings. I have disabled the "boot manager" tool, it was recommended to only use this if I am switching between OS's/systems.

2. It still hits the boot failure screen, but now after it times out and lets UEFI continue to boot, it doesn't have me select a drive to boot from, it just autoboots and it works. I assume there is no drive selection after letting UEFI boot because I disabled the boot manager. Because UEFI can boot off my drive, it leads me to believe my SSD is a GPT partitioned drive (and it is called Windows Boot Manager). But I'm still unsure of what it is trying to boot from initially that fails.

So we're closer, but for some reason it is not initially using UEFI to boot. There are a few settings in the BIOS that I did not fully recognize. For example, they call RAID "Intel RST Premium with....". So perhaps there's a setting in here that I just don't recognize the names of that is my problem.

Here's my advanced storage page, and my regular boot page: sorry for the imgur links, i used to direct embed with photobucket but now their premium service thing stops 3rd party embedding....

https://imgur.com/a/hZGKn
https://imgur.com/a/xYybu
 
Upvote 0 Downvote
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
Unfortunately the ASRock User Guide is not a model of clarity when it comes to clearly explaining to the user the boot priority process. In that respect it doesn't much differ (based on our experience) with other motherboard manuals produced during the advent of the UEFI/BIOS interface and the concomitant MBR/GPT partitioning schemes. It makes many of us yearn for those pre-UEFI days when the simplicity of the BIOS-only firmware motherboards as it pertained to boot priority made these things much more understandable to users.
 
Upvote 0 Downvote
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
(My last response was sent before I received your current post that includes the screenshots.)

The "Intel RST Premium" refers to the Intel Rapid Technology system but it's the first time I've seen that "Premium" designation. I assume that's the default setting? Is there any other setting you can select or just "Disabled" or some such? No explanation in the user guide?

Your boot settings seem right.

You're sure about the need to disable the boot manager? That's in the user guide?

Is your Samsung SSD MBR or GPT partitioned? (I don't think you've ever mentioned its size).

The bottom line is all this is that I really don't know why you're experiencing this boot problem. Have you been in touch with ASRock tech support (they have a "tech support contact form" on their website). Sometimes (it's a crapshoot!) they can be very responsive & informative, other times ...

Also, have you accessed Newegg's webpage re this motherboard to peruse the reviews and see if there's any info there that might shed some light on your problem. And you can pose a question as well that will reach those users.
 
Upvote 0 Downvote
C

Carpy2

Distinguished
Nov 18, 2011
54
0
18,640
Thanks for the help Art, I don't have a ton of time at the moment to trouble shoot this, and since it does eventually boot, at least I can use it, ha! I will peruse the ASRock forums and checking out thew newegg reviews is a great idea I had not thought of. Although I have not totally solved this issue, I think you've given me the full solution on how to move forwards with this. I will be reading more of the manual when I have time it seems!

Thanks again!
 
Upvote 0 Downvote
A

ArtPog

Admirable
Sep 17, 2014
2,951
3
8,965
Good; that's about all you can do at this point. But PLEASE; keep us informed of your progress and hopefully can report some positive results since I'm TRULY interested in this issue. Feel free to send me a private message via this Forum if that's suitable for you. Good luck!
 
Upvote 0 Downvote
J

jessejames840

Honorable
Feb 5, 2018
3
0
10,520



Did you fixed it ? I got this motherboard and have the exact same problem ..
 
Upvote 0 Downvote
J

jessejames840

Honorable
Feb 5, 2018
3
0
10,520
Finally i found a solution to this on the web, some german changed the memory banks from 1-3 to 2-4 , then the booting was fixed and also the xmp settings started to work, two things in 1 blow !!
 
Upvote 0 Downvote
Solution
C

Carpy2

Distinguished
Nov 18, 2011
54
0
18,640


I know it's been a few months but I revisited this issue recently after seeing the newest BIOS version seemed to be a pretty big step. Similar to you I also messed around with my RAM a bit and seemed to have some success. I updated my BIOS and tried switching my two ram sticks between single and dual channel mode (slots 1 and 3 and 2 and 4). With this new BIOS update dual channel memory booted just fine, and the boot issue also went away.

So it seemed to be some sort of RAM/BIOS related issue that ASRock has since patched. Hopefully everyone else with this issue has similar success with the newest BIOS versions.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom