The one dump file you uploaded and the only BSOD in your System log (since 11th March 2023) is a 0x124 WHEA_UNCORRECTABLE_ERROR, indicating a hardware error. Sometimes bad or missing drivers can trigger this BSOD, as can out of date firmware.
In the dump the call stack gives a good clue to the source of your problem...
[code]
4: kd> knL
# Child-SP RetAddr Call Site
00 ffffb98f`b12de488 fffff801`509b8a4c nt!KeBugCheckEx
01 ffffb98f`b12de490 fffff801`509b95a9 nt!WheaReportHwError+0x3ec
02 ffffb98f`b12de570 fffff801`509b96c5 nt!WheaHwErrorReportSubmitDeviceDriver+0xe9
03 ffffb98f`b12de5a0 fffff801`554037b1 nt!WheaReportFatalHwErrorDeviceDriverEx+0xf5
04 ffffb98f`b12de600 fffff801`553fcb80 storport!StorpWheaReportError+0x9d
05 ffffb98f`b12de690 fffff801`553cf07c storport!StorpMarkDeviceFailed+0x358
06 ffffb98f`b12de920 fffff801`5548edb6 storport!StorPortNotification+0x91c
07 ffffb98f`b12de9f0 fffff801`5548f574 stornvme!NVMeControllerInitPart2+0x226
08 ffffb98f`b12dea70 fffff801`5548e4af stornvme!NVMeControllerReset+0x124
09 ffffb98f`b12deaa0 fffff801`553fa275 stornvme!NVMeControllerAsyncResetWorker+0x3f
0a ffffb98f`b12dead0 fffff801`50607df5 storport!StorPortWorkItemRoutine+0x45
0b ffffb98f`b12deb00 fffff801`506bdef5 nt!IopProcessWorkItem+0x135
0c ffffb98f`b12deb70 fffff801`50655485 nt!ExpWorkerThread+0x105
0d ffffb98f`b12dec10 fffff801`50802d48 nt!PspSystemThreadStartup+0x55
0e ffffb98f`b12dec60 00000000`00000000 nt!KiStartSystemThread+0x28
[/code]
You can see calls to the storport.sys driver, which is the Windows high-level storage driver. You can also see calls to the stornvme.sys driver, this is the Windows NVMe storage driver. Neither of these drivers will be at fault however, because they are Windows drivers.
You can see that things start to go awry during the three calls to stornvme.sys (notice the call to stornvme!NVMeControllerReset, probably to reset the drive controller after some sort of error). Following these stornvme.sys calls we again see storport.sys being called to mark the device as failed and initiate the bugcheck (notice the call to storport!StorpMarkDeviceFailed).
It thus seems most likely that there has been a failure of some sort accessing your NVMe drive (the Samsung 970 Pro). Sometimes (in my experience) M.2 drive issues can be fixed by removing and re-seating the drive, so I'd try that first. If that doesn't help then download Samsung Magician and see whether there is a recent Samsung driver for that 970 Pro. You might also look for a firmware update to the 970 Pro within Samsung Magician too.
