Jump to content

BAD POOL HEADER crash randomly happens when surfing the web.


Recommended Posts

I recently built a new computer and have had a problem with my computer getting a BSOD under the name of "BAD POOL HEADER" I recently downloaded BluescreenView to get an idea of the problem but I just don't know what to make of it. I've tried alot of things uninstalling and reinstalling drivers, using cmd, even doing multiple Memchecks which all come out with nothing wrong. So if it isn't my RAM or my Drivers what is it? I would really like some help in fixing this, 

 

050916-27921-01.dmp    5/9/2016 9:38:00 PM    BAD_POOL_HEADER    0x00000019    00000000`00000020    ffffe000`d8366a00    ffffe000`d8366a20    00000000`04020003    tcpip.sys    tcpip.sys+7bd7d    TCP/IP Driver    Microsoft® Windows® Operating System    Microsoft Corporation    10.0.10586.0 (th2_release.151029-1700)    x64    ntoskrnl.exe+142760                    C:\Windows\Minidump\050916-27921-01.dmp    4    15    10586    410,244    5/9/2016 9:40:01 PM  

This is basically the DMP I have of the crash. But I really can't make heads or tails of it.   
 

Crash report 1.txt

Link to post
Share on other sites

This is a networking error, so for starters, try updating your networking drivers.
I also suggest these 5 things:
1.  Get ALL available Windows Updates.  It may take several trips to get them all
2.  Get ALL available, compatible updates for your OS from the manufacturer's website (to include BIOS/UEFI).
3.  Get ALL available, compatible updates for the programs and any additional hardware installed on your computer from the developer's website
4.  Start with these free hardware diagnostics:  http://www.carrona.org/hwdiag.html
5.  If all of the hardware tests pass, then run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

Please run this report collecting tool so that we can provide a complete analysis:  http://omgdebugging.com/bsod-inspector/
When done a Notepad document will open with the name of the file and it's location. (By default it'll be a .zip file located on your Desktop)
Simply upload the .zip file with your next post and we'll move on from there.

If it doesn't work for you, then please try this: 

 

Link to post
Share on other sites

Your UEFI/BIOS (version 0901) dates from 2015.  Please check at the manufacturer's website to see if there are any UEFI/BIOS updates available for your system.  This is just in case there has been a more recent update.

You only have 919 MB of available Physical Memory (RAM).
Please get more memory if the system is able to handle it.
While waiting to upgrade the memory, please:
- only use one program at a time
- go through your startup items and stop those that aren't essential from loading with Windows

Only 7 Windows Update hotfixes installed.  Most build 10586 (TH2/1511) systems have more than this.  Please visit Windows Update and get ALL available Windows Updates.
The actual number is not important.  Rather it's important that you checked manually, installed any available updates, and didn't experience any errors when checking or updating.

You have a NETGEAR A6210 WiFi USB3.0 Adapter

Quote

I do not recommend using wireless USB network devices.


These wireless USB devices have many issues with Win7 and later systems - using older drivers with them is almost certain to cause a BSOD.
Should you want to keep using these devices, be sure to have the latest W7/8/8.1/10 drivers - DO NOT use older drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.



J: drive only has about 5% free space.  Windows likes 15% free space in order to perform stuff "behind the scenes" without adversely affecting the system's performance.  Please free up 15% on ALL hard drives (you can get away with 10% on larger drives and won't notice a large performance penalty).  Low free space can cause BSOD's - but the actual amount depends on the files being used by the system.

Daemon Tools (and Alcohol % software) are known to cause BSOD's on some Windows systems (mostly due to the sptd.sys driver, although I have seen both dtsoftbus01.sys and dtscsibus.sys blamed on several occasions).

Quote

Please un-install the program, then use the following free tool to ensure that the troublesome sptd.sys driver is removed from your system (pick the 32 or 64 bit system depending on your system's configuration):  New link (15 Aug 2012): 

http://www.duplexsecure.com/downloads (pick the appropriate version for your system and select "Un-install" when you run it).
Alternate link:  http://www.disc-tools.com/download/sptd
Manual procedure here:  http://daemonpro-help.com/en/problems_and_solutions/registry_and_sptd_problems.html

NOTE:  The uninstaller may not find the SPTD.sys driver.  Don't worry about it, just let us know in your post.
NOTE2:  The latest version has an SPTD2.sys driver - the uninstaller is on the same page as the SPTD.sys driver - just download the version for W10!

MSI Afterburner and Riva Tuner (along with EVGA Precision) are known to cause BSOD's in some Windows systems (it's driver is usually RTCore64.sys).  Please un-install them immediately!

If you're overclocking, please stop the overclock while we're troubleshooting.  Feel free to resume the overclock once the system has been stabilized.

There's a lot of other possible issues here.  The most obvious is a suspicion that AVG isn't playing well with MalwareBytes.
I would suggest:
- download a fresh copy of the latest version of AVG
- uninstall AVG
- use this free tool (AVG Remover) to remove any remanants of AVG:  http://www.avg.com/us-en/utilities
- install the freshly downloaded version of AVG
- monitor for further BSOD's
If all of this doesn't stop the BSOD's, please run Driver Verifier according to these instructions:  http://www.carrona.org/verifier.html

Analysis:

The following is for information purposes only.
The following information contains the relevant information from the blue screen analysis:

 

 

 

Quote
**************************Mon Jul  4 07:50:21.382 2016 (UTC - 4:00)**************************

 

Loading Dump File [C:\Users\john\SysnativeBSODApps\070416-21343-01.dmp]

 

 

Windows 10 Kernel Version 10586 MP (4 procs) Free x64

 

 

Built by:

 

10586
.420.amd64fre.th2_release_sec.160527-1834

 

System Uptime:

 

0 days 1:16:52.060

 

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys

 

 

*** 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

 

19, {20, ffffe000a8f4a4a0, ffffe000a8f4a4c0, 4020008}

 

BugCheck Info:

 

 

Arguments:

 

 

Arg1: 0000000000000020, a pool block header size is corrupt.

 

 

Arg2: ffffe000a8f4a4a0, The pool entry we were looking for within the page.

 

 

Arg3: ffffe000a8f4a4c0, The next pool entry.

 

 

Arg4: 0000000004020008, (reserved)

 

 

