AMD Motherboards - Losing NVME raid after Win10 install

Print Page | Close Window

Losing NVME raid after Win10 install

Printed From: ASRock.com
Category: Technical Support
Forum Name: AMD Motherboards
Forum Description: Question about ASRock AMD motherboards
URL: https://forum.asrock.com/forum_posts.asp?TID=7546
Printed Date: 08 Sep 2025 at 7:53pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com

Topic: Losing NVME raid after Win10 install

Posted By: NorySS
Subject: Losing NVME raid after Win10 install
Date Posted: 03 Feb 2018 at 4:24am

Howdy All,

I had win10 working just fine, until recently. I got another Samsung 500GB NVME Pro to go along with the 2 500GB evos, I had in raid 0.

I installed it, deleted the array, and off I went to install windows 10. Unfortunately, afetr win10 restarts and says 'getting devices ready, need to restart' and setup stays stuck on the handoff to windows. Black screen with loading animation. All I have is acode A0 on the Dr Debug.

If I remove the USB drive, and just let it boot, it just boots to the UEFI. Wont book to anything else.

CPU: 1950X

Mobo: x399 Fatal1ty

RAM : 32GB Corsair

GPU: Titan Xp

NVME Drives: 500GB 960 Evo (x2), 512GB 960 Pro (x1)

Replies:

Posted By: MisterJ
Date Posted: 03 Feb 2018 at 4:33am

" rel="nofollow - There is not enough information to comment, NorySS. Please post all your specifications in your signature as I have. Tell us what you did after deleting the RAID0. Where were you installing W10? Enjoy, John.

-------------
Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD

Posted By: NorySS
Date Posted: 03 Feb 2018 at 4:50am

CPU: 1950X

Mobo: x399 Fatal1ty

RAM : 32GB Corsair

GPU: Titan Xp

NVME Drives: 500GB 960 Evo (x2), 512GB 960 Pro (x1)

after deleting the original array, I turned of the system, and I installed the new drive.

PS I just figured it out. I was booting in ultra fast, which is SUPPOSE to Disable CSM.

I turned off FASTboot, and disabled CSM manually.

It continuted with the setup.