BSOD followed by NVME issues, plus M.2 drives missing from BIOS setup
BSOD followed by NVME issues, plus M.2 drives missing from BIOS setup
Everything had been operating well for a couple of years on my machine until this evening. I observed it restarting, suspecting a Windows update (even though I had postponed it until July 7, but it wasn’t the first time Microsoft ignored that). Later, it restarted again after about five minutes of operation. I checked the monitor, closed unnecessary programs to see if they were causing the issue, but then encountered a BSOD with WHEA_UNCORRECTABLE_ERROR. A quick search revealed the problem was hardware-related, not software. I dismissed the PSU, GPU, and RAM as possibilities since I was saving files at that time; the NVME drive (Gigabyte AORUS NVMe Gen4 M.2 1TB) was already at full capacity before the backup started, then it froze completely and triggered the same error. When I accessed the error log, it confirmed a drive fault rather than a software glitch. After another reboot, the BIOS no longer recognized the NVME, and I turned off the system. Once calm, I restarted and it worked again. I continued trying to retrieve logs and files, but kept hitting the BSOD with the same error and full usage warning. Eventually, after several attempts, the drive disappeared entirely from the BIOS—even when I left it off or rebooted. I removed the M.2 WiFi card to test, but it still wouldn’t appear. I attempted a reset of the CMOS, but nothing changed. My two HDDs were always listed in the BIOS.
WHEA refers to problems with the CPU or PCIe components. In today’s systems, the most frequent cause is a faulty NVMe SSD. It doesn’t distinguish between a defective M.2 port/board and the actual drive, but a failing SSD is significantly more likely. Have you experienced this problem after swapping out all NVMe drives? If yes, it suggests the port or board might be the issue due to missing detection of drives.
I first considered the NVME unit but later realized the M.2 SATA model should have been recognized by the BIOS, yet it wasn’t. It’s tough to tell if the M.2 WiFi card is being picked up or not. I attempted a temporary Windows install on an external drive for more testing—though setting up a bootable USB on a Mac proved challenging—but eventually gave in and went to sleep. Now I’m trying to complete the installation of the temporary drive to verify system stability and check if the M.2 WiFi card functions. I’m also hoping to find a new motherboard at my local PC store, since only one is available, and suspect the problem might lie with the board itself.
The nearby PC shop operates just four days a week. I’m considering purchasing an NVME device to test its functionality. If successful, the problem would stem from a drive failure, as I’ve confirmed the M.2 SATA in BIOS and tried multiple approaches—disconnecting both HDDs—and only the bottom slot functions properly. I’ll buy an NVME drive tomorrow after work and let you know the outcome.
Edit: I turned on XMP for RAM, reinstalled the M.2 WiFi card (likely sharing the same lane as the NVME slot), reinstalled the other two HDDs, and everything worked fine. No GPU issues either; it seems the issue is more likely with the NVME slot itself rather than the motherboard or CPU. I also installed Windows on a spare 500GB HDD, but realized how much slower they are compared to the suspected failing NVME drive.
Collected a Crucial P3 1TB PCIe 3 NVMe, verified the motherboard recognized it in the NVMe port, which means Windows 10 is installed. It seems the Gigabyte AORUS NVMe Gen4 M.2 1TB failed after about two years and five months of continuous use. The replacement drive runs roughly half the speed (3,500 MB/s compared to the old one’s 7,000 MB/s) and will remain functional until I locate a more stable PCIe 4 NVMe unit. Upgrading was expensive—around AU$135—but it was necessary. Online price was AU$97 (including shipping), but delivery would take days. In February 2021, the original model cost AU$265! That’s a big difference. Edit: I bought an external NVMe case, but both Windows and macOS don’t list it; only the two chips near the slot appear hot, while the others stay cool—confirming failure.