My Crucial P3 1TB NVMe M.2 2280 SSD (CT1000P3SSD8E, firmware P9CR30A) suddenly disappeared from File Explorer while being used as a secondary D: drive in an ASUS ROG Strix G513QY laptop with a Ryzen 9 5980HX. The laptop had not been moved, and there were no crashes or other warning signs beforehand.
The SSD still appears in BIOS under NVMe Configuration, but it is identified only as a generic PCIe SSD and reports an NVMe size of 0.0GB. Windows Disk Management lists it as an unknown, uninitialized 1MB disk instead of showing its actual roughly 931GB capacity. PowerShell reports the same 1MB size, even though the disk appears online and healthy. CrystalDiskInfo reports 100% health, no SMART errors, and a normal temperature, but displays an obviously incorrect capacity of 4294967.2GB.
I reseated the module and tested it in both PCIe slots. The problem follows the SSD, so the laptop slots and connection seem fine. Installing the proper Micron NVMe driver did not change anything. Crucial Storage Executive crashes immediately, preventing me from checking for or applying a firmware update. I am not especially concerned about recovering the data; I mainly want to know whether the drive can be brought back.
Has anyone seen a Crucial P3 show 0.0GB in BIOS and 1MB in Windows while SMART still reports it as healthy? Is this something a firmware update can realistically fix, or does it indicate a failed controller? Is there any way to get Storage Executive working with a drive in this state?
1 Answer
That pattern usually means the SSD controller is failing or has lost access to the NAND, rather than being a Windows driver or partitioning problem. The system can still communicate with the controller well enough to report basic health information, but the controller is presenting an invalid or nearly empty namespace, which explains the 0GB BIOS reading, 1MB Windows disk, and bizarre CrystalDiskInfo capacity.
A firmware update is unlikely to work when the drive cannot report its real capacity, and forcing initialization or formatting would not repair the underlying issue. Since the problem followed the module through different slots, replacement or warranty service is the most realistic solution. The lack of a heatsink is not, by itself, enough to establish that overheating caused the failure; SSDs can fail without obvious temperature or SMART warnings.
Related Questions
Lenovo Thinkpad Stuck In Update Loop Install FilterDriverU2_Reload