How To: Fix Windows Vista Stop Error “STOP 0xC2 BAD_POOL_CALLER”
BAD_POOL_CALLER is a stop error message in Windows Vista that is caused because of problems with the memory management. This Windows Vista stop 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: 0×000000c2 (0×000000043, 0xc2528000, 0×00000000, 0×00000000) ”
You will also be greeted with an ominous message stating:
“A problem has been detected and Windows has been shut down to prevent damage to your computer”.
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 stop error message in Windows Vista.The Stop 0xC2 message in Windows Vista indicates that a kernel-mode process or driver incorrectly attempted to perform memory operations in the following ways:
- By allocating a memory pool size of zero bytes.
- By allocating a memory pool that does not exist.
- By attempting to free a memory pool that is already free.
- By allocating or freeing a memory pool at an IRQL that was too high.
- This Stop message is typically due to a faulty driver or software.
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 Operating System 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 stop errors in Windows Vista. Another method is to reinstall the Operating System 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 Systems.