07-08-2018 10:54 PM
SSD: MX500 500GB SSD M.2
Motherboard: Gigabyte Z370xp SLI
I purchased the MX500 500GB SSD through Amazon. I installed it on my motherboard, however it is not being recognized in the BIOS or in windows. Ive tried multiple times to reseat it with no luck. I've also tried it with just the SSD and no other sata connections, still no luck. At this point i dont know what to do. There is also a red light on the SSD when my PC is on; im not sure what that means. Also, I checked the list of supported motherboards and my motherboard is on it.
Probably going to send it back at this point...
Solved! Go to Solution.
07-08-2018 11:18 PM
According to the board specs - it should support it. Check you have the latest BIOS for the board. And see if there's a BIOS option to toggle between sata and pci on the m.2 slot. If there is - it wants to be sata for this drive model. There may not be an option - it may be automatic.
07-09-2018 12:43 AM
Note there are two M.2 connectors on your mobo but only one (labelled M2P_32G) can support your MX500 M.2 drive. I think it is the M.2 connector closer to CPU. Did you connect your drive to this connector?
The M2P_32G connector shares bandwidth with the SATA3 0 connector so make sure you do not connect other drive to SATA 3 0 connector.
07-09-2018 09:56 AM
I'm so confused. The website for the motherboard said it was supposed to go to the bottom so i didnt even think about trying the top one. Your comment made me try it anyways and it worked! Thanks so much
07-10-2018 12:49 AM
08-07-2018 11:52 AM
Having a similar issue on the Gigabyte H370M DS3H, the drive displays a red status LED regardless of which slot is used, and the BIOS does not recognize it. All other SATA devices are unplugged, and I took this drive home to test in my home machine (this is my bosses SSD) and it showed up perfectly and without any status LEDs (MSI Z97 MPower MAX AC). The drive was tested on two separate H370M boards (boss originally bought this for his new home machine, and realized he'd used the same board for a work machine) and the result is the same on both. Crucial's compatability checker says it's compatible, but I have a feeling there is something not right with this model of motherboard given the circumstances. Both boards are on the current BIOS revision. Resetting to defaults as well as removing from power, pulling the CR2032, and shorting the CMOS clear jumper did not help.
At this point I'm not sure there is anything Crucial can do, the drive is proven to be functional from my testing, but it might be good to do further testing on this board and possibly remove it from the compatability list or change its status if Gigabyte's implementation doesn't work. Any further ideas as to some otherwise unobvious BIOS setting which might magically make this work would be great though.
08-08-2018 09:11 PM
@Ryan_O If you have tried targetbsp & bogdan's suggestions above, then I would just go through all of the BIOS settings looking for anything that might affect the M.2 & SATA. Sometimes default settings do leave things disabled or in an improper state for some hardware. Unfortunately I'm not familiar with Gigabyte boards or the newer non-OEM BIOS settings available.
If you cannot find a solution, I would contact Crucial Support directly and let them know about the incompatibility in case they have any ideas. Also you should be able to return it for a refund if they are unable to help you get it working on the Gigabyte board. While Crucial does monitor these forums a post can sometimes be overlooked.