BUGCHECK_STR:  0x19_20

 

 

PROCESS_NAME:  mbamservice.ex

 

 

FAILURE_BUCKET_ID:

 

0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0

 

CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"

 

 

MaxSpeed:     3200

 

 

CurrentSpeed:

 

3192

 

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

 

**************************Sun Jul  3 17:22:24.941 2016 (UTC - 4:00)**************************

 

 

Loading Dump File [C:\Users\john\SysnativeBSODApps\070316-20390-01.dmp]

 

 

Windows 10 Kernel Version 10586 MP (4 procs) Free x64

 

 

Built by:

 

10586
.420.amd64fre.th2_release_sec.160527-1834

 

System Uptime:

 

0 days 2:43:16.618

 

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys

 

 

*** 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

 

19, {20, ffffe000c9f3fb60, ffffe000c9f3fb80, 4020008}

 

BugCheck Info:

 

 

Arguments:

 

 

Arg1: 0000000000000020, a pool block header size is corrupt.

 

 

Arg2: ffffe000c9f3fb60, The pool entry we were looking for within the page.

 

 

Arg3: ffffe000c9f3fb80, The next pool entry.

 

 

Arg4: 0000000004020008, (reserved)

 

 

BUGCHECK_STR:  0x19_20

 

 

PROCESS_NAME:  mbamservice.ex

 

 

FAILURE_BUCKET_ID:

 

0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0

 

CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"

 

 

MaxSpeed:     3200

 

 

CurrentSpeed:

 

3192

 

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

 

**************************Sun Jul  3 14:38:41.083 2016 (UTC - 4:00)**************************

 

 

Loading Dump File [C:\Users\john\SysnativeBSODApps\070316-18312-01.dmp]

 

 

Windows 10 Kernel Version 10586 MP (4 procs) Free x64

 

 

Built by:

 

10586
.420.amd64fre.th2_release_sec.160527-1834

 

System Uptime:

 

0 days 22:23:00.762

 

*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys

 

 

*** 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

 

19, {20, ffffe00186211e00, ffffe00186211e20, 4020006}

 

BugCheck Info:

 

 

Arguments:

 

 

Arg1: 0000000000000020, a pool block header size is corrupt.

 

 

Arg2: ffffe00186211e00, The pool entry we were looking for within the page.

 

 

Arg3: ffffe00186211e20, The next pool entry.

 

 

Arg4: 0000000004020006, (reserved)

 

 

BUGCHECK_STR:  0x19_20

 

 

PROCESS_NAME:  mbamservice.ex

 

 

FAILURE_BUCKET_ID:

 

0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0

 

CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"

 

 

MaxSpeed:     3200

 

 

CurrentSpeed:

 

3192

 

¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

 

 

The rest of the memory dump summaries are hidden in the Spoiler tag below.  Click on "Show" to reveal them.

 

 

 

 

 
 
**************************Sat Jul  2 16:15:02.470 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\070216-20875-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 17:31:55.148
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001038a06b0, ffffe001038a06d0, 4020010}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001038a06b0, The pool entry we were looking for within the page.
 
Arg3: ffffe001038a06d0, The next pool entry.
 
Arg4: 0000000004020010, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri Jul  1 22:42:36.926 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\070116-18562-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 20:05:51.604
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0004eebc310, ffffe0004eebc330, 4020012}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0004eebc310, The pool entry we were looking for within the page.
 
Arg3: ffffe0004eebc330, The next pool entry.
 
Arg4: 0000000004020012, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri Jul  1 02:36:11.613 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\070116-24265-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 4:31:57.290
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001ae8e0970, ffffe001ae8e0990, 402000e}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001ae8e0970, The pool entry we were looking for within the page.
 
Arg3: ffffe001ae8e0990, The next pool entry.
 
Arg4: 000000000402000e, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun 30 22:03:43.789 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\063016-19171-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 3:53:52.466
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0017fb5a1c0, ffffe0017fb5a1e0, 4020005}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0017fb5a1c0, The pool entry we were looking for within the page.
 
Arg3: ffffe0017fb5a1e0, The next pool entry.
 
Arg4: 0000000004020005, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun 30 18:09:19.959 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\063016-24156-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 1:10:08.637
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001f2d4a8e0, ffffe001f2d4a900, 4020011}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001f2d4a8e0, The pool entry we were looking for within the page.
 
Arg3: ffffe001f2d4a900, The next pool entry.
 
Arg4: 0000000004020011, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun 30 16:58:39.439 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\063016-22187-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 5:38:57.116
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001f7e6c850, ffffe001f7e6c870, 4020085}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001f7e6c850, The pool entry we were looking for within the page.
 
Arg3: ffffe001f7e6c870, The next pool entry.
 
Arg4: 0000000004020085, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun 30 11:19:12.030 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\063016-20718-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 9:16:27.759
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0010f0ec160, ffffe0010f0ec180, 4020005}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0010f0ec160, The pool entry we were looking for within the page.
 
Arg3: ffffe0010f0ec180, The next pool entry.
 
Arg4: 0000000004020005, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun 30 01:56:45.297 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\063016-21000-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 3:33:24.975
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001272d7880, ffffe001272d78a0, 4020088}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001272d7880, The pool entry we were looking for within the page.
 
Arg3: ffffe001272d78a0, The next pool entry.
 
Arg4: 0000000004020088, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Wed Jun 29 22:22:44.474 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062916-22421-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 6:14:52.211
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00180ee6be0, ffffe00180ee6c00, 402000e}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00180ee6be0, The pool entry we were looking for within the page.
 
Arg3: ffffe00180ee6c00, The next pool entry.
 
Arg4: 000000000402000e, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Wed Jun 29 16:07:20.187 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062916-20046-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 11:06:03.865
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00206d92d60, ffffe00206d92d80, 4020029}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00206d92d60, The pool entry we were looking for within the page.
 
Arg3: ffffe00206d92d80, The next pool entry.
 
Arg4: 0000000004020029, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Wed Jun 29 05:00:47.067 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062916-20453-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 8:59:29.745
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0018edfccc0, ffffe0018edfcce0, 4020017}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0018edfccc0, The pool entry we were looking for within the page.
 
Arg3: ffffe0018edfcce0, The next pool entry.
 
