bad_pool_caller BSOD error

BiGBrOwNPimpsta · Aug 31, 2007, 09:00 PM

Well with this comp time to time I have been getting BSOD errors saying BAD_POOL_CALLER and Windows dumps the memory (all I remember is a percentage fill up) and the computer resets. Then when its booting up, it takes a bit longer for the hard drives to be detected. about maybe 10 seconds longer. When I start up windows, this is the error I get

Quote:

Problem signature
Problem Event Name: BlueScreen
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 4105

Files that help describe the problem (some files may no longer be available)
Mini082507-01.dmp
sysdata.xml
Version.txt

View a temporary copy of these files
Warning: If a virus or other security threat caused the problem, opening a copy of the files could harm your computer.

Extra information about the problem
BCCode: c2
BCP1: 00000007
BCP2: 0000113D
BCP3: 00000000
BCP4: FEAD2128
OS Version: 6_0_6000
Service Pack: 0_0
Product: 256_1

now before you all start flaming me "go back to XP", I'd like to say I refuse to because I get MORE crashes on XP, and screw that when I have a 8800 GTS and need DX10 for games like Bioshock. But thankfully vista caught that error and gave me some type of report where the issue starts. But I have no idea where to go from here...

ChaosMinionX · Sep 1, 2007, 07:20 AM

Quote:

Originally Posted by BiGBrOwNPimpsta

Well with this comp time to time I have been getting BSOD errors saying BAD_POOL_CALLER and Windows dumps the memory (all I remember is a percentage fill up) and the computer resets. Then when its booting up, it takes a bit longer for the hard drives to be detected. about maybe 10 seconds longer. When I start up windows, this is the error I get

now before you all start flaming me "go back to XP", I'd like to say I refuse to because I get MORE crashes on XP, and screw that when I have a 8800 GTS and need DX10 for games like Bioshock. But thankfully vista caught that error and gave me some type of report where the issue starts. But I have no idea where to go from here...

Its 1 of a few things.

1 - Bad Software installed
2- A bad driver
3- bad memory - check it with Memtest 86+

Also , next time you see it see if it lists any specific program or driver listed as the culprit.

If not head over here
AnandTech - Bad_Pool_Caller BSOD

And ask for some help

dclive has a website on how to troubleshoot BSODs, I am not one for wanting to look at stop codes haha.

His blog> Bluescreens

BiGBrOwNPimpsta · Sep 1, 2007, 06:09 PM

i think its my nvidia driver.... after running the verifier...its the beta driver but even with the regular driver it still crashed.

Tipstaff · Sep 1, 2007, 07:22 PM

Same conclusion here. However, it may not be the nVidia driver directly, but something that might be interfering with it. What caught my eye was the secondary error code, 00000007, which you probably saw like this: 0x000000C2 (0x00000007). This can indicate a conflict between drivers, or something that loads a kernel driver, such as anti-spyware programs, anti-viurs programs, or even something to do with your SATA/IDE drivers, or network card driver.

Is the error consistent? By this I mean does it happen after so many minutes, during bootup, or when you are doing a specific thing, like gaming? Also, how are you running the hard drives? Do you have the system setup in RAID or AHCI mode, and if so, I assume you have Intels Matrix Storage Manager running?

Necrosis · Sep 1, 2007, 07:31 PM

Quote:

Originally Posted by Tipstaff

What caught my eye was the secondary error code, 00000007, which you probably saw like this: 0x000000C2 (0x00000007). This can indicate a conflict between drivers, or something that loads a kernel driver, such as anti-spyware programs, anti-viurs programs, or even something to do with your SATA/IDE drivers, or network card driver.

Is the error consistent? By this I mean does it happen after so many minutes, during bootup, or when you are doing a specific thing, like gaming? Also, how are you running the hard drives? Do you have the system setup in RAID or AHCI mode, and if so, I assume you have Intels Matrix Storage Manager running?

Hmm he was having issues w/ his raid/ide setup if everyone remembers.

Tipstaff · Sep 2, 2007, 01:57 AM

Quote:

Originally Posted by Necrosis

Hmm he was having issues w/ his raid/ide setup if everyone remembers.

Honestly, only after you mentioned it.

Wow.. that's sad.. my memory is failing me faster than I rememb... errr... um...

... nvrm.

Lelisevis · Sep 2, 2007, 02:03 AM

Sounds very much like the issue I had with the latest WHQL nvidia drivers, went away with the latest beta again though it resurfaces every few vista sets. Bizarrely I was also getting the error on xp recently but it turned out to be a corrupt SD card from my camera, everytime I put it in my card reader I got that error.

BiGBrOwNPimpsta · Sep 2, 2007, 04:18 PM

my sata issues have been gone since i installed the matrix manager and removed the reg key. this has to be done everytime i do a fresh install. i have noticed the BSOD's are triggered MORE if i start to shut down windows or starting up a game.

WardenWolf · Sep 2, 2007, 04:57 PM

I'm pretty sure that's a memory error, but there's other possibilities. I haven't had problems with any recent Nvidia driver, and I'm running at 8800 GTS as well. Given that (1) you had crashes with XP AND Vista, and (2) the driver and software requirements are drastically different, it's highly unlikely it's a driver problem.

Investigate, in this order:

