Wednesday, December 29, 2010

Windows Code 28 Error Message

A code 28 error message is displayed by Windows when there is a problem with a piece of hardware that is connected to the computer. This type of error message is one of the Device Manager error codes, which are specific codes that are used to indicate that there is a problem with a device, from issues with drivers to conflicts within the system to other hardware problems like faulty installations. In the case of a code 28 error message, this code is used to indicate the driver(s) for the particular piece of hardware have not been installed.

Because this code is so specific, it makes it easier to troubleshoot and resolve the issue. While there are numerous reasons for faulty or missing drivers, the good news is that the same steps are followed to correct the problem, so you don’t actually have to determine why the driver(s) are missing.

The first thing that should be done is to restart the computer. In some cases, there may just be a glitch or bug that will disappear by rebooting the system. If you restart your computer and you still get the same error message, then you need to move on to the following.

If you had updated or installed a new piece of hardware directly before the code appeared, then it is likely that this is what is causing the problem. Uninstall and re-install the hardware to see if that corrects the issue. Also, if you had upgraded a driver, you can roll it back to the previous version. If the code 28 error message appears and you haven’t changed or added anything to your computer lately, it could be that a driver is out of date. In this case, you need to update the driver for the hardware to the latest version. In some cases, the error may be due to Windows, so installing the latest Service Pack could rectify the issue.

Finally, if you have tried all the above, the problem may actually be with the hardware itself. If this is the case, then you will have to replace the hardware with a new piece.

Wednesday, December 22, 2010

Runtime Error 76

The runtime error 76 message is displayed on a computer screen when the path cannot be found by the program that is running. What this means is that the spot where the program should be storing, or writing, data cannot be located. In other words, the program doesn’t know where it should be looking. This often results in the program freezing or crashing. This type of error can occur at any time with any program, as running programs are constantly accessing and rewriting data as they are used. As soon as a problem occurs in this process, error messages will begin to appear.

There are a number of reasons why the path to the data cannot be found. If the program was not installed correctly, the locations of files may not be correct. This means that the program will think that a file should be in a particular place, but in fact it won’t be there. Also, moving files can cause this error as again, the program will expect a file to be in a specific location. By moving it, the program continues to go to the original spot, but nothing will be found there.

It is relatively easy to correct for these types of runtime errors. First, you should run a virus check to ensure that the program has not become corrupted in some way. If you have moved files or folders, moving them back to their original locations should correct the problem. Should you still be having problems, try uninstalling and re-installing the program to ensure that all files are installed correctly.

Thursday, December 16, 2010

Illegal Operation Error Messages

Illegal operation error messages are often displayed by Windows when it receives a request from a program running on the computer that is not understood by Windows. As a result of the request that is not understood, what the program is trying to do will not be completed. When this occurs, Windows usually stops or shuts down the program that sent the offending request and then displays the illegal operation message on the computer screen.

Illegal operations can be caused by several different factors including corrupt files, bugs in software programs, errors in the Windows operating system itself (which are rare) and sometimes, viruses or malware files. Illegal operation errors can vary in severity with some causing fatal crashes of the system and others just stopping the program that is running. In some cases, work that is being done using the offending program will be lost.

Manually fixing the cause of an illegal operation error message can be difficult as it can be hard to find and replicate what actually caused the error message in the first place. If the program is frozen, you can close it using Task Manager and try restarting it. Sometimes the illegal operation error is due to a conflict with another program so restarting the program or rebooting your system may be enough to correct the issue. If you are consistently getting the error with one particular program, you can try uninstalling and re-installing it. Finally, using a registry cleaner can help get rid of corrupt registry files that may be causing illegal operation errors.

Tuesday, December 14, 2010

HTTP 503 Service Unavailable Error

Like all HTTP errors, the HTTP 503 Service Unavailable error message can be customized to fit the site. This is unlikely, but common messages that appear when there is a 503 error include:
  • Service Unavailable
  • Service Temporarily Unavailable
  • 503: Service Unavailable
  • HTTP 503: Service Unavailable
No matter what message displays within your browser, they all mean the same thing that the server that stores the website that is trying to be visited is not available. There are a number of reasons that can cause a server to be unavailable from too much traffic trying to visit the server (it is overloaded) to maintenance being done on the site or the server to a problem with the Internet connection to that server.

The good news is that this is a server-side problem, so there is nothing wrong with your computer or your Internet connection. In fact, you should be able to view other websites without any difficulties. You should only get the HTTP 503 error on the site that has the server problems. On the downside, you cannot resolve the problem. What you can do is to try refreshing the website, for temporary glitches, or you can try coming back later. Unfortunately, you are at the mercy of those who run the server and will have to wait for them to correct the problem causing the server to be unavailable.

Wednesday, December 8, 2010

Windows Installer Error 1714

Error 1714 is often displayed when a user is trying to install a later version or upgrade of a program that is already found on the computer. When installing a new version or upgrade, it isn’t necessary to remove the previous versions. During an upgrade, the Windows Installer usually removes any previous versions that are no longer necessary and then installs only those parts of the later version required to run the program. If there is a problem during the removal process, this is when the error 1714 message will be displayed.

There are several reasons why an error 1714 message may be displayed, including:
  • Corrupt of missing files that are required to uninstall the program.
  • Windows files that are outdated.
  • Malware and viruses.
  • Corrupt registry files.
To resolve the 1714 error, there are a number of different solutions available. First, you should try and remove the older version of the program using the Add/Remove Program tool from within Control Panel (Programs and Features in Windows 7). Choose the program you are trying to update from the list and then follow the steps to uninstall it manually. You can also try to repair the previous version by re-installing it using the original installation CD or a download from the Internet.

If either of the above fails and you are given information on what files are causing the problems, you can try to delete them manually. This should be done with extreme caution as you don’t want to cause problems with other programs running on your computer.

Wednesday, December 1, 2010

HTTP 502 Bad Gateway Error

HTTP 502 is another common status code that is given by a server that is connected to the Internet. If a web page, site or some functionality within the page or site doesn’t load properly, these types of codes are displayed to identify what is causing the problem on the page. When an HTTP 502 error is displayed, it means that the server that is trying to load the web page you are trying to view received an invalid response from the server where the web page actually resides. What this means is that the web page cannot be loaded and you will not be able to view it.

The HTTP 502 Bad Gateway Error is used to identify a problem that is occurring between two servers on the Internet. It has nothing to do with the computer that is being used to access the web page or the Internet connection from that computer. Unfortunately, this means that you may not be able to resolve the issue that is causing the error. There are a few things that can be done though if an HTTP 502 error message is encountered:
  • Refresh the page. Sometimes the error is only temporary and by refreshing or reloading the page, the error may be removed.
  • Retry the page later. Because this is a problem with a server accessing the Internet, it means that someone may need to troubleshoot and correct the problem causing the error. This can take some time, so you may have to try revisiting the page at a later time or date.
  • Contact the webmaster for the site. If you find that after some time you are still receiving the 502 error message, you can try contacting the webmaster for the site to let them know of the issue. This could then lead to them making the necessary corrections so the page will load again.

Monday, November 29, 2010

Beginning Dump of Physical Memory Error Message

On starting your computer, you may find yourself faced with a blue or black screen and a message stating “Beginning dump of physical memory.” Of course, this is never a good sign, and while rebooting your computer may cause it to disappear temporarily, it is likely to come back. So, what is meant by a message claiming it is beginning dump of physical memory and what should you really do?

In the majority of cases, this error message is due to a hardware problem. It can be as simple as a loose connection, or as serious as a faulty piece of hardware, but the fact is, you will be probably dealing with the RAM found within your computer or an external memory device, such as an external hard drive or a USB memory stick.

If you have external memory devices connected to your computer, you should remove them and then run the computer to see if you still get the message. If your computer appears to work fine, without the message appearing again, you can try adding your external devices one by one. A loose connection or a bit of dirt or debris in the connection could be all that is causing the problem.

Reseating your RAM within your computer may also correct the problem. As with external devices, a loose connection or dirt or debris can cause problems when your computer tries to access the RAM. Also, if you have added memory to your computer, there could be a conflict. Finally, if none of these correct the issue, it could be that your RAM is corrupt. In this case, a visit to your local computer technician is probably in order.

Monday, November 22, 2010

Cyclic Redundancy Check Error

A cyclic redundancy check (CRC) ensures that when data is being transferred, it is secure and uncorrupted … or cyclic redundancy checks are done to make sure your data is OK. Basically, it is a procedure that continuously checks data to ensure it wasn’t damaged during the transfer process. When a CRC error message is displayed, it usually means that the file the computer is trying to access has been corrupted in some way. Although this type of message may be daunting, on the plus side, it does not always mean that you have lost all of the data.

Data that is being transferred is broken down into small pieces, and each of the blocks of data is assigned a CRC value. If something goes wrong when the data is moving between the origination of the transfer and its final destination, the CRC value that it arrives with will not match the original one that was assigned when the transfer was started. It is at this time that the CRC error message will appear.

These types of error can occur with any type of data transfer, including sharing files over the Internet or a network or trying to read data from a CD or DVD. If the error occurred during the transfer process, the original data should still work fine, so in many cases trying the transfer again should correct the problem.

