System frozen in RAID configuration.
System frozen in RAID configuration.
Hello. I'm just starting out here and I'm facing an issue I can't resolve. I recently purchased a new PC and from the beginning I've encountered a problem. I upgraded my old SATA SSD to an NVMe drive. After installing it, I followed the usual steps to set up Windows and rebooted the system. However, the drive isn't recognized as a bootable device and displays an error code in the blue screen that doesn't provide any solution. My PC specs are: CPU 7600X, M.2 slot, gigabyte B650M, B650M K Rev 1.1, NVMe model Western Digital SN770 1TB. Regarding my attempts and to save time, I've checked several things: - Verified the drive is AHCI mode, NVMe RAID disabled in BIOS - Tried Windows setup with only the NVMe connected - Used different Windows versions - In the software dashboard (Western Digital), the drive appears in RAID mode and works fine as a secondary drive - Swapped the two SATA slots on the motherboard; no manual mentions that occupying an NVMe slot makes other SATA ports unusable - From RaidXpert2, it doesn't recognize the NVMe as a raid device unless NvMe RAID is enabled I'm curious about what 'legacy' means in the information from RaidXpert2. All recent updates are handled by the chipset and BIOS, but I can't recall any settings well enough. Thanks to anyone who can assist. Also, a friend recommended a low-level format for the disk. Is this helpful?
Depends on your hardware configuration. Your mobile device only has the M key slot, similar to the B450 model, and if your SSD uses a B+M slot, it won’t work. Both need matching keying. NVMe drives typically can’t boot directly from OS discs, especially on lower-end models—you’d need a SATA SSD to install the operating system. Use AHCI settings. SATA ports are usually managed by the chipset, so they shouldn’t be an issue unless you’ve disabled them in BIOS. The older listings apply mainly to past technologies or revisions. Knowing your exact make and model would help provide a more precise solution. Are you aiming to boot the NVMe drive directly?
Make sure the drive is bootable with an OS installed. Avoid using RAID configurations. Provide details about the specific model and version of your devices. Confirm if you have any error messages or unusual behavior. Let me know if you need further help.
This actually provides a very useful clue—it aligns perfectly with my understanding. A straightforward method to figure out whether you're working with legacy or UEFI is by checking how many partitions the installer generated. MBR usually creates two, while UEFI typically creates three. Of course, it's not a strict rule, but it's easy to verify. Various factors can influence this, but immediately after installing Windows, it helps narrow down the likely reasons.
Great question! Just to confirm, you're asking about a situation where there might have been two partitions, and you're unsure if this is related to a problem. You also mentioned trying some conversion steps to GPT but they didn't help. Let me know if you'd like further clarification!
I suggest using the Windows Media utility to download the ISO file alone. Then apply a tool such as Rufus to generate the UEFI boot image. The problem with employing the Windows Media tool for boot image creation is that it may produce a legacy boot device when used on an older system and vice versa.
The configurations are set up using the media tool. I removed the divisions first, then started the drive by clicking "new" during setup, which created partitions and allowed me to install Windows in the main partition. The USB drive includes the newest Windows version. Do you think it treats a brand-new PC as outdated? Anyway, your assistance was very helpful—I'll try Rufus and share the outcome. Thanks!