Experienced three BSODs in one day with different reasons

After Window 10 1703 upgrade my laptop experienced three BSODs in one day, and according to reliability history they had different reasons that caused Windows stopped working.The first bugcheck: 0x000000d1, second: 0x0000001e, third: 0x00000139

The info zip Attachment 157803
Minidump files Attachment 157805

Please let me know if any additional information is required.
Thank you all in advance.

Possibly RAM related, best to run the Windows Memory Diags for a few passes just for piece of mind

Hello Peter,

I have looked at your crash dumps and they all show a problem with your Intel WiFi driver (Netwbw02.sys Thu Apr 16 13:33:36 2015 (552FAC20) c:\windows\system32\drivers\netwbw02.sys (17.16.2.1, 3.34 MB (3,506,464 bytes))


Please try to update this from the HP website where there is a slightly newer version or directly from INTEL.

philc43 said:

Hello Peter,

I have looked at your crash dumps and they all show a problem with your Intel WiFi driver (Netwbw02.sys Thu Apr 16 13:33:36 2015 (552FAC20) c:\windows\system32\drivers\netwbw02.sys (17.16.2.1, 3.34 MB (3,506,464 bytes))


Please try to update this from the HP website where there is a slightly newer version or directly from INTEL.

Thanks for your reply. Can I choose 'update driver' from device manager instead of downloading from HP website?

kingtez1984 said:

Possibly RAM related, best to run the Windows Memory Diags for a few passes just for piece of mind

I ran the Windows memory diagnostic tool just now and it said "no problem found".

peterhogunner said:

Thanks for your reply. Can I choose 'update driver' from device manager instead of downloading from HP website?

You can try but this will only work if MS recognises that there is an update available - it may think your current driver is OK. Best to try the HP website route first and if this makes no difference try the INTEL website where you can do an automatic check of your drivers.

philc43 said:

You can try but this will only work if MS recognises that there is an update available - it may think your current driver is OK. Best to try the HP website route first and if this makes no difference try the INTEL website where you can do an automatic check of your drivers.

I just updated the WiFi driver. I would like to know if this is the reason for all my BSODs? Because according to reliability monitor these BSODs were caused by different reasons.

peterhogunner said:

I just updated the WiFi driver. I would like to know if this is the reason for all my BSODs? Because according to reliability monitor these BSODs were caused by different reasons.

What did it say? These guys know what there talking about matey. Years and years of combined experience in this forum lol

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.