Thursday, November 18, 2010

Duplicate Name Exists

If you are using a computer that is connected to a network, whether at home or in the office, the duplicate name exists error message is displayed when the name of a Windows computer is the same as or causes a conflict with another computer already connected to the network. In most cases, the error appears when more than one computer has been assigned the same name, or the Windows workgroup has the same name as the computer attempting to connect to the network.

When the duplicate name exists error message is displayed, the computer that receives the error message will be unable to join the network. While the user will still be able to use the computer, it will run in an offline mode, thus any shared documents, folders or hardware will not be accessible. For most people, working offline is not acceptable, but the good news is that this type of error is usually very easy to fix.

Basically, all that needs to be done is to change the name of the computer so that it is not the same as another computer in the network or the Windows workgroup. Computer names can be accessed System in the Control Panel. Enter the new name and the computer should be able to once again connect to the network.

Monday, November 15, 2010

Limited or No Connectivity Message

The limited or no connectivity message is usually displayed when you are trying to connect to either a computer network or the Internet. When this happens, you will either be faced with an error message that reads similar to “Limited or no connectivity: The connection has limited or no connectivity. You might be unable to access the Internet or some network resources.” Or there may be a yellow exclamation point over connectivity icon in the task bar.

There are a number of different reasons why this type of message may appear, and based on your situation, one of the following should correct it:
  • If you connect to the Internet using a broadband router, resetting your router often clears the glitch that is causing the connectivity problems. To reset your router, unplug it for 15 to 30 seconds and then plug it back in. If this only temporarily corrects the issue, try the next step.
  • Check the IP address for your computer (see the IP address error post). Powering off your modem and your router can clear this issue. You may also need to restart your computer.
  • If you are connecting using an Ethernet cable, the problem could be with the cable. Replacing the cable with one that you know works will clarify if this is the issue.
  • For users who connect using WiFi, your security key may be incorrect. Check and update the security configuration to re-establish connectivity.

Monday, November 8, 2010

IP Address Conflict

An IP address, or Internet Protocol address, is a label that consists of a string of numbers that is assigned to any computer or device that is attached to a computer network or the Internet. The main reasons that IP addresses are assigned is that it gives a name to each device attached to the network or Internet and allows the location to be addressed.

When you receive an IP address conflict error message, it means that an IP address has been assigned to two or more computers or devices attached to the network or Internet at the same time. When this occurs only one of the computers or devices will be able to access the network or Internet.

While this can be frustrating for the user who cannot access the network or Internet, it is quite easy to fix, all you need to do is release and renew your IP address by completing the following steps:
  1. From the Start menu in Windows, open the Command Prompt.
  2. Enter ipconfig in this window to determine if you have been assigned an IP address and if your computer is holding it.
  3. If an IP address is listed, type ipconfig/release to clear the address.
  4. Next, type ipconfig/renew to have a new IP address assigned. (Complete this step whether an IP address was listed for your computer or not.)

Monday, November 1, 2010

IRQL_NOT_LESS_OR_EQUAL

Unfortunately, when you see the IRQL_NOT_LESS_OR_EQUAL message, it usually means that your computer has just crashed and you are now facing a blue or black screen with just this message displayed. In most cases, when you are confronted with the IRQL_NOT_LESS_OR_EQUAL message, it is likely that you have a hardware issue and not a software problem.

What the IRQL_NOT_LESS_OR_EQUAL message means is that your computer tried to go to a point in the memory of your computer and either what is was looking for wasn’t there or the address for the point was incorrect. While being faced with the blue screen of death can be daunting, particularly if you were in the middle of working on something, there are things that can be done to your computer up and running.

For many people, the IRQL_NOT_LESS_OR_EQUAL message is displayed when your central processing unit (CPU) has overheated. You can check this by restarting your computer right away and then pressing the F2 during the start up sequence to go to the BIOS screen. From there, you can check the temperature of your CPU. If it is too hot, purchasing a simple external fan for your computer is a quick fix for this problem.

More seriously, this error message may indicate that you have a memory problem. This is more difficult to rectify and often means having to purchase new memory and then reinstall your programs etc.

Sunday, October 31, 2010

Rundll Error Messages

Rundll error messages are often encountered when attempting to start a computer or to run a program loaded on the computer. The reason that these types of errors are encountered at these times is due to what the rundll files actually do. Rundll.exe and rundll32.exe are used to launch dll files stored on the computer. Rundll.exe and rundll32.exe are important parts of the Windows operating systems and are key to having other programs run properly.

Unfortunately, a number of viruses, malware and spyware applications have used the same filename, which is usually when errors begin to occur. Valid rundll files are located within the following folder: Windows\System32. If you find rundll files in any other places, it is likely that they are viruses.
Rundll errors occur because the program that is trying to be launched cannot access the appropriate files. In most cases, the error message will state that the program cannot be loaded due to a missing file.

There are several ways to correct rundll errors based on whether they are due to an error in the registry or whether through a virus infection. Listed below are a number of steps that can be followed so that the rundll error can be fixed.
  • Restart your computer – In some cases, just restarting your computer will correct the problem. Usually, it is better to shut down and then start it again, instead of choosing restart. If this doesn’t help, you should move on to the following.
  • Uninstall / re-install the program – As stated above, the error message often clearly states what program cannot be launched when a rundll error is encountered. Uninstall the program and try installing a new and up-to-date version. When you have uninstalled the program, be sure to delete and files or folders and then re-install the new version. Restart your computer after the installation completes and try running the program.
  • Run an anti-virus scan – Using Windows Task Manager, you can check the directory for any file. By opening Task Manager and clicking on the Processes tab, you will be able to see all instances of rundll.exe / rundll32.exe that are currently running. You need to have the Command Line column present to see the path for the file. To view the Command Line column, go to View \ Select Columns and then tick the check box beside Command Line. If you see an instance of the file not found in the System32 folder, you should run a virus check to find and fix the virus.

Wednesday, October 27, 2010

No Signal Message

Nothing can be more frustrating than turning on your computer and then being faced with the No Signal message being displayed on your monitor, particularly if your computer has started fine and appears to be running (fans whirring, lights on, etc.). Of course, to make matters that little bit more annoying, you can’t see what your computer is doing.

The No Signal message literally means that your monitor is not getting a signal from your computer, but it does have power. There are many different reasons why this could be happening, so the solution will depend on what the actual cause is.

Check the Cable

Before doing anything else, you should make sure that the problem is not due to the cable connecting your monitor and computer. First, you should ensure that the cable is plugged in properly to both the monitor and the computer. Also, ensure that it has not been damaged in anyway. If the cable appears fine, yet you are still faced with the No Signal message, you may want to try another cable just to be sure. If possible, use a cable that you know works. If you are still faced with the No Signal message, then the next cause to check is the monitor itself.

Faulty Monitor

Often, if there is a problem with the monitor, not only does the No Signal message appear on its screen, but most computers also beep on start up when the monitor should be connecting. To determine whether it is your monitor, try plugging the suspect monitor into another computer. Also, you can try plugging a different monitor into your computer. If the monitor doesn’t work when plugged into another computer, then it is likely that you need to have something repaired. If you try a number of different monitors and none of them work, then there is a problem with your computer.

Update Drivers

If you have one monitor work but not another, it could be down to the fact that you have an out of date or faulty driver. Use the Device Manager in Windows to update and fix any drivers. Once you have checked your drivers, try plugging the monitor in to see if it now works.

Graphic Card Issues

Sometimes a faulty graphic card can interfere with how a monitor works. Again, you can check the drivers for a graphic card using Device Manager. Also, you can test the graphic card compatibility by taking out one card and putting in another. If you feel uncomfortable doing this, take your computer to a repair technician so that you don’t cause any further damage.

Wednesday, October 20, 2010

HTTP 500 Error

HTTP 500 errors can occur with any browser at any time. As with most browser errors, 500 errors can be customized based on the website where it is encountered. No matter how the error looks though, it will always mean the same thing. When you are faced with a message telling you that there is an HTTP 500 error, it means that there is a problem on the server where the website is being hosted.

All 500 errors will be shown as a normal web page within the browser and will contain messages similar to the following:
  • 500: Internal Server Error
  • HTTP 500 Error – Internal Server Error
  • 500 Error
This is a very general code that is used to show that something is wrong on the server, but the exact problem is unknown. Fortunately (and unfortunately), this means that the problem has nothing to do with your computer or the browser you are using, but instead with the website itself. In other words, it is a server-side error.

While the error is due to something wrong on the server, there are things you can do to try and get to the web page you want to look at.

First, try reloading the URL that you are visiting. In some cases, these errors are due to a very temporary glitch and reloading or refreshing the page can often rectify the situation. You can try hitting the refresh button or you can try re-typing the URL into the address bar.

If reloading the website doesn’t help, try visiting the page later. Most 500 errors are temporary in nature and while some seem to correct themselves right away, others do need the web developer to make some corrections. If this is the case, visiting the site later will give the developer time to make any necessary corrections.

