Blue screen error
Posted: Fri Jan 20, 2006 1:22 pmI've started to get the ocassional blue screen error message Bad_Pool_Caller.
Isnt that a memory module error? Whats causing it?
Isnt that a memory module error? Whats causing it?
Page 1 of 2
Posted: Fri Jan 20, 2006 1:22 pmSome Specifics
Posted: Fri Jan 20, 2006 2:32 pmSome things that may be required to troubleshoot are what version of windows your running , if you just upgraded it , did you just insert ram, the full bluescreen including paremiters...
Posted: Fri Jan 20, 2006 3:34 pmThanks for the reply
Oops,ok. Well I have'nt done anything to my pc for ages, 6 months or more. Im running XP and have 512MB of SDRAM. Its only been happening when Ive been trying to install the game Far Cry. Ive installed other games recntly and Ive had no problems
Oops,ok. Well I have'nt done anything to my pc for ages, 6 months or more. Im running XP and have 512MB of SDRAM. Its only been happening when Ive been trying to install the game Far Cry. Ive installed other games recntly and Ive had no problems
Posted: Fri Jan 20, 2006 5:36 pmIt depends on the stop error code parameters that goes along with this error as to what the problem is
It should look something like this:
STOP: 0x000000C2 (0xParameter_1, 0xParameter_2, 0xParameter_3, 0xParameter_4)
BAD_POOL_CALLER
The first set of parameters will tell you what the error is like
Parameter 1 = 0x01, 0x02, or 0x04 : Pool header has been corrupted
Parameter 1 = 0x06 : Attempt to free a pool that was already freed
The rest of the parameters tell you the Starting address, Current IRQL and so on.
You can read the article from Microsoft about bad_pool_calls .
It should look something like this:
STOP: 0x000000C2 (0xParameter_1, 0xParameter_2, 0xParameter_3, 0xParameter_4)
BAD_POOL_CALLER
The first set of parameters will tell you what the error is like
Parameter 1 = 0x01, 0x02, or 0x04 : Pool header has been corrupted
Parameter 1 = 0x06 : Attempt to free a pool that was already freed
The rest of the parameters tell you the Starting address, Current IRQL and so on.
You can read the article from Microsoft about bad_pool_calls .
Posted: Fri Jan 20, 2006 6:31 pmPosted: Fri Jan 20, 2006 7:34 pmPosted: Sat Jan 21, 2006 12:09 pmPosted: Wed Jan 25, 2006 12:16 pmPosted: Mon Jan 30, 2006 11:44 pmJust had another one...
STOP 0x00000077(0xc000000E,0x000000E,0x0000000,0x0011A000)
KERNAL_STACK_INPAGE_ERROR
Each ones a little different but they are becoming a little more frequent!!
STOP 0x00000077(0xc000000E,0x000000E,0x0000000,0x0011A000)
KERNAL_STACK_INPAGE_ERROR
Each ones a little different but they are becoming a little more frequent!!
Posted: Tue Jan 31, 2006 3:05 amAssuming that you have scanned for a boot sector virus I would say try testing the ram first,
go to and download the file to create the boot device of your choice (floppy/CD)
Create the boot device media and reboot from that media.
Let memtest run at least an hour to get true results.
If your memory passes and you have no virus then you should check the drive for bad sectors.
First backup important files now your drive might be about to go!
Then right click on your OS drive (c:\) select properties
On the tools tab, Error Checking section, check now button
Put checks next to both boxes and click yes and yes to check on next startup reboot
This will take a number of hours to complete because it will check for bad blocks/sectors on the drive.
go to and download the file to create the boot device of your choice (floppy/CD)
Create the boot device media and reboot from that media.
Let memtest run at least an hour to get true results.
If your memory passes and you have no virus then you should check the drive for bad sectors.
First backup important files now your drive might be about to go!
Then right click on your OS drive (c:\) select properties
On the tools tab, Error Checking section, check now button
Put checks next to both boxes and click yes and yes to check on next startup reboot
This will take a number of hours to complete because it will check for bad blocks/sectors on the drive.
Posted: Tue Jan 31, 2006 1:51 pmThe drive is only about 3 years old and it says it status is ok when booting up. Mmmmm,I never seem to have much luck with drives.
Posted: Tue Jan 31, 2006 7:34 pmPosted: Tue Jan 31, 2006 7:55 pmPosted: Tue Jan 31, 2006 9:44 pmPosted: Wed Feb 01, 2006 12:13 amJust ran both tests but no errors were found. Not sure what I do now