BSOD - bad_pool_caller
#1
Posted 31 January 2011 - 10:24 AM
Tech Info:
0x000000C2 (0x00000007, 0x00000CD4, 0x02040001, 0x847D6CF0)
Never had this one before, so my notes are useless.
Anyone?
#2
Posted 31 January 2011 - 01:42 PM
"STOP 0x000000C2 BAD_POOL_CALLER - 0xC2, Kernel-mode process or driver problem.
The Stop 0xC2 message indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:
•By allocating a memory pool size of zero bytes
•By allocating a memory pool that does not exist
•By attempting to free a memory pool that is already free
•By allocating or freeing a memory pool at an IRQL that was too high
This Stop message is typically due to a faulty driver or software."
Since it's a new hard drive, I guess that I would test the RAM, using Memtest86+ - Advanced Memory Diagnostic Tool - http://www.memtest.org/#downiso
Memtest86+ Guide-How To's - Overclockers Forums - http://www.overclockers.com/forums/showthread.php?t=409152
Louis
#3
Posted 02 February 2011 - 11:35 AM
Could it be a faulty driver on my XP install CD? I would think not, but one never knows.
This post has been edited by Jay18: 02 February 2011 - 11:36 AM
#4
Posted 02 February 2011 - 11:43 AM
#5
Posted 04 February 2011 - 11:32 AM
#6
Posted 04 February 2011 - 11:35 AM
Also, are you using an original, retail XP CD?
#7
Posted 04 February 2011 - 11:54 AM
Install starts, drivers load, then I get "Setup is Starting Windows".
At this point I get the following BSOD:
A problem has been detected...
BAD_POOL_CALLER
And the technical info from the original post.
For the record:
Acer Aspire 3000 (Model No. ZL5)
Win XP Pro Retail, Slipstreamed w/SP2
This post has been edited by Jay18: 04 February 2011 - 11:55 AM
#8
Posted 04 February 2011 - 12:02 PM
Also, here is a similar situation that was resolved:
http://www.cyberspacesupport.com/question.php?question_id=2770
#9
Posted 04 February 2011 - 02:03 PM
Many, many thanks!
#10
Posted 04 February 2011 - 03:00 PM

Help


Back to top









