Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

7 Blue Screens within 30 days


  • Please log in to reply
21 replies to this topic

#1 Azryu

Azryu

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:IA
  • Local time:11:50 AM

Posted 17 February 2016 - 01:17 AM

Hello everyone,

 

I've been getting a BSOD quite regularly now since 01/22/16 and it's beginning to be a bit worrying. I've attached all the BSOD info from the last 30 days.

 

It could be I always seem to be playing video games, but for the most part it seems to only occur when playing them. I seem to notice it happens more when I open up something on my second screen while playing a game on the first.

Attached Files


Edited by Azryu, 17 February 2016 - 01:30 AM.


BC AdBot (Login to Remove)

 


#2 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:11:50 AM

Posted 17 February 2016 - 01:20 AM

Hi. . .

 

Please run the BSOD Posting Instructions app -  http://www.bleepingcomputer.com/forums/t/576314/blue-screen-of-death-bsod-posting-instructions-windows-10-81-8-7-vista/

 

Attach the resulting zip files to your next post in this thread.

 

I see tcpip.sys in your text attachments, so networking may be involved.

 

Be sure to update both wifi and Ethernet drivers -- even if one is not used, update the driver anyway as it does get loaded into RAM.

 

Regards. . .

 

jcgriff2


Edited by jcgriff2, 17 February 2016 - 01:22 AM.

Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#3 Azryu

Azryu
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:IA
  • Local time:11:50 AM

Posted 17 February 2016 - 01:31 AM

Thanks for the reply. I have posted the requested documents. All of my drivers have been updated to my knowledge ( I have Driver Booster, is this bad?) but I'm using the verifier tool mentioned in the post to double check.


Edited by Azryu, 17 February 2016 - 01:39 AM.


#4 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:11:50 AM

Posted 17 February 2016 - 01:47 AM

Check Device Manager.  Networking drivers are updated frequently, so wifi and Ethernet drivers  should have a 2015 or 2016 date on them.

 

You can get the driver name, then look it up for the update site - https://www.sysnative.com/drivers

 

Regards. . .

 

jcgriff2

 

EDIT: do go ahead and run Driver Verifier.

 

http://www.bleepingcomputer.com/forums/t/576333/driver-verifier-bsod-related-windows-10-81-8-7-vista/


Edited by jcgriff2, 17 February 2016 - 01:52 AM.

Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#5 Azryu

Azryu
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:IA
  • Local time:11:50 AM

Posted 17 February 2016 - 01:54 AM

My wireless adapter seems to be outdated. 

netr28ux.sys

MediaTeck, INC

 

It's a Netgear A6210-100PAS. I tried the driver a small while ago available from Netgear for the item however Netgear Genie refused to recognize the network adapter was connected. I'm trying the standalone version without the software this time to see if it helps.



#6 Azryu

Azryu
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:IA
  • Local time:11:50 AM

Posted 17 February 2016 - 02:01 AM

Updating the driver was a success.  Oh, look at that, I can finally see the 5ghz network now!

 

Thanks for the recommendation. Made a donation to your Sysnative forums via PayPal as a thanks for the timely and plentiful replies.


Edited by Azryu, 17 February 2016 - 02:02 AM.


#7 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:11:50 AM

Posted 17 February 2016 - 02:02 AM

All 7 dumps had the same bugcheck (0x19 - bad pool header -- corrupted pool block header size) and all listed the same probable cause - mwac.sys = Malwarebytes.

 

Update (reinstall) the Malwarebytes program installation - https://www.sysnative.com/drivers/driver.php?id=mwac.sys

 

If BSODs continue, remove it completely.

 

Regards. . .

 

jcgriff2

Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020516-6656-01.dmp]
Built by: 10586.63.amd64fre.th2_release.160104-1513
Debug session time: Fri Feb  5 20:11:22.774 2016 (UTC - 5:00)
System Uptime: 0 days 17:38:08.441
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
Bugcheck code 00000019
Arguments 00000000`00000020 ffffe000`39fefb80 ffffe000`39fefba0 00000000`04020011
BiosVersion = P2.10
BiosReleaseDate = 07/27/2015
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3100
CurrentSpeed: 3100
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\020516-7187-01.dmp]
Built by: 10586.63.amd64fre.th2_release.160104-1513
Debug session time: Fri Feb  5 02:32:54.643 2016 (UTC - 5:00)
System Uptime: 0 days 0:00:41.310
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
Bugcheck code 00000019
Arguments 00000000`00000020 ffffe000`48dd8960 ffffe000`48dd8980 00000000`04020005
BiosVersion = P2.10
BiosReleaseDate = 07/27/2015
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3100
CurrentSpeed: 3100
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021016-6390-01.dmp]
Built by: 10586.103.amd64fre.th2_release.160126-1819
Debug session time: Wed Feb 10 23:55:38.138 2016 (UTC - 5:00)
System Uptime: 0 days 12:10:07.805
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
Bugcheck code 00000019
Arguments 00000000`00000020 ffffe001`21a981e0 ffffe001`21a98200 00000000`04020005
BiosVersion = P2.10
BiosReleaseDate = 07/27/2015
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3100
CurrentSpeed: 3100
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021216-7359-01.dmp]
Built by: 10586.103.amd64fre.th2_release.160126-1819
Debug session time: Fri Feb 12 22:04:38.496 2016 (UTC - 5:00)
System Uptime: 1 days 22:08:39.163
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
Bugcheck code 00000019
Arguments 00000000`00000020 ffffe001`ac8bd4d0 ffffe001`ac8bd4f0 00000000`04020017
BiosVersion = P2.10
BiosReleaseDate = 07/27/2015
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3100
CurrentSpeed: 3100
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021416-5375-01.dmp]
Built by: 10586.103.amd64fre.th2_release.160126-1819
Debug session time: Sun Feb 14 05:46:58.020 2016 (UTC - 5:00)
System Uptime: 1 days 7:29:34.691
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
Bugcheck code 00000019
Arguments 00000000`00000020 ffffe001`e8a8ef60 ffffe001`e8a8ef80 00000000`04020017
BiosVersion = P2.10
BiosReleaseDate = 07/27/2015
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3100
CurrentSpeed: 3100
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\021716-21671-01.dmp]
Built by: 10586.103.amd64fre.th2_release.160126-1819
Debug session time: Wed Feb 17 01:00:15.561 2016 (UTC - 5:00)
System Uptime: 2 days 18:21:17.231
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
Bugcheck code 00000019
Arguments 00000000`00000020 ffffe001`0de4f190 ffffe001`0de4f1b0 00000000`04020019
BiosVersion = P2.10
BiosReleaseDate = 07/27/2015
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3100
CurrentSpeed: 3100
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
Loading Dump File [C:\Users\PalmDesert\_jcgriff2_\dbug\__Kernel__\012216-7000-01.dmp]
Built by: 10586.63.amd64fre.th2_release.160104-1513
Debug session time: Fri Jan 22 20:56:02.140 2016 (UTC - 5:00)
System Uptime: 4 days 2:48:04.273
*** WARNING: Unable to verify timestamp for mwac.sys
*** ERROR: Module load completed but symbols could not be loaded for mwac.sys
Probably caused by : fwpkclnt.sys ( fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+1dd )
BUGCHECK_STR:  0x19_20
DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT
PROCESS_NAME:  mbamservice.ex
FAILURE_BUCKET_ID:  0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
Bugcheck code 00000019
Arguments 00000000`00000020 ffffe001`7cee1a00 ffffe001`7cee1a20 00000000`04020005
BiosVersion = P2.10
BiosReleaseDate = 07/27/2015
SystemManufacturer = To Be Filled By O.E.M.
SystemProductName = To Be Filled By O.E.M.
MaxSpeed:     3100
CurrentSpeed: 3100
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
  

Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#8 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:11:50 AM

