the stack, below, is sorted in First in, last out order, which means the things on top happened after the ones below
Error 1 (just a portion)
ffffc28874b255a0 fffff806
5c240fe5 : 0000000000000000 ffffc288
74b257c0 ffffc807d94661a0 ffffc807
d9457de0 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
ffffc28874b25600 fffff806
5c23a450 : 0000000000000000 ffffc807
d94661a0 ffffc807d946b1a0 00000000
00000000 : storport!StorpWheaReportError+0x9d
ffffc28874b25690 fffff806
5c220b90 : fffff80659d24440 00000000
00000000 0000000000000000 00000000
00000001 : storport!StorpMarkDeviceFailed+0x358
ffffc28874b25920 fffff806
5c1cc9c6 : ffffc807d9421020 ffffc807
d9421020 0000000000000000 00000000
00000000 : storport!StorPortNotification+0x139a0
ffffc28874b259f0 fffff806
5c1cd1c4 : ffffc807d9421020 ffffc807
c1000002 ffffc807ee6f8100 00000000
00000003 : stornvme!NVMeControllerInitPart2+0x226
now just ignore all the codes and just look at the text at the end.
that too me looks like its the nvme, even though its passing the tests
Error 2( very similar)
fffff5051a64c570 fffff800
54bb60a5 : 0000000000000000 00000000
00000062 ffffba0359bb9710 ffffba03
55075000 : nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
fffff5051a64c5a0 fffff800
56840fe5 : 0000000000000000 fffff505
1a64c7c0 ffffba034a2651a0 ffffba03
4a258de0 : nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
fffff5051a64c600 fffff800
5683a450 : 0000000000000000 ffffba03
4a2651a0 ffffba034a26a1a0 00000000
00000000 : storport!StorpWheaReportError+0x9d
fffff5051a64c690 fffff800
56820b90 : fffff80055324440 00000000
00000000 0000000000000000 00000000
00000001 : storport!StorpMarkDeviceFailed+0x358
fffff5051a64c920 fffff800
567cc9c6 : ffffba034a213020 ffffba03
4a213020 0000000000000000 00000000
00000000 : storport!StorPortNotification+0x139a0
fffff5051a64c9f0 fffff800
567cd1c4 : ffffba034a213020 ffffba03
c1000002 ffffba03553ffe00 00000000
00000003 : stornvme!NVMeControllerInitPart2+0x226
fffff5051a64ca70 fffff800
567cc0bf : ffffba034a213020 ffffba03
4a265050 ffffba03553ffee0 ffffcc00
0c000180 : stornvme!NVMeControllerReset+0x124
they are pretty much same thing, the NVME controller seems to be causing the problem. The controller is on the NVME. I don't know if the WD software would see a bad controller
Now lets look at software.
Update your bios, you on F11 and there are 4 since though 2 are just updates to let motherboard use more CPU. Might still help.
install newest chipset driver
nvme looked after by CPU so not any software I can offer.