Bad_Pool_Caller dump file

Brian_143

Commendable
Aug 20, 2016
1
0
1,510
On Fri 8/19/2016 6:34:52 PM GMT your computer crashed
crash dump file: C:\WINDOWS\Minidump\081916-11828-01.dmp
This was probably caused by the following module: ntoskrnl.exe (nt+0x142940)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE001F3371768)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\ntoskrnl.exe
product: Microsoft® Windows® Operating System
company: Microsoft Corporation
description: NT Kernel & System
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
The crash took place in the Windows kernel. Possibly this problem is caused by another driver that cannot be identified at this time.



On Fri 8/19/2016 6:34:52 PM GMT your computer crashed
crash dump file: C:\WINDOWS\memory.dmp
This was probably caused by the following module: mfewfpk.sys (mfewfpk+0xFB8B)
Bugcheck code: 0xC2 (0x7, 0x126C, 0x0, 0xFFFFE001F3371768)
Error: BAD_POOL_CALLER
file path: C:\WINDOWS\system32\drivers\mfewfpk.sys
product: SYSCORE
company: McAfee, Inc.
description: Anti-Virus Mini-Firewall Driver
Bug check description: This indicates that the current thread is making a bad pool request.
This appears to be a typical software driver bug and is not likely to be caused by a hardware problem.
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: mfewfpk.sys (Anti-Virus Mini-Firewall Driver, McAfee, Inc.).
Google query: McAfee, Inc. BAD_POOL_CALLER
 
Solution
The problem could be the McAfee antivirus software, it could be a side effect of a old network driver or some other driver corrupting the virus scanners data. It is hard to tell without looking at the actual memory dump. Even then you might have to set debugging flags to be sure. If your virus scanner is up to date, I would update the the network drivers from the motherboard vendors website. It is pretty common for network drivers to cause antivirus software to mess up.
The problem could be the McAfee antivirus software, it could be a side effect of a old network driver or some other driver corrupting the virus scanners data. It is hard to tell without looking at the actual memory dump. Even then you might have to set debugging flags to be sure. If your virus scanner is up to date, I would update the the network drivers from the motherboard vendors website. It is pretty common for network drivers to cause antivirus software to mess up.
 
Solution