Random BSOD's while gaming, watching videos, or idle

Hello and welcome Josh sorry you have had to wait so long. Mate in the dump files there is an issue with a Windows update hence the machine working ok after the install - until the culprit is installed again. Finding it is another thing but what I usually do is system restore and wait for the failure and then look at the latest batch of updates were and try to winkle it out.
There is also a reference to MBAM too and I am at a loss as to why that is mentioned and this seems to be the theme in this old thread Arc is great at this stuff Windows 7 Random bsod caused by tcpip.sys .

Code:

*******************************************************************************
*                                                                             *
*                        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: fffffa800b64e5c0, The pool entry we were looking for within the page.
Arg3: fffffa800b64e5e0, The next pool entry.
Arg4: 0000000004020005, (reserved)
Debugging Details:
------------------

BUGCHECK_STR:  0x19_20
POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff800034bc100
GetUlongFromAddress: unable to read from fffff800034bc1c0
 fffffa800b64e5c0 Nonpaged pool
CUSTOMER_CRASH_COUNT:  1
DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT
PROCESS_NAME:  mbamservice.ex
CURRENT_IRQL:  0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) amd64fre
LAST_CONTROL_TRANSFER:  from fffff800033b7cbe to fffff80003282ec0
STACK_TEXT:  
fffff880`02a80398 fffff800`033b7cbe : 00000000`00000019 00000000`00000020 fffffa80`0b64e5c0 fffffa80`0b64e5e0 : nt!KeBugCheckEx
fffff880`02a803a0 fffff880`01928d2d : 00000000`00000012 00000000`00000004 00000000`676e7049 fffff880`05fbf068 : nt!ExFreePool+0xd8a
fffff880`02a80450 fffff880`01636066 : 00000000`00000000 fffff880`016320c3 00000000`00000000 fffffa80`0b0ee790 : tcpip!IppInspectBuildHeaders+0x65d
fffff880`02a80730 fffff880`0920612d : 00000000`0000002c 00000000`00000014 00000000`00000000 fffffa80`0b974a80 : fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+0x20a
fffff880`02a807d0 00000000`0000002c : 00000000`00000014 00000000`00000000 fffffa80`0b974a80 fffffa80`0b974a94 : mwac+0x612d
fffff880`02a807d8 00000000`00000014 : 00000000`00000000 fffffa80`0b974a80 fffffa80`0b974a94 fffff700`00000006 : 0x2c
fffff880`02a807e0 00000000`00000000 : fffffa80`0b974a80 fffffa80`0b974a94 fffff700`00000006 00000000`00000000 : 0x14

STACK_COMMAND:  kb
FOLLOWUP_IP: 
fwpkclnt!FwpsConstructIpHeaderForTransportPacket0+20a
fffff880`01636066 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:  533f5b09
IMAGE_VERSION:  6.1.7601.18438
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
---------

Josh this smacks of something quite wrong with either the power adaptor (check the volts mate with a digital meter or that internal charging system is failing.

Also it seems that the laptop can function perfectly fine just running off of battery, and not charging it,