1 Solution
Ah, that type of configuration (OS Boot driver outside of array + Raid) was not supported and could explain your issues if you used the wrong drivers. Try using these Chipset/Raid drivers.
Yup. They seem to be pretty crappy 
amdmatt I've registered just to report that I'm also seeing the same issue.
Windows is installed on a RAID0 NVMe array, it boots fine but when shutting down or restarting has to be powered off manually.
I don't know if it's related or not, but I could not get the boot drivers to work on Windows 10 1809, I had to use an 1803 image or the drivers hung during loading. Once Windows was installed, it picked up RAID drives no problem.
Here's my current setup:
I installed 1803 from scratch on the RAID array, my EFS boot partition is on the same array. Using the current latest drivers, 9.2.0.70 (SATA and NVMe RAID) on a Gigabyte Auros Xtrreme with a TR 2950x.
The 3rd NVMe slot is populated with a drive that's NOT in RAID.
Additionally, I have 1x 4TB HDD and 1x SATA SSD, also not in RAID.
Is there any other information I can give that would help diagnose the fault? Any log files or anything I can supply?
I appreciate that a couple of the drives are in "legacy" mode, but these aren't boot drives at all. That shouldn't affect things?
amdmatt Good news! I have resolved the issue thanks to your help.
For reference, here's what my configuration looks like now:
Better still, I did _not_ have to reinstall Windows! You're correct, I couldn't just rearrange the RAID volumes as there's no way of doing it either through the BIOS or via RaidXpert (Is that something that would be possible in a feature update? It would certainly make fixing this issue much easier)!.
What I had to do was delete Array 1 and 2 (deleting all data in the process....), reboot into the BIOS and recreate them there, which brought the previous Array 3 (my boot array) to position 1. Deleting and recreating them via RaidXpert would retain their previous Array Id's, so this needed to be done via the BIOS.
After rebooting again and updating to the latest drivers just to be safe, I have successfully shut down without having to do a hard power off!
Thank you again for your help with this issue, I'd never have figured it out.
Here's my array order. I was looking in BIOS for the feature to swap arrays to re-arrange them again just to be on the safe side and that feature is missing unless I am looking in the wrong place. The User Guide is pretty poorly written so it's quite hard to follow it.
Yes I could not find that feature either inside the Zenith. I think that feature is mostly available on our internal motherboards which is what motherboard manufacturer's base their designs off.
believe RaidXpert2 lists the arrays in the order they were created. Here is what my configuration looks like.
From looking at your screenshot everything looks okay. Perhaps in your case something is not setup correctly in the BIOS. If you are using an adapter card to fit 4x nVME drives inside, did you set up the PCI-E lanes option in the BIOS correctly?
In your case I would ask MSI to try and reproduce your issue and provide them with clear and detailed reproduction steps using identical hardware one by one that they can follow.
I don't think disk management reveals anything useful as it appears as though mine is in the wrong order with my Boot drive showing last in the list.
Negative ghost rider 
Same behavior.
Can you try uninstalling the PCI Driver? Follow these steps to do it.
Select Modify.
Uncheck everything apart from AMD PCI Device Driver, restart system.
Test.
Negative ghost rider
