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)