I recently demoted my FW16 (gen1) to being a desktop-replacement device as it was much too heavy to keep hauling everywhere after over a year of doing so and replaced it with a FW13 with the HX370 of the current gen.
The FW16 has a 2TB WD black in it for which I have had ZERO issues.
I have had the FW13 for less then 2 months and it has a Samsung 990EVO and I have issues.
Every few days windows is complaining it wants to ‘repair my drive on next reboot’ and after it does it will be fine for maybe a day or 3, then it does it again.
Also (and I think this maybe related to the BIOS as a FW13 BIOS update note specifically said it addresses a ‘no boot device issue’ with opal drives; I have not been able to determine if the Samsung Evo 990 is OPAL or not), 3 weeks ago I set my working laptop to the side and went to the kitchen and upon returning I was staring at a QR code from the bios saying no boot drive present.
Made the mistake of following some microsoft guide that started with bootrec /fixmbr which marked the drive as a MBR drive instead of gpt which turned a 30min fix (when I found the resolution into a multi hour ordeal. Eventually Easeus Partition Master from Hirens bootcd said my partitions were ‘lost’ (presumably the partition table got deleted somehow); but could be restored.
After it restored all the partitions the MBR vs GPT issue came to light when I could not mark partition1 as a efi system partition, and all of the like 3 or 4 different commands to convert mbr to gpt failed… I wound up taking my newly restored windows partition and backing it up off device and then having the windows installation disk format everything back from scratch, then put the windows partition I backed up back in place (with a little bcdedit /set commands to fix some errors around the boot entries not lining up right)…
AFTER that ordeal I went looking in the event viewer to try and figure out WTH even happened and the last log recorded before it went offline was ‘event id 129 stornvme device reset’.
That error was happening every few minutes until I discovered and installed the bios/uefi update that mentioned the no boot device thing in its fix notes.
Now that error/event went from once a minute all day every day to being like 5 a day, so the situation is much improved, but I am at a loss for what else can be adjusted… short of buying a new drive that is not samsung (which I placed the amazon order for a WD drive a few hours ago, for this exact reason) and 30 minutes ago windows just complained about wanting to repair the drive again…
my understanding the only difference between the current gen FW13, and FW16 is the power envelope allowed by the cooling solutions and battery size, otherwise I believe it is the same chips in play, so my issues might be relevant to your query.
