There are many kinds of login services, but some of the most problematic are those that involve connecting to a network or to an ISP for an Internet connection.

What is the point of a login service? Well, it goes beyond simply entering the correct username and password. In fact, a large portion of login service errors have nothing to do with the details. They’re caused by a failed connection or a loose configuration setting.

Of course, that’s not to say that you should rule out the possibility of a mistaken password or username altogether. Always check the details that you enter, making sure that the caps lock is turned off to prevent a system misinterpreting what is essentially the same combination through the use of different case. And check again just to make sure.

If you’re still having trouble with the login service, it’s probably down to the connection. If you enter the correct details, you will be granted access by the login service. If you enter incorrect details, obviously you won’t be. But if you enter the right details without having a working connection, you’ll receive a potentially misleading error. You must be connected to the login service to be able to reach the verification mechanism. Without verification, you’ll be locked out. Correct details or not.

If you are using the Windows Login Service and your password isn’t being accepted, you may have been the victim of a virus attacking the core of the system. Some viruses are capable of altering a system user or password to cause maximum damage and lock a user out of the operating system.

The best way to avoid such circumstances is to use the trusted road of anti-Virus protection. Always protect your machine from third party software and malicious hackers. You should have a firewall in place at all times when using the Internet, and preferably a commercial scale anti-Virus suite too.

It’s possible to reset the Login Service password by accessing your Windows registry and changing the key information. But this can be problematic if the virus has locked you out completely. A complete scan of the system with both a cleaning utility and a registry scanner will eliminate the threat of harmful viruses.

If you are having problems with the login service of a remote ISP, there could be many different causes to blame. First and foremost, check the connectivity of your hardware devices. This involves resetting modems, checking network wires and removing the static from plugs if necessary. If you can’t use the login service, it doesn’t necessarily indicate a problem with the software. You could be suffering from a hardware detection issue which happens to terminate at that particular time.

Some login services require the enabling of additional technologies. For example, web based Login Services might require JavaScript to validate details against the authorized list. In these cases, ensure that scripting is enabled in the Advanced tab of your Internet Options.

When logging in to any local network, ensure that the relevant cable is attached and working. If this isn’t correct, you might not even see a login screen. A “Page Cannot Display” message is quite common in scenarios where the login service can’t initiate, whether it be through a faulty Internet connection, a network hardware issue or even a system virus.

No Comments »

If you receive an error stating “Cannot find C:\Windows\System32\System32.exe” when booting your copy of Windows XP, it’s highly likely that you’re suffering from a well documented problem associated with the W32.KWBot.C.Worm virus.

Also known as Worm.P2P.Tanked.14 and Win32/HLLW.Kwbot.C, this particular virus operates through the Kazaa and Limewire sharing environment. It’s a medium threat virus, so while it isn’t totally destructive, it can cause some significant damage to your system.

So, naturally you’re already thinking, how can I get rid of this threat? Well the good news is that it’s quite easy to remove, as long as you’re careful when working and don’t go making any brash mistakes!

The actual “Cannot find C:\Windows\System32\System32.exe” error is thrown AFTER the virus has been removed. Not a very successful removal after all, you’d think. And you’d be right. The major anti-Virus suites are all guilty of an occasional loophole. In the case of the System32.exe error, that loophole is usually an incomplete removal of all registry traces of the W32.KWBot.C.Worm virus.

If you run through a standard virus scan of your computer and delete a few troublesome looking files, it’s possible that the next time you boot Windows; you’ll be presented with this error. To get to the bottom of it, we need to access the Windows registry and make a few slight alterations to remove the last traces of the virus.

Now, as ever, you should note that using the Registry Editor requires a great deal of attention. It’s not the sort of utility that you open up and play around with callously. In fact, a single bad edit can leave you locked out of your Windows XP system!

We would suggest that you download one of the many free registry cleaners if you’re lacking confidence in the area of critical system edits. In fact, we can’t stress it highly enough. A registry cleaner will usually get rid of stray entries and you’ll notice that the errors disappear with them.

But for the sake of knowing what you’re doing to your system, here’s how you can remove the W32.KWBot.C.Worm virus entries manually.

• Go to Start, then Run, and type “regedit”.
• Locate the following keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
CurrentVersion\Run\SystemSAS system32.exe HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
CurrentVersion\Run\CMD cmd32.exe HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
CurrentVersion\RunServices\SystemSAS system32.exe HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\
CurrentVersion\RunServices\CMD cmd32.exe HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\
CurrentVersion\RunOnce\SystemSAS system32.exe HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\
CurrentVersion\RunOnce\CMD cmd32.exe HKEY_Local_Machine\Software\Krypton

• Click on the Edit menu option.
• Delete each key.
• Find the HKEY_Local_Machine\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell key.
• Click on the Edit menu option
• Click Modify and enter Explorer.exe as your value.

Finally, you will need to delete any of the remaining corrupted entries from the Kazaa and iMesh libraries. You will only need to do this for the program which you have installed.

Search for any values that point to C:\%Windir%\User32 or C:\%Windir%\UserTemp, and delete them.

You should then save your registry and restart Windows. In most cases, the error will have disappeared. If it remains, you will definitely need to download a comprehensive registry cleaning utility. This will search out any extra complications. As an absolute last resort, a full Windows repair may be necessary. This shouldn’t be considered until the other avenues have been exhausted. The registry edits above will fix the problem nine times out of ten.

Get a Free Online Diagnostic Scan with RegCure PC Optimizer (Download Takes 2 Mins)

