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.