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 »

It’s the screen that we all dread. It nearly always means that there’s something seriously wrong with an operating system, and in many cases, fixing it can require drastic measures. Yes, of course. We’re talking about the blue screen of death!

One of the errors that you might encounter is marked as 0×00000000.

For example, you might receive an error like the one below:

STOP: 0×0000009C (0×00000004, 0×00000000, 0xb2000000, 0×00020151) “MACHINE_CHECK_EXCEPTION”

There are several different causes for the 0×00000000 error. But in most cases where you receive it, your system will be unusable. In extreme situations, you might not have any access to the Windows operating system at all. The error often triggers a system restart, and can appear without warning. Needless to say, its one of the more frustrating problems out there! It should also be noted that the error is typically found on Windows XP.

The official Microsoft documentation suggests that the error arises when the Machine Check Exception detects an unrecoverable problem with the hardware on an XP OS. This is slightly ambiguous, so how do we know where the problem is coming from?

To get to a fix, we have to look at the hardware of the system.

It’s possible that you’re suffering from a memory partition problem. A re-format of the hard drive would be the solution in this situation. But it’s much more likely that there’s a problem with the system bus.

System bus errors are painstakingly tricky to fix and you’ll need to take the computer to a technician and cough up for the full repair treatment.

It’s also possible that you’re running off higher specifications than your machine can handle. Over-clocking of the processor is a notorious problem and it is associated with the blue screen 0×00000000 error. To handle the higher performance applications, you should consider an upgrade to the processor and memory.

In most cases, you’ll be well aware if your processor is being over-clocked with unrealistic expectations. Poor performance will be noticeable long before the errors begin to crop up.

Ensure that the system has sufficient ventilation and that the fan is powerful enough to cool the CPU. This is the cause of many a system failure, but many look beyond what can be treated as basic thermal management of the computer.

It’s also important to stay up to date with the latest anti-Virus protection. If you find yourself attacked by one of the malicious shell-targeting viruses that are in circulation, it can have a crippling effect on the system resources.

Download a system cleaning utility and run a thorough check for malicious files. Remove anything that looks suspicious and you should notice an improvement in performance, which can be noted from the Task Manager.

Ultimately, if Windows is refusing to start up, or if the 0×00000000 errors are too persistent to ignore, you should take your computer to the nearest (or cheapest) repair store and ask a qualified technician to troubleshoot the actual hardware components. It’s very likely that the problem is being caused by either damaged memory or insufficient system resources, both of which can be pricey to fix.

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

2 Comments »