Hello, and welcome to the forum!
Taking all five dumps in the upload together, there is a strong indication that this is a hardware problem and most likely RAM. The bugcheck codes are different in each BSOD, the operation that was in progress is different, and, more importantly, there are no third-party drivers referenced in any of the dumps. That's a strong indication that this is most probably a hardware problem. In addition, some of the dumps fail with 0xC000005 exceptions (invalid memory reference) in Microsoft functions. Another fails with a 0xC000001D exception code (invalid opcode) caused by a misaligned instruction pointer. One dump has a check image failure, indicating a corruption in an executable image (win32kfull.exe)...
Code:
CHKIMG_EXTENSION: !chkimg -lo 50 -d !win32kfull
fffff09deb14d630-fffff09deb14d65d 46 bytes - win32kfull!xxxMNCanClose+e0
[ a0 48 8b 45 a0 ff 40 08:40 55 53 56 57 41 54 41 ]
fffff09deb14d66a-fffff09deb14d672 9 bytes - win32kfull!xxxMNCanClose+11a (+0x3a)
......
fffff09deb21decf-fffff09deb21dedf 17 bytes - win32kfull!GreRectangle+3f3 (+0x32)
[ 00 00 66 0f 6e 44 24 68:48 8b 44 24 78 49 8b cf ]
WARNING: !chkimg output was truncated to 50 lines. Invoke !chkimg without '-lo [num_lines]' to view entire output.
fffff09deb45674a-fffff09deb45674b 2 bytes - win32kfull!TraceLoggingRegisterEx_EtwRegister_EtwSetInformation+82
[ c2 88:32 94 ]
fffff09deb4567c7-fffff09deb4567c8 2 bytes - win32kfull!CreateTlgAggregateSession+5f (+0x7d)
[ f5 e4:75 f2 ]
fffff09deb456eda-fffff09deb456edb 2 bytes - win32kfull!PlaySoundPostMessage+9de (+0x713)
[ b2 21:62 25 ]
2354 errors : !win32kfull (fffff09deb14d630-fffff09deb456edb)
I would suggest that firstly you should test your RAM thoroughly...
- Download Memtest86 (free), use the imageUSB.exe tool extracted from the download to make a bootable USB drive containing Memtest86 (1GB is plenty big enough). Do this on a different PC if you can, because you can't fully trust yours at the moment.
- Then boot that USB drive on your PC, Memtest86 will start running as soon as it boots.
- If no errors have been found after the four iterations of the 13 different tests that the free version does, then restart Memtest86 and do another four iterations. Even a single bit error is a failure.
Let us know how that goes.