autoexec.bat & config.sys problems

The autoexec file was originally created for MS-DOS and Windows 3.x operating systems. Autoexec.bat was used in conjunction with the config.sys file as an easy way of loading the files that were required for various hardware devices and the operating system to run properly. In later revisions of MS-DOS and Windows 3.x these files were required in order for the operating system to load at all. In newer versions of Microsoft operating systems, these files are no longer required to load the operating system, however, a user may need to edit the information within these files from time to time.

Now, just to be safe, we recommend that before you edit the autoexec.bat or config.sys files that you create a copy of the original ones with a different name so that they can be recovered in the case that you make an error and things do not work properly after.

The most common way of editing the autoexec.bat and config.sys files is by using the MS-DOS command Edit. In order to edit these files you simply need to type “edit c:\autoexec.bat or config.sys” into a MS-DOS command prompt. However, on newer computer systems, the more common way to edit these files is to click on “Start” and then “Run”. Now you will want to type sysedit into the dialog box provided and click on the “OK” button. This will quickly display the System Configuration Editor within which the autoexec.bat, config.sys, win.ini and system.ini files are displayed for easy editing.

If you want to remove a line from one of these files, the most advised method is to use the remark command “REM” in front of the line you no longer want to execute. This will tell the computer to ignore this line when the operating system is loading, but also will allow you to easily remove your remark command to include the line again in the future if you do not get the result that you want or if you wish to use the line again at a later time. This will help you to easily restore that line of code without having to worry about where in the file it should be placed or the syntax that it should be written with.

With the increasing number of programs that are being loaded by an operating system when it first starts, getting additional memory is always as big advantage for any computer user. There is a way in the config.sys file that you can tell the operating system to load the files more efficiently into memory, which will help you have more memor for other programs and games on your system, especially in MS-DOS computers. In order to do this there are three lines that you will want to have at the beginning of your config.sys file:

DEVICE=C:\Windows\HIMEM.SYS
DOS=HIGH,UMB
DEVICE=C:\Windows\EMM386.EXE NOEMS

By using the DOS=HIGH, UMB command on the second line, you can potentially save memory because it is now loading DOS into upper memory before loading the memory manager. The first and third lines cannot be loaded into the upper memory areas however as they are the memory managers themselves. The best technique for saving memory is to load all of your devices in your config.sys file and autoexec.bat file into high memory.

How to fix DLL Errors

DLL files, or Dynamic Link Library files, are the tiny resources that make it possible for our applications and programs to interact with modern day versions of Microsoft Windows. To fix DLL errors, you have to possess a good understanding of DLL files in general, and the way that we can troubleshoot these tricky errors and locate their true source on the Windows platform.

To fix DLL errors, you should know that they can occur at any time and are rarely ever obvious in the message text. That is, when you read the debugging message, it’s unlikely that you’ll know instantly where the DLL error is stemming from. Through trial and error – and a fair bit of experience – we can begin to fix DLL errors manually by simply understanding how Windows relates them.

A lot of the time, DLL errors are triggered by the incomplete removal of programs via the Windows Control Panel. Some software also have their own uninstall scripts written which for obvious reasons, can be about as effective as the developers that wrote them. It depends from program to program. What you need to remember when you fix DLL errors, however, is that not every uninstall is successful – even though it may look it on the surface if you can no longer see the program in question.

Every Windows application comes with its own batch of DLL files, and it needs them to interact with the default operating system files. However, some of these files can linger on the operating system after their parent application has been removed. Attempting to access the same memory and reference points at a later date can trigger DLL errors since Windows thinks the memory should be available, but for whatever reason, it isn’t.

Find yourself a registry scanning utility and run regular registry scans. These will help to stamp out the problems and fix DLL errors before they become a greater issue. How do you know that they’ve progressed in to a greater issue? Well, runtime errors, illegal operations performed and the dreaded blue screen of death are generally great pointers!

In some cases, to fix DLL errors e can simply rename the original DLL file that is calling the problem and then re-run the application’s installation procedure. You will notice that many of these installation scripts come with an “Upgrade/Repair” option after Windows recognises that the app is already present. By renaming the DLL file and re-running through this process, Windows will write a fresh DLL file to the system and you should be able to regain the program’s functionality.