Arg4: 0000000004020017, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri Jun 24 22:33:49.820 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062416-14484-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 4:04:05.497
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0015ff73ce0, ffffe0015ff73d00, 4020025}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0015ff73ce0, The pool entry we were looking for within the page.
 
Arg3: ffffe0015ff73d00, The next pool entry.
 
Arg4: 0000000004020025, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri Jun 24 18:29:10.189 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062416-20109-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 0:22:58.866
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00115edba80, ffffe00115edbaa0, 4020022}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00115edba80, The pool entry we were looking for within the page.
 
Arg3: ffffe00115edbaa0, The next pool entry.
 
Arg4: 0000000004020022, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri Jun 24 18:05:41.602 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062416-19343-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 5:39:22.281
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001c574c080, ffffe001c574c0a0, 4020008}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001c574c080, The pool entry we were looking for within the page.
 
Arg3: ffffe001c574c0a0, The next pool entry.
 
Arg4: 0000000004020008, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri Jun 24 12:25:42.135 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062416-19781-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 20:23:57.812
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0014139a4b0, ffffe0014139a4d0, 402000e}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0014139a4b0, The pool entry we were looking for within the page.
 
Arg3: ffffe0014139a4d0, The next pool entry.
 
Arg4: 000000000402000e, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun 23 16:01:12.660 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062316-15078-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 4:16:32.397
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0019aab5340, ffffe0019aab5360, 4020006}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0019aab5340, The pool entry we were looking for within the page.
 
Arg3: ffffe0019aab5360, The next pool entry.
 
Arg4: 0000000004020006, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun 23 01:16:27.966 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062316-18625-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 6:59:11.643
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe000ed3b0370, ffffe000ed3b0390, 4020011}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe000ed3b0370, The pool entry we were looking for within the page.
 
Arg3: ffffe000ed3b0390, The next pool entry.
 
Arg4: 0000000004020011, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Wed Jun 22 18:16:45.845 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062216-18171-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 5:03:49.524
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00010152f60, ffffe00010152f80, 4020004}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00010152f60, The pool entry we were looking for within the page.
 
Arg3: ffffe00010152f80, The next pool entry.
 
Arg4: 0000000004020004, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Wed Jun 22 09:06:08.737 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062216-16375-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 15:12:49.414
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe000ceb78b00, ffffe000ceb78b20, 4020017}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe000ceb78b00, The pool entry we were looking for within the page.
 
Arg3: ffffe000ceb78b20, The next pool entry.
 
Arg4: 0000000004020017, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Tue Jun 21 17:52:48.847 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062116-16921-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 3:58:06.526
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00020e903e0, ffffe00020e90400, 4020005}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00020e903e0, The pool entry we were looking for within the page.
 
Arg3: ffffe00020e90400, The next pool entry.
 
Arg4: 0000000004020005, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Mon Jun 20 08:32:51.732 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\062016-27375-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
1 days 13:12:20.409
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0013051bbf0, ffffe0013051bc10, 4020003}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0013051bbf0, The pool entry we were looking for within the page.
 
Arg3: ffffe0013051bc10, The next pool entry.
 
Arg4: 0000000004020003, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Sat Jun 18 19:19:59.622 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\061816-20000-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 20:07:54.314
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe000ef208a40, ffffe000ef208a60, 402000e}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe000ef208a40, The pool entry we were looking for within the page.
 
Arg3: ffffe000ef208a60, The next pool entry.
 
Arg4: 000000000402000e, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri Jun 17 15:46:57.483 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\061716-15328-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.420.amd64fre.th2_release_sec.160527-1834
 
System Uptime:
0 days 3:49:44.173
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001d37dfc80, ffffe001d37dfca0, 4020067}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001d37dfc80, The pool entry we were looking for within the page.
 
Arg3: ffffe001d37dfca0, The next pool entry.
 
Arg4: 0000000004020067, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Wed Jun 15 11:25:08.972 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\061516-19593-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 20:08:28.666
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0016f02b340, ffffe0016f02b360, 402000c}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0016f02b340, The pool entry we were looking for within the page.
 
Arg3: ffffe0016f02b360, The next pool entry.
 
Arg4: 000000000402000c, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Tue Jun 14 02:55:00.219 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\061416-15718-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 11:02:37.911
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001d3434370, ffffe001d3434390, 402000c}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001d3434370, The pool entry we were looking for within the page.
 
Arg3: ffffe001d3434390, The next pool entry.
 
Arg4: 000000000402000c, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Mon Jun 13 15:51:43.165 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\061316-18859-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 1:37:08.857
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001262201f0, ffffe00126220210, 4020008}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001262201f0, The pool entry we were looking for within the page.
 
Arg3: ffffe00126220210, The next pool entry.
 
Arg4: 0000000004020008, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Mon Jun 13 14:13:54.316 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\061316-15843-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 11:21:34.007
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0000de54270, ffffe0000de54290, 4020027}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0000de54270, The pool entry we were looking for within the page.
 
Arg3: ffffe0000de54290, The next pool entry.
 
Arg4: 0000000004020027, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun  9 15:56:55.211 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\060916-18125-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 3:57:51.903
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00106e06100, ffffe00106e06120, 4020010}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00106e06100, The pool entry we were looking for within the page.
 
Arg3: ffffe00106e06120, The next pool entry.
 
Arg4: 0000000004020010, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun  9 11:58:25.058 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\060916-14109-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 6:28:18.750
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0019648a3a0, ffffe0019648a3c0, 4020017}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0019648a3a0, The pool entry we were looking for within the page.
 
Arg3: ffffe0019648a3c0, The next pool entry.
 
Arg4: 0000000004020017, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun  9 05:29:15.719 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\060916-22281-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 9:35:32.413
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00021c70a60, ffffe00021c70a80, 402000e}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00021c70a60, The pool entry we were looking for within the page.
 
Arg3: ffffe00021c70a80, The next pool entry.
 
Arg4: 000000000402000e, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Mon Jun  6 02:42:35.843 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\060616-16562-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 2:34:46.565
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001f259ab60, ffffe001f259ab80, 4020008}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001f259ab60, The pool entry we were looking for within the page.
 
Arg3: ffffe001f259ab80, The next pool entry.
 