Most websites provide a way to contact the web developer or designer (usually by providing an e-mail address). Contacting this person is one way to ensure the issue is noted and that the person gets to work on the situation as soon as possible.

Wednesday, October 13, 2010

Spool32 Error Message

With older versions of Windows, 95, 98 and ME, spool32.exe was the application necessary to control print jobs. Spooling allows print jobs to be stored on the hard drive of a computer prior to them being sent to the printer for printer. The print jobs are stored temporarily while the printing is occurring. The reason behind spooling is that by moving the print job from the program from which it was sent to the hard drive of the computer, the user would be able to begin using the program again much more quickly instead of having to wait for the printing to finish.

If something within the computer is preventing this process from happening correctly, spool32 error messages will be generated and displayed. Generally, one of the following messages will be displayed when a spool32 error occurs:
  • SPOOL32 caused a General Protection Fault in module Kernal32.dll at [system address].
  • SPOOL32 caused an Invalid Page Fault in module Kernal32.dll at [system address].
  • SPOOL32 causes a Stack Fault in module Kernal32.dll at [system address].
No matter what error message you receive, you should try each of the following to correct it. Upon completing one of the steps, try to print. If a spool32 error message still occurs, move on to the next step.
  • Perform a Clean Boot – A clean boot disables all third party programs and ensures another program, such as an anti-virus program, is not causing the problem.
  • Change How Print Files are Handled – Instead of having print jobs spooled, you can change the format from Enhanced Metafile (EMF) to RAW. In order to change the spooling settings, you need to open the Properties dialog box for your printer. On the Details tab, click Spool Settings and then click Print Directly to the Printer. In the Spool Data Format box, choose RAW.
  • Update or Fix Printer Drivers – Outdated drivers or drivers with errors can cause printing to stop working. Within the Windows Device Manager, you can check if a printer driver has an error (usually shown by an exclamation point on the driver). Also, from within the Properties of your printer, you can update the drivers.

Wednesday, October 6, 2010

Firefox is Already Running Error Message

A common error message that is encountered when using Firefox is:
“Firefox is already running but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.”

This error message will appear when a Firefox is initially being started, and it can be caused by a number of different reasons, including:
  • Firefox did not shut down properly the last time it was used,
  • The Firefox profile folder cannot be found or accessed by Firefox, and
  • There is an issue with access rights available for Firefox.
Each of these issues can cause the Firefox is already running error to be displayed when a new instance of Firefox is attempted to be launched. Unfortunately, the error message is always the same, so there is no way of knowing which issue is causing the problem. As such, each fix will have to be worked through until the error is corrected. Profiles and access rights will be addressed in the future.

Using Task Manager to Close Firefox


If Firefox did not close properly the last time you used it, you can either restart your system or use Windows Task Manager to correct the problem.

In most cases, when you open Task Manager (Ctrl+Alt+Del), you will not see an instance of Firefox running in the Applications tab. Instead, you will have to go to the Processes tab and close Firefox from there. Scroll down through the processes until you find firefox.exe. Click it to highlight it and then click the End Process button. Do this for all entries you find.

You should now be able to start Firefox normally.

Restarting Windows to Close Firefox


In some cases, even though you closed Firefox, it may still be running in the background (due to an error on closing). You can close all background applications by shutting down and restarting your system. If it is running in the background, you may receive an error when the computer is trying to close asking if you want to shut down the program.

When your computer starts up again, you should be able to start Firefox as normal.

Friday, October 1, 2010

R6034 Runtime Error

R6034 runtime errors often occur when browsing the Internet or opening or closing an Internet browser, usually Firefox, Internet Explorer or Google Chrome. They can also appear when trying to shut down a computer. Many computer users can become frustrated very quickly with R6034 runtime errors as they do not know when or why they are occurring.

In most cases, an R6034 runtime error is caused by a damaged or corrupted file in the Windows registry. Because the role of the Windows registry is to keep track of all activity that occurs on a computer, installing, removing and using applications means that changes are constantly being made to the registry and the files found within it. Over time, the registry will begin to accumulate damaged files or fragments of files, usually due to installations or removals that do not complete properly. These files can then affect how well the registry runs and cause errors such as the R6034 runtime error.

Removing R6034 Runtime Errors


While these errors can be annoying, they are often quite easy to correct. In most cases, running a virus check and a registry cleaner should find and fix any errors within the registry that are causing errors such as the R6034 runtime error. There are many registry scans and cleaners available for download. Most provide a free scan of the computer, but will ask users to pay for the fix side of the program.

After downloading and installing a virus scanner and registry cleaner, you should start your computer in Safe Mode before running them. The reason to do this in Safe Mode is that most functionality isn’t available, which will allow you to make changes to the registry without affecting the rest of the computer.

To run in Safe Mode, restart the computer and when the screen appears showing the computer hardware, begin to tap the F8 key. This will take you to the Advanced Boot Options screen, which allows you to choose how you want to start your Windows session. Scroll down using the arrow keys until Safe Mode is highlighted and then press the Enter key. Once your computer has booted in Safe Mode, run the virus scan and then the registry cleaner. When these applications are finished and the errors have been corrected, you can restart your computer and it will automatically boot to a normal Windows system.

Wednesday, September 29, 2010

MSN Messenger Error 80048820

Error 80048820 can occur when trying to launch and log on to the Microsoft Messenger application. When this happens, you will often be greeted by a pop-up box that says “Sorry, we were unable to sign you in to the MSN Messenger at this time. Please try again later.” In the bottom left hand corner, a numeric code is shown that tells you which error you have encountered, in this case, 80048820.

In most cases, this error is triggered because the system time or date is incorrect and needs adjusting. Other possible causes of error 80048820 include: Internet Explorer has an incorrect proxy setting, the softpub.dll file has become de-registered, or firewall problems. In order to resolve this error and stop it from happening, you can do the following:
  1. Log on as an administrator and correct the computer’s clock and date so that it is showing the right time. This is the most common cause of this error, so once you have done this, try launching MSN Messenger. If this did not correct the error, move on to the following.
  2. In Internet Explorer, go to the Tools menu and click Internet options. Go to the Connections tab in the pop-up box that opens and then click LAN setting. In the LAN setting box, make sure that the check box beside “Use a proxy server for your LAN (These settings will not apply to dial-up or VPN connections)” is unchecked and then check the box beside “Automatically detect settings.” Click OK through the boxes to save the settings.
  3. Turn off your firewall temporarily and try to connect. If you can, then you need to adjust your settings in your firewall so that MSN Messenger is allowed access when the firewall is turned on.
  4. Finally, in some cases, correcting this issue can be as easy as unplugging your modem. Removing the power source for 15 – 30 seconds from your modem resets the connection and may be all you need to get yourself back on Messenger.

Wednesday, September 22, 2010

Internet Connection Error 619

When attempting to connect to the Internet from a computer that has Windows XP installed, a connection error may be generated. If connection error 619 occurs, it often causes the connection attempt to fail, which means that you will not be able to browse the Internet at all.

Internet connection error 619 can be caused by a number of different factors, including: a third party program, a problem with the access numbers provided by your Internet Service Provider (ISP) for those using dial-up, a modem problem, or a router problem. Depending on what is causing the error, there are different methods for resolving it.

If a third party program is causing a problem with your Internet connection, your best bet is to uninstall it. Once the program has been uninstalled, you should try connecting to the Internet to ensure that has resolved the problem. If you can once again connect to the Internet, you can try re-installing the program to see if it was just an issue with that installation. If it once again interrupts your connection, you should remove the third party program from your computer.

With a dial-up connection, there are often several numbers you can try to connect to the Internet. You should try all of them to see if any of them will connect. If you are still having issues, you may have to make some changes to your telephone line, like removing call waiting or adding a custom prefix when dialing your ISP.

To confirm if there is a problem with your modem, you should check its status in Device Manager. If there is an X or any issues, you can uninstall your modem. Once it has been uninstalled restart your computer and it will attempt to install the hardware. You may have to provide a disk for this. Once your modem has been installed, you can run a query on its set up from within the Properties window. If it appears to be set up correctly, try connecting again.

To resolve issues with your router, you will need the manual that was sent with it. Within that, you will find an IP address to enter so that you can check the configurations of your router. Follow the steps and ensure your router is set up as provided by your ISP.

If none of these remedies work, contact your ISP to determine if the problem is at their end.

Thursday, September 16, 2010

npswf32.dll Error

When browsing different sites on the Internet, it is not uncommon to come across sites that use Flash and Shockwave as part of their programming. Particularly those sites that are animated will have some kind of Flash programming embedded. The npswf32.dll file is associated with the plug-in that is needed to run the Shockwave animations on these websites.

When there is an issue with npswf32.dll, it will often cause a browser to crash, particularly with older versions. The fact that your browser crashes and you get an npswf32.dll error means that either your browser is out of date or the version of the npswf32.dll file on your computer is out of date.

