It just loops over these error codes:

21

12

33

de

ad

a2

for now I used the bios flashback functionality to back to the previous bios, but I would like to make use of the NVME raid in future. ( just running a single SSD at the moment, no raid at all )

Not sure what RAID settings were prior to flashing the bios.  

there's a sata m2 ssd on the board, and a single spinning rust disk on one of the sata connectors. there is no raid involved at all.

when I flashed back the 1.50 I did reset to defaults, and tried to flash the 1.70 from the bios with the same results. ( the looping status codes ), with no way to actually enter the bios.

I can try to do it without the sata devices connected when I have more time, it's a pain to access the m2 slot to remove the ssd in there, maybe this weekend I have more time to experiment, but during the week, I need my pc operational.

Yup get the same issue with the same codes. Downgrading to 1.50 fixes the issues. 1.70 is borked for me.

Config is Windows 10 on a SATA SSD and an NVMe SSD as a data drive.

Even if the vendor allows it - it is ALWAYS better to upload the bios file to a pen drive, clear cmos, reboot, enter UEFI again, flash, reboot, enter UEFI, set everything up again.

This is happening to me as well... I have 2x NVMe, 1x SATA (all in M.2 slots).

One thing that might not be clear (based on your response parsec) is that the above boot codes loop, as in they keep going repeating over and over (not once each power up).

It doesn't stop on A2, it just... loops again and again, running through all of the above debug codes.

Is there any BIOS update on the horizon soon? I really want to use NVMe RAID and SATA simultaneously...

Thanks

No, it's not restarting and starting the post codes from the beginning... When you hit the power switch, it goes through several debug codes until it gets to the above codes, then it loops them without restarting.

I actually believe the order its generating them is like this: de ad a2 21 12 33, loop... if that helps. I seem to remember before it loops back to de that there were other codes before the first de loop.

On 1.50, I can't say I watched the entire boot code pattern, but I'm relatively sure 99 is the last one I see before a successful boot.

I do have my SATA drive in M2_1, and my NVMe drives in M2_2 and M2_3 (because I might switch to a U2 drive later, and the manual says M2_1 is disabled if using a U2 drive).

I'll check on Wednesday if removing the SATA drive (or changing it to port M2_3 like free-eagle says) lets it boot on 1.70.

The first boot after the ssd switch failed to show anything on the screen, with the debug display showing either 94 or a4 (I forget).

The second (and third) boots worked fine, except the NVMe ssd in M2_1 doesn't show up, and the debug display continues to say a6 even though the screen/bios is responsive.

At this point I'm going to put a cheapish 1tb intel 600p nvme drive in instead of the 1tb sata drive, and call it a day... 

I'd like to actually use the new system I built instead of leaving it on my desk opened forever, lol.

X399 Taichi, 1950x, 64GB Ram  (4x16GB)

RAM= G Skill TridentZ RGB F4-3200C14-16GTZR  (FYI: ram seems to be stable with XMP enabled at 3200)

Board is at 1.70, has been since I built it 3-4 weeks ago.  I setup the system with Win10 on a single M.2 in slot 3.  Using onboard RAID for some SATA drives.

When I was setting up drives, I installed 2 cheapish 128GB drives I had laying around, with the intent to get 2 matching M.2 drives a later date (when my wallet stopped crying).  The system would not POST with any M.2 configuration other than Slot 3 alone... At the time I thought it was one of my low cost drives, so I just moved on.

Today saw the arrival of two brand-spank'n new M.2, 500GB Crucial SSDs.  The plan was to RAID0 for my OS drive.  Popped the drives into slot 1 and 2 and booted up to the same code loop:

DE, AD, A2, 21, 12, 33

I can not get into BIOS.

Install ONE drive into slot 3, no problem, any unit.

My present 128GB drive no problem windows boots.

Install either one of the new modules, no problem  (obviously no OS installed, but it will POST, BIOS sees the disk and lists the make/model)

I have pulled the ol' BIOS reset... no change.

I have un-plugged the SATA drives, no change.

I have tried every combination of M.2 modules in every available slot, no change.

System does not seem to care about the exact M.2 plugged in, just where (i.e. ONLY M.2_3!!!)

ASRock, please support,  I can post details where needed.

I was not aware this was a user only forum.  Thanks for informing me. 

The computer does not boot if any module is in slots 1 or 2.  (W10 SSD must be in slot 3)  New drives are seen only if installed in 3, nothing in 1 or 2.

I guess I could individually install the new 500GB modules in slot 3, boot via live USB drive, GPT and format... after doing that for each, install all three and see what happens.  *shrug*

I'll submit a ticket with tech support so that they are at lease aware of the issue.

To me, installing drives does not seem like something that should cause a boot failure.  That said; new, new stuff we have here, bound to be some hiccups along the way. 

in my configuration before 1.7 the sata m2 ssd worked in all slots. in bios 1.7 the sata ssd works only in slot 3. in slot 1 and 2 i have real nvme ssd´s and they work fine there.

free-eagle, I have not used any other version than 1.7.  Thank you for following up with your experience.  I would try to downgrade, but I have some work that needs to be done. 

 I'll update if I can get my hands on a true PCIE SSD.

FYI, I did open a ticket with ASRock, very quick to respond.  They obviously want me to, unplug all, clear CMOS, re-seat...  if this does not work,  they are already proposing an RMA... but from what I see,  it feels like  a BIOS issue, not my particular board.  I'll update as we move forward.

The issue only seems to apply to SATA m.2 drives, i have multiple 2.5 sata devices plugged in just fine.

Of course, I can't have secure boot enabled with the amd raid... windows says rcbottom.sys fails digital signature check.

PS: Don't install the samsung NVMe driver if you use samsung nvme drives and the amd raid, it might completely screw your install... it did mine.

I installed two new PCIe SSDs in slots 1 and 2.  I was able to boot with out issue.

I built a RAID 0 array with both and installed windows.

Ran this configuration with and without a SATA SSD in slot 3. No problem either way.

Currently running the RAID 0 in 1 and 2 with slot 3 open.  I also have a RAID 0 array with two seagate 3TB drive, a standalone 2TB disk and a standalone 2.5" 256GB SATA SSD.

To me this confirms the SATA vs. NVMe and issues with BIOS 1.7.

I can't afford to have my system down for an RMA, I will discuss further with tech support.  

1900x Threadripper /399 Taichi board, 2x crucial sata M.2 drives, 2x rx580 GPUs in crossfire