Arg4: 0000000004020008, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri Jun  3 19:12:18.530 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\060316-19218-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 13:25:55.222
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00133415180, ffffe001334151a0, 4020005}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00133415180, The pool entry we were looking for within the page.
 
Arg3: ffffe001334151a0, The next pool entry.
 
Arg4: 0000000004020005, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri Jun  3 05:45:28.845 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\060316-18218-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
1 days 1:03:19.537
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe000f215cbe0, ffffe000f215cc00, 4020017}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe000f215cbe0, The pool entry we were looking for within the page.
 
Arg3: ffffe000f215cc00, The next pool entry.
 
Arg4: 0000000004020017, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Thu Jun  2 04:41:31.147 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\060216-22687-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 9:15:20.891
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0001cd1ec60, ffffe0001cd1ec80, 4020005}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0001cd1ec60, The pool entry we were looking for within the page.
 
Arg3: ffffe0001cd1ec80, The next pool entry.
 
Arg4: 0000000004020005, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Wed May 25 17:03:43.222 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\052516-18093-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 7:21:30.916
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001a1f34dd0, ffffe001a1f34df0, 4020017}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001a1f34dd0, The pool entry we were looking for within the page.
 
Arg3: ffffe001a1f34df0, The next pool entry.
 
Arg4: 0000000004020017, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Sun May 22 02:26:30.281 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\052216-18328-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 9:11:29.973
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0000d0da170, ffffe0000d0da190, 4020017}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0000d0da170, The pool entry we were looking for within the page.
 
Arg3: ffffe0000d0da190, The next pool entry.
 
Arg4: 0000000004020017, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Sat May 21 17:14:27.909 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\052116-20484-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 11:19:25.601
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00176495c50, ffffe00176495c70, 4020008}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00176495c50, The pool entry we were looking for within the page.
 
Arg3: ffffe00176495c70, The next pool entry.
 
Arg4: 0000000004020008, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Mon May 16 11:26:28.410 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\051616-21500-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 5:06:48.101
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0008e97bd00, ffffe0008e97bd20, 4020005}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0008e97bd00, The pool entry we were looking for within the page.
 
Arg3: ffffe0008e97bd20, The next pool entry.
 
Arg4: 0000000004020005, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Sun May 15 02:57:12.953 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\051516-22390-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 2:34:18.645
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001a3e82940, ffffe001a3e82960, 4020011}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001a3e82940, The pool entry we were looking for within the page.
 
Arg3: ffffe001a3e82960, The next pool entry.
 
Arg4: 0000000004020011, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Sun May 15 00:22:15.070 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\051516-34609-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 13:48:31.760
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0014ef99380, ffffe0014ef993a0, 4020010}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0014ef99380, The pool entry we were looking for within the page.
 
Arg3: ffffe0014ef993a0, The next pool entry.
 
Arg4: 0000000004020010, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Sat May 14 03:58:38.101 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\051416-28875-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 4:18:27.792
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00127eaa5f0, ffffe00127eaa610, 402000f}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00127eaa5f0, The pool entry we were looking for within the page.
 
Arg3: ffffe00127eaa610, The next pool entry.
 
Arg4: 000000000402000f, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri May 13 23:39:35.964 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\051316-35609-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 3:49:52.656
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0010b4c2860, ffffe0010b4c2880, 4020017}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0010b4c2860, The pool entry we were looking for within the page.
 
Arg3: ffffe0010b4c2880, The next pool entry.
 
Arg4: 0000000004020017, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri May 13 19:49:10.336 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\051316-30718-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 12:06:45.028
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe001a3e21130, ffffe001a3e21150, 4020005}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe001a3e21130, The pool entry we were looking for within the page.
 
Arg3: ffffe001a3e21150, The next pool entry.
 
Arg4: 0000000004020005, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri May 13 07:41:51.409 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\051316-53296-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 1:03:07.102
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00165112600, ffffe00165112620, 402000a}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00165112600, The pool entry we were looking for within the page.
 
Arg3: ffffe00165112620, The next pool entry.
 
Arg4: 000000000402000a, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri May 13 04:21:41.293 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\051316-35078-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 1:17:58.984
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe0008dece0e0, ffffe0008dece100, 402000e}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe0008dece0e0, The pool entry we were looking for within the page.
 
Arg3: ffffe0008dece100, The next pool entry.
 
Arg4: 000000000402000e, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri May 13 03:03:07.810 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\051316-46000-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 1:04:51.501
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe00122a17220, ffffe00122a17240, 4020022}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe00122a17220, The pool entry we were looking for within the page.
 
Arg3: ffffe00122a17240, The next pool entry.
 
Arg4: 0000000004020022, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
**************************Fri May 13 01:57:37.249 2016 (UTC - 4:00)**************************
 
Loading Dump File [C:\Users\john\SysnativeBSODApps\051316-38937-01.dmp]
 
Windows 10 Kernel Version 10586 MP (4 procs) Free x64
 
Built by:
10586
.306.amd64fre.th2_release_sec.160422-1850
 
System Uptime:
0 days 5:47:52.941
 
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
 
*** 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
19, {20, ffffe000f3213310, ffffe000f3213330, 4020005}
 
BugCheck Info:
 
Arguments:
 
Arg1: 0000000000000020, a pool block header size is corrupt.
 
Arg2: ffffe000f3213310, The pool entry we were looking for within the page.
 
Arg3: ffffe000f3213330, The next pool entry.
 
Arg4: 0000000004020005, (reserved)
 
BUGCHECK_STR:  0x19_20
 
PROCESS_NAME:  mbamservice.ex
 
FAILURE_BUCKET_ID:
0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0
 
CPUID:        "Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz"
 
MaxSpeed:     3200
 
CurrentSpeed:
3192
 
¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``
 
 
 


3rd Party Drivers:

The following is for information purposes only.
My recommendations were given above. The drivers that follow belong to software or devices that were not developed by Microsoft.  You can find links to the driver information and where to update the drivers in the section after the code box:

 

 

 

