• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 4091
  • Last Modified:

Blue Screen Stop Error: BAD_POOL_CALLER

Blue Screen Stop Error:
STOP: 0x000000C2 (0x00000007, 0x00000CD4, 0x000004C0, 0xE14D0040)

What is causing this?  The computer is Windows XP XP2.
  • 5
  • 4
  • 3
  • +2
2 Solutions
This can be caused by a bad driver or buggy software.


A kernel-mode process or driver incorrectly attempted to perform memory operations. Typically, a faulty driver or buggy software causes this.

0x000000C2 {KB 265879} Win 2000, Win XP
0x000000C2: BAD_POOL_CALLER {KB 310527} Win XP (upgrading Compaq Professional Workstation AP550 from Win 2000 to XP)
Computer with ATI RAGE FURY MAXX Video Adapter Stops Responding After Upgrade to Win XP {KB 307151} Win XP

ehessAuthor Commented:
I know it's either faulty driver or software.  How do I narrow it down?  This is a brand new Dell OptiPlex Gx 620.  
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

Brand new system! return to Dell, though.
When does the BSOD occur? While booting or while running? If while booting, you could start the system and press F8 to get your boot menu. One of the menu options should be to log the boot process. It then lists all the loaded drivers until the system crashes. That should give you an idea.

If it happens while the system is running, try to find out if it crashes when you are doing something specific, this should also give you an idea of the reason. If there is any easily removable hardware, remove that to eliminate any addon hardware from the equation.
ehessAuthor Commented:
It always happens when the user is logging on to the computer.  
That could still belong to the booting process, so check the option with the boot log. Also try not having the NIC connected.
If you haven't installed new hardware or software preceding the BSOD, you may have a bad memory stick. If Dell doesn't provide a memory test app try MemTest86:

Some version of the following software may cause bugcheck code C2. If you can provide the minidump, I can find out the culprit.

removeIT    http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21732641.html#15929339
klpf.sys  http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21768119.html
klpid (Anti-hacker)
tm_cfw.sys (Trend Macro)
ThinkVantage Resuce & Recovery

Bugcheck may also caused by faulty ram or bad paging space. You had better run chkdsk /r and re-allocate the paging space. Run memtest to stress test the ram.

Faulty RAM  http://www.experts-exchange.com/Operating_Systems/WinXP/Q_21323441.html#13522656
ehessAuthor Commented:
----- 32 bit Kernel Mini Dump Analysis

MajorVersion        0000000f
MinorVersion        00000a28
DirectoryTableBase  0a4c0020
PfnDataBase         80e86000
PsLoadedModuleList  8055c700
PsActiveProcessHead 80562818
MachineImageType    0000014c
NumberProcessors    00000002
BugCheckCode        000000c2
BugCheckParameter1  00000007
BugCheckParameter2  00000cd4
BugCheckParameter3  000004c0
BugCheckParameter4  e14d0040
PaeEnabled          00000001
KdDebuggerDataBlock 8054c2e0
MiniDumpFields      00000dff

ServicePackBuild      00000200
SizeOfDump            00010000
ValidOffset           0000fffc
ContextOffset         00000320
ExceptionOffset       000007d0
MmOffset              00001068
UnloadedDriversOffset 000010a0
PrcbOffset            00001878
ProcessOffset         000024c8
ThreadOffset          00002728
CallStackOffset       00002980
SizeOfCallStack       000003c4
DriverListOffset      00002fd8
DriverCount           00000087
StringPoolOffset      000057f0
StringPoolSize        000012c8
BrokenDriverOffset    00000000
TriageOptions         00000041
TopOfStack            bacebc3c
DebuggerDataOffset    00002d48
DebuggerDataSize      00000290
DataBlocksOffset      00006ab8
DataBlocksCount       00000004

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

Kernel base = 0x804d7000 PsLoadedModuleList = 0x8055c700
Debug session time: Wed Mar 21 13:27:31 2007
System Uptime: 0 days 0:00:35
start    end        module name
804d7000 806e2000   nt             Checksum: 001EE49F  Timestamp: Tue Dec 19 0
12:17 2006 (45880F61)

Unloaded modules:
bac30000 bac35000   Cdaudio.SYS    Timestamp: unavailable (00000000)
bac28000 bac2d000   Flpydisk.SYS    Timestamp: unavailable (00000000)
bac20000 bac27000   Fdc.SYS     Timestamp: unavailable (00000000)

Finished dump check
ehessAuthor Commented:
I spoke with a Dell Tech. and ran the Crash Test Tool.
The faulty program appeared to be NavEx15.sys.  
I reinstalled the NIC driver and reinstalled Symantec Antivirus and haven't crashed yet.  We'll see what happens now.  
Get Avast! Antivirus personal, free for home use, doesn't use as many resources as Norton by a long way, and in my point of view is much more stable and detects more malware. With symantec products you tend to get all kinds of problems.

If you provide the minidump, I will find out the culprit. Re-post if you still have o/s issues.
ehessAuthor Commented:
The last minidump is already posted.  I haven't had another blue screen after the reinstallation of the NIC driver and SAV.  
You posted the output of dumpchk which is insufficient to find out the root cause. The output of windbg has much diagnostic information.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 5
  • 4
  • 3
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now