PC Performance Clinic Blog

Introduction to Runtime Errors

A runtime error is an error that occurs during the execution of a software. Runtime errors indicate problems that the designers had anticipated but could do nothing about, or just bugs in the software. For example, running out of memory will often cause a runtime error. Runtime errors are somtimes recoverable, except they may cause loss of unsaved data. Some applications even provide runtime error handlers that are stored in Windows Registry to deal with programming exceptions when they occur.

Causes for Runtime Errors

Runtime errors can be caused by unexpected data entries, empty or erroneous references to programming and application component entries stored in Windows Registry for COM/ActiveX controls, application paths, shell extensions, runtime error exception handlers, or even font entries. In other words, your running applications are fed with false information that was stored in your Windows Registry and eventually they will crash unexpectedly.

Tips to Fix Runtime Errors

Although in general, you need to keep your Windows and software patches up to date in order to avoid runtime errors caused by programming quality issues, the best solution to fix and put a stop to runtime errors is to always maintain a clean and optimized Windows Registry, which contains nothing but registry keys and values that are absolutely necessary and correct for the Windows operating system and legitimately installed applications.

The most effective, secure and feasible way to completely eliminate runtime errors is to use a reputable and trustworthy Windows optimization software such as RegCure.

Are you getting annoying messages such as “A Runtime Error has occurred. Do you wish to Debug?” or “Internet Explorer Script Error. An error has occurred in the script on line 1. Do you wish to continue running scripts on this page?”

There are three reasons why these problems occur. The first is that the web page author made some programming error. The second reason may be that you are running a pop-up killer that closes pop-up windows so fast that the script on the web page fails. The third is that you might have some adware or spyware installed on your computer that opens the script error pop-ups.

How to disable script and runtime errors
You can configure Internet Explorer to ignore these script and runtime errors. Please follow this step-by-step guide:

1. Open Internet Explorer.

2. Click on Tools, then on Internet Options.

3. Click on the Advanced tab.

4. Look for the “Disable script debugging” line and put a check mark in the box.

5. Now look for the “Display a notification about every script error” line and remove the check mark in the box.

Still getting script errors?

f you still get the script or runtime error messages after disabling them in Internet Explorer, the problem might be that you have some unwanted spyware or adware installed on your computer. We recommend that you scan your computer with one anti-spyware. We recommend Pareto Logic Anti Spyware.

An runtime error is an error that occurs during the execution of a program. In contrast, compile-time errors occur while a program is being compiled. Runtime errors indicate bugs in the program or problems that the designers had anticipated but could do nothing about. For example, running out of memory will often cause a runtime error.

Note that runtime errors differ from bombs or crashes in that you can often recover gracefully from a runtime error.

Possible Causes:

The runtime or run-time error message can be caused by:

1. Confliction with TSR or other running program
2. Software issue
3. Computer Virus
4. Memory issue

Solution:

Confliction with TSR or other running program

If you are encountering a runtime error message while in Windows or above ensure that the issue is not being caused by a third-party program or TSR by end tasking all open programs.

If, after end tasking all TSRs, you continue to experience the same issue and are running Windows 95 or Windows 98, verify that no utility or program is being loaded in the autoexec.bat / config.sys that is causing your issue by temporally renaming the files. To do this, follow the below instructions.

1. Boot to a MS-DOS prompt.
2. Once at the MS-DOS prompt, type:cd\ <press enter>
   ren autoexec.bat autoexec.ch <press enter>
   ren config.sys config.ch <press enter>Once completed, reboot the computer.

Software issue

If your issue persists it is possible that the program, utility or game causing the runtime error may have issues. Verify through the developer’s web site that all updates or patches that may be available have been downloaded and applied.

If no patches or updates are available, attempt to uninstall and/or reinstall the program that is causing the issue. If you are having a runtime error in your operating system, reinstall the operating system.

Add-on, plug-in, or other extra software

Many runtime errors are also caused by other add-ons, plug-ins, or other extra software that has been installed onto the computer and is associated with the program generating the error. If you have any extra software installed that is associated with the program generating the error make sure there are no available updates for the programs and/or try uninstalling each of them to verify they’re not the cause of your issue.

Computer virus

Because computer viruses are capable of tampering with the system settings / memory it is possible for a computer virus to generate a runtime error. If you are currently running a virus protection program on your computer ensure it has the latest updated patch or .dat file.

If you do not have a computer virus protection program it is recommended one be purchased or that a demo be temporarily downloaded to scan your computer hard disk drive for viruses.

Memory issue

Finally, if you have followed all of the above recommendations, it is possible that you may be encountering a hardware / memory related issue. We recommend that you first contact the developer of the program causing the issue for any possible solutions. If no solutions are found, we recommend you contact the computer or motherboard manufacturer for additional recommendations and/or service.