Answered by:
BSOD - BAD POOL CALLER
Question
-
I keep getting the BSOD every time I boot my PC and the error is always BAD POOL CALLER. I usually have to try a few times before the PC boots successfully. Please advise me on how to resolve the error. Below is a link to the dump files. Thanks for your help.
https://onedrive.live.com/redir?resid=B96A3EC185768282!150&authkey=!AGfUSn9X55-aElI&ithint=file%2czip
Wednesday, June 3, 2015 9:17 AM
Answers
-
@Acreed02
Um no. Although running a system file check cannot hurt.
@IreriD
These were all Related to btmhsf.sys Bluetooth HighSpeed Filter Driver from Intel Corporation.. Yours is 6 years old. Completely remove the current driver and install the newest driver available
Microsoft (R) Windows Debugger Version 10.0.10075.9 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\zigza\Desktop\060315-71245-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654 Machine Name: Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e46890 Debug session time: Wed Jun 3 02:18:22.214 2015 (UTC - 4:00) System Uptime: 0 days 0:00:53.088 Loading Kernel Symbols ............................................................... ................................................................ ......... Loading User Symbols Loading unloaded module list .. No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, 109b, d0040, fffffa800ad39920} *** WARNING: Unable to verify timestamp for btmhsf.sys *** ERROR: Module load completed but symbols could not be loaded for btmhsf.sys GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 Probably caused by : btmhsf.sys ( btmhsf+668f ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 0000000000000007, Attempt to free pool which was already freed Arg2: 000000000000109b, (reserved) Arg3: 00000000000d0040, Memory contents of the pool block Arg4: fffffa800ad39920, Address of the block of pool being deallocated Debugging Details: ------------------ GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 SYSTEM_SKU: A6X05UAR#ABA SYSTEM_VERSION: 068B210014204710000620100 BIOS_DATE: 05/21/2012 BASEBOARD_PRODUCT: 1802 BASEBOARD_VERSION: 10.59 BUGCHECK_P1: 7 BUGCHECK_P2: 109b BUGCHECK_P3: d0040 BUGCHECK_P4: fffffa800ad39920 POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 fffffa800ad39920 Nonpaged pool BUGCHECK_STR: 0xc2_7 CPU_COUNT: 8 CPU_MHZ: 893 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 2a CPU_STEPPING: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 10.0.10075.9 amd64fre LAST_CONTROL_TRANSFER: from fffff80002daabf9 to fffff80002c73a40 STACK_TEXT: fffff880`0337db98 fffff800`02daabf9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`000d0040 : nt!KeBugCheckEx fffff880`0337dba0 fffff880`0b4a068f : 00000000`00000500 0000057f`00000000 fffffa80`004d6253 fffffa80`09fc2000 : nt!ExAllocatePoolWithTag+0x1951 fffff880`0337dc50 00000000`00000500 : 0000057f`00000000 fffffa80`004d6253 fffffa80`09fc2000 fffff880`009b3180 : btmhsf+0x668f fffff880`0337dc58 0000057f`00000000 : fffffa80`004d6253 fffffa80`09fc2000 fffff880`009b3180 0000057f`f603ffd8 : 0x500 fffff880`0337dc60 fffffa80`004d6253 : fffffa80`09fc2000 fffff880`009b3180 0000057f`f603ffd8 fffffa80`09fc0040 : 0x0000057f`00000000 fffff880`0337dc68 fffffa80`09fc2000 : fffff880`009b3180 0000057f`f603ffd8 fffffa80`09fc0040 fffffa80`09fc0040 : 0xfffffa80`004d6253 fffff880`0337dc70 fffff880`009b3180 : 0000057f`f603ffd8 fffffa80`09fc0040 fffffa80`09fc0040 00000000`00000001 : 0xfffffa80`09fc2000 fffff880`0337dc78 0000057f`f603ffd8 : fffffa80`09fc0040 fffffa80`09fc0040 00000000`00000001 fffff880`00f29c70 : 0xfffff880`009b3180 fffff880`0337dc80 fffffa80`09fc0040 : fffffa80`09fc0040 00000000`00000001 fffff880`00f29c70 00000000`00000000 : 0x0000057f`f603ffd8 fffff880`0337dc88 fffffa80`09fc0040 : 00000000`00000001 fffff880`00f29c70 00000000`00000000 fffff880`0b49bf17 : 0xfffffa80`09fc0040 fffff880`0337dc90 00000000`00000001 : fffff880`00f29c70 00000000`00000000 fffff880`0b49bf17 0000057f`f603ffd8 : 0xfffffa80`09fc0040 fffff880`0337dc98 fffff880`00f29c70 : 00000000`00000000 fffff880`0b49bf17 0000057f`f603ffd8 0000057f`f603ffd8 : 0x1 fffff880`0337dca0 00000000`00000000 : fffff880`0b49bf17 0000057f`f603ffd8 0000057f`f603ffd8 fffffa80`09fc02a0 : Wdf01000!FxWmiIrpHandler::m_WmiDispatchTable+0x1030 STACK_COMMAND: kb FOLLOWUP_IP: btmhsf+668f fffff880`0b4a068f ?? ??? SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: btmhsf+668f FOLLOWUP_NAME: MachineOwner MODULE_NAME: btmhsf IMAGE_NAME: btmhsf.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e0232f6 FAILURE_BUCKET_ID: X64_0xc2_7_btmhsf+668f BUCKET_ID: X64_0xc2_7_btmhsf+668f PRIMARY_PROBLEM_CLASS: X64_0xc2_7_btmhsf+668f ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xc2_7_btmhsf+668f FAILURE_ID_HASH: {fe410e6e-e878-9d52-96ca-53de352a183e} Followup: MachineOwner ---------
Wanikiya and Dyami--Team Zigzag
- Edited by ZigZag3143x Wednesday, June 3, 2015 12:28 PM
- Proposed as answer by Kate LiMicrosoft employee Thursday, June 4, 2015 6:10 AM
- Marked as answer by Kate LiMicrosoft employee Friday, June 5, 2015 8:43 AM
Wednesday, June 3, 2015 12:27 PM
All replies
-
The dump files all show you are crashing on ntoskrnl.exe, which unfortunately can be caused by multiple things. I would start by downloading your hard drive manufacturers scan to test the hard drive. I would then test your memory using memtest - this can be found here:http://www.memtest86.com/download.htm
I would then run sfc /scannow from an elevated command prompt.
If neither of those scans come up with any errors I'd begin to update/reinstall all of your drivers, and turn off any anti-virus you may have running.
Keep in mind that a clean install may be the best and quickest solution to the problem.
- Edited by Acreed02 Wednesday, June 3, 2015 12:27 PM
Wednesday, June 3, 2015 12:21 PM -
@Acreed02
Um no. Although running a system file check cannot hurt.
@IreriD
These were all Related to btmhsf.sys Bluetooth HighSpeed Filter Driver from Intel Corporation.. Yours is 6 years old. Completely remove the current driver and install the newest driver available
Microsoft (R) Windows Debugger Version 10.0.10075.9 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\zigza\Desktop\060315-71245-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Symbol Path validation summary ************** Response Time (ms) Location Deferred SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols Symbol search path is: SRV*D:\Symbols*http://msdl.microsoft.com/download/symbols Executable search path is: Windows 7 Kernel Version 7601 (Service Pack 1) MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Built by: 7601.18798.amd64fre.win7sp1_gdr.150316-1654 Machine Name: Kernel base = 0xfffff800`02c01000 PsLoadedModuleList = 0xfffff800`02e46890 Debug session time: Wed Jun 3 02:18:22.214 2015 (UTC - 4:00) System Uptime: 0 days 0:00:53.088 Loading Kernel Symbols ............................................................... ................................................................ ......... Loading User Symbols Loading unloaded module list .. No .natvis files found at C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\Visualizers. ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* Use !analyze -v to get detailed debugging information. BugCheck C2, {7, 109b, d0040, fffffa800ad39920} *** WARNING: Unable to verify timestamp for btmhsf.sys *** ERROR: Module load completed but symbols could not be loaded for btmhsf.sys GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 Probably caused by : btmhsf.sys ( btmhsf+668f ) Followup: MachineOwner --------- 4: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* BAD_POOL_CALLER (c2) The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc. Arguments: Arg1: 0000000000000007, Attempt to free pool which was already freed Arg2: 000000000000109b, (reserved) Arg3: 00000000000d0040, Memory contents of the pool block Arg4: fffffa800ad39920, Address of the block of pool being deallocated Debugging Details: ------------------ GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 SYSTEM_SKU: A6X05UAR#ABA SYSTEM_VERSION: 068B210014204710000620100 BIOS_DATE: 05/21/2012 BASEBOARD_PRODUCT: 1802 BASEBOARD_VERSION: 10.59 BUGCHECK_P1: 7 BUGCHECK_P2: 109b BUGCHECK_P3: d0040 BUGCHECK_P4: fffffa800ad39920 POOL_ADDRESS: GetPointerFromAddress: unable to read from fffff80002eb0100 GetUlongPtrFromAddress: unable to read from fffff80002eb02e0 GetUlongPtrFromAddress: unable to read from fffff80002eb0490 fffffa800ad39920 Nonpaged pool BUGCHECK_STR: 0xc2_7 CPU_COUNT: 8 CPU_MHZ: 893 CPU_VENDOR: GenuineIntel CPU_FAMILY: 6 CPU_MODEL: 2a CPU_STEPPING: 7 CUSTOMER_CRASH_COUNT: 1 DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT PROCESS_NAME: System CURRENT_IRQL: 0 ANALYSIS_VERSION: 10.0.10075.9 amd64fre LAST_CONTROL_TRANSFER: from fffff80002daabf9 to fffff80002c73a40 STACK_TEXT: fffff880`0337db98 fffff800`02daabf9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`000d0040 : nt!KeBugCheckEx fffff880`0337dba0 fffff880`0b4a068f : 00000000`00000500 0000057f`00000000 fffffa80`004d6253 fffffa80`09fc2000 : nt!ExAllocatePoolWithTag+0x1951 fffff880`0337dc50 00000000`00000500 : 0000057f`00000000 fffffa80`004d6253 fffffa80`09fc2000 fffff880`009b3180 : btmhsf+0x668f fffff880`0337dc58 0000057f`00000000 : fffffa80`004d6253 fffffa80`09fc2000 fffff880`009b3180 0000057f`f603ffd8 : 0x500 fffff880`0337dc60 fffffa80`004d6253 : fffffa80`09fc2000 fffff880`009b3180 0000057f`f603ffd8 fffffa80`09fc0040 : 0x0000057f`00000000 fffff880`0337dc68 fffffa80`09fc2000 : fffff880`009b3180 0000057f`f603ffd8 fffffa80`09fc0040 fffffa80`09fc0040 : 0xfffffa80`004d6253 fffff880`0337dc70 fffff880`009b3180 : 0000057f`f603ffd8 fffffa80`09fc0040 fffffa80`09fc0040 00000000`00000001 : 0xfffffa80`09fc2000 fffff880`0337dc78 0000057f`f603ffd8 : fffffa80`09fc0040 fffffa80`09fc0040 00000000`00000001 fffff880`00f29c70 : 0xfffff880`009b3180 fffff880`0337dc80 fffffa80`09fc0040 : fffffa80`09fc0040 00000000`00000001 fffff880`00f29c70 00000000`00000000 : 0x0000057f`f603ffd8 fffff880`0337dc88 fffffa80`09fc0040 : 00000000`00000001 fffff880`00f29c70 00000000`00000000 fffff880`0b49bf17 : 0xfffffa80`09fc0040 fffff880`0337dc90 00000000`00000001 : fffff880`00f29c70 00000000`00000000 fffff880`0b49bf17 0000057f`f603ffd8 : 0xfffffa80`09fc0040 fffff880`0337dc98 fffff880`00f29c70 : 00000000`00000000 fffff880`0b49bf17 0000057f`f603ffd8 0000057f`f603ffd8 : 0x1 fffff880`0337dca0 00000000`00000000 : fffff880`0b49bf17 0000057f`f603ffd8 0000057f`f603ffd8 fffffa80`09fc02a0 : Wdf01000!FxWmiIrpHandler::m_WmiDispatchTable+0x1030 STACK_COMMAND: kb FOLLOWUP_IP: btmhsf+668f fffff880`0b4a068f ?? ??? SYMBOL_STACK_INDEX: 2 SYMBOL_NAME: btmhsf+668f FOLLOWUP_NAME: MachineOwner MODULE_NAME: btmhsf IMAGE_NAME: btmhsf.sys DEBUG_FLR_IMAGE_TIMESTAMP: 4e0232f6 FAILURE_BUCKET_ID: X64_0xc2_7_btmhsf+668f BUCKET_ID: X64_0xc2_7_btmhsf+668f PRIMARY_PROBLEM_CLASS: X64_0xc2_7_btmhsf+668f ANALYSIS_SOURCE: KM FAILURE_ID_HASH_STRING: km:x64_0xc2_7_btmhsf+668f FAILURE_ID_HASH: {fe410e6e-e878-9d52-96ca-53de352a183e} Followup: MachineOwner ---------
Wanikiya and Dyami--Team Zigzag
- Edited by ZigZag3143x Wednesday, June 3, 2015 12:28 PM
- Proposed as answer by Kate LiMicrosoft employee Thursday, June 4, 2015 6:10 AM
- Marked as answer by Kate LiMicrosoft employee Friday, June 5, 2015 8:43 AM
Wednesday, June 3, 2015 12:27 PM -
Zig,
Interesting, what program are you using to analyze those DMP files? Here is what I get on all files I analyze.
Probably caused by : ntoskrnl.exe ( nt+72a40 )
Followup: MachineOwner
---------
4: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************
BAD_POOL_CALLER (c2)
The current thread is making a bad pool request. Typically this is at a bad IRQL level or double freeing the same allocation, etc.
Arguments:
Arg1: 0000000000000007, Attempt to free pool which was already freed
Arg2: 000000000000109b, (reserved)
Arg3: 00000000000d0040, Memory contents of the pool block
Arg4: fffffa800ad39920, Address of the block of pool being deallocated
Debugging Details:
------------------
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** Type referenced: nt!_POOL_HEADER ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** Type referenced: nt!_KPRCB ***
*** ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: nt
FAULTING_MODULE: fffff80002c01000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 5507a73c
POOL_ADDRESS: fffffa800ad39920
BUGCHECK_STR: 0xc2_7
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80002daabf9 to fffff80002c73a40
STACK_TEXT:
fffff880`0337db98 fffff800`02daabf9 : 00000000`000000c2 00000000`00000007 00000000`0000109b 00000000`000d0040 : nt+0x72a40
fffff880`0337dba0 00000000`000000c2 : 00000000`00000007 00000000`0000109b 00000000`000d0040 fffffa80`0ad39920 : nt+0x1a9bf9
fffff880`0337dba8 00000000`00000007 : 00000000`0000109b 00000000`000d0040 fffffa80`0ad39920 00000000`004d6253 : 0xc2
fffff880`0337dbb0 00000000`0000109b : 00000000`000d0040 fffffa80`0ad39920 00000000`004d6253 fffffa80`08982610 : 0x7
fffff880`0337dbb8 00000000`000d0040 : fffffa80`0ad39920 00000000`004d6253 fffffa80`08982610 00000000`00000020 : 0x109b
fffff880`0337dbc0 fffffa80`0ad39920 : 00000000`004d6253 fffffa80`08982610 00000000`00000020 00000000`00000000 : 0xd0040
fffff880`0337dbc8 00000000`004d6253 : fffffa80`08982610 00000000`00000020 00000000`00000000 00000000`000007ff : 0xfffffa80`0ad39920
fffff880`0337dbd0 fffffa80`08982610 : 00000000`00000020 00000000`00000000 00000000`000007ff 00000000`00000000 : 0x4d6253
fffff880`0337dbd8 00000000`00000020 : 00000000`00000000 00000000`000007ff 00000000`00000000 00000000`00000063 : 0xfffffa80`08982610
fffff880`0337dbe0 00000000`00000000 : 00000000`000007ff 00000000`00000000 00000000`00000063 fffffa80`09fe7b00 : 0x20
STACK_COMMAND: kb
FOLLOWUP_IP:
nt+72a40
fffff800`02c73a40 48894c2408 mov qword ptr [rsp+8],rcx
SYMBOL_STACK_INDEX: 0
SYMBOL_NAME: nt+72a40
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: ntoskrnl.exe
BUCKET_ID: WRONG_SYMBOLS
Followup: MachineOwner
Wednesday, June 3, 2015 12:31 PM -
Acreed02
I figured as much, like you I am using windows debugger. Your problem is that (as it says) you do not have the "symbols" (or the path to them is wrong) and because of that WInDB is confused.
You need to download the "symbols" for any OS you want to Analyze. If you do vista, 7,8, &10 thatcomes to about 50Gb.'
If interested email me from the email on my profile page.
*************************************************************************
*** ***
*** ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
Wanikiya and Dyami--Team Zigzag
- Edited by ZigZag3143x Wednesday, June 3, 2015 12:43 PM
Wednesday, June 3, 2015 12:43 PM -
Thanks Acreed02 and Team Zigzag for your response.
@Zigzag
I removed the blue tooth driver and I haven't gotten the BSOD after booting the PC a couple of times. Removing the driver appears to have resolved the error.
Thank you so much for your help.
Cheers!
Thursday, June 4, 2015 11:40 PM -
Thanks for letting us know
Wanikiya and Dyami--Team Zigzag
Thursday, June 4, 2015 11:43 PM
