Solved

ASUS Z-170P Motherboard behaving oddly with MyDigitalSSD 480GB BPX m.2 SSD

I have an ASUS Z-170P motherboard with a MyDigitalSSD 480GB BPX m.2 SSD. I also have a Mushkin Reactor 1 TB SATA SSD, two Western Digital 1 TB SATA hard drives and a SATA DVD writer.

I installed Windows 10 on the m.2 drive from a USB flash drive and, upon starting Windows, saw that the SATA SSD drive (the Mushkin) with all my data wasn't visible in File Explorer. After some troubleshooting, I went into Windows Disk Management and found the drive without a letter assigned. I re-lettered all my drives and that brought my data drive back in File Explorer. But the strangeness didn't end there.

Every time I booted up, the system would take me to a screen where I would choose Windows 10 or some blank entry that I suppose the system thought was bootable. I went into Windows' advanced system configuration to turn off the dual-boot option. This hadn't happened with previous Windows installations.

Finally, I noticed that, in the BIOS, the boot drive was listed as the Mushkin drive, even though the OS was on the m.2 drive and the system presumably was booting from that drive since it was the only one with an OS installed. When I set the hard drive priority to make the m.2 drive (BPX) the first boot option, however, I got into a loop where rebooting would take me back into the BIOS. It was only upon changing the boot option back to the Mushkin drive that it booted into Windows. I should also note that the OS Type under Secure Boot has to be set on "Other OS" rather than Windows UEFI.

One other observation - the m.2 drive has a single boot partition, and none of the other partitions I've come to expect on the boot drive.

What's going on and can I fix it? Everything is working but I'm not convinced it's configured optimally.
3 answers Last reply Best Answer
More about asus 170p motherboard behaving oddly mydigitalssd 480gb bpx ssd
  1. Best answer
    Your boot partition is still on the Mushkin drive. If you look at that drives partitions using a partition manager you should see the small boot partition, it will be 500MB or smaller most of the time. This partition needs to be on the m.2 and that can be done albeit not without a lot of messing around.
    If I were you I would remove all drives except the m.2 and start over. This will install the boot partition on the m.2 and after you get Windows up and running you can add the other drives back in.
  2. BadAsAl said:
    Your boot partition is still on the Mushkin drive. If you look at that drives partitions using a partition manager you should see the small boot partition, it will be 500MB or smaller most of the time. This partition needs to be on the m.2 and that can be done albeit not without a lot of messing around.
    If I were you I would remove all drives except the m.2 and start over. This will install the boot partition on the m.2 and after you get Windows up and running you can add the other drives back in.


    Your solution was right on the money. I didn't have a visible boot partition on the Mushkin drive, but it was an active partition and the MyDigitalSSD drive was not. I tried to make the m.2 drive active and rebuild the boot files on it using my Windows 10 USB recovery stick, but that didn't work. I ended up doing just as you suggested, removing all drives but the m.2 drive and starting over. The m.2 drive now has the partitions I would expect to see (recovery partition, EFI system partition and the primary partition), I'm booting from the m.2 drive, and everything in the BIOS is working as it's supposed to, even the Secure Boot setting (Windows UEFI).

    Thanks for your help!
  3. Glad to help and glad you got it working!
Ask a new question

Read More

Asus SSD Windows Motherboards