Solved Inconsistant BSOD error 0x19

[Mirikaj]

Hello, I have been experiencing this Bugcheck for about a week now and would appreciate any assitance you guys could offer I have the DM log as well as a minidmp of the crash (will upload the zip if needed).
Thanks

 

[Mirikaj]

Bumping this up, still need some assistance.

 

[koolkat77]

Patience buddy. Patience.

All your blue screens seemed to be caused by the Malware Bytes software. Check for an update, or uninstall the software to test if they stop.

Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\JAKE-Tue_05_26_2015_125234_02\052415-22183-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0364f000 PsLoadedModuleList = 0xfffff800`03893670
Debug session time: Mon May 25 09:02:05.263 2015 (UTC + 6:00)
System Uptime: 0 days 16:24:10.120
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
..................................
Loading User Symbols
Loading unloaded module list
..................
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa8008da1e50, fffffa8008da1e70, 4020002}

*** 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+20a )

Followup: MachineOwner
---------

Microsoft (R) Windows Debugger Version 6.3.9600.16384 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Users\YUSRA\Downloads\Compressed\JAKE-Tue_05_26_2015_125234_02\052615-22869-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available


************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*c:\symbols*http://msdl.microsoft.com/download/symbols
Executable search path is: 
Windows 7 Kernel Version 7601 (Service Pack 1) MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.17944.amd64fre.win7sp1_gdr.120830-0333
Machine Name:
Kernel base = 0xfffff800`0360d000 PsLoadedModuleList = 0xfffff800`03851670
Debug session time: Tue May 26 23:25:35.900 2015 (UTC + 6:00)
System Uptime: 0 days 0:12:33.102
Loading Kernel Symbols
.

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

..............................................................
................................................................
...............................
Loading User Symbols
Loading unloaded module list
.....
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa800930b970, fffffa800930b990, 4020009}

*** 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+20a )

Followup: MachineOwner
---------

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 19, {20, fffffa800c964160, fffffa800c964180, 4020016}

*** 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+20a )

Followup: MachineOwner
---------

5: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

BAD_POOL_HEADER (19)
The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arguments:
Arg1: 0000000000000020, a pool block header size is corrupt.
Arg2: fffffa800c964160, The pool entry we were looking for within the page.
Arg3: fffffa800c964180, The next pool entry.
Arg4: 0000000004020016, (reserved)

Debugging Details:
------------------


BUGCHECK_STR:  0x19_20

POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800038b7100
GetUlongFromAddress: unable to read from fffff800038b71c0
 fffffa800c964160 Nonpaged pool

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

PROCESS_NAME:  mbamservice.ex

CURRENT_IRQL:  0

ANALYSIS_VERSION: 6.3.9600.16384 (debuggers(dbg).130821-1623) amd64fre

LAST_CONTROL_TRANSFER:  from fffff800037b2cae to fffff80003687fc0

STACK_TEXT:  
fffff880`0cc96258 fffff800`037b2cae : 00000000`00000019 00000000`00000020 fffffa80`0c964160 fffffa80`0c964180 : nt!KeBugCheckEx
fffff880`0cc96260 fffff880`017a21dd : 00000000`00000008 00000000`00000008 00000000`676e7049 fffff880`0586f3c6 : nt!ExDeferredFreePool+0x12da
fffff880`0cc96310 fffff880`01884046 : 00000000`00000000 fffff880`018800c3 00000000`00000000 fffffa80`07b271e0 : tcpip!IppInspectBuildHeaders+0x65d
fffff880`0cc965f0 fffff880`0bc2c12d : 00000000`00000000 00000000`00000014 00000000`00000000 fffffa80`0adc89f0 : fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+0x20a
fffff880`0cc96690 00000000`00000000 : 00000000`00000014 00000000`00000000 fffffa80`0adc89f0 fffffa80`0adc8a04 : mwac+0x612d


STACK_COMMAND:  kb

FOLLOWUP_IP: 
fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a
fffff880`01884046 85c0            test    eax,eax

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: fwpkclnt

IMAGE_NAME:  fwpkclnt.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  5034f679

IMAGE_VERSION:  6.1.7601.17939

FAILURE_BUCKET_ID:  X64_0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a

BUCKET_ID:  X64_0x19_20_fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x19_20_fwpkclnt!fwpsconstructipheaderfortransportpacket0+20a

FAILURE_ID_HASH:  {863e217f-0693-d7a3-6d21-a4c5a3f57698}

Followup: MachineOwner
---------

5: kd> lmvm fwpkclnt
start             end                 module name
fffff880`0187a000 fffff880`018c4000   fwpkclnt   (pdb symbols)          c:\symbols\fwpkclnt.pdb\B2E52E809450423B900BC83AA59054011\fwpkclnt.pdb
    Loaded symbol image file: fwpkclnt.sys
    Mapped memory image file: c:\symbols\fwpkclnt.sys\5034F6794a000\fwpkclnt.sys
    Image path: \SystemRoot\System32\drivers\fwpkclnt.sys
    Image name: fwpkclnt.sys
    Timestamp:        Wed Aug 22 21:10:49 2012 (5034F679)
    CheckSum:         00055FFF
    ImageSize:        0004A000
    File version:     6.1.7601.17939
    Product version:  6.1.7601.17939
    File flags:       0 (Mask 3F)
    File OS:          40004 NT Win32
    File type:        2.0 Dll
    File date:        00000000.00000000
    Translations:     0409.04b0
    CompanyName:      Microsoft Corporation
    ProductName:      Microsoft® Windows® Operating System
    InternalName:     fwpkclnt.sys
    OriginalFilename: fwpkclnt.sys
    ProductVersion:   6.1.7601.17939
    FileVersion:      6.1.7601.17939 (win7sp1_gdr.120822-0331)
    FileDescription:  FWP/IPsec Kernel-Mode API
    LegalCopyright:   © Microsoft Corporation. All rights reserved.

 

[Mirikaj]

I'm sorry if I seemed impatient, I did not mean to in the slightest. I will give your suggestion a try and report back in a bit.

 

[Mirikaj]

Well, it seems as if my problem is gone, thank you for the assistance koolkat.

 

[koolkat77]

No problem. post if you have further issues.