1. Hard drive. A hard drive can very easily do this. I have seen it before. Windows crashes, you reinstall it, and it starts crashing again. There is no outward sign that it's the drive, and it appears, even to an experienced tech, to be memory. Turn on SMART monitoring if your motherboard supports it, and check the status of your drives. If you can't find anything, consider investing in a copy of SpinRite from grc.com. If it gives you early warning, you'll be happy you did.

2. Memory. A failed memory register can cause crashes if the problem is not detected and the faulty register blacklisted by your system. If critical data falls into the black hole, the system crashes. Memory is the likely culprit, but, since a hard drive failure means data loss, investigate that first.

3. Faulty USB devices. Unplug all but the bare minimum from your system, and see what happens. Not likely, but possible, and it's easier to check than most other things.

4. Drivers. It's common knowledge that a driver can cause this. However, Vista's refusal to install unsigned drivers makes this less likely.

Tipstaff · Sep 2, 2007, 06:57 PM

Quote:

Originally Posted by BiGBrOwNPimpsta

my sata issues have been gone since i installed the matrix manager and removed the reg key. this has to be done everytime i do a fresh install.

This would be the deletion of the "Paramaters" listing under

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Servic es\iaStor

correct?

Sep 1, 2007, 06:09 PM	Thread Starter #3
BiGBrOwNPimpsta HH's #1 Hustla and Pimp Join Date: Jan 2003 Location: The Dirty Dot Posts: 7,717 Rep Power: 107 System Specs	i think its my nvidia driver.... after running the verifier...its the beta driver but even with the regular driver it still crashed. __________________ Sound Blaster X-Fi Xtreme Music \| Logitech Z-5500 THX 5.1 Surround Sound Speakers \| 2 Lite-On 20x S-ATA Burners \| Logitech G700 Mouse \| Logitech MX5500 Bluetooth Keyboard

Sep 1, 2007, 07:22 PM	#4
Tipstaff HardwareHeaven Extreme Member Join Date: Jul 2002 Location: Real capital of Canada: Torauna Posts: 6,773 Rep Power: 191 System Specs	Same conclusion here. However, it may not be the nVidia driver directly, but something that might be interfering with it. What caught my eye was the secondary error code, 00000007, which you probably saw like this: 0x000000C2 (0x00000007). This can indicate a conflict between drivers, or something that loads a kernel driver, such as anti-spyware programs, anti-viurs programs, or even something to do with your SATA/IDE drivers, or network card driver. Is the error consistent? By this I mean does it happen after so many minutes, during bootup, or when you are doing a specific thing, like gaming? Also, how are you running the hard drives? Do you have the system setup in RAID or AHCI mode, and if so, I assume you have Intels Matrix Storage Manager running? __________________ Portal: The Flash Version _________________________________ Brain: So, you sacked the cocky khaki Kicky Sack sock plucker? Mr. Sackett: The second cocky khaki Kicky Sack sock plucker I've sacked since the sixth sitting sheet slitter got sick.

Sep 2, 2007, 04:18 PM	Thread Starter #8
BiGBrOwNPimpsta HH's #1 Hustla and Pimp Join Date: Jan 2003 Location: The Dirty Dot Posts: 7,717 Rep Power: 107 System Specs	my sata issues have been gone since i installed the matrix manager and removed the reg key. this has to be done everytime i do a fresh install. i have noticed the BSOD's are triggered MORE if i start to shut down windows or starting up a game. __________________ Sound Blaster X-Fi Xtreme Music \| Logitech Z-5500 THX 5.1 Surround Sound Speakers \| 2 Lite-On 20x S-ATA Burners \| Logitech G700 Mouse \| Logitech MX5500 Bluetooth Keyboard

Sep 2, 2007, 02:03 AM	#7
Lelisevis Howlin at the moon Join Date: Sep 2003 Posts: 1,663 Rep Power: 0	Sounds very much like the issue I had with the latest WHQL nvidia drivers, went away with the latest beta again though it resurfaces every few vista sets. Bizarrely I was also getting the error on xp recently but it turned out to be a corrupt SD card from my camera, everytime I put it in my card reader I got that error.

Sep 2, 2007, 04:57 PM	#9
WardenWolf DriverHeaven Junior Member Join Date: Jul 2007 Posts: 43 Rep Power: 0 System Specs	I'm pretty sure that's a memory error, but there's other possibilities. I haven't had problems with any recent Nvidia driver, and I'm running at 8800 GTS as well. Given that (1) you had crashes with XP AND Vista, and (2) the driver and software requirements are drastically different, it's highly unlikely it's a driver problem. Investigate, in this order: 1. Hard drive. A hard drive can very easily do this. I have seen it before. Windows crashes, you reinstall it, and it starts crashing again. There is no outward sign that it's the drive, and it appears, even to an experienced tech, to be memory. Turn on SMART monitoring if your motherboard supports it, and check the status of your drives. If you can't find anything, consider investing in a copy of SpinRite from grc.com. If it gives you early warning, you'll be happy you did. 2. Memory. A failed memory register can cause crashes if the problem is not detected and the faulty register blacklisted by your system. If critical data falls into the black hole, the system crashes. Memory is the likely culprit, but, since a hard drive failure means data loss, investigate that first. 3. Faulty USB devices. Unplug all but the bare minimum from your system, and see what happens. Not likely, but possible, and it's easier to check than most other things. 4. Drivers. It's common knowledge that a driver can cause this. However, Vista's refusal to install unsigned drivers makes this less likely.