Again, we come to the arena of Microsoft Visual Basics and just another one of the many runtime errors that can occur due to program and system conflicts within the operating system environment. The Runtime Error 13 is a type mismatch or program error that can happen when running all sorts of programs that utilises the Visual Basics Environment as part of its launch matrix. This can range from financial software all the way to antivirus software, all of which, in some way or the other, make use of the VB environment. Solving this error is quite similar to the way everyone solves other runtime errors, which is identifying the break in the chain.

A runtime error occurs when there is a hiccup within the sequence of launches or system components that run in a specific order to launch a software. For example, when launching a game, Windows needs to load the appropriate data files, system files, game data files and many others before the shell of the game can be launched. Normally, these files are run in a sequence (which is where the term 'runtime' comes from) and when this happens, the problems will rear their heads when there is either a missing file, an inert file, a file with a wrong file name or any other conflict. When it comes to the VB environment, there are usually conflicts and system errors.

What you need to do is try to identify the files (used by the program itself) that have caused the error. Check for possible reported conflicts online by the specific developers and they usually will have instructions on how to avoid these conflicts. They might even have posted a software patch for you to install that will solve the problem, and this is the easiest way to resolve runtime errors. Another way is to reinstall the software, as a bad install might be one of the cases where run time errors can occur, especially when it comes to critical drivers and system files needed by Windows and VB to run the specific program. Reinstallation usually solves this problem.

Another option is to get a PC or Registry Cleaner, which is one of the best ways to get rid of program conflicts (said to be the major cause of runtime errors). It might even be just a problem with the integrity of the registry, all of which a registry cleaner can fix and sort out within a few minutes. These are some of the ways that you can adopt to solve the problem, but if it goes beyond that, then there might be an issue of a Trojan or even a virus that has infected the operating system. They have been known to cause runtime errors by changing the code of random files and even the VB environment. Scan your computer with a good anti virus software and you might be able to find and weed out a pesky Trojan or worm hiding in your system memory.


Article Source: http://EzineArticles.com/?expert=Logan_Albright

The common thing that most computer users end up doing when their computer freezes up on them is usually a show of temper of some sort, be it banging their hands on their desks in frustration or restraining the urge to hit any nearby computer peripherals (the usual 'victim' being the screen). Some might even hit the CPU case thinking that doing so might help get the computer working again.

What everyone needs to remember is that the computer is not a sentient living being with a mind of its own, which fears reprimand every time it acts up. Abusing the computer physically (or even verbally) will not help at all. If you have ever found yourself asking the question "What do I do if my computer keeps freezing" then this article will answer that question for you.

The fact is, freezing computers are a common phenomenon, and for those with relatively outdated systems it has become almost an inevitable expectation of sorts. Common symptoms include a frozen cursor and the inability to launch any program, and your desktop would for all intents and purposes be frozen in a sort of suspended animation. This is usually followed by beeping noises coming from the CPU when you try and tap the keys of your keyboard, indicating that all signals to the motherboard and back have been blocked.

At this point most people might be looking at the reset or power button in fear, especially if they have not had the chance to save their work prior. Let's face it, by now there is pretty much nothing you can do but hope that the auto-save feature kicked in before your computer froze.

What needs to be done is to ensure that the computer does not freeze in the first place, and in order to avoid this inconvenience from ever occurring again, we need to look into the various reasons why it does so. One of the common reasons happens to be a lack of memory, and to put it simply, with insufficient memory the computer becomes stressed at having to handle memory intensive programs that it simply gives up and stops functioning.

If you're running memory intensive programs be sure you're not running them simultaneously. Run them one at a time to avoid overwhelming your computer's limited memory resources. If you absolutely need to run multiple memory intensive programs then perhaps you should look into upgrading your memory. Buy additional sticks of RAM, which are relatively cheap these days, and boost the memory of your system.

Also, another possible reason for system freezes could be bad code in programs, especially games and high-end software, which can lock up your computer when Windows cannot execute the code written in them. Always check the integrity of the programs that you are going to install and check for any possible conflict issues with other software or even hardware. Hardware conflicts are pretty common as well, so make sure you have those sorted out before buying anything new and expensive.

There may also be a conflict in the registry between local keys and null values, which means that the OS will lock up whenever you try to launch a program. One of the best ways to fix these conflicts and even clean up and speed up your PC is to get a registry or PC cleaner, which can solve most software based problems and clean out the junk in your system folders which can lead to memory overload and the infamous computer freeze. A good registry cleaner has been the saviour of many computers and yours should be no exception.


Article Source: http://EzineArticles.com/?expert=Logan_Albright

While many of you might be stumped as to what a Dr. Watson error is, it is actually relatively commonplace within the environment of computers and systems. Dr. Watson is the name given to a diagnostic and debugging program that comes with Microsoft Windows, a program that is used to detect, log and decode all and any errors within the runtime environment of Windows and the operating systems within it.

Dr Watson pops up when Windows programs run and there is a debug error, which means that the very structure of the code of the program has been identified as faulty or is running in conflict with the operating system itself. While not a very advanced tool in itself, it is quite an adequate tool when it comes to debugging and finding out the problems behind various forms of crashes and interruptions when running programs in Windows.

If you do get a lot of errors when running Windows or any Windows based programs, then it is a good idea for you to run the Dr Watson tool to determine the root cause of the problem or even log a report so you can investigate further. By itself, using Dr Watson alone is not enough, as the applications of its matrix are quite general and it is not a highly specific software that can tackle anything more than a simple debug. It is the first step however, as using Dr. Watson can help you to pinpoint which program, which source or even which code is flawed, so that you're able to use other "fix-it" programs to rectify the problem.

If you are wondering where to find the logs of the doc himself, all it takes is a simple search of the drwstn32.log or user.dump, which can be found in the documents and settings folder in your C drive. One important note when using the Dr. Watson utility is that determining the exact cause of the problem amidst the complex matrix of Windows is a tedious task, one that you have to be careful with because it's quite possible for you to inadvertently alter critical system files, which might lead to a system crash.

You will need other software that has enough delicate touch to deal with such problems. Considering the fact that a good majority of such errors are caused by flaws within the system registry, you should download a registry cleaner so that the program is able to delve deep into the matrix of your computer and sort the null values, bad code, conflicts, orphan keys, or other registry-related errors that might have been affecting your computer.

A registry cleaner is by far more superior than Dr. Watson because of its functionalities. While Dr. Watson is mostly a diagnostic tool, a registry cleaner does what its name sets itself out to be. It literally cleans the system registry, going through each piece of code, each command line, and figuring out what goes where, and what should be in specific places.



Article Source: http://EzineArticles.com/?expert=Logan_Albright