This will help if the problem lies in a DLL file becoming corrupt. But sometimes viruses and spyware will latch on to the files making it quite a challenge to go through manually and fix DLL errors. It’s important to have good anti-virus software installed, as this will prevent malicious third party users gaining access to your DLL resources ad further damaging the operating system. You’ll find it twice as hard to fix DLL errors if spyware is present on your computer so browse the Internet safely!

Computer Registry DLL Problems

When you install a fresh copy of Microsoft Windows, you’ll notice that all of your programs and applications seem to run so smoothly and without errors. It can be quite disheartening when a few months on, your operating system seems to have grinded to a halt with lots of applications failing to respond as they once did.

There are many reasons why your copy of Windows may be degrading in performance. DLL problems and issues with the computer registry are two of the most documented reasons for such a downturn in performance. The Windows registry sits behind the operating system as the backbone of files. It stores all the key application variables and handles configuration settings that we come to rely on.

DLL problems are just as critical as registry problems if allowed to get out of hand. DLL files are written to Windows every time we install a program. They are the libraries that sit behind our applications and allow them to perform all of their tasks. Every time we install a new program, we add a new set of DLL files to Windows. Likewise, when we remove a program or application, we hope that the DLL files associated with that particular program are removed as well.

In some cases, however, after attempting to uninstall a program, the DLL files will remain present on Windows and this can lead to some pretty drastic errors at a later date. Ensuring that you keep Windows free of stray DLLs is one of the tasks that many of the registry cleaning suites have made a priority out of.

DLL problems may be months in the making, without you knowing any better until a new application attempts to access your system memory and can’t because the same memory is corrupted by past DLLs. Keeping the PC clean is important and going back to the original point, one of the top reasons why Windows loads so much faster when you boot it up for the first time.

DLL problems can also be caused by malicious third party software latching on to the system resources. Windows likes to know what its allocating memory to, and if spyware or adware starts to leech from the memory that it previously set aside for other recognise applications, you can expect your attention to be drawn to many runtime errors and illegal operations.

Yes, those runtime errors that can plight system performance if left to develop over time. Most of us have seen them at some point, and they’re usually caused by bad registry entries or interrupted uninstall procedures. These lead on to DLL problems and if an application has DLL problems, it may terminate without warning, or simply function in a wayward manner.

The blue screen of death is another unfortunate symptom of DLL problems. Are you experiencing random blue screens while you try to run ordinary application? It could be because of DLL files being left behind, or becoming corrupted over time. Be sure that you run regular registry scans, and be extra careful when removing programs from Windows.

20 Most Common DLL Errors

OLEAUT32.DLL
DLL errors related to the oleaut32.dll file are usually caused by an incorrect version of this particular DLL file being installed on the operating system. The error is triggered when you attempt to run a Microsoft Office product, although some programs will run better than others. You’re most likely to see the oleaut32.dll error when running Microsoft Excel.

HLINK.DLL
DLL errors sprung from the hlink.dll library are typically found when attempting to view a Powerpoint presentation on Microsoft Windows. The file may have become corrupt, or could require updating to function effectively. You can update your hlink.dll file by downloading the latest Windows security package, or by running the installation package that comes with Internet Exporer. The old hlink.dll file should be removed first.

WAB.DLL
The wab.dll error is usually accompanied by a message stating that the file is missing. This could be down to a corrupt version of the file exiting, or it may have been deleted by access. To resolve these kinds of DLL errors, you will need to rename the old wab.dll file and then re-install Outlook Express. The re-installation will write a fresh working version of the wab.dll to your system.

OMINT.DLL
DLL errors that produce a message stating that the required component omint.dll is missing are usually restricted to older versions of Outlook Express. If you are trying to run Outlook Express 98, for example, you may find that your version of the omint.dll file is newer than the application itself. In this case, you will need to roll back to an older version. It’s also possible that the registry entries have become corrupted.

GWMSPI.DLL
The gwmspi.dll error message is caused by a conflict between two applications. These applications are Microsoft Outlook 2000 (standard edition only), and Novell. You will need to create two separate messaging profiles to get rid of DLL errors such as this. Uninstall one of the two applications and then install from scratch as an additional method of fixing the error.

RICHED20.DLL
When accessing Microsoft Outlook, you may notice an access violation DLL error related to the riched20.dll file. This shows that the file has become corrupt and you will need to repair Microsoft Outlook to fix the problem. Before you run the repair function, be sure to rename the riched20.dll file so as not to compromise the effectiveness of the repair.

