Entries Tagged as ''

Windows Runtime Error

The windows runtime errors occur on almost all computers running on the Windows OS at some point in time. You will generally get to see an error message and the most common will be:

“There is not enough memory available to run this program.
Quit one or more programs, and then try again.”

There are several windows runtime errors like this that are mostly caused due to the following:

  • Software problem
  • Confliction with TSR or any other running program
  • Memory Problem
  • Computer Virus

The Solution for windows runtime errors

There are different solutions for different windows runtime errors and the only way you can actually troubleshoot a runtime error is when you know the type of error it is.

For example: If you see the “Runtime error 48 error loading in DLL”, then it has been caused by a bad installation. The solution is to remove the program that showed the error and try installing it again. If it still shows the error then you will have to remove the program from you computer and do a fresh install.

Software issue: Several windows runtime errors are caused by software problems. There are several windows runtime errors like 64bad file error or 74/can’t rename with different drive that will need immediate attention. You can remove the particular software and re-load it again but if the problem persists then you can jump to the next step which is downloading updates for that particular software. Most of the time, software related issues can be sorted out by downloading updates. There are different types of plug-ins or Add-ons are available for the same and you can download them to see if the program or software runs smoothly or not.

Confliction with TSR: When you get windows runtime errors that show a confliction with the TSR’s like error loading DLL and similar problems then the best solution is to do the following:

Boot at MS-DOS prompt.
At MS-DOS prompt, type:
cd\ <press enter>
ren autoexec.bat autoexec.ch <press enter>
ren config.sys config.ch <press enter>

Once this is done, you can reboot your computer.

Memory Problem: The memory problem is one of the many windows runtime errors that you will face while working on Windows OS and especially after a program download. Some of the windows runtime errors related to memory include:
7/out of memory
28/out of stack space
61/ disk is full
68/device is unavailable
1001/out of memory

When there is a memory error then there are two options: either you can contact the developer if a program is causing the problem or format the primary drive if it is a disk error.

Computer virus: The best solution for viruses is the use of an anti-virus program like Norton or MacAfee etc.

What are driver errors?

Driver Errors

Driver errors are not uncommon and you will find some when you are installing/uninstalling a particular program. Drivers are basically a type of software program that enables an operating system as well as the different programs that are installed on them to effectively communicate with different hardware devices, device controllers, as well as peripherals that are connected to your PC. You can say that drivers are like instruction manuals that provide the different software’s located on your PC with the right information regarding control and enhances communication with various hardware devices.

Dealing with driver errors

There is a huge database of drivers on all computers and it might become difficult and even impossible at times to keep track of the drivers you have on your computer. So if driver errors do occur, it might be difficult for you to correct it at time. There are several reasons that can be attributed to causing the driver errors. Let us take a look at some of the possible driver errors and their probable solutions:

Problem 1

Device has not been properly connected to your PC
The Solution: In such a scenario, if you get driver errors then you need to check the cables connecting the particular device to your computer. Check for any loose connection. If the device is a card then open your cabinet and check if the card is in the right slot and has been properly seated.

Problem 2

You see driver errors showing failed device driver. Such a problem will occur only when:

  • The driver installed by you is buggy
  • The driver has been poorly designed
  • The driver is incompatible with your OS
  • Problems occurred during a driver update
  • There is a hardware conflict

The easiest solutions for the above mentioned problems are two fold: Either find a driver update or find a replacement driver. In either case, when you download or run them then the driver errors will stop showing up. Sometimes, updating a specific component within the driver can also resolve the issue and enhance the performance of your computer. The best place to look for driver updates, new drivers and options for troubleshooting driver errors is the manufacturer’s website. One more thing that you need to check always while downloading a new driver is the Operating System specifics. Drivers are available these days on the basis on the Windows OS being used by you. You can’t download and run a driver specified for Win98 on a WinXP computer.

In Windows XP, you can fix most of the driver errors by visiting the Device Manager utility, which will provide you all information regarding the various devices configured on your PC.

Windows Installer Error

Windows Installer errors can occur on any computer and at any point in time. You might be working on your computer at peace and suddenly you will find an error message saying: “1719/Windows Installer service could not be accessed. Contact your support personnel to verify that it is properly registered and enabled.”

All windows installer errors have a particular code, which starts from 1000 and goes on till 3002. The installer errors with codes that are between 1000 and 1999 are generally known as ship errors and they have to be authored to the windows installer errors table. The error codes which are from 2000 onwards are mostly internal errors and might not have an authored string. These installer errors can occur only when the installation package has been authored incorrectly.

The Symptoms

Even if you don’t get an error message stating installer errors you will still be able to figure out if there is an installer problem or not. Normally, you will get to see certain errors when you are trying to install/uninstall a particular application and the messages will be like:

“Windows Installer Service couldn’t be started”
“The Windows Installer Service could not be accessed”
“Could not start the Windows Installer service on Local Computer. Error 5: Access is denied.”
“Windows Installer cannot delete a system file protection catalog from the cache.”
“Windows Installer cannot retrieve a system file protection catalog from the cache.”

The Solution

There are different solutions for different installer errors but here are a few common ways of troubleshooting

Solution 1

First you need to unregister the windows installer and then re-register it. Here’s how you can do it:

  • Open the Start menu and click on Run
  • When a box opens, type msiexec /unreg, and press ENTER.
  • Go back to the start menu and click on Run
  • When a box opens, type msiexec /regserver and press ENTER

Solution 2

The second solution that you can apply for windows installer errors is upgrade to the next version of the windows installer. To get an upgrade, you can do the following:

  • Go to Microsoft Internet Explorer and find the Microsoft Web site or directly click on
    http://msdn.microsoft.com/downloads
  • When you see the left pane tree menu, click on Setup and System Administration and then on Setup
  • Next click on the Windows Installer and also click on the appropriate link for your operating system
  • Finally click on Download and get the new version

Solution 3

The third solution for installer errors is to use a windows installer clean-up program, which can help you to uninstall the failed program. You can find the windows installer cleanup utility at:
http://support.microsoft.com/default.aspx?scid=kb;en-us;290301