What is bad_pool_caller????

[vegasgmc]

I keep getting a BSOD today with this message. Google search didnt turn up anything useful.

 

[Goalie]

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....

 

[vegasgmc]

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

 

[Goalie]

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.

 

[vegasgmc]

XP Pro. There is a Stop string but I didnt wright it down.

 

[Goalie]

The stop string contains the critical numbers...

 

[StormBringer]

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.

 

[Goalie]

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.

 

[RealBlackStuff]

Audigy is the magic word here.
Remove and re-install the latest drivers.

 

[vegasgmc]

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.