MSVCP60.DLL
DLL errors tied to the msvcp60.dll file are notoriously hard to repair and usually require the complete re-installation of the Microsoft operating system. The error appears when trying to run features of Clip Gallery 5.0 in particular.

WMP.EXE
If you encounter an error related to the wmp.exe file, you could easily be misled in to believing that you have a problem with Windows Media Player itself. This is false. The problem actually stems from the DLL library associated to the program. You will need to re-register WMP.DLL to fix the problem, and can do so from the Run command on recent versions of Windows.

WMPDXM.DLL
DLL errors are quite common with Windows Media Player versions 9 and 10. The wmpdxm.dll error is directly related to the media player, as you’d expect, and is usually caused by the DLL file not being registered. To fix, you should attempt to re-register the DLL file. In some cases, a fresh version may be required as the DLL may have become corrupted or deleted.

MSI.DLL
If you’re trying to install a Microsoft Office product, and receive an msi.dll error, it’s likely that you will need to update Microsoft Installer which relies on the DLL file. The problem can be caused by a download being interrupted or by one of many types of corruptions. Visit the Microsoft website and upgrade your Installer to the latest version to resolve the error.

OFFICEAV.DLL
DLL errors related to the officeav.dll file are triggered when attempting to open a document in Microsoft Word while having a damaged officeav.dll library. The file is typically sound in the Norton add-on that caters for Microsoft products. You can fix the error by renaming the officeav.dll file and then re-activating the Norton plugin.

OLE32.DLL
The ole32.dll error may appear when attempting to add a clipart image to your open Word document. DLL errors such as this are usually caused by the ole32.dll library not being registered correctly on the Windows operating system. You can try re-registering the file, but if this doesn’t work, a complete Windows re-install may be necessary.

DLBAPRP.DLL
If you have Lexmark or Dell printers installed on your system, you may eventually encounter DLL errors related to the dlbaprp.dll file. This typically appears when you try to print or save a document in Microsoft Word. Besides from contacting the manufacturer directly, you can attempt to fix this DLL error by copying your key printer DLL files and placing them in the Windows/System32 folder.

HPAFD32.DLL
DLL errors linked to the hpafd32.dll file will cause Microsoft Word to close suddenly and without prior warning. The error is caused after a user has been using an HP printer model 1200 or 3200, and subsequently attempts to update to a newer model from HP. The installation won’t automatically update the hpafd32.dll file, and thus the printer will have problems. A driver upgrade is necessary.

MSVCRT.DLL
If your program has caused an illegal operation and been forced to shut down because of a msvcrt.dll error, it’s likely that your DLL files for the Word add-in with Microsoft Works have become corrupt. You should deactivate the Word plug-in before restoring it. This will force new copies of the files and will fix the DLL errors in most cases.

MSJAVA.DLL
The msjava.dll error is caused when you access a web page that attempts to load a script which the browser isn’t capable of handling. DLL errors related to the Java virtual machine – like this one – can usually be fixed by updating to the newest version of the JVM. Also ensure that you actually have scripting enabled in your Internet Explorer settings.

KERNEL32.DLL
The kernel32.dll error is generally caused by MacAfee software which runs a quick scan when you close a window in Internet Explorer – and occasionally Microsoft Outlook. The best way to get rid of these kinds of DLL errors is to access the MacAfee software directly and disable these scanning features.

ACTXPRXY.DLL
DLL errors related to the actxprxy.dll library are triggered when the user tries to open a fresh window in Internet Explorer, but the browser crashes and throws an error instead. Unfortunately, these DLL errors are related to the Windows registry itself and may be a giveaway sign that you’ve got several corruptions in the core files. Consider a registry scanning tool which should help to get rid of bad entries and fix this variety of DLL errors.

MSHTML.DLL
This is one of a select few very rare DLL errors that you shouldn’t be experiencing unless you’re running the extremely outdated Internet Explorer version 5.5 or earlier. The mshtml.dll error can be triggered by IE settings which involve the use of high or true colours. To fix, simply reset your settings to use 256 colours in the colour palette. Alternatively, you can upgrade your video card drivers via the manufacturer’s website.

SHELL64.DLL
Occasionally, you may encounter an error in Internet Explorer stating that the application has struck an error and will need to close. The shell64.dll error is caused in Internet Explorer version 6 when a third party program attempts to attach itself on to the browser and write a separate shell64.dll file to the system folder. Delete or rename the file to fix the problem.

File / Folder Access Denied Errors