To stop your browser from crashing when you visit pages that include Shockwave applications, you can do one of two things (in some cases, you may need to do both):
  1. Update your browser – Older versions of Internet browsers may not be able to connect properly with newer Flash plug-ins. Whichever browser you are using, you should download and install the latest version available. If you are still having problems after doing this, then it is likely that you will also have to update the npswf32.dll file version.
  2. Update the npswf32.dll file – If you don’t know what version of the npswf32.dll file you are using, it won’t hurt to try updating it. You can do this in a number of ways. The easiest and best way is to install the latest version of the Flash player. By doing this, you will be installing all the most up-to-date files associated with it. The npswf32.dll file is often found in a number of places on your computer, so you could copy it from another location, or download it from the Internet and replace the file you have.

Tuesday, September 14, 2010

Windows Media Player Error C00D11B1

If Windows Media Player cannot play a particular file, you may encounter the C00D11B1 error message. There are a number of different reasons that this error message is displayed, including:
  • The driver for the sound card in your computer needs to be updated.
  • The sound device you are trying to use to play the file has an out of date driver.
  • The sound device is not functioning properly.
  • A sound card or hardware to output sound has not been installed on your computer.
  • If trying to play an Internet file, the server hosting the file may be busy.
  • The file itself may be corrupt.
Because this is such a wide ranging and varied list, the first thing that needs to be done is to determine what is causing the error itself. Obviously, if you haven’t got a sound card or sound device installed, then you will need to do so. If you do have a sound card and sound device installed, then the best way to determine if one of them is the issue is to use Device Manager.

To run Device Manager, right click Computer (My Computer) in the Start menu and then click Manage. When the window opens, choose Device Manager from the left hand column. In the center column, expand Sound, video and game controllers. This should list your devices. If there is an X beside any of them, then it has been disabled. Right click and click enable.

To update the driver, right click your sound card or device in Device Manager and click Update Driver Software.

If the problem is with an Internet file, you can’t do a lot about it and will just have to try later. Finally, if the file is corrupt, you will not be able to play it and should try to find a new version of the file, one that is not damaged.

Wednesday, September 8, 2010

Runtime Error 339

One of the most common error types to come across when working with a Windows computer is runtime errors. Particularly as computers age and are used more and more, it is likely that runtime errors will occur more often.

Runtime error 339 commonly occurs due to a missing file when trying to install software on a computer. Specifically, this error occurs if the file that is missing is an .ocx file. OCX files are commonly referred to as ActiveX controls. These types of files can be used by many different software programs and usually control the interface between the user and the program.

Unfortunately, runtime error 339 doesn’t occur when you are installing the program, but is usually triggered when you try to launch it after installation or try to use some part of the program. The specific activity requires the missing .ocx file, which in turn causes the error message.

The most common reason for runtime error 339 messages is missing or corrupt Java files or ActiveX controls. Ensuring your versions of Java and ActiveX are up-to-date is one way of combating these types of errors. Also, the files may have been corrupted due to errors in the registry of your computer. In this case, it is worth running a scan of your hard drive and then using a registry cleaner to get rid of any corrupt or damaged files. Once you have done so, you should try re-installing the program.

Friday, September 3, 2010

Windows Installer Error 1722

While most software programs come with their own installation program, it is not uncommon for the installation to actually be run by the Microsoft Windows Installer. Microsoft included the Microsoft Windows Installer as a built in feature of Windows XP, 2000, 2003 and Vista.

If everything is running normally, upon starting the installation, you would just have to click through each window in the step-by-step process until the installation is complete. Unfortunately, this doesn’t always happen and, when there is a problem with a software installation, that is when the error 1722 message can appear.

Installer error 1722 occurs when the Windows Installer cannot run the necessary files required to install the program. As a result, the installation may fail and quit prematurely or you may get a message saying there is a fatal error during installation. The reason the installation fails is usually due to the files being damaged, corrupted or missing or due to a problem with the Windows Installer itself.

There are a number of ways to fix an installer error 1722, which include:
  • Try using a different software program. If you have downloaded it, delete the original and download again as there may have been a problem during the download. If you are installing from a disk, try using a different one to see if the problem persists.
  • Ensure the latest version of InstallShield is installed on your computer. If not, download and update your version.
  • If you are prompted that the files can’t be found, you can do a search to point the installer to the correct location. If the files are in fact missing, you will need a new program to install.
  • Finally, if none of the above work, you may need to run a registry cleaner to remove any corrupt files left from previous attempts at installation. Once your hard drive has been cleaned up, the installer should run fine.

Tuesday, August 31, 2010

Fixing JavaScript Errors

Different Internet browsers show that there are JavaScript Errors in different ways. In most cases, you will have either a warning sign in the status bar or a window will pop up explaining that there are problems with a script running on the page. If you only get the warning icon, you can find out what’s wrong by clicking on it. This will open the window and give the details of the errors that are encountered. There are times where the error will state that there is a JavaScript error, although most of the time it will just say there is a problem with a script running on the web page.

How to Fix JavaScript Errors

If you get a scripting error message, the first thing you should do is close the window and try to load the web page again. If you get the same error on trying to load the page again, there can be a number of causes.

Internet connections can actually effect how well and if sites will load and run. With dial up or slower broadband and cable connections, more complex web pages may not run. This is due to the time taken for the site to download and the capability of the Internet connection.

Ensure that you have JavaScript installed in your browser and also make sure that it is an up-to-date version. You can find out if your browser runs Java by checking the following:
  • Firefox – Tools > Options > Content, check the box Enable JavaScript
  • Internet Explorer – Tools > Internet Options > Programs, click the Manage add-ons button and scroll down to make sure that JavaScript is enabled.
If you are unsure, visit the Java website and follow the instructions for installing Java for the browser you are using.

Finally, if none of this helps, there may be a problem with the code, and if you did not write the web page, then there is little that you can do, except contact the webmaster for the site and let them know.

Thursday, August 26, 2010

Introduction to JavaScript Errors

At one time or another, it is likely that all Internet users have been confronted with a JavaScript error. While what happens depends on the browser being used and the type of error, what JavaScript errors tell you is that a script on the web page that is being viewed either contains an error or not running properly, but what does this mean?

What is JavaScript?

JavaScript is a type of scripting language used to code the elements of web pages and web sites. There are a number of different scripting languages in use, including HTML, which is the most basic, but JavaScript is one of the most popular languages used for coding advanced web sites. JavaScript is referred to as a client side language, which means that it runs on the client’s browser and not on the server where the web page is stored. In other words, everything that happens due to JavaScript coding happens on your computer.

What Causes JavaScript Errors?

One of the simplest answers to why JavaScript errors occur is because it is a client side language, which in turn means that there is greater scope for things to go wrong when a web page is attempting to load and run. Web pages that are coded using JavaScript are compiled on the Internet browser on the user’s computer. As web sites become more and more advanced, the additional features can make them slower to load and even cause them to stop running altogether. It is when this happens that JavaScript errors begin to appear.

Tuesday, August 24, 2010

Five Tips for Resolving ntdll.dll Errors

As stated previously, there are a number of different ntdll.dll error messages that can be caused by a variety of reasons. Here are five ways to try to resolve ntdll.dll errors when they appear:
  1. If this is the first time you have received an ntdll.dll error, the first thing you should do is shut down and restart your computer. The error message could be a one-time glitch and restarting your computer may correct the problem.
  2. Should you get the error message during or just after installing a new version of Windows, the first thing to do is check the actual disk you used to make the install. If the disk is damaged in some way, scratches for example, the install may have completed successfully, but errors may have been caused during the process. If the disk is fine, try installing again. If you are still having problems, you may have a faulty version of Windows itself, so you should try installing from a different disk.
  3. An ntdll.dll error that appears when you launch or run a particular program is a pretty good indication that there is something wrong with that program. Uninstall and re-install the program. Also, make sure you have the latest version and have installed any updates, etc.
  4. If you get the error on running Internet Explorer, it may be caused by an add-on. To test this theory, try using a competing browser like Firefox to determine if you get the same message. If you don’t, then the problem is specifically with Internet Explorer. You can either disable each add-on and test to see if you get the message or uninstall and re-install a clean version.
  5. Make sure you have installed all the latest versions of Windows service packs. Outdated service packs can conflict with programs and cause ntdll.dll errors. Microsoft has addressed issues that caused ntdll.dll errors previously, and by keeping your Windows updates up-to-date, you can benefit from these fixes.

Wednesday, August 18, 2010

What are ntdll.dll Errors?

ntdll.dll is a Microsoft file that can be found in all versions of its operating systems, from Windows NT and XP all the way through Windows 7. The operating system installed on the computer will determine where the ntdll.dll file is found.

There are a number of different causes of ntdll.dll errors and various error messages can be displayed. In most cases, ntdll.dll errors are due to an unknown error on the hard drive. This error can cause errors with Internet Explorer and Windows Explorer, and can even make the computer crash.

ntdll.dll Error Messages

ntdll.dll error messages may be displayed when a program is starting up, running or shutting down. Also, they can appear during Windows start up or shut down. In some cases, the error message may even appear during an installation of Windows. One of several common error messages appear when an ntdll.dll error has occurred, including:
  • STOP: C0000221 unknown hard error \SystemRoot\System32\ntdll.dll
  • STOP: 0xC0000221 unknown hard error C:\Winnt\System32\Ntdll.dll
  • STOP: C0000221 unknown hard error Path\File_name
  • Crash caused in ntdll.dll!
  • Unhandled exception at [ANY ADDRESS] (NTDLL.DLL)
