Analyzing a memory dump

[mgodinez]

Dear Greater I.T. Intellect,

I had a user that got the BSOD w/ the following stop message:

bad_pool_caller
stop error
(0x000000c2, 0x0000007, 0x000000cd4, 0x000000, 0x0012d898)

Seems like the 0xc2 stop error is all over the internet. Forums suggest running the ms debug tool for analysis. My output from the tool reads:

C:\Program Files\Support Tools>dumpchk c:\windows\minidump\minidump.dmp
Loading dump file c:\windows\minidump\minidump.dmp
----- 32 bit Kernel Mini Dump Analysis

DUMP_HEADER32:
MajorVersion 0000000f
MinorVersion 00000a28
DirectoryTableBase 3ca82000
PfnDataBase 81053000
PsLoadedModuleList 8054c150
PsActiveProcessHead 8054e1b8
MachineImageType 0000014c
NumberProcessors 00000001
BugCheckCode 000000c2
BugCheckParameter1 00000007
BugCheckParameter2 00000cd4
BugCheckParameter3 00000000
BugCheckParameter4 0012d898
PaeEnabled 00000000
KdDebuggerDataBlock 8053c2e0
MiniDumpFields 00000dff

TRIAGE_DUMP32:
ServicePackBuild 00000100
SizeOfDump 00010000
ValidOffset 0000fffc
ContextOffset 00000320
ExceptionOffset 000007d0
MmOffset 00001068
UnloadedDriversOffset 000010a0
PrcbOffset 00001878
ProcessOffset 000024c8
ThreadOffset 00002720
CallStackOffset 00002978
SizeOfCallStack 0000092c
DriverListOffset 00003538
DriverCount 00000089
StringPoolOffset 00005de8
StringPoolSize 00001318
BrokenDriverOffset 00000000
TriageOptions 00000041
TopOfStack ba7c36d4
DebuggerDataOffset 000032a8
DebuggerDataSize 00000290
DataBlocksOffset 00007100
DataBlocksCount 00000004


Windows XP Kernel Version 2600 (Service Pack 1) UP Free x86 compatible
Kernel base = 0x804d4000 PsLoadedModuleList = 0x8054c150
Debug session time: Mon Jan 31 12:42:35 2005
System Uptime: 0 days 3:57:04
start end module name
804d4000 806bb000 nt Checksum: 001DA0E9 Timestamp: Fri Oct 22 00:
28:47 2004 (4178B6AF)

Unloaded modules:
ba0ab000 ba0af000 PalmUSBD.sys Timestamp: unavailable (00000000)
f7f40000 f7f41000 drmkaud.sys Timestamp: unavailable (00000000)
ba0de000 ba10d000 MidiSyn.sys Timestamp: unavailable (00000000)
ba120000 ba143000 aec.sys Timestamp: unavailable (00000000)
ba60d000 ba61a000 DMusic.sys Timestamp: unavailable (00000000)
ba61d000 ba62b000 swmidi.sys Timestamp: unavailable (00000000)
f7d97000 f7d99000 splitter.sys Timestamp: unavailable (00000000)
f7c33000 f7c38000 Cdaudio.SYS Timestamp: unavailable (00000000)
f7683000 f7686000 Sfloppy.SYS Timestamp: unavailable (00000000)

Finished dump check

C:\Program Files\Support Tools>

I don't see anything apparent in the dump file. Any ideas on what the bad pool caller is addressing? Intuitively, I'm thinking bad RAM...ran the memtest tool as well w/ a slew of memory errors.

Much Obliged,

Mike Godinez
Seattle, WA

SUNNY!!!

 

[linney]

I think you have answered your own question what with all the RAM errors.

How to interpret a Stop 0xC2 or Stop 0x000000C2 error message on a Windows XP-based computer

http://support.microsoft.com/default.aspx?scid=kb;en-us;314492&FR=1&PA=1&SD=HSCH