Windows Recovery bootloop on NVMe RAID

[JCRM]

Hey Everyone, I've been lurking for a long time, and usually can fix issues on my own with some Googling, or just figuring it out. But I'm officially in over my head on this one.
I'm running a Ryzen 1700 on an Asus B450 F Gaming motherboard, with 1TB NVMe drives installed. The drives do not match, they are different brands and models. (I know this isn't best practice.)

I have been running an NVMe RAID for my Windows 10 install for a few months now. I had issues before with the system not rebooting properly during updates, but (I believe) this was caused by me not finishing the setup of the RAID properly. However today I restarted my machine to attempt to fix an issues, and it would not boot into the normal Windows environment. It would only boot into Recovery. I tried a few things that didn't work, and disabled recovery so I could get to a bluescreen and find an error.

File: \Windows\system32\ntoskrnl.exe
Error Code 0xc0000221

That's what I got. So it would seem that the Windows kernal has become corrupted somehow. I've tried a medley of things, but I'm too fried to remember all of them right now, and none of them worked. The machine was working fine for the last week through a Windows update, and a couple of other restarts. Any help with this is appreciated.

[TrigrH]

When you setup RAID and do literally everything wrong, shit like this happens.

 

Stop using raid.

[JCRM]

40 minutes ago, TrigrH said:

When you setup RAID and do literally everything wrong, shit like this happens.

 

Stop using raid.

Would you like to explain what I did wrong to help me then? I read up and watched videos on how to set it up, and it was running fine up until I restarted it myself. I also back up everything to a NAS, so I'm not too concerned with data loss on this computer.

[TrigrH]

26 minutes ago, JCRM said:

Would you like to explain what I did wrong to help me then? I read up and watched videos on how to set it up, and it was running fine up until I restarted it myself. I also back up everything to a NAS, so I'm not too concerned with data loss on this computer.

 

3 hours ago, JCRM said:

Hey Everyone, I've been lurking for a long time, and usually can fix issues on my own with some Googling, or just figuring it out. But I'm officially in over my head on this one.
I'm running a Ryzen 1700 on an Asus B450 F Gaming motherboard, with 1TB NVMe drives installed. The drives do not match, they are different brands and models. (I know this isn't best practice.)

I have been running an NVMe RAID for my Windows 10 install for a few months now. I had issues before with the system not rebooting properly during updates, but (I believe) this was caused by me not finishing the setup of the RAID properly. However today I restarted my machine to attempt to fix an issues, and it would not boot into the normal Windows environment. It would only boot into Recovery. I tried a few things that didn't work, and disabled recovery so I could get to a bluescreen and find an error.

File: \Windows\system32\ntoskrnl.exe
Error Code 0xc0000221

That's what I got. So it would seem that the Windows kernal has become corrupted somehow. I've tried a medley of things, but I'm too fried to remember all of them right now, and none of them worked. The machine was working fine for the last week through a Windows update, and a couple of other restarts. Any help with this is appreciated.

Onboard AMD chipset for NVME raid is not reliable.

You didn't finish the setup properly according to you.

The drives don't match.

 

There is almost ZERO advantage to nvme raid anyway since the drives are already fast.

 

raid 1 or 0?

[JCRM]

32 minutes ago, TrigrH said:

 

Onboard AMD chipset for NVME raid is not reliable.

You didn't finish the setup properly according to you.

The drives don't match.

 

There is almost ZERO advantage to nvme raid anyway since the drives are already fast.

 

raid 1 or 0?

I wasn't aware of the unreliability. I've seen users with it, and didn't see or hear of any issues like mine. Maybe it's my bad luck, or their good luck. It's possible I didn't dig deep enough.
That was the first install I did while I was learning to make it work. I had done it fully and properly most recently.
If the non-matching drives are THE issue behind this, then I'll fix that. I was looking to see if there was anything else to be done.

I was going to use JBOD because of the small advantages in most tasks, and just expand my storage, however I wanted to try RAID 0 because it does have an improvement in my workflow. Not a huge one, but its a bit. Plus I knew I wouldn't be losing data, because it wasn't being permanently stored on the array.

[TrigrH]

3 minutes ago, JCRM said:

I wasn't aware of the unreliability. I've seen users with it, and didn't see or hear of any issues like mine. Maybe it's my bad luck, or their good luck. It's possible I didn't dig deep enough.
That was the first install I did while I was learning to make it work. I had done it fully and properly most recently.
If the non-matching drives are THE issue behind this, then I'll fix that. I was looking to see if there was anything else to be done.

I was going to use JBOD because of the small advantages in most tasks, and just expand my storage, however I wanted to try RAID 0 because it does have an improvement in my workflow. Not a huge one, but its a bit. Plus I knew I wouldn't be losing data, because it wasn't being permanently stored on the array.

I would clear and go back to JBOD.