**************************Mon Jul  4 07:50:21.382 2016 (UTC - 4:00)**************************

	libusbK.sys                 Tue Jul  3 22:59:39 2012 (4FF3B19B)

	AsIO.sys                    Wed Aug 22 05:54:47 2012 (5034AC67)

	ScpVBus.sys                 Sun May  5 17:31:26 2013 (5186CFAE)

	xspltspk.sys                Wed Jun 11 16:59:54 2014 (5398C34A)

	mwac.sys                    Tue Jun 17 22:07:00 2014 (53A0F444)

	LGVirHid.sys                Fri Apr 24 17:20:53 2015 (553AB3B5)

	LGJoyXlCore.sys             Fri Apr 24 17:20:57 2015 (553AB3B9)

	LGBusEnum.sys               Fri Apr 24 17:21:00 2015 (553AB3BC)

	CorsairVBusDriver.sys       Wed May  6 09:10:40 2015 (554A12D0)

	CorsairVHidDriver.sys       Wed May  6 09:10:41 2015 (554A12D1)

	A6210.sys                   Thu May 28 10:28:52 2015 (55672624)

	lgcoretemp.sys              Tue Jun  9 12:52:10 2015 (557719BA)

	MBAMSwissArmy.sys           Wed Jul 29 00:26:01 2015 (55B855D9)

	mbam.sys                    Tue Aug 11 13:35:19 2015 (55CA3257)

	e1d65x64.sys                Thu Aug 13 05:14:29 2015 (55CC5FF5)

	dtlitescsibus.sys           Thu Sep 24 16:17:21 2015 (56045A51)

	TeeDriverW8x64.sys          Thu Oct  8 14:13:00 2015 (5616B22C)

	intelppm.sys                Thu Oct 29 22:09:51 2015 (5632D16F)

	dtliteusbbus.sys            Mon Dec 28 08:05:52 2015 (568133B0)

	RTKVHD64.sys                Fri Jan 22 10:09:21 2016 (56A24621)

	asmtxhci.sys                Thu Feb  4 02:22:05 2016 (56B2FC1D)

	asmthub3.sys                Thu Feb  4 02:22:26 2016 (56B2FC32)

	nvhda64v.sys                Thu Mar 24 15:26:36 2016 (56F43F6C)

	nvvad64v.sys                Tue Apr 12 04:46:52 2016 (570CB5FC)

	NvStreamKms.sys             Sun May  1 17:00:16 2016 (57266E60)

	nvlddmkm.sys                Thu Jun  2 23:11:28 2016 (5750F560)

	¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

	**************************Sun Jul  3 14:38:41.083 2016 (UTC - 4:00)**************************

	xusb22.sys                  Thu Oct 29 22:41:10 2015 (5632D8C6)

	¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

	**************************Sat Jul  2 16:15:02.470 2016 (UTC - 4:00)**************************

	hiber_storport.sys          Thu Oct 29 22:42:02 2015 (5632D8FA)

	¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

	**************************Thu Jun  9 15:56:55.211 2016 (UTC - 4:00)**************************

	RTCore64.sys                Fri Apr 24 03:01:47 2015 (5539EA5B)

	nvhda64v.sys                Mon Sep 21 05:44:17 2015 (55FFD171)

	nvlddmkm.sys                Wed Apr 27 07:17:14 2016 (57209FBA)

	¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

	**************************Mon Jun  6 02:42:35.843 2016 (UTC - 4:00)**************************

	nvvad64v.sys                Mon Mar 14 02:27:42 2016 (56E659DE)

	¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

	**************************Sat May 14 03:58:38.101 2016 (UTC - 4:00)**************************

	avgldx64.sys                Wed Oct 21 11:16:44 2015 (5627AC5C)

	avgwfpa.sys                 Thu Dec 10 04:34:49 2015 (56694739)

	avgidsha.sys                Tue Jan 26 05:04:23 2016 (56A744A7)

	avgloga.sys                 Tue Feb 16 09:04:03 2016 (56C32C53)

	avgdiska.sys                Tue Feb 16 09:07:26 2016 (56C32D1E)

	avgmfx64.sys                Tue Mar 29 10:39:41 2016 (56FA93AD)

	avgrkx64.sys                Thu Apr 14 04:54:09 2016 (570F5AB1)

	avgidsdrivera.sys           Wed Apr 20 08:17:38 2016 (57177362)

	avguniva.sys                Wed May  4 10:58:23 2016 (572A0E0F)

	¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨¨``

	**************************Fri May 13 19:49:10.336 2016 (UTC - 4:00)**************************

	NvStreamKms.sys             Fri Apr  1 21:18:58 2016 (56FF1E02)

	[/CODE]



libusbK.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=AsIO.sys
http://www.carrona.org/drivers/driver.php?id=ScpVBus.sys
http://www.carrona.org/drivers/driver.php?id=xspltspk.sys
http://www.carrona.org/drivers/driver.php?id=mwac.sys
http://www.carrona.org/drivers/driver.php?id=LGVirHid.sys
http://www.carrona.org/drivers/driver.php?id=LGJoyXlCore.sys
http://www.carrona.org/drivers/driver.php?id=LGBusEnum.sys
http://www.carrona.org/drivers/driver.php?id=CorsairVBusDriver.sys
http://www.carrona.org/drivers/driver.php?id=CorsairVHidDriver.sys
http://www.carrona.org/drivers/driver.php?id=A6210.sys
http://www.carrona.org/drivers/driver.php?id=lgcoretemp.sys
http://www.carrona.org/drivers/driver.php?id=MBAMSwissArmy.sys
http://www.carrona.org/drivers/driver.php?id=mbam.sys
http://www.carrona.org/drivers/driver.php?id=e1d65x64.sys
http://www.carrona.org/drivers/driver.php?id=dtlitescsibus.sys
http://www.carrona.org/drivers/driver.php?id=TeeDriverW8x64.sys
http://www.carrona.org/drivers/driver.php?id=intelppm.sys
dtliteusbbus.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=RTKVHD64.sys
http://www.carrona.org/drivers/driver.php?id=asmtxhci.sys
http://www.carrona.org/drivers/driver.php?id=asmthub3.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=xusb22.sys
http://www.carrona.org/drivers/driver.php?id=hiber_storport.sys
http://www.carrona.org/drivers/driver.php?id=RTCore64.sys
http://www.carrona.org/drivers/driver.php?id=nvhda64v.sys
http://www.carrona.org/drivers/driver.php?id=nvlddmkm.sys
http://www.carrona.org/drivers/driver.php?id=nvvad64v.sys
http://www.carrona.org/drivers/driver.php?id=avgldx64.sys
http://www.carrona.org/drivers/driver.php?id=avgwfpa.sys
http://www.carrona.org/drivers/driver.php?id=avgidsha.sys
http://www.carrona.org/drivers/driver.php?id=avgloga.sys
http://www.carrona.org/drivers/driver.php?id=avgdiska.sys
http://www.carrona.org/drivers/driver.php?id=avgmfx64.sys
http://www.carrona.org/drivers/driver.php?id=avgrkx64.sys
http://www.carrona.org/drivers/driver.php?id=avgidsdrivera.sys
avguniva.sys - this driver hasn't been added to the DRT as of this run. Please search Google/Bing for the driver if additional information is needed.
http://www.carrona.org/drivers/driver.php?id=NvStreamKms.sys