This is not a list of all of the ntdll.dll error messages that can be received, just an example of some of them.

Causes of ntdll.dll Errors

While there are a wide range of causes of ntdll.dll errors, in most cases, the error is down to the ntdll.dll file itself. Many times errors occur because the actual file has been corrupted in some way. Other common causes of ntdll.dll errors are hardware drivers that have been damaged or corrupted and issues occurring between Windows and other programs. In some rare instances, an ntdll.dll error is a result of malfunctioning hardware.

Friday, August 13, 2010

Repairing Corrupt Exe Files

In the previous post, we looked at how to replace .exe files, or the files needed to run all programs and applications installed on a computer. The other way to correct .exe errors when they occur is to repair the file that is causing the problem.

Repairing an Exe File

If the file that is causing the errors cannot be replaced, then repair is the other option available. There are two different ways that .exe files can be repaired, and one is definitely a lot more difficult and should only be attempted by advanced computer users. Basically, when it comes to repairing files, you can either find the step-by-step instructions on the Internet or the second way is to use pre-made software and tools to make the corrections.

There are many help pages and forums that can be found with a quick search of the Internet. These sites will provide the detailed steps that are required to locate and then address any errors that may be found in the .exe file. Of course, this means that the person making the repairs must have some basic knowledge of programming code and also, be meticulous in following the steps. As stated, this is not easy, but it is doable by many computer users, even those who are not trained programmers.

The other option is to run a registry scan. This will go through the entire drive of the computer and highlight any potential errors or flaws that are causing problems for the computer. It will also find files that are not required and could be removed safely, which could cause problems with other programs as well. Once errors have been found, there are software programs available that will fix any errors found by a registry scan, including .exe files. The scanning part of these programs is often free, but it usually costs to have the error correction part of the program.

Tuesday, August 10, 2010

Fixing Exe Errors by Replacing the Files

Computer files that end in .exe are executable files, which means the file will cause the computer to carry out certain functions based on encoded instructions. In other words, these types of files are what are needed to run the programs, or applications, found on any computer. Of course, because these files are used all the time, it is inevitable that eventually errors will crop up.

If an .exe file stops working properly, you basically have two choices for correcting the issue. You can either:
  1. Replace the file, or
  2. Repair the file.
Replacing an Exe File

Before you can replace the .exe file that is causing the problem, you need to identify which program it belongs to. In some cases, this will be relatively obvious, especially if you get the error when you are trying to run a specific program. In the times when it isn’t so clear, the best bet is to do a search on the Internet for the filename. It is highly likely that you will find out information on the file, including what program it runs.

You may be able to just replace the .exe file with a clean version (either the original or one that has been downloaded), but in most cases, it is likely that you will actually have to uninstall and reinstall the entire program to which the .exe file is related.

Friday, July 16, 2010

400 Bad Request/Bad File Request

Web errors offer little information as to why they happen and what to do to fix them. Moreover, any information they do offer can be quite cryptic and mired in technical jargon, usually undecipherable to the common user.

A common web error is the “400 Bad Request/Bad File Request” as it can often come from minor mistakes in the web address or the Uniform Resource Locator, URL. For many web servers, the URL must be exactly accurate in order to reach the page that is requested. The error will occur if there is an error in the spelling of the URL, including case sensitive characters. This means that all of the capital and lowercase letters in the intended URL must be the same as what the user enters into the address bar.

Essentially, what the 400 Bad Request is telling you is that there is some part of the URL that has been entered incorrectly. The web server hosting the site cannot find what you have requested. This gives the error the name of “Bad Request.” If you are entering a specific file path or name and have entered it incorrectly, you may get the “Bad File Request.” In fact, all 400 series of errors imply that the issue is with the user and so the solution must be with the user as well.

This can be difficult with longer URL addresses as many have long complicated strings of seemingly unrelated letters. Try to use hyperlinks directly by clicking on them wherever possible or by copying links and pasting them into the address bar instead of recalling them from memory, especially if they are these kinds of long complicated URLs.

The wrong punctuation can also cause this error as the web server hosting the page or file you are trying to access will read punctuation as letters. Keep in mind that these are considered letters in many different areas of computing.

Finally, you may not be authorized to view the specific file that you are attempting to access. However, in this case, you will usually receive a very specific 400 error message that states “403 Forbidden/Access Denied,” which refer specifically to this instance.

Wednesday, July 14, 2010

Blackberry Synchronization Errors

Synchronization software is almost deceptively complicated to create and make run effectively. The complications related to this type of software become more plentiful as the sophistication of both the computer and their synchronized peripherals increases. When many of us have mobile devices that approach the complexity and computing capacity of our desktops or notebooks, or even exceed those credentials, synchronization software is running to keep up.

Blackberrys are no exception. The many models under the Research in Motion brand comprise a market share of 41.6% of smart phones in the US market. To put this in perspective, Apple iPhone brand takes second place in market share with 25.3%. Most phone carriers will have two or three Blackberry models on their product line. Additionally, when users consider that many of the same or similar programs available on their computer operating systems are installed on their Blackberry, complications can arise.

Blackberrys practice a system called two-way mirroring. This means that programs subject to synchronization, such as e-mail and calendar programs, not only update data from the computer onto the Blackberry, but vice versa. Occasionally data will have to be either expanded or compressed to fit the operating system on both devices.

Most synchronization errors stem from incompatible versions of the Blackberry operating system and Blackberry manager on your computer. Make sure that all versions and patches are up to date. Blackberry also uses Intellisync software to sync devices. Issues can arise with this software in terms of data file paths and new versions.

If you are having issues with Intellisync, you may need to configure the software to be specific to your device. Select the option to configure the PIM, which is your archiving software. Once you have selected the relevant options to your device. Also be sure that the ability to see hidden folders in your documents as these folders will not be included in the sync, but may have relevant information that may cause issues with the sync.

Other sync issues may be with the specific programs themselves, so if synchronization issues persist, makes sure the programs on your computer are set up for hand-held device use. The programs on the Blackberry will be set to sync as a default.

Monday, July 12, 2010

DES is Turned Off, Press Any Key to Continue

Many users try to power down their machines as responsibly as possible by using the Start menu, clicking the “Shut Down” button and choosing the “Shut down” option and, once all programs have been closed, turning off the machine if applicable. But unexpected power offs happen. Power outages, tripped power cords and depleted laptop batteries don’t always allow users to treat their machines the way they would like. When a power off does happen, all users can do is hope they’ve saved their work and expect no complications once a new power source is found.

If your machine has a Gigabyte motherboard, you may encounter the error “DES is turned off, press any key.” DES stands for “Dynamic Energy Saver,” which is a background firmware program meant to optimize the use of your motherboard’s energy efficiency. However, if the machine is not shut down properly, the Energy Saver is not able to guide the energy efficiency necessary to safely power down. Simply put, during an unexpected shut off, the DES will automatically revert into off mode.

Unlike the dialog promises, the command of pressing any key will not work. At this point your only option will be to shut off the machine and try again. However, this error message and the corresponding unresponsive command will persist until some hardware modifications are complete.

Once the machine is off, remove the battery, which will disconnect any residual power source to the motherboard and reset the basic input/output system (BIOS) back to its default settings. This is necessary as a default setting for the DES system is to be on. The battery should be the only thing you remove. Once you start removing other cards and hardware components, a variety of errors can occur.

Replace the battery and turn the machine back on. It may need to restart in safety mode to ensure that Windows 7 starts properly. This should allow all of the default settings in both the operating system and the BIOS to repair itself.

After the machine has started normally and you have not gotten the DES error message, select the Start menu with the Windows 7 logo and find the Gigabyte program. Disable the Dynamic Energy Saver program to ensure that you do not get the same error message again.

Friday, July 9, 2010

Operating System Not Found

You can encounter the frustrating error of “Operating System Not Found” as soon as your machine starts up. It can also appear as “Missing Operating System” or “Setup did not find any hard drives installed on your computer.“ Often, it will not allow you to interface at all with any of the operating system functions. This means there is little that you can do as a user to correct the problem.

This usually happens to machines that have Windows XP installed. The error appears at the start up and does not allow further interaction with the interface of the machine. Users can take some relief that this error is likely not caused by something they did.

When this error appears, it means that there has been a problem with the firmware of the machine. Firmware is a type of electronic and computing system that in some ways could be thought of as software, but is typically much simpler and more integral to the operation of a machine than other software.

Setting the time on a microwave is a user interacting with firmware; the firmware of the microwave. The firmware tells the machine how long to operate for. However, it might be a stretch to call the time settings on a microwave “software.” In computing, the line between these two programming systems often blurs, but computers do have many programs that are clearly defined as software. For our purposes, we can think of software as a program where a change does not affect hardware. Any changes to firmware, however, can and often do affect the hardware.