“Access Denied” errors are quite common on Windows XP, and indeed, the older versions of Microsoft’s operating system as well.

They can be quite diverse in their meaning, and equally confusing in terms of what is necessary to fix the problem. What does Access Denied mean? Well, besides the obvious of not being able to access said file, it typically implies that the source is locked, corrupt or unavailable at that present time.

Much depends on the context in which you’re receiving the error. Are you trying to access a webpage online? Some pages are locked on the Internet and a username and password are required, otherwise an Access Denied error will be returned. If you try to visit a secured page, or if you enter a wrong username and password combination, you will see an Access Denied message. Depending on the web browser that you’re using, this will usually be preceded by a login box. So you will know when you’re trying to access protected content.

Sometimes, however, the Access Denied error will spring up for no particular reason when you try to access files on your local hard disk. Once again, we must take the situation I to perspective of what you are trying to do.

Are you trying to rename or move a file that is already open? Are you trying to write to a file which is read-only? Both of these scenarios could potentially lead to an Access Denied message.

If a file is opened, it will be locked from many of the basic Windows commands. You can’t rename a file while it’s already in use. Close the file and try accessing it again. This should fix the problem. The same situation applies to system services which are required for other programs to operate.

If you open up Windows Task Manager and attempt to shut down a service which is critical to the way that the system functions, you will receive the error. And in cases like that, your access is usually denied for a reason.

You may have seen an error like the one below:

“Folder is not accessible. Access is denied.”

This is a problem which stems from re-installing the operating system and trying to access a folder which was created on a NTFS file system in a past installation. For example, if you re-installed your My Documents folder to a different volume, you will find an Access Denied error when you try to access it on the new system.

The solution is to turn off Simple File Sharing – an option which is set to on by default on Windows XP systems. To do this, you should go to My Computer, followed by the Tools tab. Under the View tab on Folder Options, you will have the chance to enable or disable the Simple File Sharing System. Set it to Off.

Once complete, you can right click on the problematic folder and alter the settings through the Properties tab.

Go to Security, then Advanced, and Owner. Now you simply need to ensure that your current user group has access to the folder. Save the changes where necessary and exit. The folder should now be accessible.

“Access Denied” errors are quite common on Windows XP, and indeed, the older versions of Microsoft’s operating system as well.

They can be quite diverse in their meaning, and equally confusing in terms of what is necessary to fix the problem. What does Access Denied mean? Well, besides the obvious of not being able to access said file, it typically implies that the source is locked, corrupt or unavailable at that present time.

Much depends on the context in which you’re receiving the error. Are you trying to access a webpage online? Some pages are locked on the Internet and a username and password are required, otherwise an Access Denied error will be returned. If you try to visit a secured page, or if you enter a wrong username and password combination, you will see an Access Denied message. Depending on the web browser that you’re using, this will usually be preceded by a login box. So you will know when you’re trying to access protected content.

Sometimes, however, the Access Denied error will spring up for no particular reason when you try to access files on your local hard disk. Once again, we must take the situation I to perspective of what you are trying to do.

Are you trying to rename or move a file that is already open? Are you trying to write to a file which is read-only? Both of these scenarios could potentially lead to an Access Denied message.

If a file is opened, it will be locked from many of the basic Windows commands. You can’t rename a file while it’s already in use. Close the file and try accessing it again. This should fix the problem. The same situation applies to system services which are required for other programs to operate.

If you open up Windows Task Manager and attempt to shut down a service which is critical to the way that the system functions, you will receive the error. And in cases like that, your access is usually denied for a reason.

You may have seen an error like the one below:

“Folder is not accessible. Access is denied.”

This is a problem which stems from re-installing the operating system and trying to access a folder which was created on a NTFS file system in a past installation. For example, if you re-installed your My Documents folder to a different volume, you will find an Access Denied error when you try to access it on the new system.

The solution is to turn off Simple File Sharing – an option which is set to on by default on Windows XP systems. To do this, you should go to My Computer, followed by the Tools tab. Under the View tab on Folder Options, you will have the chance to enable or disable the Simple File Sharing System. Set it to Off.

Once complete, you can right click on the problematic folder and alter the settings through the Properties tab.

Go to Security, then Advanced, and Owner. Now you simply need to ensure that your current user group has access to the folder. For that U goto permission and add user .Save the changes where necessary and exit. The folder should now be accessible.

Blue screen of death problem 0×00000000

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.

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.

Causes of bad pool caller problem

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.

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.