[/INDENT]

Edited by usasma
Link to post
Share on other sites

I uninstalled AVG completely, downloaded an updated BIOS driver, and am still checking around for any other outdated drivers. As for my ram Speccy says  I have more than 919mb of physical mem. Also the RAM that I have is an 8GB so see the ammount it has drop to the ammount you told me is alraming to me but I may be wrong on understanding how RAM works. 

Speccy stats on RAM

 Memory slots
Memory
    Type    Unknown
    Size    8192 MBytes
    Channels #    Single
    DRAM Frequency    1203.6 MHz
    CAS# Latency (CL)    16 clocks
    RAS# to CAS# Delay (tRCD)    16 clocks
    RAS# Precharge (tRP)    16 clocks
    Cycle Time (tRAS)    39 clocks
    Command Rate (CR)    2T
Physical Memory
    Memory Usage    46 %
    Total Physical    7.92 GB
    Available Physical    4.25 GB
    Total Virtual    9.17 GB
    Available Virtual    4.52 GB
SPD
    Number Of SPD Modules    1
        Slot #1

What it is currently. 

 

I Uninstalled  Daemon Tools as well as MSI afterburner and RIVA tuner. I also have Driver verification active so I'll be waiting for the results on that. 

As for my Wireless adapter I honestly don't know what to do about that. 

" These wireless USB devices have many issues with Win7 and later systems - using older drivers with them is almost certain to cause a BSOD.
Should you want to keep using these devices, be sure to have the latest W7/8/8.1/10 drivers - DO NOT use older drivers!!!
An installable wireless PCI/PCIe card that's plugged into your motherboard is much more robust, reliable, and powerful.

It may be the wireless adapters doing but I haven't see any outdated drivers as far as Device Manager can tell. Then again I was told that Device Manager isn't always correct in assuming drivers are up to date so I will continue looking for outdated drivers. 

Link to post
Share on other sites

The amount of physical RAM available will change as circumstances with the computer change.
We don't know why it was so low when you ran the systeminfo.txt report.
It may have just been a fluke, or it may be a deeper problem with the system.
We'll have to wait and see if there are further problems of this nature.

Driver Verifier isn't needed unless you get more BSOD's
It's supposed to cause BSOD's on it's own as it stresses the drivers.

Wireless USB adapters have been a problem since the days of Vista.
The problems associated with them have decreased in frequency over the last several years - but they still exist
Step 1 is to ensure that you have all the latest drivers for this device - and that the manufacturer states that the device is compatible w/Windows 10.
Further steps may be required if the BSOD's continue.

A relatively simple test is to remove the wireless USB wifi adapter and see if that stops/lessens the BSOD's
If it does, then you know where the problem lies.
Unfortunately, this'll leave you without internet access - unless you can temporarily connect with a wired connection.

Another option is to purchase a wireless PCI/PCIe card to put into your motherboard.
They're relatively inexpensive - and it can be good to have one on hand in case you have internet problems later on.
But, if you purchase it from a place that will let you return it - you can test with it and then return it for your money back.

When checking for drivers in Device Manager, the system will check Windows/Microsoft update.  Manufacturer's haven't been reliable at uploading newer drivers to Windows/Microsoft update, so I don't suggest using it (except as a last resort).

The best place to check for device drivers is the place that manufactured the device.  In the case of devices on a motherboard, the best place is the motherboard manufacturer (as they sometimes change drivers that the manufacturer supplies).  If that doesn't work, then you get the device manufacturer's drivers from their website.  This gets very complicated - especially when dealing with the multiple different products/devices installed on a system.
 

Link to post
Share on other sites

  • 1 month later...

I've been having random Bad_Pool_Header failures when surfing the web, too. But only on one of the two systems I have.

I think I've "fixed" the problem.

No BPHs             Random BPHs

System 1             System 2

Notebook             PC

UEFI/GPT            Classic/MBR

Win10Pro             Win10Pro

                            Dual Boot/Linux

AHCI                   RAID

First discovery: it's only related to MWAC, the Malicious Website Protection service. Switch that off, and it goes away.

Second discovery: It started in Windows 10. (after I upgraded from Win7). When I installed Windows again, on a new SSD, I still had the problem. When I re-installed Linux, I still had the problem, but I had a new problem: my Linux wouldn't recognise the NTFS windows partitions, or the RAID NTFS drives either. The file/volume structure is "incoherent", thanks to Microsoft's new FastStart, and Sleep/Restore facilities. Once I had eliminated those facilities from Win10, the Linux system happily "saw" the (coherent) NTFS drives. Since I've done that, with Malicious Website Protection now turned on again, I haven't had a single Bad Pool Header. (but maybe next week.....). Normally I would have got at least 1 per day.

Regards, 

Link to post
Share on other sites

1 hour ago, usasma said:

Do you use BitDefender?  If so, please be sure to get the most updated version (older versions has BSOD issues).

Sorry, was that question aimed at me?

No, I stopped using Bit Defender some time ago. I use Avast Pro + Malwarebytes. The Bad Pool Header problems were only ever associated with MalwareBytes, and over 6 months, I kept hoping they would be fixed, but everytime I reloaded MalwareBytes and updated the software, it still had these same issues. Until I switched off Malicious Website, and now Fast Restart and Sleep (hyperfil.sys?)

Link to post
Share on other sites

Yes it was aimed at you.

Most of the problems that we've seen here have been due to BitDefender.
But, that's not the only thing that can cause it.

 