All PCs have a protocol called a BIOS, which stands for “basic input output system.” The BIOS is part of the firmware of your PC. When you start your machine, you may see the Windows logo and status bars that indicate to you the machine is starting up. Inside the machine, however, is a very different story. This BIOS is connecting the hard disk where your information is stored to Windows XP, so you can access it.
The “Operating System Not Found” error can mean one of the following things:
  • The basic input/output system (BIOS) does not detect the hard disk.
  • The hard disk is damaged.
  • Your hard drive has a malformed master boot record, meaning that there has been a problem with the processes of your computer booting up.
Unfortunately, as this is an issue with the firmware, which can affect the hardware, some extensive physical repairs may need to be done. Check the physical state of your machine to make sure no liquids or dents are in the casing. Check for any exposed components, which may have become damaged. It may be necessary to contact the actual manufacturer of your machine instead of Microsoft and take it to one of their repair centers. Hardware damage can cause irreparable data loss, so back up often!

Wednesday, July 7, 2010

iPhone Error 0xE8000025

Most users probably have a lot of their personal and important information stored on their computer, but the iPhone promised to transfer much of this information to a user’s pockets with its impenetrable exterior and constantly evolving interface. Unfortunately, for many users though, the first time trying to transmit this information can cause the iPhone “0xE8000025” error.

When a user attaches the iPhone to their computer through a USB cable, iTunes, if not already opened should start up. Other programs will start up as well depending on the apps (applications) the user has downloaded onto his or her iPhone. These can include calendar programs and camera software. iTunes, however, is the main program responsible for transmitting music and apps updates. The user should be able to see his or her iPhone in the sidebar of iTunes and its progress when it is sync-ing with the program. This is when the error most often occurs.

The sync-ing software is complex and must ensure that all programs on the iPhone are compatible with all information on your computer. An outdated version of iTunes will not be compatible with the iPhone so a user will have to download a version of iTunes equal to or higher than 7.5. This is because iOS 3, and soon iOS 4 on the iPhone 4, are only compatible with later versions of iTunes. This causes the “0xE8000025” error.

The software can usually be downloaded directly from Apple for free. You may be notified of this the first time you connect the iPhone to the computer, as the iPhone will search for the correct version of iTunes. However, if you are using your iPhone on a different computer than you usually do, you will get the “0xE8000025” error, meaning that it cannot find the correct version and update your iPhone.

Also, to download apps, you must start an iTunes store account. If your account name has a character outside of letters, numbers and basic punctuation, iTunes will not be able to negotiate the updates for your iPhone as the sync-ing software does not know how to read this punctuation.

This error can be common for iPhone users, but is easily fixed by either updating your version of iTunes for free or changing your iTunes user account name to simple letters, numbers and nothing beyond basic punctuation.

Tuesday, July 6, 2010

Wii Error Code 51330

Like many gaming consoles, the Wii console can be integrated with you home WiFi system. This integration is commonplace and allows online gaming as well as for users to connect with other gamers remotely. Wii allows you to create small avatars of yourself, known as Mii that can appear in the games of users all around the world.

However, like network connection errors with standalone computers, errors can occur with your Wii connection. A common error for Wii gamers is the Error Code 51330, which has to do with security settings of your WiFi network.

Currently, Wii is only compatible with an older security certification program, known as the Wired Equivalent Privacy (WEP). If you have set your network access to a certification program called WiFi Protected Access (WPA), the network will have stricter security protocols as set-out by the IEEE 802.11 standards of WiFi protection. This update of the standards for WiFi connections was due to issues involving PC operating system compatibility and key attacks, which are not relevant to the Wii.

Your Wii broadcasts something called a Service Set Identifier (SSID), which identifies it to the router. Your Wii will only broadcast the SSID that is compatible with a WEP, which will cause problems if you have set your router to a WPA standard and password. These setting can be changed either by calling your service provider or by making the switch on your router. Of course, if you change this setting on your router, you will have to set other devices to WEP to make sure they will be able to connect as well.

Error Code 51330 can also be resolved without changing the actual settings of your router. Instead, you can enter the WEP password manually through your Wii’s settings. On the router menu, select the manufacturer of your router and match the router to the menu list.

Typically, if the Wii cannot negotiate this network compatibility, a restart of both the Wii and the router may resolve it to make sure the SSIID broadcast is clearer. The Wii should pick up the SSID automatically, but require a manual configuration of the settings by you.

Check the manual you received with your Wii to ensure that you have compatible hardware to gain WiFi access. The hardware should be able to resolve the issue as long as the WEP password is enabled.

Tuesday, June 29, 2010

Outlook Connection Errors

When you try to send and receive e-mail using Microsoft Outlook, you may be familiar with some of the common error messages that indicate there is a problem with the connection or server. The server cannot be found or the server being interrupted are both common error messages that Outlook users may receive.

Listed below are just a few of the most common connection related error messages that are sent by Outlook:
  • The server could not be found (0x800ccc0d)
  • Sending and Receiving reported error (0x800ccc0f)
  • Sending and Receiving reported error (0x80042109)
  • The operation timed out waiting for a response from the POP server (0x8004210a)
  • A time out occurred while communicating with the server (0x800ccc19)
Although these error messages appear to be different, they all basically indicate a problem with the connection, which is often due to:
  • Your e-mail service is temporarily unavailable
  • You are not connected to the Internet
  • Outlook was accidentally removed from your computer or was damaged during installation
To troubleshoot through these common connection problems, try the following:
  1. Try to connect two or three times. Sometimes if an e-mail server is unavailable, it is only for a few minutes before it works again. E-mail service problems can only be repaired from the service end. It may be as simple as waiting for your connection to be reinstated.
  2. Verify that you are connected to the Internet by starting your browser and typing in an address. If you are able to load the page, then this is not the issue.
  3. Send yourself a test e-mail using your Outlook. If this works, it would appear that connectivity and Outlook are both working as they should be.
  4. You can start from scratch and re-install Outlook on your computer system by either installing a brand new version or doing an Internet search for the latest service pack for your operating system. If you choose to do this, you should visit the Windows website and identify the Windows program that you currently have, so you download the correct service pack for your system. This download will provide you with a fresh copy of Outlook without any problems.

Friday, June 25, 2010

USB Device Error Code 10 in Windows XP

Plugging a USB storage device into your computer can often result in either nothing or an error code; both being frustrating for the user. USB stands for Universal Serial Bus which is a way for a computer to establish a communication link between a device, such as a memory stick or flash drive, and the host computer.

Portable storage devices are small and can be purchased with different amounts of memory on them. Many people use portable storage devices to store information that they can easily transfer from one computer system quickly and easily. As with any computer equipment, you have to be prepared that systems, devices and connections don’t always work as they are intended. USB error codes do occur and usually in a few steps, problems with the device or the USB port can be easily remedied.

If you get any type of USB error code, you first want to ensure that the device itself is working. Plug the USB flash drive into the USB port on another system and see if you have any problems. If not, the device is not the problem; rather it is the configuration of the computer that would not accept the device. As with other errors, different codes mean different things. For instance, the code 10 error indicates that the device cannot start.

If you are using Windows XP and have encountered a USB error code, the best way to resolve it is to remove and re-install all of the USB controllers:
  • Click on Start
  • Right click on My computer
  • Click on Properties
  • Click the Hardware tab
  • Expand the Universal Serial Bus Controllers Section
  • Right click the devices under the USB controllers and click Uninstall to remove them one at a time
  • Restart the computer, which will allow the computer to reinstall the USB controllers
  • Plug in the removable USB storage device
  • Test your USB device to see that this has resolved the issue and the error code 10
If you continue to have problems with USB error codes you should first contact Microsoft Support or your local computer repair shop for further assistance, as this could actually be a faulty connection in the computer hardware itself.

Tuesday, June 22, 2010

Mac Error Code 0

It may make you wonder why any error code would have a 0 rather than a number to identify it. This is a good question that remains without an answer, but error code 0 does mean something in the world of Mac computers. The error message often says that the file cannot be copied or an unexpected error has occurred, code 0. This usually signifies that the file is too big to copy.

The Mac error code 0 is considered an unidentified error that typically occurs when transferring files that are bigger than 4GB to a FAT32 hard drive. The File Allocation Table (FAT) system is used on many computer file systems and memory cards as a way to organize data in a relatively simplistic way. It is commonly criticized because it is said to make poor use of disk space, which causes overloading. It is supported by almost all of the current operating systems, which makes it very versatile. Placing many files on a system that has a FAT32 system can cause the system to slow down and even crash.

A Mac has a file size limit of 4GB by design. This means that it is likely that you will receive an error message if the file that you are trying to download or copy is too large for the file system. Typically, this will occur when you are attempting to copy a large file to a disk that is in the FAT32 or MS-DOS format. These systems are not equipped to accommodate files that are larger than 4GB, even if there is enough space on the drive to do so.

If you are trying to copy a file of 4GB or larger, you will need to reformat the hard drive to accommodate the size of the file. You can reformat your hard drive by:
  • Backup all of your files before attempting reformatting.
  • Open the Disk Utility from /Applications/Utilities/Disk Utility.
  • Double click on the Disk Utility program to bring up a list of all of the drives available on the computer.
  • Choose the name of your hard disk by highlighting it.
  • Select the Erase tab. This will display the options for erasing the hard drive and reformatting it to work on the Mac.
  • From the Volume Format menu you will choose Mac OS Extended. It is also recommended that you name your hard drive.
  • Click the Erase button and then click Erase again to confirm this is what you want to do.
  • Once the erase function has finished, quit out of Disk Utility and then you can reload any data you have backed up from your backup copy.