No Comments »

It’s the screen that we all dread. It nearly always means that there’s something seriously wrong with an operating system, and in many cases, fixing it can require drastic measures. Yes, of course. We’re talking about the blue screen of death!

One of the errors that you might encounter is marked as 0×00000000.

For example, you might receive an error like the one below:

STOP: 0×0000009C (0×00000004, 0×00000000, 0xb2000000, 0×00020151) “MACHINE_CHECK_EXCEPTION”

There are several different causes for the 0×00000000 error. But in most cases where you receive it, your system will be unusable. In extreme situations, you might not have any access to the Windows operating system at all. The error often triggers a system restart, and can appear without warning. Needless to say, its one of the more frustrating problems out there! It should also be noted that the error is typically found on Windows XP.

The official Microsoft documentation suggests that the error arises when the Machine Check Exception detects an unrecoverable problem with the hardware on an XP OS. This is slightly ambiguous, so how do we know where the problem is coming from?

To get to a fix, we have to look at the hardware of the system.

It’s possible that you’re suffering from a memory partition problem. A re-format of the hard drive would be the solution in this situation. But it’s much more likely that there’s a problem with the system bus.

System bus errors are painstakingly tricky to fix and you’ll need to take the computer to a technician and cough up for the full repair treatment.

It’s also possible that you’re running off higher specifications than your machine can handle. Over-clocking of the processor is a notorious problem and it is associated with the blue screen 0×00000000 error. To handle the higher performance applications, you should consider an upgrade to the processor and memory.

In most cases, you’ll be well aware if your processor is being over-clocked with unrealistic expectations. Poor performance will be noticeable long before the errors begin to crop up.

Ensure that the system has sufficient ventilation and that the fan is powerful enough to cool the CPU. This is the cause of many a system failure, but many look beyond what can be treated as basic thermal management of the computer.

It’s also important to stay up to date with the latest anti-Virus protection. If you find yourself attacked by one of the malicious shell-targeting viruses that are in circulation, it can have a crippling effect on the system resources.

Download a system cleaning utility and run a thorough check for malicious files. Remove anything that looks suspicious and you should notice an improvement in performance, which can be noted from the Task Manager.

Ultimately, if Windows is refusing to start up, or if the 0×00000000 errors are too persistent to ignore, you should take your computer to the nearest (or cheapest) repair store and ask a qualified technician to troubleshoot the actual hardware components. It’s very likely that the problem is being caused by either damaged memory or insufficient system resources, both of which can be pricey to fix.

Get a Free Online Diagnostic Scan with RegCure PC Optimizer (Download Takes 2 Mins)

2 Comments »

“A Runtime Error has occurred. Do you wish to Debug?”

If you have been receiving this message while browsing the Web, it’s likely that you’re suffering from scripting errors caused by configuration options or malicious malware.

Runtime errors can arise out of many things. Maybe you have a pop up blocker installed. When a window opens to execute a script, the pop-up blocker terminates the script before it can complete its command. This leads to what is known as a runtime error.

With every runtime error, you’ll have the chance to debug where the problem is in the code. Of course, as a casual web browser, this isn’t really any of our business. So instead we end up clicking through “OK” messages until the alerts disappear. As such, it can take several clicks to load a single page!

Another problem involves the configuration of anti-Virus software. While it’s certainly advisable to browse with protection, always make sure that you have the right permission levels within the application. If you switch off scripting, you’re likely to get quite a few runtime errors. It’s also important that your anti-Virus suite is configured NOT to scan the Temporary Internet Files. This can lead to all kinds of problems.

Some people find themselves flooded with annoying runtime errors, yet the website itself seems to function properly. To fix this, follow the steps below.

• Go to Tools and Internet Options in Microsoft Internet Exporer
• Click on the Advanced Settings.
• Disable script debugging.
• Disable the script error notification box.
• Save changes and relaunch your browser

This will prevent reports of errors being returned when you load a page. Note that it won’t prevent the actual collision. But you won’t have to click OK several times before a page actually loads.

It’s possible that runtime errors are the result of a spyware infestation. Many malicious users design software which sits under the browser and springs up pop-ups. Due to the rough cut nature of most malwares, they can lead to an unhealthy number of errors. Ultimately, they’re not designed with the end user in mind and in desperation to blitz your browser with third party ads; you’ll be fighting off many errors.

To deal with spyware, there are many excellent free system cleaning utilities available on the market. These will tear through your computer and eliminate the bad apples. They’ll also clean the registry and improve the overall performance of your computer. Most runtime errors are born from collisions with the code. If you’re getting them persistently on reputable websites, the problem is most likely spyware or a spreading virus.

It’s not out of the question, however, that the runtime error is the fault of the developer who created the page. Programming languages aren’t a walk in the park by any means and there is plenty of scope for errors. If the site is using bad code, there’s nothing you can do other than to find a different website. You can eliminate the error reporting however, as we mentioned above, and this is often enough to make a website usable.

You can usually tell when the problem is on the part of the developer. If the errors are occurring on innocuous websites designed for the masses, it’s likely a fault at your own end. Remember that most reputable businesses and organizations are forced to design tidy code that won’t clash with pop-up blockers and anti-Virus software. Still having problems? Remember the three most likely reasons;

• Spyware
• Pop-up blockers and anti-Virus software
• Script configuration settings in Internet Options

 Get a Free Online Diagnostic Scan with RegCure PC Optimizer (Download Takes 2 Mins)

2 Comments »