Question

Locked

Bad Pool Caller

By n00bst4r23 ·
Hi,

I have a Dell Precision 390 with Windows XP Sp2 on it. Recently I am getting Blue Screen on it whenever I try to boot it. On the blue screen, it gives me the error - Bad_Pool_Caller and at the bottom it shows ****npchmqsx.sys - Address F78F020E base at F78EF000, Datestamp 48b4014a.

With some googling, I am guessing that "Bad Pool Caller" could be because of some hardware issue or driver issue. But, I have no information about "npchmqsx.sys" or what this driver is about.

Any ideas?

This conversation is currently closed to new comments.

2 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Answers

Collapse -

Bad Pool Caller Fix

Bad Pool Caller Fix

BAD_POOL_CALLER is a stop error message that is caused because of problems with the memory management. The error is seen when the computer is started up and displays the blue screen of death and gives the following message: ?A problem has been detected and windows has been shut down to prevent damage to your computer?.

BAD_POOL_CALLER. stop: 0x000000c2 (0x000000043, 0xc2528000, 0x00000000, 0x00000000) ?

Each of these stop error parameters is for a different problem. There is a list of more than thirty such causes that can give you this error message. If the stop error is consistent every time the system is rebooted, the following method will be effective in solving the problem:
The hardware and RAM should be checked initially.
Boot the system once again using the OS setup CD, or use a boot setup that has a GUI like BartPE.
With RunScanner it is possible to use a memory test tool.
Select a single account
If all the accounts open then the system registry hive might be the problem.
Locate the hive damaged and rename it, do not delete it.
Create another hive from the backup or from the restore point.
Initially uses the latest one and keep checking the restore points that come later.
Avoiding harvesting any replacement hives from the hard drive booted Windows.
After which compare the hives for differences.
This is one of the ways of fixing BAD_POOL_CALLER errors. Another method is to reinstall the OS but occasionally shows a disk read error or an error on the same lines. Switching the computer off for a minute or more and then switching it on can solve it since the error is only a slight glitch in the system operation.

The BAD_POOL_CALLER is seen for the first time after installing a hardware or software it is recommended that the computer be restarted. If it doesn?t solve the problem, the installation of the hardware or software should be checked for correction. The manufacture should also be contacted if there are any Windows updates required to correct the error. If the problem persists the installed hardware and software should be disabled, and the BIOS memory options like caching or shadowing should be disabled too. The safe mode can be used as well to remove or stop components. To enable the safe mode just press F8 when the machine is being restarted and select it from the Advance Startup options and correct the problem. The installation of the graphics card is another reason the BAD_POOL_CALLER error shows up. A simple reinstallation of the driver can solve the problem. Microsoft has also acknowledged that the BAD_POOL_CALLER Stop 0xC2 error pops up when trying to print a document that contains a corrupt font. A hot fix is available at www.support.microsoft.com, where the telephone number can be acquired to contact support. The call to the support team is charged except if the support team has resolved that the update will solve the problem. The error message with relation to this parameter of the BAD_POOL_CALLER error is seen only in the Win2000 Professional, Server and Advanced Server Operating

Please post back if you have any more problems or questions.
If this info is useful, please give a thumbs up. Thanks

Collapse -

One additional step I take

by jdclyde In reply to Bad Pool Caller Fix

is boot to a liveCD.

If it boots or not, cuts in half where you have to look for the problem.

If yes to the boot, not a hardware problem.

If no, like you said, Memory or any recent changes are the first two things to start with.

Back to Software Forum
2 total posts (Page 1 of 1)  

Related Discussions

Related Forums