One in two M.2 SSDs goes unnoticed by the system or Windows.
One in two M.2 SSDs goes unnoticed by the system or Windows.
Hello, yesterday I assembled a new PC. Most components are functioning properly except for my ›Samsung SSD 980 M.2 PCIe 3.0 x4 3D-NAND TLC‹ which isn’t recognized by my BIOS or Windows. I also have a SATA-SSD (SATA-Port 5) and another m.2-SSD from my previous setup, both of which are detected and operating fine at the moment. My specifications: OS – Windows 11 Pro (fully activated), CPU – Intel Core i7-12700F, Mainboard – Gigabyte Z690 UD DDR4 S1700 rev. 1.0, RAM – 32GB (2x16GB) Corsair Vengeance LPX schwarz DDR4-3600 DIMM, with XMP profile enabled, GPU – PowerColor Radeon RX 6950 XT, and Drives – 1TB Samsung SSD 980 M.2 PCIe 3.0 x4 3D-NAND TLC (MZ-V8V1T0BW) and a WD_BLACK SN750 500GB NVMe (working), plus a WD Blue SATA SSD 1TB (also working, OS installed). Power supply – 850 Watts quiet. I’ve saved screenshots from the BIOS for reference and can share more details if needed. Thank you for your support.
Have you experimented by exchanging the two M.2 drives in their respective slots?
I haven't attempted this yet since it's located directly beneath the GPU, which is quite large and difficult to remove. I'll consider it later if other solutions fail. @SamClan The red circle represents the Samsung 980 that isn't being recognized. The green one is the detected device that's functioning properly. The SATA-SSD is connected via SATA-Port 5.
Certain boards can encounter odd problems when multiple M.2 SSDs are added, as they rely on SATA connections. Make sure the M.2 slot has a red ring in the correct position. If not, try moving it to a different slot or re-seat it properly.
Focus on the specific configuration you're seeing. When reviewing NVME connections, it appears only the second M.2 SSD is displayed.
It seems you're referring to adjusting the PCIe version for each M.2 slot, ranging from 4.0 to 3.0. There may be related configuration options nearby.
I resolved the problem. The SSD was slightly misplaced, preventing the mainboard from recognizing it. @SamClan was correct. Thank you all for your assistance!