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: 0×000000c2 (0×000000043, 0xc2528000, 0×00000000, 0×00000000) ”

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

Get a Free Diagnostic Scan with RegCure PC Optimizer (Download Takes 2 Mins)

No Comments »

The problem of the Bad Pool Caller - which occurs during the upgrading of the Microsoft operating system from Windows 2000 to Windows XP - causes the installation process to stop by the display of an error message on the blue screen. This blue screen has been spoken of many times and you’re probably aware of it by now. It’s called the blue screen of death for good reason! If you’re seeing it, something serious has happened to Windows.

In the event of the Bad Pool Cooler error, expect to see a message that reads along the lines of this:

“A problem has been detected and Windows has been shut down to prevent damage to your computer”.

The BAD_POOL_CALLER problem which is displayed as “stop: 0×000000c2″ and other similar varieties essentially happens because of certain issues in managing the memory of the computer.

Now if the error message conveying the problem displays the same set of alphanumeric code every time the system reboots itself, the problem can actually be tackled without going for professional technical help. To begin with, the user must verify the RAM and the hardware of the computer and reboot the operating system once more with the help of a setup disk or maybe by using a boot setup having a GUI similar to that of BartPE.

Try booting in to Safe mode using F8 at the relevant screen. This will try to load Windows using the absolute most basic of files. If you still can’t access the Operating System, you’re going to need the setup disk.

If you’ve bothered to make copies of the key Windows files on a floppy disk, they’re about to become extremely useful and you can use these to regain entry to the core Windows system by replacing just these. You will need to set your BIOS to give preference to the floppy disk drive when booting the system.
Once you regain access to Windows, this is to be followed by running a memory test using a RunScanner and subsequently selecting one single account. In case all the accounts open up, the problem should lie in the system registry hive which is to be renamed and not deleted. From the available backup, another hive is to be created and harvesting of any replacement hive must be avoided in any case.

Apart from this relatively lengthy and somewhat complicated method, there are a couple of quite gimmick like tricks which sometimes solve this problem. One of them is to have the operating system installed once again. This will of course reset Windows to its factory set state, saving a large amount of trouble. But it comes at the price of all your saved files that will not be recovered in the reinstallation. Think long and hard before agreeing to reinstall Windows, it should be the last resort.

Another such trick is to switch off the computer for an extended period of time and then switch it back on once more. It sounds like a ridiculous solution but there are many unexplainable scenarios where such an action can have a good effect.

Get a Free Diagnostic Scan with RegCure PC Optimizer (Download Takes 2 Mins)

No Comments »

The bad pool caller problem is much documented and can occur at any time on a system that is suffering from memory problems or a hardware configuration issue. The error can be either fatal or recoverable. You’re likely to see it when loading up your Windows operating system during the boot process.

A standard bad pool caller error will read as below:

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

The blame for this, in most cases - will fall on the hardware that you have installed on your system and the integrity of the memory. Check your RAM for problems, if this is within your knowledge. Has the problem started occurring following the installation of a new hardware device? In that case, you may want to disconnect it completely and remove it from the boot start-up list. Bad references in the Windows registry can completely decimate your Operating System, and these are often caused by hardware installations gone wrong.

Speaking on a technical note, it can be said that this particular bad pool caller problem may arise in a situation where the system has already got a Winnov Videum AVI video capture adapter along with the Videum software of the 2.9.2 version installed in the computer.

The problem is most annoyingly realized during the process of installing the operating system. Typically, an option appears for getting updated setup files and recommending the download of those files. However, clicking on either of the options such as ‘Yes, download the updated setup files’ or ‘Details’ results in the appearance of messages informing that the items are not compatible with the OS Windows XP and these problems must be resolved before attempting to run the setup once more.

Thus, if the user decides to go for the remaining option of ‘No, skip this step and continue installing Windows’ the blue screen appears carrying an error message saying that “STOP 0xC2 BAD_POOL_CALLER”.

Anybody who’s dealt with Windows for any meaningful period of time will be aware of the problems that come with the infamous blue screen of death. You can find yourself locked out of Windows completely, depending on the nature of the pool caller error.

You may have also noticed that the bad pool caller error arises shortly after installing a font on certain versions of Microsoft Windows. Well, in this case, it’s the font that’s causing the problem. Windows will respond stubbornly and thrown the blue screen error if it detects a bad font, although you shouldn’t suffer from repeated bad pool caller errors. And if you do, it’s likely another factor at work.

The system registry hive is another checking point for bad pool callers. If your registry hive fails or becomes corrupted, you can expect to see a whole lot more of the blue screen errors. In most cases, an error of this magnitude will result in being locked out of the computer completely.

Get a Free Online Diagnostic Scan with RegCure PC Optimizer (Download 2 Mins)

No Comments »

If you are getting a blue screen in your Windows operating system that says something about a bad pool caller, you are in for a tough ride. The bad pool caller error means that some piece of software somewhere on your computer has done something wrong. For this reason it is important to write down the error codes that you receive with this message to help in determining what exactly is going on.If you have successfully been able to record these error codes in some way and have access to a computer that is working, the best place to start is on the Microsoft website. Once you get to their website, try entering the error codes that you have written down to see if they can give you more detailed information about the software that is causing the problem and any possible solutions to correct the issue.If you have not been able to find a solution to your bad pool caller error using the above method, then there are a few things that you can try. Often a hardware device can also cause problems that result in the bad pool caller error message, especially USB devices. Start by removing all of your peripherals including printers, scanners, external modems, USB hubs, etc. if you do not receive the error message once you have done this, then add one device back at a time, until you find the source of your problem. If this works and you know what device was causing the issue, you can try reinstalling the software for that device or replacing the USB cable that is connected to that device to see if that will solve the problem. If the problem still persists, it would be a good idea to run MemTest86, which can be downloaded online, to test your RAM for errors. A bad hard drive can also result in bad pool caller messages.If you have recently purchased your computer or have warranty on your computer, perhaps the easiest way to deal with this difficult problem is to take it back to them. Because of the nature of a bad pool caller message, which can be caused by almost anything, it is easier to have them deal with it rather than trying to isolate and correct the issue on your own.If you have built your own computer or are working on an older computer that no longer has a warranty, then you may also be able to get some clues into what is causing the problem by looking through the Windows Event Viewer for error messages or information. If you do not know how to do this, then a quick search online will explain how things are logged in the Event Viewer and how to interpret the information provided.Finally if all else fails and you are sure the problem is not related to a peripheral or other hardware device, then you can reload the Windows operating system on your computer. This can be done without losing your personal data and files, but be sure that you perform a complete backup before attempting this step just in case. There are the odd situations in which a bad pool caller error will occur during the installation of Windows in which case you will need to try and completely reformat your hard drive and start from scratch.

Get a Free Online Diagnostic Scan with RegCure PC Optimizer (Download Takes 2 Mins)

3 Comments »