Thanks for posting that.
I'm rather taken by the old timestamps on some of the 3rd party drivers.
stdcfltn.sys Fri Jul 13 19:30:14 2012 (5000AF86) - ST Microelectronics Disk Class Filter Driver for Accelerometer IntelPcc.sys Tue Apr 29 20:13:23 2014 (53604023) - Intel Collaborative Processor Performance Control (CPPC) driver e1d65x64.sys Thu Jun 18 12:37:56 2015 (5582F3E4) - Intel Ethernet - Driver Reference Table (DRT) | e1d65x64.sys (sysnative.com) O2FJ2w7x64.sys Tue May 13 21:46:47 2014 (5372CB07) - O2Micro SD Reader Driver - Driver Reference Table (DRT) | O2FJ2w7x64.sys (sysnative.com) dptf_acpi.sys Tue Jun 10 15:52:05 2014 (539761E5) - Intel Dynamic Platform Thermal Framework Driver - Driver Reference Table (DRT) | dptf_acpi.sys (sysnative.com) ST_Accel.sys Sun Apr 20 23:28:44 2014 (5354906C) - STM 3-Axis Accelerometer driver DellRbtn.sys Fri Aug 3 17:32:54 2012 (501C4386) - OSR Open Systems Resources Airplane Mode Switch Driver - Driver Reference Table (DRT) | DellRbtn.sys (sysnative.com) Netwtw04.sys Mon Dec 31 10:32:13 2018 (5C2A367D) - Intel wifi driver - Driver Reference Table (DRT) | Netwtw04.sys (sysnative.com)
The above all pre-date Windows 10, except for the last one. I noted it here because networking drivers are typically updated at least once per year and yours is 2+ years old. There are several other drivers from 2016, 7, 8, 9 as well, but they were written for W10 as their timestamps are >2015.
However, as W10's drivers are updated, so should 3rd party drivers.
All of the above listed drivers were loaded into RAM at the time of the BSODs and therefore could be involved in future BSODs.
Regards. . .
jcgriff2