If you're interested in an analysis of your events, please create a new topic and upload this set of reports:
Please run this report collecting tool so that we can provide a complete analysis: (from the pinned topic at the top of the forum)  


FYI - I don't often use the Perfmon report, so if it doesn't work please just let me know.
NOTE:  On problem systems it can take up to 20 minutes for the log files to complete.  Please be patient and let it run.

If you still have problems with it running, there's an alternate tool here (direct download link):  https://github.com/blueelvis/BSOD-Inspector/releases/download/1.0.5/BSODInspector-1.0.5.exe

NOTE:
Please zip up the (.ZIP) files - do not use .RAR or other compression utilities. 
.ZIP is the type file that can be uploaded to the forums.

 

Link to post
Share on other sites

Thanks for the analysis tools, but I don't think I'll get the problem anymore; but if I do, I'll certainly use your suggestion.

When I have my system 'stable' at last, I'm not very inclined to go back and re-create all the issues I had with Fast Start messing up the file structure integrity.

I think the biggest issue I have, is that over the past 9 months, I'm not sure that MalwareBytes have acknowledged that THEY have a problem. I know correlation isn't causation, but the correlation of Bad Pool Headers with MalwareBytes being installed, simply drives people away from a very good product, without necessarily informing you of the reason. Thankfully, the general incidence rate doesn't appear to be so high, so it's likely to be a combination of factors. In my case, I did a clean install of Windows10Pro to an empty SSD, and I install 'defence' software quite quickly after that. The BPHs came quite soon after that. But I have a very unusual BIOS configuration. Actually, in my case, I think the real culprit is Microsoft, who have 'broken the file integrity' rules with Fast Start. People just have to code around such vandalism.....

Link to post
Share on other sites

  • 3 months later...

I know this is rather an old thread but I think it's worth posting to.

I had exactly the same problem, on both my computers, my home-built desktop and wife's laptop.  Both running Windows 8.1 Pro, Bitdefender Total Security 2015 & then 2016, and Malwarebytes Pro.  TCP/IP BSOD is a result of conflict between security suite & Malwarebytes Pro.

WHAT FIXED IT FOR ME was to;

disable "Malwarebytes>Settings>Detection and Protection>Malicious Website Protection"

& uncheck "Malwarebytes>Advanced Settings>Enable Malicious Website Protection when Malwarebytes Anti-Malware starts>"

And then wait for a fix.

Apparently there was a fix in either the latest version of Malwarebytes Pro or Bitdefender 2017, or both, because that is no longer a problem for me.

I have not seen even one instance on these boards of anyone admitting there's a problem with Malwarebytes & certain of the security suites out there.  Sadly, they will run you through every hoop known to man, have you send them log after log, blame your computer, memory, internet security etc.  but never tell you there's a conflict between your security suite & Malwarebytes.

I don't blame either Malwarebytes or Bitdefender or whoever for the conflict happening, these things happen, and in my case with Bitdefender, even though I turned off web browser checking/http scanning in Bitdefender it didn't actually turn off.  At least with Malwarebytes I could turn it off!

Still, I think they could be more forthcoming and admit the problem, tell people how to stop it until they fix it, and then fix it.

 

Link to post
Share on other sites

The MalwareBytes staff thoroughly investigated the problem between MalwareBytes and BitDefender.
BitDefender fixed it.  I do not post over at the BitDefender forums - so I have no clue about what or how they handled it.

As for other problems, a recent change in Windows (in the Fast Ring Insider build (beta)) caused problems with MalwareBytes.
Both the MalwareBytes staff and the Microsoft staff worked hard to fix it, and the fix happened rather quickly.

In both cases, workarounds were quickly posted so that users could continue to use the products that they were comfortable with.

 The price we pay for increased technological sophistication (and usefulness) is increased technological complexity.
So, when things break because of it, it's going to take a bit of time to fix it.
I applaud the hard work and dedication of the developers in hunting down and fixing these problems so rapidly.

Edited by usasma
Link to post
Share on other sites

8 hours ago, usasma said:

In both cases, workarounds were quickly posted so that users could continue to use the products that they were comfortable with.

Well this is just blatantly untrue!  The only "workaround" for the Bitdefender/Malwarebytes conflict resulting in BSOD was to disable Malicious Website Protection" and that was NEVER suggested by Malwarebytes. 

The "Fix" appears to have been Bitdefender version 2017 and i believe that came just about a year after the problem started!  Hardly a "quickly posted" anything!  As far as I know it's STILL the only fix for anyone running Malwarebytes Pro WITH Bitdefender IS 2016.

In any case, what point to your post?  It's just another defensive post by another thin skinned forum "expert".  This forum is filled with posts like this and offers nothing helpful.

Gratitude is reserved for unpaid forum members, like yourself, who take their time to actually help others.  That is, "help others", not attack them.

Otherwise, gratitude is reserved for paid employees who actually provide the product or service they sold and which I've paid money for, but then, that should work in both directions.

 

Link to post
Share on other sites

Regarding USASMA's comment, I can't let this self-congratulatory message go unchallenged (either).

This forum is full of BSOD-type failures, starting well into mid 2015. I myself reported a BAD POOL Header failure in March (over 6 months ago), and only got another "What antivirus are you using? " - I clearly stated MBAM and Avast - "and if it's BitDefender then etc etc..." - none of it in the slightest bit relevant to the problem. Lots of "please create a minidump" and "check your drivers are uptodate" and constant reference to BitDefender - none of it relevant to me. All these BSOD problems do not indicate stable software or a clean codebase (and I've worked in IT since 1968)

MBAM is the least stable software on my PC and laptop. No other software gives me this severity of failure. 

So maybe congratulations will be in order in six months time, but certainly not yet.

Link to post
Share on other sites

I am a volunteer and not associated with MalwareBytes in any way other than my posting in these forums in my free time.

I question your research methods and your qualifications.
Your accusations were posted without any supporting documentation.
 

borncofuzd says that the fix was supposed to be in MalwareBytes Pro or BitDefender 2017.
The actual fix was first released by BitDefender for BitDefender 2016 and was documented here in these forums.
As were the same suggestions for work arounds. 

My suggestions initially were to 1) stop MalwareBytes Pro from running at Windows startup; and 2) downgrade to BitDefender 2015.
I am not a developer, so I took a back seat once the MalwareBytes staff started working this problem in the forums and in their labs.
The remainder of the workarounds came from members of the staff.

