Here is the analysis:
Code:
1. Fri Oct 13 09:12:37.080 2017 (UTC + 1:00)
BugCheck 139, {3, ffffd08061b06100, ffffd08061b06058, 0}
*** WARNING: Unable to verify timestamp for Netwbw02.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sys
Probably caused by : vwififlt.sys ( vwififlt!FilterSendNetBufferListsCompleteLegacy+145 )
2. Thu Oct 12 14:09:35.951 2017 (UTC + 1:00)
BugCheck D1, {8, 2, 1, fffff80c4803cfe1}
*** WARNING: Unable to verify timestamp for Netwbw02.sys
*** ERROR: Module load completed but symbols could not be loaded for Netwbw02.sys
Probably caused by : Netwbw02.sys ( Netwbw02+1ccfe1 )
3. Thu Oct 12 15:28:22.462 2017 (UTC + 1:00)
BugCheck 1E, {ffffffffc0000005, fffff803c67f3087, ffffc080eadf2fb8, ffffc080eadf2800}
Probably caused by : vwififlt.sys ( vwififlt!FilterSendNetBufferListsLegacy+13e )
The driver vwififlt.sys is a MS windows driver and so is not the problem but it gets highlighted because it was involved in the kernel thread, in the item 3 listed above the netwbw02 just did not get picked up.
So yes, I would say my suggestion was appropriate for all the crashes listed. Let me know if you require any more information and of course post a new set of files if you continue to get BSODs.