Bad pool caller

[Lenine]

Hey,

I just got a new PC and installed windows and every few hours I keep getting a blue screen with alot of error messages saying Bad pool caller. I have to restart the PC.

Usually this happens when I am away from the comp so I'm not sure if any particular program initiated it.

Does anyone know what's up with this and how I can fix it?

 

[bendixG15]

http://www.google.com/search?sourceid=n...GGLG:2006-14,GGLG:en&q=Bad+pool+caller

 

[Lenine]

Originally posted by: bendixG15
http://www.google.com/search?sourceid=n...GGLG:2006-14,GGLG:en&q=Bad+pool+caller

yeah that doesn't help much the error can be one of a million things.

Anyway... I managed to run windows debugger on the memory dump file and this is the output

1: 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: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 02060001, Memory contents of the pool block
Arg4: 88c97100, Address of the block of pool being deallocated

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


POOL_ADDRESS: 88c97100 Nonpaged pool

FREED_POOL_TAG: TCPc

BUGCHECK_STR: 0xc2_7_TCPc

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 8054a583 to 804f9c37

STACK_TEXT:
bacf791c 8054a583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b
bacf796c b7a4b417 88c97100 00000000 bacf79b4 nt!ExFreePoolWithTag+0x2a3
bacf797c b7a4aca7 8664e200 8664e270 8664e270 tcpip!TCPClose+0x16
bacf79b4 b79db6e1 89334860 8664e200 b79dafe1 tcpip!TCPDispatch+0x101
WARNING: Stack unwind information not available. Following frames may be wrong.
bacf79c0 b79dafe1 89334860 8664e200 00000002 vsdatant+0x3e6e1
bacf79e0 b79df68e 88f00e20 88f00000 8664e270 vsdatant+0x3dfe1
bacf79f4 b79db665 89334860 8664e200 8664e210 vsdatant+0x4268e
bacf7a1c b79db502 88f00cc0 b79db672 00000000 vsdatant+0x3e665
bacf7a24 b79db672 00000000 89bbc308 8664e200 vsdatant+0x3e502
bacf7a34 80544421 89c575e0 bab38570 89c575e0 vsdatant+0x3e672
bacf7a44 804efd17 bacf7a90 baa92c87 4efd1700 nt!KeSynchronizeExecution+0x21
89c575e0 89c575e0 89c575e8 89c575e8 89c575f0 nt!IoReleaseCancelSpinLock+0x11
baa88a49 565351ec 8b0c758b 00009886 3d8b5700 0x89c575e0
baa88a4d 8b0c758b 00009886 3d8b5700 baa8b438 0x565351ec
baa88a51 00000000 3d8b5700 baa8b438 035b026a 0x8b0c758b


STACK_COMMAND: kb

FOLLOWUP_IP:
vsdatant+3e6e1
b79db6e1 c20c00 ret 0xc

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 4

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: vsdatant+3e6e1

MODULE_NAME: vsdatant

IMAGE_NAME: vsdatant.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 4419a4ed

FAILURE_BUCKET_ID: 0xc2_7_TCPc_vsdatant+3e6e1

BUCKET_ID: 0xc2_7_TCPc_vsdatant+3e6e1

Followup: MachineOwner

My other 4 crash files are also similar except they talk about ntoskrnl.exe

0: 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: 00000007, Attempt to free pool which was already freed
Arg2: 00000cd4, (reserved)
Arg3: 02060008, Memory contents of the pool block
Arg4: 88a9b670, Address of the block of pool being deallocated

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


POOL_ADDRESS: 88a9b670

FREED_POOL_TAG: TCPc

BUGCHECK_STR: 0xc2_7_TCPc

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

LAST_CONTROL_TRANSFER: from 00000000 to 804f9c37

STACK_TEXT:
bacf3908 00000000 02060008 88a9b670 00000000 nt!PspReaper+0x25


STACK_COMMAND: kb

FOLLOWUP_IP:
nt!PspReaper+25
804f9c37 5d pop ebp

FAULTING_SOURCE_CODE:


SYMBOL_STACK_INDEX: 0

FOLLOWUP_NAME: MachineOwner

SYMBOL_NAME: nt!PspReaper+25

MODULE_NAME: nt

IMAGE_NAME: ntoskrnl.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 42250a1e

FAILURE_BUCKET_ID: 0xc2_7_TCPc_nt!PspReaper+25

BUCKET_ID: 0xc2_7_TCPc_nt!PspReaper+25

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

From what I gather both ntoskrnl.exe and vsdatant.sys are causing me to crash. Am I reading the files right?


Also, I'm going to uninstall zonealarm but how do I fix ntoskrnl.exe?

 

[stu1811]

I just ran into the same issue. Ram was bad. Run MemTest. Find the bad stick and replace it.

 

[xtknight]

Hmm...I vaguely remember somebody having a problem with ZoneAlarm before causing BSODs. Only thing to do would be to remove it out of the Winsock LSP stack but then it won't be a firewall anymore, so you might as well just uninstall it. Of course unless this is a hardware problem (memory?)

 

[Lenine]

I ran memtest 86+ v 1.55 in my BIOS and it passed twice with no errors.

Are you sure it is my hardware? No one can read the debug file to give me an exact answer? If I know it is definitely my hardware then atleast I can replace it.

I uninstalled zonealarm so hopefully that solves one of my problems.

 

[stu1811]

try downloading the latest version of memtest and let it run overnight.