also @ TechSpot: Digital game purchases: do we really "own" them?
Welcome to the TechSpot OpenBoards. Please read the FAQ if you have any questions. Sign up or Login to participate.

Go Back   TechSpot OpenBoards > Software > Windows OS

Begin your free trial now Pay-as-you-go options starting at $10/user/month

What is bad_pool_caller????

Thread Tools Search this Thread
  #1  
Old 08-15-2004
vegasgmc's Avatar
TechSpot Chancellor
 
Location: Las Vegas
Member since: Mar 2002, 1,743 posts
What is bad_pool_caller????

I keep getting a BSOD today with this message. Google search didnt turn up anything useful.
  #2  
Old 08-15-2004
TechSpot Addict
 
Location: Jefferson City, MO, USA
Member since: Oct 2002, 703 posts
What operating system??

A quick google indicates this is a device driver conflict usually. This can be between two devices, or a virtual driver installed by a program. One of the more frequently mentioned items was two CD writing softwares butting heads. If you've installed any software lately, that's probably your first place to look.

Are there any more details, including numbers, to the BSOD?

This information would help greatly....

Last edited by Goalie; 08-15-2004 at 07:04 PM..
  #3  
Old 08-15-2004
vegasgmc's Avatar
TechSpot Chancellor
 
Location: Las Vegas
Member since: Mar 2002, 1,743 posts
No more info. Thats whats so frustrating. Ive gotten other BSOD's as well but they are general too. This is a clean install of XP. I may just do it over. That might be why Im having problems gaming. Thanks
  #4  
Old 08-15-2004
TechSpot Addict
 
Location: Jefferson City, MO, USA
Member since: Oct 2002, 703 posts
I promise you there's more info- it probably says Stop(0x0000, 0x00 etc) down at the bottom. The screen cannot merely say "bad_pool_caller" and that's IT.
  #5  
Old 08-15-2004
vegasgmc's Avatar
TechSpot Chancellor
 
Location: Las Vegas
Member since: Mar 2002, 1,743 posts
XP Pro. There is a Stop string but I didnt wright it down.
  #6  
Old 08-15-2004
TechSpot Addict
 
Location: Jefferson City, MO, USA
Member since: Oct 2002, 703 posts
The stop string contains the critical numbers...
  #7  
Old 08-15-2004
StormBringer's Avatar
TechSpot Evangelist
 
Location: USA
Member since: Apr 2002, 2,871 posts
contrary to popular belief, those numbers can be very helpful in determining the problem, especially if it is a "known issue" that may be documented in MSKB.
  #8  
Old 08-16-2004
TechSpot Addict
 
Location: Jefferson City, MO, USA
Member since: Oct 2002, 703 posts
Even when the numbers aren't directly useful, they usually provide enough information to get a working direction even.

The most common bad_pool_caller stop I saw was 0x2c, which was a driver conflict iirc. MS is pretty good about documenting the basic meaning of a stop error, even when it's not specific.
  #9  
Old 08-16-2004
TechSpot Evangelist
 
Location: has left the building
Member since: Aug 2003, 8,165 posts
Audigy is the magic word here.
Remove and re-install the latest drivers.
  #10  
Old 08-25-2004
vegasgmc's Avatar
TechSpot Chancellor
 
Location: Las Vegas
Member since: Mar 2002, 1,743 posts
I was having problems with the Audigy card for a week. Removed and re-installed everything. All is working good and no more BSOD's.
Closed Thread

Similar Topics
Topic Replies Forum
Bad_pool_caller c2 8 Windows BSOD, Freezing, Restarting Help
Bad_pool_caller 1 Windows BSOD, Freezing, Restarting Help
Bad_pool_caller (c2) 2 Device Drivers
Bad_pool_caller 6 Windows OS
Bad_pool_caller 1 Windows OS

Thread Tools Search this Thread
Search this Thread:

Advanced Search
All times are GMT -4. The time now is 11:04 PM.