Posted 17 February 2016 - 02:06 AM

Hi. . .

 

We're x-posting here....

 

Thank you very much.

 

I'm glad the network driver update was successful, but according to the dumps, it was not involved.

 

However... Malwarebytes may have been "phoning home" at the time of the BSODs, so it is possible that the networking driver is involved after all. Time will tell -- if you encounter additional BSODs.

 

Regards. . .

 

John


Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#9 Azryu

Azryu
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:IA
  • Local time:11:50 AM

Posted 17 February 2016 - 02:07 AM

 

Update (reinstall) the Malwarebytes program installation - https://www.sysnative.com/drivers/driver.php?id=mwac.sys

 

If BSODs continue, remove it completely.

 

Done. I re-installed it for now



#10 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:11:50 AM

Posted 17 February 2016 - 02:17 AM

If you started Driver Verifier, I would let it run for the next 24 hours.  You may notice some system slowness while it's running. 

 

Save your work often because if Driver Verifier detects a driver violation, it will force a BSOD immediately.

 

Regards. . .

 

John


Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#11 Azryu

Azryu
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:IA
  • Local time:11:50 AM

Posted 18 February 2016 - 12:10 AM

Even with Driver Verifier on I've yet to BSOD so far. So far so good!



#12 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:11:50 AM

Posted 18 February 2016 - 01:16 AM

NO BSODs with Driver Verifier running for this length of time is a good sign indeed.

 

I really would like to know if the Netgear driver (netr28ux.sys) clashed with the Malwarebytes driver (mwac.sys) thus causing the BSODs because as you know, an innocent party was left at the scene of the crash and got blamed - Microsoft's networking related driver (tcpip.sys). 

 

mwac.sys was named in the dumps as well, but in a very subtle manner compared to tcpip.sys.

 

I'll just have to go on theorizing about that one as there is no way to prove it.

 

Thanks for the status update.

 

Regards. . .

 

John


Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#13 Azryu

Azryu
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:IA
  • Local time:11:50 AM

Posted 18 February 2016 - 03:17 AM

Considering that the last crash happened exactly as I went to load a YouTube video @1080p as I was playing Overwatch Beta, wouldn't it be more likely the networking? I haven't the faintest idea myself, just thinking about it is all. Looking back on it... this never happened before I upgraded my internet from 5 to 100mbps.


Edited by Azryu, 18 February 2016 - 03:17 AM.


#14 jcgriff2

jcgriff2

  • BSOD Kernel Dump Expert
  • 1,109 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:New Jersey Shore
  • Local time:11:50 AM

Posted 18 February 2016 - 09:08 PM

I agree with you that updating the network driver may have been the absolute answer here.

 

It is unusual for Malwarebytes to BSOD a system, which is why I theorize that it was "phoning home" via Internet, which would of course caused it to interact with the networking driver.

 

Then there is Microsoft tcpip.sys which of course would interact with both.

 

Since we have Windbg debugger symbol fules for all Microsoft files, tcpip.sys was recognizable on the stack; hence the reason it got the blame. We don't have private debugger symbol files for drivers like your Netgear or MBAM.


Microsoft MVP 2009-2015
Microsoft Windows Insider MVP 2018 - Present

#15 Azryu

Azryu
  • Topic Starter

  • Members
  • 11 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:IA
  • Local time:11:50 AM

Posted 19 February 2016 - 03:50 AM

I just blue screened again... just hours after I finally disabled Driver Verifier. Uninstalled Malwarebytes... really unfortunate. I guess I'll give it a few days and we'll find out if it was the cause. Again it happened as I was opening a YouTube video (after watching several)


Edited by Azryu, 19 February 2016 - 03:55 AM.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users