Okay, so let's try to figure out what's going on here. The user has a Ryzen 7 5800X3D on an ASUS TUF B550 Plus Wifi II motherboard. They're experiencing an issue where the WD Black SN810 NVMe drive isn't detected in the M.2_2 slot during cold boots, but works after a warm boot. The TeamGroup Cardea works fine in both slots. The user is considering buying a new motherboard or NVMe drive to fix this.
First, I need to recap the problem. The WD drive doesn't get detected in M.2_2 on cold boot, but works in M.2_1. The TeamGroup works in both. This started after upgrading to the 5800X3D from a 5600X, which didn't have this issue. They've tried a lot of fixes: BIOS updates, CMOS resets, swapping drives, adjusting PCIe settings, etc., but nothing worked.
The key points here are:
1. The issue is specific to the WD Black in M.2_2 slot during cold boots.
2. The TeamGroup works in both slots regardless.
3. The problem arose after switching to the 5800X3D.
So why is this happening? The M.2_2 slot is connected to the B550 chipset, not the CPU. The 5800X3D's 3D V-Cache might be causing timing issues during initialization. The WD drive's firmware might not handle the delay introduced by the cache, leading to detection failures. The TeamGroup's firmware is more tolerant, so it works.
The user is considering buying a new motherboard (X570) or a new NVMe drive. Let's evaluate both options.
For a new motherboard, the X570 might have better chipset handling and more PCIe lanes, possibly resolving the detection issue. However, X570 boards with dual CPU-connected M.2 slots (like the MSI MEG X570 Unify) would bypass the chipset entirely for both drives, eliminating the problem. But this is a costly solution.
Replacing the WD drive with another NVMe (like Samsung 980 Pro) could work if the new drive's firmware handles the initialization better. This is cheaper but not guaranteed.
Alternatively, using the WD in M.2_1 and TeamGroup in M.2_2 is a viable workaround without spending money. Since the user's main issue is cold boot detection, and the WD works in M.2_1, this setup would be stable.
The user might also want to check for firmware updates for the WD drive, though OEM drives often have limited updates. Pressuring ASUS for a BIOS update that addresses 5800X3D compatibility could be another avenue.
In summary, the problem is likely a firmware/BIOS incompatibility between the 5800X3D, B550 chipset, and WD drive's initialization timing. The solutions are: use the current setup with drives in compatible slots, replace the WD drive, or upgrade to an X570 motherboard for better compatibility.
-DeepSeek
A decent 2TB nvme drive cost the same as a new motherboard AM4 B550 chipset
