Windows BSOD - BAD_POOL_CALLER

[drakos]

Hi, I'm having trouble with my laptop, it seems it keeps BSODing if i use it for extended periods...or its just plain luck that it happens alot, either way its annoying.

The BSOD details are:

BAD_POOL_CALLER

***STOP: 0x000000C2 (0x00000007,0x00000CD4,0x020f0001,0x887E8618)

Ive searched google for some information and found people pointing out the following websites:

http://msdn2.microsoft.com/en-us/library/ms796120.aspx

http://support.microsoft.com/kb/q265879/

http://support.microsoft.com/kb/314492/EN-US/

http://support.microsoft.com/kb/254649/

http://support.microsoft.com/kb/315271

but apart from the usual ramblings of microsoft, most of the information there means nothing to me so i need some help understanding it.

One thing i did do however is download windows support tools and run dumpchk on the minidump, the results were as follows:

---------------------------

C:\Program Files\Support Tools>dumpchk -x C:\WINDOWS\Minidump\Mini042107-02.dmp

Loading dump file C:\WINDOWS\Minidump\Mini042107-02.dmp

----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:

MajorVersion 0000000f

MinorVersion 00000a28

DirectoryTableBase 0a580020

PfnDataBase 81086000

PsLoadedModuleList 8055c700

PsActiveProcessHead 80562818

MachineImageType 0000014c

NumberProcessors 00000002

BugCheckCode 000000c2

BugCheckParameter1 00000007

BugCheckParameter2 00000cd4

BugCheckParameter3 020f0005

BugCheckParameter4 89c740c8

PaeEnabled 00000001

KdDebuggerDataBlock 8054c2e0

MiniDumpFields 00000dff

TRIAGE_DUMP32:

ServicePackBuild 00000200

SizeOfDump 00010000

ValidOffset 0000fffc

ContextOffset 00000320

ExceptionOffset 000007d0

MmOffset 00001068

UnloadedDriversOffset 000010a0

PrcbOffset 00001878

ProcessOffset 000024c8

ThreadOffset 00002728

CallStackOffset 00002980

SizeOfCallStack 00000bb8

DriverListOffset 000037c8

DriverCount 0000008d

StringPoolOffset 000061a8

StringPoolSize 00001378

BrokenDriverOffset 00000000

TriageOptions 00000041

TopOfStack bad0b448

DebuggerDataOffset 00003538

DebuggerDataSize 00000290

DataBlocksOffset 00007520

DataBlocksCount 00000004

Windows XP Kernel Version 2600 (Service Pack 2) MP (2 procs) Free x86 compatible

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700

Debug session time: Sat Apr 21 11:30:06 2007

System Uptime: 0 days 0:09:15

start end module name

804d7000 806d8000 nt Checksum: 001E4186 Timestamp: Wed Feb 28 19:

45:54 2007 (45E5484A)

Unloaded modules:

b0c32000 b0c5d000 kmixer.sys Timestamp: unavailable (00000000)

b5383000 b53ae000 kmixer.sys Timestamp: unavailable (00000000)

b53ae000 b53d1000 aec.sys Timestamp: unavailable (00000000)

baf63000 baf64000 drmkaud.sys Timestamp: unavailable (00000000)

b54ee000 b54fb000 DMusic.sys Timestamp: unavailable (00000000)

b54fe000 b550c000 swmidi.sys Timestamp: unavailable (00000000)

badf0000 badf2000 splitter.sys Timestamp: unavailable (00000000)

b5a66000 b5a76000 Serial.SYS Timestamp: unavailable (00000000)

b57ad000 b57c1000 Parport.SYS Timestamp: unavailable (00000000)

bad90000 bad94000 kbdhid.sys Timestamp: unavailable (00000000)

bac80000 bac85000 Cdaudio.SYS Timestamp: unavailable (00000000)

bad8c000 bad8f000 Sfloppy.SYS Timestamp: unavailable (00000000)

bac78000 bac7d000 Flpydisk.SYS Timestamp: unavailable (00000000)

bac70000 bac77000 Fdc.SYS Timestamp: unavailable (00000000)

Finished dump check

---------------------------------

I have also run Windbg and the report shows (i think) that nltdi.sys is the problem (can someone back me up on this?)

*******************************************************************************

* *

* Bugcheck Analysis *

* *

*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck C2, {7, cd4, 20f0005, 89c740c8}

Unable to load image nltdi.sys, Win32 error 2

*** WARNING: Unable to verify timestamp for nltdi.sys

*** ERROR: Module load completed but symbols could not be loaded for nltdi.sys

Probably caused by : nltdi.sys ( nltdi+ac8 )

Followup: MachineOwner

---------

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: 020f0005, Memory contents of the pool block

Arg4: 89c740c8, Address of the block of pool being deallocated

Debugging Details:

------------------

POOL_ADDRESS: 89c740c8

FREED_POOL_TAG: Cnn.

BUGCHECK_STR: 0xc2_7_Cnn.

