Your weird BSoD startup errors could mean a dozen different things, all caused by Windows halting after not finding system components where it expects them to be. And especially when multi-drive RAIDs, JBODs, or Microsoft's drive spanning is used. Especially when Windows boots and runs from (at least) one of the drives being moved. Just saying that (at least as of Win7/8/10) you can't always expect things to play nice when you move your drive hardware around. Not helped by the fact that Windows also creates an extra (hidden) partition, Recycle Bins and System Volume Information (and other) system folders onto each drive, etc etc. Windows often makes things blurred and complex when swapping drives around from port to port, it puts physical drive IDs and logical drive IDs and all sorts of (permanent or session) tables and boot data onto boot records.

I have 5 SSD's, 2 HDD's hooked up to the motherboard, I have always connected the drives from the top to bottom orientation on the SATA ports.ĭo all of your drives have active bootable system partitions? Chances are that you've installed your WinOS on one bootable system ( C: ) drive and Windows then automatically configured/mounted all other drives as non-system storage disks. SSD Boot drive: Samsung EVO 960 NVMe 500gb Is this an issue which can be resolved via new BIOS drivers? or is this a hardware issue?

I've restart my computer several times, and have not had any further issues.

No other changes were done except for this.

I then switched the orientation of the SATA connections to be from bottom to top.

I tested each drive 1 by 1, and same issue as it seemed like a hard drive issue.

It seems when I have the drives connected in this way, I'll get a BSOD on startup, Startup failed or freezing load screen.

I have 5 SSD's, 2 HDD's hooked up to the motherboard, I have always connected the drives from the top to bottom orientation on the SATA ports.

There is an issue with the 10 SATA connections, I'm not sure if this is just me, but I've spent 3 hours testing.

Discovered an issue with the Rampage V Edition 10 motherboard.

Download rog rampage v edition 10