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 »

In Windows based PCs, the Recycle Bin is the place where all your deleted files and folders are stored. A file or folder ends up in the recycle bin when you select a particular file or folder and press on the delete button. This functionality has been provided in Windows to prevent loss of critical data, which might arise due to accidental deletion of files and folders.

The recycle bin is a stable functionality in Windows and you can always rely on it for recovering your deleted files and folders. However, there might be times when the recycle bin itself fails to show up on your desktop, making it impossible for you to recover your deleted files and folders. There can be many reasons for this such as a third-party program, a group policy setting or a TweakUI program, but in most cases, it’s just some missing registry information.

The solution that often works well for restoring recycle bin to its original state in Windows Vista requires you to access Control Panel, click on “Appearances and Personalization’ and select “Personalization”. After this you just need to click on “Change Desktop Icons”, select “Recycle Bin” and click OK. If your lost recycle bin is just because of some missing registry information, it will come back on your desktop as soon as you do this.

To restore recycle bin, you can also make some changes directly to the Windows Registry. Information on this is readily available on Microsoft’s support Website, which you can use for restoring recycle bin to its original state. However, this method might prove tricky for beginners and if you are not all that proficient in technical matters, I will recommend that you try this method only when the Control Panel method does not work for you. That’s all that is there to restoring your Windows Recycle Bin.

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

No Comments »

Okay now before we go on to populate this page with some of the file extensions, lets first see what exactly it is all about. File extensions are unique identification letters given to some files so as to indicate their type and sometimes even their contents. Some of the important file extensions are given below:

AR: Javasoft JRE 1.3 Library File

ARC: Archive

ASC: ASCII Text

ASP: Active Server Page

AUTOCONF: UNIX File

AVI: Audio Video Interleave file

BDF: X11 Bitmap Distribution Format

BIF: Binary Information File

BMF: BMF Bitmap

BPC: BuildPro File

BRS: Corel Painter Brush File

BRX: Multimedia Browsing Index

BUC: Photoshop Elements Backup File (Adobe Systems Inc.)

BUF: WinXL File

Bug: Bug (problem) File

CAB: Cabinet File (Microsoft Corp.)

CB: Clean Boot File (Microsoft)

CBL: COBOL Program

CCK: Corel Clipart Format (Corel)

CCX: CorelDraw File

CDB: Clipboard File

CDR: Sound File

CDT: CorelDraw Template (Corel)

CLS: Visual Basic Class Mode

CMD: DOS CP/M Command File

CMP: JPEG Bitmap

CMT: CorelDraw

COB: COBOL Program File

COM: Command

CONF: Linux Configuration File

CTC: PC Installer Control

DAO: Windows Registry Backup

DDT: Linux Configuration File

DIR: Directory Indicator (Microsoft)

DOC: Microsoft Document/Documentation

DOS: Network Driver File

EXE: Executable File (Microsoft)

GIF: Graphic Interchange Format

HIPS: Bitmap Graphic

HTML: Hypertext Markup Language

IDX: Index

IP: Internet Protocol

ISP: Internet Communication Settings

JAR: Java Archive Software

JPEG: JPEG/JIFF Image

KEY: Keyboard Definition File

MIME: Multi Purpose Internet Mail Extensions File

MP3: AlbumWrap Wrapped Music File Archive

MP4: MPEG-4 Video File

OGG: Ogg Vorbis Codec Compressed Multimedia File

OMF: Open Media Format File

RAR: WinRAR compressed Archive

SAT: Firefox Bookmark Backup File

SIS: Symbian OS Installer File

TFT: Text Formatter Plus Text File Information

These were just some of the many file extensions known, which helps the user to get a brief idea of the type of software he is downloading and whether or not the file is compatible with his system.

No Comments »