Hello and welcome to TenForums
You are right it is not evident from the crash dumps whether a non-Microsoft driver is involved.
In these situations we usually assess if the variety of different bugchecks indicate possible hardware problems or we pursue the driver route by using driver verifier.
Code:
2019-03-13T16:23:24.457 The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffff860a5cdcd166, 0x0000000000000000, 0xfffff802788c71cc, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 39b7e4b4-5b92-4360-a332-c396b4f6228c.
2019-03-13T16:34:55.070 The computer has rebooted from a bugcheck. The bugcheck was: 0x0000003b (0x0000000080000003, 0xfffff80452431af1, 0xffffb385e80e1220, 0x0000000000000000). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 45e4c5b6-d03a-449d-836f-897ed3a41634.
2019-03-13T17:21:11.030 The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffc7094a8ef30c, 0x0000000000000000, 0xfffff8037957da51, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 0cb293b1-ed47-4c16-a99a-6cf9d0d88337.
2019-03-13T18:35:02.120 The computer has rebooted from a bugcheck. The bugcheck was: 0x000000d1 (0x000000000000000f, 0x0000000000000002, 0x0000000000000000, 0xfffff8075402ec0b). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 176592c1-e479-46b6-82c7-b95f45c16fc0.
2019-03-13T19:36:18.531 The computer has rebooted from a bugcheck. The bugcheck was: 0x00000050 (0xffffc8035872d2cc, 0x0000000000000000, 0xfffff8063161aa51, 0x0000000000000002). A dump was saved in: C:\WINDOWS\MEMORY.DMP. Report Id: 3492a188-6c7e-4f02-a472-4bf100eb00c5.
Based on the above I would not be too sure which way to go so I'd advise running driver verifier for about 48h to see if it throws up any drivers that are not functioning correctly. Follow the tutorial below.
Diagnostic Test
DRIVER VERIFIER
Warning
Please make a backup of your important files and get your rescue media or
create one.
Please create a restore point.
Please read and run driver verifier.
If you suspect a driver is causing a problem but do not have a clear idea which one it is then Driver Verifier stresses your drivers and will crash your pc if any driver fails due to a violation.
Driver verifier should be performed for a max of 48 hours, or until you have a bluescreen, whichever comes first.
If driver verifier has found a violation and you can't get back into windows normally, try to boot into safe mode and reset driver verifier from within safe mode, or in the troubleshooting options open command prompt and type verifier /reset.
Note
Your system will act very sluggishly while driver verifier is enabled, this is normal as your drivers will be being subjected to heavy testing in order to make them crash.