Castoff

Sure, I've just sent you the most recent minidump and memory.dmp files via WeTransfer.

Unfortunately, Bitdefender does not appear to be the culprit. On your advice I removed Bitdefender and restarted my machine. Once I was back on the desktop the first thing I did was re-enable Malwarebyte's Web Protection. Once this was done and I and the Web Protection was shown as "on", I opened Chrome and before I even began browsing any sites was met by the same BAD_POOL_HEADER BSOD once again. As an aside, back in December when I first encountered this issue I was using Avast and the problem was equally prevalent at that time, so I consider it doubtful that Bitdefender is at fault in this instance.

+1 this. As described by the topic creator, this same issue that I experienced regularly around December is back with an absolute vengeance - it's never consistent, sometimes the system will behave itself for a good while, other times it will produce a BAD_POOL_HEADER BSOD shortly after the system starts and Chrome is launched. I've attached my logs below, on this occasion I'd been using Chrome to browse random sites for a while without encountering the BAD_POOL_HEADER error. I then launched Steam, signed into the Steam Community and launched Torment: Tides of Numenera, upon hitting the title screen for that game, the BAD_POOL_HEADER error hit (Chrome was still running in the background). Using Windows 10 64bit, which is up to date with the latest updates in conjunction with Malwarebytes 3.0 Premium and Bitdefender Total Security. Malwarebytes version: 3.0.6.1469 Component Package version: 1.0.75 Update Package version : 1.0.0 From a WhoCrashed report: On Tue 07/03/2017 16:55:39 your computer crashed crash dump file: C:\WINDOWS\Minidump\030717-17468-01.dmp This was probably caused by the following module: tcpip.sys (tcpip+0x15F665) Bugcheck code: 0x19 (0x20, 0xFFFFA504BBE1A170, 0xFFFFA504BBE1A190, 0x4020017) Error: BAD_POOL_HEADER file path: C:\WINDOWS\system32\drivers\tcpip.sys product: Microsoft® Windows® Operating System company: Microsoft Corporation description: TCP/IP Driver Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue). The crash took place in a standard Microsoft module. Your system configuration may be incorrect. Possibly this problem is caused by another driver on your system that cannot be identified at this time. On Tue 07/03/2017 16:55:39 your computer crashed crash dump file: C:\WINDOWS\memory.dmp This was probably caused by the following module: mwac.sys (mwac+0x6C8A) Bugcheck code: 0x19 (0x20, 0xFFFFA504BBE1A170, 0xFFFFA504BBE1A190, 0x4020017) Error: BAD_POOL_HEADER file path: C:\WINDOWS\system32\drivers\mwac.sys product: Malwarebytes Web Protection company: Malwarebytes description: Malwarebytes Web Protection Bug check description: This indicates that a pool header is corrupt. This appears to be a typical software driver bug and is not likely to be caused by a hardware problem. This might be a case of memory corruption. More often memory corruption happens because of software errors in buggy drivers, not because of faulty RAM modules. This problem might also be caused because of overheating (thermal issue). A third party driver was identified as the probable root cause of this system error. It is suggested you look for an update for the following driver: mwac.sys (Malwarebytes Web Protection, Malwarebytes). Google query: Malwarebytes BAD_POOL_HEADER Logs are attached, for now I've no choice but to disable the Web Protection in Malwarebytes, which I'm not too happy about but random BSODs are unacceptable. Addition.txt FRST.txt logs.zip