Reformatting your drive should both eliminate the Mac error 0 and allow you to have more space on your hard drive.

Saturday, June 19, 2010

Firefox Unresponsive Script Warnings

Firefox is a web browser designed by Mozilla and is an alternative to Microsoft Internet Explorer. When using Firefox, you may receive an error message that states Warning: Unresponsive script or a script on this page may be busy or it may have stopped responding. A script is the set of instructions that provide a program with the directions to carry out a task. An unresponsive script is one that cannot move to action to carry out the command being asked of it.

Usually, Firefox generates these types of error messages because it thinks a script may be running out of control, or the web page you are trying to access is not working. Whatever the reason for the unresponsive script warning, there are a number of things that can be done to rectify the situation.

First, you can let the script run and see if it corrects itself. You can choose to click the Continue button, which will allow the script to keep running. Over time, it may finish running and the web page will begin working again. Unfortunately, this is not always the case and clicking the Continue button may just bring up the same error message again. If the Continue button does not work out the error, take the following steps to increase the length of time you allow the script to run:
  • In the address bar, type about:config and press Enter.
  • A warning message that states “This might void your warranty!” may pop up. If this comes up, click the “I’ll be careful, I promise!” button.
  • You will be sent to the about:config page. Search the available options for the dom.max_script_run_time. You can type the preference name in the Filter: box to speed up the process.
  • Double click on this preference.
  • Change the 10 to a 20 and click the OK button. This will increase the amount of time the script is able to run in the hopes that it will have enough time to fix the error by itself.
If you have noticed that you only receive unresponsive script warnings when accessing certain websites, blocking these scripts from running on those sites will solve the problem.
  • Do an Internet search for the Firefox YesScript extension and download it.
  • Install YesScript as an add-on by following the prompts that will walk you through the download process.
  • Restart Firefox.
  • Open the Firefox window and click Tools.
  • Select Add-ons from this menu.
  • Click Options.
  • In the YesScript Blacklist box, type the URL of the site where you are having script error problems.
  • Click Add.
By completing the above steps, YesScript will block the site from running script errors when you are on it.

Thursday, June 17, 2010

CPU Problems

The central processing unit (CPU) does most of the data processing in the computer, making it an integral system of the computer system. There are some common computer symptoms that are caused by CPU issues; however, CPU failure is much less common than other types of issues that come along with being a computer owner. It can be difficult to determine if a faulty CPU or motherboard is the culprit of your computer problem, but if you rule out other issues and are still left with a problem, it is likely that an issue with the CPU is probably the culprit.

Computer freezes, error messages, strange sounds and the inability to turn the computer on or off can all be indicators of CPU problems. Power failures or surges or electrical problems are the most common causes of CPU issues. Purchasing a surge protector is one of the main things that you can do to prevent CPU damage. CPU damage can be costly because it often requires complete replacement of your computer or minimally the CPU unit.

A power failure will most likely produce one of the following problems that could damage the CPU and will prevent your computer from working properly:
  • Corruption of the operating system, motherboard, memory, power supply or CPU
  • Only the fan runs when you turn on your computer
  • The computer freezes up randomly
  • The PC randomly shuts itself off
All of these scenarios are probably indicators of power supply issues or CPU problems. Start by checking the power supply and ensure that everything is connected properly, and then try restarting your PC. If this does not work, you may be looking at motherboard or CPU damage, which will usually require the expertise of a trained technician to rectify.

CPU issues are fatal to your system. Often the symptoms of errors or problems with your computer can be one of many things. Ruling out the small things can help to better determine if the CPU has been damaged. If you have had a power failure or do not have a power strip with a surge protector during a power loss, it is very possible that there is serious damage to your system. Ruling out corrupted memory, software installation problems and viruses before consulting with a computer repair technician may save you a few dollars in diagnostic costs.

Monday, June 14, 2010

The dlhost.exe Imposter

Problems with dll files, including corrupted or missing files, can cause an array of issues with your computer system. dll files are necessary to ensure that the operating system of the computer is functioning properly. These files are not only prone to errors, but to virus imposters that may pose as the files to get into the computer system and infect it.

The dllhost.exe is a crucial part of the Windows Operating System and manages the dll-based computer applications. The dllhost.exe program controls the processes in the IIS, or Internet Information Services, and many programs utilize this application to function properly. dllhost.exe comes preinstalled on your system when you purchase it, and it is always located on your hard drive in the following location: C:\Windows\System32\dllhost.exe.

Unfortunately, there is a spyware virus circulating that uses the same name as the dllhost.exe file. The virus disguises itself as an executable file in an attempt to fool the user. The best way to determine if the dllhost.exe file is valid is to take a look at your C drive. The correct dllhost.exe file is the one that is installed as listed above. If you find a dllhost.exe file located in areas of your computer other than as listed, it is because of a virus or spyware. Note that a dllhost file that is posing as a virus or spyware may be spelled slightly different than the original file. Remember that a virus and spyware is smart enough to be able to infect programs. This may be misspelled purposefully to keep you from locating and removing it.

By performing a search for dll files in each of your drives, you will be able to quickly produce a list of the dll files. Doing a quick search will make it easy for you to check to see if there is an imposter dll file in a drive other than the C drive. If the dll file is listed in any drive other than C you can assume that you have a virus. At this point, you should run a virus scan and remove any potentially threatening files that result from the scan.

If you can determine that the dllhost.exe file is in the correct location and with the exact spelling, a virus is probably not the cause for the issue. By ruling this out you can move on in your search for the dll error culprit, as viruses are not the only causes of dllhost.exe errors, but they are one of the more common ones.

Saturday, June 12, 2010

Common Runtime Errors

A runtime error is a computer error message that occurs during the execution of a program. Runtime errors indicate problems with the program or design of the program. Typically, these errors are a nuisance, but usually, they are not critical or fatal. In most circumstances, there is an easy fix to this type of error that can be completed successfully by the user.

Runtime error messages may arise while trying to access a webpage or while opening a program or working in a document. There are several kinds of runtime errors that you may receive. Like other common computer errors, runtime errors are given with a number after the error, which explains what causes the error.

For example, you may receive an error message that states: runtime error 48. The fact that 48 is included with the error message is a way to clarify what exactly is causing the error with your machine. In order to best fix the error, users should use the numeric code to find the reason for the error, which should also identify the best approach for fixing it.

The following are a few fairly common runtime errors. Listed below each error is a possible cause, as well as an option for fixing the error.

Runtime Error 48 – Error Loading DLL
  • Conflicts with other programs
Sometimes when too many programs are running at once this can prompt a runtime error. Close down all open programs and try again to open the program, document or webpage that you were working on when you originally received the error message. It may seem too easy that just closing out multiple programs will eliminate this error, but this simple solution is often the all that you need to do.

Runtime Error 58 – File Already Exists
  • Software issues, add ons or plug ins
If you are receiving a runtime error while trying to use software, add ons or plug ins that have been installed on the computer, you can check your recently installed software to see if there are available updates for it. Often times, running out-of-date software can prompt a runtime error. When you receive a prompt that indicates that upgrades are available for your programs, you should accept these updates regularly as this will help eliminate these errors from occurring. If updating the software does not eliminate the runtime error, it may indicate that there is a problem with the software itself. In this case, you can uninstall and then reinstall the software. If this does not work, you should notify the support that is offered with the software package for assistance.

Runtime Error 7 – Out of Memory
  • Memory issues
A runtime error 7 indicates that your computer is low on memory. You can start by deleting files and programs that you no longer use. This will help, but probably will not offer a long-term solution. The more programs you install and files that you save on your system, the more memory is taken up. If runtime errors are chronic, you may want to consider purchasing more memory. Memory can easily be purchased and installed by any computer repair shop.

Thursday, June 10, 2010

The acrord32.exe Application Error

Most people are familiar with Adobe Acrobat Reader, which was developed by Adobe in the 1990’s to access and read PDF, or portable document format, files. PDF is a universal computer text file format that was designed by Adobe that preserves a document and allows it to be read by any computer that has the Adobe program installed. The acrord32.exe application error is usually a fault of Adobe Acrobat Reader and typically occurs because this is such a large program.

The acrord32.exe file is a file that automatically runs on your system whenever you are using Adobe Acrobat Reader to view a PDF file. In order for the file to be loaded and viewed properly, acrord32.exe needs to be intact and running properly. Sometimes, internal issues occur that cause the acrord32.exe to send an error message, such as acrord32.exe application error.

When you open Adobe Acrobat Reader, acrord32.exe automatically runs, and when you close Adobe Acrobat Reader, it should automatically shut down after the program closes. This process of running and stopping should start and end automatically, without any command from the user. The acrord32.exe file is very large and takes up a great deal of memory. In older computers or computers without sufficient memory, using Adobe can take up a great deal of computer memory space, causing computer freezes, slowing the computer down or generating an acrord32.exe application error. If you frequently use PDF files, increasing your memory is the best option to eliminating the frustration of this error.