CUSTOMER_CRASH_COUNT: 2

DEFAULT_BUCKET_ID: DRIVER_FAULT

PROCESS_NAME: System

LAST_CONTROL_TRANSFER: from 8054a583 to 804f9f13

STACK_TEXT:

bad0b4c4 8054a583 000000c2 00000007 00000cd4 nt!KeBugCheckEx+0x1b

bad0b514 8054a95f 89c740c8 00000000 bad0b530 nt!ExFreePoolWithTag+0x2a3

bad0b524 b6d61ac8 89c740c8 bad0b540 b6d6e920 nt!ExFreePool+0xf

WARNING: Stack unwind information not available. Following frames may be wrong.

bad0b530 b6d6e920 b6d74df0 89c740c8 bad0b550 nltdi+0xac8

bad0b540 b6d65f99 89c740c8 89c740c8 bad0b8a4 nltdi+0xd920

bad0b550 b6d6876d 00000001 bad0b937 880fdf99 nltdi+0x4f99

bad0b8a4 b6d690af bad0b8e4 00000002 bad0b9a0 nltdi+0x776d

bad0b8b4 b6d64062 bad0b8e4 8905e6fc bad0bab8 nltdi+0x80af

bad0b9a0 b6d64de3 8905e620 8905e6fc bad0bab8 nltdi+0x3062

bad0ba90 b6d61923 88fb94f8 8905e620 8905e6fc nltdi+0x3de3

bad0bac0 804ef163 88fb94f8 8905e620 000000d5 nltdi+0x923

bad0bad0 b6d13544 88393758 89a7bd40 b6d2c98c nt!IopfCallDriver+0x31

bad0baf4 b6d13391 bad0bb1c 88393828 000000d5 netbt!TdiSendDatagram+0x1b8

bad0bb38 b6d13754 88393758 c0a801ff 000000d5 netbt!UdpSendDatagram+0x14c

bad0bb64 b6d13608 881abd68 88393758 00000000 netbt!SendDgram+0xe7

bad0bb94 b6d2d118 88393700 00000000 881c5008 netbt!SendDgramContinue+0xf8

bad0bbd0 b6d2d1aa 89bd829a 00000000 00000083 netbt!NbtSendDatagram+0x22b

bad0bc08 b6d138a4 88fb5d30 00000000 883244a0 netbt!NTSendDatagram+0x54

bad0bc24 804ef163 00fb5d30 881c50e4 881c5008 netbt!NbtDispatchInternalCtrl+0xe3

bad0bc34 b564f9c1 881c5008 bad0bca0 b56500c4 nt!IopfCallDriver+0x31

bad0bc40 b56500c4 881c5008 88fb5d30 bad0bc64 srv!StartIoAndWait+0x1b

bad0bca0 b564ffa5 883c7e48 883244a0 89bd8278 srv!SrvIssueSendDatagramRequest+0xb4

bad0bccc b564fda6 bad0bd1c e39e9010 e39e90bc srv!SrvSendDatagram+0xbe

bad0bd68 805759d5 89a36a38 88867b48 805637bc srv!SrvConfigurationThread+0x155

bad0bd7c 80537aff 88867b48 00000000 89e3c020 nt!IopProcessWorkItem+0x13

bad0bdac 805cea08 88867b48 00000000 00000000 nt!ExpWorkerThread+0xef

bad0bddc 8054546e 80537a10 00000001 00000000 nt!PspSystemThreadStartup+0x34

00000000 00000000 00000000 00000000 00000000 nt!KiThreadStartup+0x16

STACK_COMMAND: kb

FOLLOWUP_IP:

nltdi+ac8

b6d61ac8 ?? ???

SYMBOL_STACK_INDEX: 3

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nltdi

IMAGE_NAME: nltdi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 44906724

SYMBOL_NAME: nltdi+ac8

FAILURE_BUCKET_ID: 0xc2_7_Cnn._nltdi+ac8

BUCKET_ID: 0xc2_7_Cnn._nltdi+ac8

Followup: MachineOwner

---------

Edited April 21, 2007 by drakos

[rajputwarrior]

run memtest on your computer. bad pool caller is a pretty generic windows error, meaning it doesn't tell you anything

[Gowcra]

i was just reading thru that log, what are you doing usually when this thing happens chum? are you playing games, doing word, whats open? Certain times? temp inside the room? rain outside? anything could greatly help us. cheers chum

i will check this thread laters.

[drakos]

erm it can vary from running on battery power from chatting online...usually doesn't happen when playing games...ive uninstalled netlimiter and so far nothing has happened as far as BSOD's go so see if that fixed it or not

[windshear]

Sometimes I get the same error.

I think its because some error with the wireless drivers.

Happens to me with when bittorrent + kaspersky scan running at the same time, not always but sometimes.

[drakos]

im beginning to think its something to do with the wireless =\ usually happens when it goes through a period where it connects to the wireless network then disconnects again then like 10 seconds later connects again then goes through the same steps......