|Attention Before you read this tutorial, I highly recommend you check out my resources page for access to the tools and services I use to not only maintain my system but also fix all my computer errors, by clicking here!|
Runtime errors generally occur when certain processes or files that a particular application requires has either been deleted or corrupted.
Runtime error 7 is a relatively common error which pops up at random intervals while using your computer. It may appear with an “Out Of Memory” error message, and abruptly halt whatever application you are using at the time. Runtime error 7 occurs primarily as the result of an issue within the coding of the application. To summaries, it’s essentially the result of poorly designed software or a coding bug. Moreover, although the error message may say the issue is memory related, in most cases you will find that loss of memory has absolutely nothing to do with the error.
What Causes Runtime Error 7?
The most commonly associated error message that the end user will come face to face with, will appear something like the following:
Runtime Error 7: Out of Memory
Already touching briefly on the cause of this error, one of the main reasons why runtime error 7 occurs is because of the corruption of file FM20.dll. The FM20.dll file is used by Visual Basic for the purpose of encoding specific settings and functions within an application.
This file is used exclusively by Visual Basic, and will usually be the cause of an error due to it being unsupported by Visual Studio and other similar programming interfaces. Fortunately, it is possible for you to fix this file by carrying out a number of set instructions, which I will touch on later in this post.
Runtime error 7 may also occur due to corruption of the comctl32.ocx file.
Just like with the FM20.dll file, repairing the error is simply a matter of replacing the file with a working compatible version. A process which you may or may not find challenging, depending on your level of expertise.
How to Fix It
Fixing runtime error 7 in most cases has a lot to do with repairing the FM20.dll file. But as I’ve stated, it’s not the only file known to cause this particular error.
That said repairing this error can prove to be quite difficult, depending on the method you choose to adopt. Fortunately, there are much simpler solutions, which is why I recommend you try the solutions I’ve mentioned below in the order that they appear.
The recommended repair solution to runtime error 7 is to use Reimage, which is a Windows repair tool, capable of scanning your operating system and finding corrupt and/or missing DLL files and replacing them with new compatible versions of the file for your specific version of Windows. Reimage boasts of over 25 million files in its repository which it can and does use to fix corrupted files on your computer. Running Reimage for the first time will give you a complete PC report of all the issues on your computer, in addition to that, this tool can and will also carry out a free antivirus and spyware scan of your system.
Some of the additional benefits to running Reimage include its ability to enhance the overall performance of your computer, stopping repeated system freezing and crashing, as well as making your system more stable. When Reimage is used more regularly, it will constantly keep your operating system fresh, which will ensure your computer is always running at its best. Reimage is a quick, safe and without a doubt the easiest solution to repairing this problem.
You can acquire this powerful tool from the following link:
Run a Registry Scan
Another common cause for runtime error 7 is issues within the Windows registry. The registry, if you don’t know what it is, is basically the central database, used for storing all the most important hardware and software settings, which the operating system will call upon whenever the end user attempts to run an application.
What often tends to happen is that data within the registry becomes corrupted due to constant writing and rewriting of data within it, this leads to degraded system performance and a plethora of different errors.
To fix this problem, you will need to run a full scan of your registry using a professional registry cleaning tool like SpeedyPC Pro. This tool will thoroughly scan of your computer, finding and repairing damaged file references and registry keys, which should repair the error.
For more information on SpeedyPC Pro, please visit the following link:
Run a Virus Scan
Antivirus programs (if you don’t already know what they are) are basically software tools designed to scan your computer and remove any and all malicious files that it finds. Once a virus gets onto your computer can infect important DLL files on your computer, corrupted these files, making them unreadable to the operating system.
To ensure that a virus is not what is causing the runtime error 7, you will need to run a thorough scan of your computer. To do this, you can either use your current solution (assuming you already have software on your computer) or you can use SpyHunter, which is currently one of the very best antimalware tools available today.
For more information on this powerful tool, I highly recommend you visit the following link:
|The solution(s) below are for ADVANCED level computer users. If you are a beginner to intermediate computer user, I highly recommend you use the automated tool(s) above!|
Remove File FM20.dll
If you’ve created an application using Visual Basic which has inadvertently led to the runtime error 7 every time you attempt to run it or any other application on your computer, then you should consider removing the FM20.dll file from your computer. The reason why you may want to do this is because the error is likely the result of a conflict.
A shared file like FM20.dll, designed to carry out various functions across multiple applications can sometimes become corrupted, resulting in the various error messages you are seeing. Thus, as a sort of workaround, you should consider removing the file altogether.
In order to do that, simply do the following:
1. First you will need to boot into your computer with full administrative rights.
2. Then press + R, type cmd and click on OK.
3. Once Command Prompt loads up, type regsvr32 -u fm20.dll then hit the Enter key.
Note: This will unregister file FM20.dll, once you have done that, you will be able to remove or delete the file from your computer.
4. Next, Press + R, type C:\Windows\System32 into the Run Command box and click on OK.
5. When the System32 Folder opens, locate the FM20.dll file, then right click on it and select Delete.
Replace Comctl32.ocx File
Comctl32.ocx is an important Windows file that is used for controlling various components of Visual Basic. Unfortunately, this file is highly susceptible to corruption, leading to the runtime error 7 you’re experiencing now. One of the most effective ways to manually repair this error is to replace the comctl32.ocx file, in order to do that, simply do the following:
Note: The Comctl32.ocx file is only present on Windows XP systems.
1. First, follow steps 1 – 2 of Remove File FM20.dll.
2. Once Command Prompt is up and running, type regsvr32 -u comctl32.ocx then press the Enter key.
3. Once you have unregistered the Comctl32.ocx file, you can now delete it. In order to do that, press + R, type C:\Windows\System32 then click on OK.
4. When the System32 Folder successfully loads, simply locate the Comctl32.ocx file, then right click on it and select Delete.
Note: Once you have successfully removed the Comctl32.ocx file, you will need to replace it with a working version.
5. Now, using one of the many reputable download sites, download a working version of Comctl32.ocx for your operating system.
Note: Make sure you download the file from a reputable source and scan it (with a virus scanner) prior to copying it to your computer.
6. Then copy it to the C:\Windows\System32 folder.
7. Once you have done that, open Command Prompt again, by pressing + R, typing cmd and click on OK.
8. When Command Prompt loads up, type regsvr32 Comctl32.ocx and press Enter.