If there appears to be problems running Adobe Acrobat Reader or the acrord32.exe file does not shut down when you close out Adobe, this is a sign of a potential problem such as virus. What sometimes happens is that a virus may pose as an acrord32.exe file and attempt to infect your computer system. If you are seeing repeated issues when using Adobe or with your computer in general, like slow running programs or frequent error messages, you may have a virus. At this stage it is important to run a virus scan on your system.

If you are confident that there is nothing critically wrong with your computer and want to eliminate this error from randomly popping up, this can be done in a few small steps. Open Adobe Acrobat Reader. Click Edit on the menu bar. Select Preferences and under the Categories heading, select Internet. Where the web browser option box is located, uncheck the box that says Display PDF in Browser. Close Adobe Reader and restart your computer. By doing this, the reader will not be displayed within your Internet browser automatically, which can then improve connection times greatly.

Tuesday, June 8, 2010

Windows Vista - BOOTMGR is Missing Error

Encountering the BOOTMGR is missing error while trying to boot a Windows Vista computer is not that uncommon. While this can be annoying, particularly if you are in the middle of something, on the positive side, this type of error is typically not related to an internal problem or hardware issue. Missing BOOTMGR errors are usually relatively quick and easy to fix.

Unfortunately, Windows Vista was released with a few bugs, but the good news is that they can be repaired quite easily. For many of these errors, including the BOOTMGR is missing error, you will need the Windows Vista CD. It is a good practice to keep all of your computer software available and in good working condition in the event that you ever need to reload a program in the future.

The reason that the BOOTMGR is missing error occurs is because the system may find a corrupted or missing file when trying to boot up. As we all know, problems with corrupted files often lead to many of the errors that we face when trying to use our computers.

When you receive the BOOTMGR is missing error, you correct the error by taking the following steps:
  • Insert the Windows Vista CD.
  • Press CTRL + ALT + DEL to restart your computer.
  • When the computer starts up, you may be asked questions such as: what language you want to proceed in, the time and so on. Answer these questions appropriately.
  • Click Next at the first prompt that you receive after booting up.
  • A link will be provided with an option that reads: Startup Repair. Click this link.
  • The installation process will search your computer for the Vista installation directory. If there is more than one directory, select Microsoft Windows Vista and click Next.

Your system will now be checked for the problems that are causing the BOOTMGR is missing error. Don’t be alarmed if the process takes a few minutes. Your computer may also restart itself randomly during the repair process; this is normal. Once the process is complete, you can reboot your system and remove the installation CD.

These simple steps should remedy the problems at boot up and the BOOTMGR missing error should disappear.

Friday, June 4, 2010

Understanding POST Error Codes

POST, or Power on Self Test, is a series of tests done by a computer, router or printer before booting up and is done every time a computer is turned on. POST is controlled by your computer’s BIOS, and similar to BIOS, POST also uses BEEPS to communicate boot up problems. For more information, on the BIOS beep errors, please see the BIOS Beep Error post.

When detected, the POST error will cause a beep and then may also display an error code on the screen. POST errors are generated from a problem with the tests that automatically happen during the boot up process. The BIOS generates the errors in the POST and a series of beeps that may include a number code will be generated. The beep codes in addition to the error message can be used to determine what the problem is, and hopefully offer a simple solution.

POST error codes are different from system error codes. Although the codes may share numbers with some common error messages such as the STOP code or system error code, POST codes have very different meanings and solutions than other error codes. A POST error code is a code generated using the hexadecimal number system, which is a number system that uses 16 symbols to represent values and is common in computer language.

There are hundreds of different beep codes. The specifics of the beeps and the meaning of them will depend largely on your system. Many operating systems are similar but not exact in the beep codes used to identify an error. If you are attempting to troubleshoot through a POST error, be sure you are using the information as it relates to your specific system.

Understanding how BIOS and POST works is the best first step to being an informed computer user. For example: in IBM computers, two short beeps indicate one of many general POST errors. When an error occurs the computer will generate the beeps along with the specific error code that is displayed on the computer screen. Also specific to IBM computers, a continuous beep indicates that a power supply or a keyboard problem exists. Errors such as these are very simple to fix. A power supply may be unplugged or the keyboard may be detached.

Often, POST errors provide specific information that can be easily understood, allowing the user to repair the problem quickly and easily. Other errors indicate much more serious problems, such as one long and one short beep, which indicates system board issues, and four beeps indicating a motherboard timing issue. The more serious errors will require the assistance of a trained technician.

Knowing your system information and what the beep codes mean can give you the knowledge you need to fix the simple things yourself and leave the more complex errors to the trained professionals.

Thursday, June 3, 2010

Kernel Panic in Mac OS X

A kernel panic is a term specific to UNIX operating systems, such as Mac OS X, and it is the equivalent to the term bug check in the Windows world. It panic is the action taken when an internal fatal error is detected by the system. A kernel panic is designed by the operating system to react by sending out an error when something goes wrong.

If you receive a kernel panic error message that says you need to restart your computer, or that your Mac won’t start up in Mac OS X, the first thing you should do is restart your system to see if the same error remains when you boot back up. Basically, when a kernel panic occurs, there has been a system crash in Mac OS X. The computer system responds to the panic by doing one of two things: waiting for the system to be manually rebooted or initiating an automatic reboot.

There are several reasons why a kernel panic occurs. The information provided with a kernel panic is often very technical, and it has the goal of assisting a system administrator in diagnosing a computer problem. Some of the causes of kernel panics may require technical assistance beyond that of the average user. Listed below are a few of the causes and how to go about resolving them.

Defective or incompatible RAM or lack of hard disk space or RAM

This is the most frequent cause of a kernel panic error. You can first try to defragment your system and clean up your hard drive to get more available memory. In the Applications directory, open the Utilities folder and then open the Disc Utility Program. Select the drive you want to defragment by highlighting this drive from the list available. This process may take some time so plan to do this during a time when you will not need your computer, overnight for instance.

Defragmenting may work for the short term, but the best way to resolve a RAM issue over the long term is to purchase more RAM. Memory can easily be purchased through a computer store, and either you or a computer technician can install it. It is important to ensure that the RAM is compatible with Mac OS X.

Incompatible, or corrupted kernel extensions, or drivers

Third party hardware that is outdated or programs that are incompatible with the Mac OS X system being used can cause a kernel panic error. Ensure that the software and hardware that you are using is compatible with your Mac OS X system. This should be listed in the software documentation that you have. If you find you are using something that is not compatible, you should remove it and install something that is compatible. You can also check the website of the applications you are using and download or agree to updates as they are available. Most software prompts you periodically to search for updates. If you know that your software is compatible, keeping it up to date is the best way to avoid kernel panics.

Hard disk corruption

When there is a problem with your hard disk, it will often result in the freezing of your computer or your computer running slowly. If freezing occurs, it is a sure sign of trouble internally. In this case, you will want to obtain assistance from a professional to repair your corrupted hard disk.

Tuesday, June 1, 2010

DNS Lookup Failed Error

The Domain Name System (DNS) is a system of servers that translates domain names into IP addresses. The DNS system handles the workings of making Internet connections and DNS lookup failed simply means that you are unable to connect to a specific website. This can in fact happen for a variety of reasons.

Issues with the DNS do not always cause an actual error message to surface; rather they may take the form of other symptoms; such as:
  • Inability to log on or very slow logon.
  • Unable to join a domain or run a logon script.
  • Inability to access an IP address.
Interestingly, when you visit websites, Windows automatically places DNS information about the site into a cache on your computer. A cache is a type of supply closet on your computer and the DNS stores negative and positive entries here. When the information on the website matches with what is stored by Windows, the connection is successful. If the Internet Service Provider does not update the DNS information, this may conflict with the information stored on your computer, creating a negative entry that causes a DNS lookup failed error.

DNS lookup failed errors may or may not be something that you can correct. These errors can be due to issues with the Internet Service Provider (ISP) or your cache may just be overloaded with negative or conflicting information. Cleaning out your cache is the first thing you can do, which will also let you know whether the error is due to your system or the ISP.

Flushing your cache will empty all the information stored on your computer and start you back at a clean slate. By cleaning out all of the information in the cache, there will be no conflicting information to cause DNS lookup failed errors. To do this, you will need to open the command screen.

For all Windows users except Vista and Windows 7, go to Start > Run. Click Run and in the pop-up box that opens, type: com or command and press Enter.

For Windows Vista and Windows 7 users, go to Start > All Programs > Accessories > Command Prompt. Right-click on Command Prompt and select Run as Administrator.

The remaining instructions are the same for all Windows users. Type ipconfig/flushdns and hit Enter. Once the DNS cache has been flushed, a confirmation window should open stating that the DNS resolver cache was successfully flushed. This should eliminate future DNS lookup failed errors. It is not a bad idea to do this when you begin to experience any of the symptoms listed above.

If you are still experiencing DNS failed lookup errors after you have flushed your cache, then it is likely an error at the ISP end of things. Unfortunately, there is not a lot you can do about this, which means you may not be able to access the site until the error is resolved.