As for cbx1 - it's a shame that you didn't think to include any substantiating documentation for your allegations.
I have worked with solving BSOD's since the days of Windows XP - and have worked with actually fixing computer since the late 1960's (rather than just "being in IT")..

I note that your post (linked to below) is full of things that you won't do - yet you expect the people here to help and support you despite that.
Because of the statements you made in your post, I also have to question the depth of you involvement in IT (since 1968).
You seem to display a huge gap in your knowledge of how these things are handled - both in the IT department and by the user.
And, heaven forbid, if someone should make a simple mistake you feel free to condemn them here.
Here is the link to the post that I suppose you are complaining about: 

I do not want to listen to you anymore.
As such, I have blocked both of you and will not respond to you.

Link to post
Share on other sites

Well, your decisions are your own: that's fine. 

I have no expertise in Intel or Microsoft. My expertise, however, runs in previous generations of mainframes, from the lowest level of hardware (imagine diagnosing a "once-a-month" user program failure, down to a 20ns spike on a single bit of a single arithmetic register within a mainframe the size of a built-in wardrobe, or flying to Melbourne Australia, to diagnose a random failure down to an intermittent crack in the copper track buried inside a motherboard) or "dump-cracking" - determining the failure point from the hexadecimal dump of memory and registers, through to kernel modifications, project management of software teams, product development, and ending with strategic IT decisions for a company spending $300m per year on IT alone. I don't say I am uniquely qualified to make judgement on a complex and often low-level diagnostic utility like anti-virus software: especially where it needs to operate in a hostile environment. 

I try to be careful when I say what I say. 

For example, over the past month, since receiving the latest Windows10 update, in the slow ring of the Insider program, I have been failing to load my notebook, first time, to the Windows login. It works on the second boot. This behaviour can be entirely eliminated by switching off Malware protection, without needing to switch off Malicious Website protection. This consistent behaviour has been tested and checked over the past 2 weeks or so. Have I raised an issue in this forum? No. Yesterday, I thought through some of the other actions I've taken in the past month: like installing a USB-Bluetooth adaptor. I've now deleted those drivers and uninstalled all their software. The system reloads with some new Intel bluetooth drivers I've never seen before. When I switch MBAM Malware protection on again, I now no longer get the load failures from before! Everything is fine!

So I'd say this looks like a driver failure. But why is it associated with MBAM? If MBAM is finding something it "doesn't like" in low memory (for example), why isn't this reported in a diagnostic, with an option to reboot or carry on (etc)? A consumer will naturally blame MBAM for the evidenced performance of the system. 

You know what is the worst strategic failure a company can encounter? It's not from software failure, or from cyber-insecurity. It's from the destruction of its reputation. 

If MBAM is to operate at these low levels to help customers secure their environments, then it needs to protect ITSELF from mis-diagnosis of failure. 

Regards,

Link to post
Share on other sites

On 11/28/2016 at 4:57 AM, usasma said:

I do not want to listen to you anymore.
As such, I have blocked both of you and will not respond to you.

Childish, and emblematic of the attitude I've observed by too many on these forums.  Better to just not respond than to do so defensively.  It doesn't reflect well on anyone, and it doesn't help anyone.

5 hours ago, cxb1 said:

So I'd say this looks like a driver failure. But why is it associated with MBAM? If MBAM is finding something it "doesn't like" in low memory (for example), why isn't this reported in a diagnostic, with an option to reboot or carry on (etc)? A consumer will naturally blame MBAM for the evidenced performance of the system. 

I'm a consumer, I'm also a user of computers over a period of 30 years.  I've been in positions/situations where I had to be my own tech support.  From the time we bought our 1st pc, a Compaq 286/10 running DOS in @1986 to today, because I just find it easier.  I also do repair & maintenance on many PCs for family & friends.  I build my own desktops & have for many years.  As a "Consumer" I will make the charge that what you expertly refer to as a "driver failure" is in fact a failure caused by MBAM! 

As I've said already, I don't blame Malwarebytes for any particular conflict, these things happen!  What I blame Malwarebytes for is not getting ahead of it.  Not admitting and owning a conflict, announcing it, giving guidance on how to deal with it temporarily while it being fixed, and then FIXING IT! 

Samsung had a problem with the Note 7.  Batteries were exploding/catching fire!  MIND YOU only a very small fraction of a single percent of the Note 7s they shipped exhibited any problem, but Samsung bought them all back!  Not once but TWICE!  Along with all the accessories that were sold for it!  Millions of units at a cost of billions of dollars!  They got in front of the problem, owned it, took responsibility for it and fixed it.  They will survive.

6 hours ago, cxb1 said:

You know what is the worst strategic failure a company can encounter? It's not from software failure, or from cyber-insecurity. It's from the destruction of its reputation.

This.  And the response example above doesn't help. 

I'm now at the point of removing Malwarebytes from my computer, my wife's computer and from the computers of everyone I help.  My trust has been eroded too far.  I see problems like a BSOD caused by a conflict that shouldn't be, that's denied by software company that claims to be compatible, the blame shifting, confrontational/argumentative responses by staff and forum "experts" and I think, why do I need this?

The protective benefits of the software is far outweighed by our computers crashing, or....I have to turn off one of the modules in order to stop the BSOD or in the latest example, Outlook can't connect to Microsoft Exchange with that module enabled.

So, go ahead, come at me again.  Try and make it look like I'M the unreasonable one.  Explain to me just how easily I could fix the problem if only I'd listen to my betters.

But I've been told that when I find myself hip deep in a hole, that the first thing I should do is stop digging.

I'm asking Malwarebytes to stop digging.  Fix the issues that are causing your users problems BEFORE you release version 3.  I will tell you, I for one have zero interest in your all in one package.  I'm even more not interested in it when the specialized version 2.xxx I'm currently using hasn't been fully useable for most of a year, and apparently will not be for some time to come.

Ok, rant over.  I probably won't post on these forums again.  Things will get fixed or they won't.  If they do, I'll continue using the product.  If they don't I'll move on.

In any case, I wish us all well.

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.