January 2008

Monthly Archive

Access Violation error

Posted by admin on 01 Jan 2008 | Tagged as: Access Violation, configuration, error, hardware

An Access Violation error is the abbreviated term for what’s known as a segmentation fault. It is a problem that occurs when a program, or a piece of software, tries to access memory that it doesn’t have permission to use.

It’s the computer equivalent of walking in to a locked door, you could say. The files that you want are protected by a security layer, or are simply locked and inaccessible from your current environment.

Access Violation errors are also a very common trait of software that is configured incorrectly. While UNIX machines will receive a SIGSEGV signal about the invalid memory, users on Microsoft Windows operating systems will be presented with the STATUS_ACCESS_VIOLATION exception – better known as an Access Violation.

If, for example, you have a hardware device which is recently installed, and software which is used by other programs, it’s possible that you’ll receive an Access Violation when trying to use the new hardware device – if its drivers are being used by another source. These sort of collisions will often result in Access Violations where a piece of software is in demand from two or more pieces of hardware, and it can only feed one at a time.

The memory is thus locked, and any attempt to access the important source files will be blocked out. The Access Violation error is returned, and you – the end user- will be left to scratch your head.

You may have also received an Access Violation exception when attempting to access a typical file or folder that you wouldn’t expect to be involved with any system processes or crucial drivers. In most cases, this is down to the attribute of the file.

If you try to write to a file which is designated as Read-Only, you will be attempting to breach the security permissions of that particular file. This is blocked out by the Access Violation exception. But the good news is, such errors are easy to fix.

To resolve a permission error, we need to enter the Command Prompt and make a change to the attributes of the file. If you can’t open it, we need to make it readable. If you can’t write to it, we need to make it writeable. And so forth.

The Dos command for making changes to the attribute of a file is shown below:

ATTRIB [+R | -R] [+A | -A] [+S | -S] [+H | -H] [[drive:][path]file] [/S]

If this is no more than random gibberish to you, don’t worry. It’s quite simple when broken down.

The plus sign is used to add attributes, and the minus sign takes them away.

R is the READ-ONLY attribute.
A is the ARCHIVE attribute.
S is the SYSTEM FILE attribute.
H is the HIDDEN FILE attribute.

Obviously, if you have a file which is Read-Only, you are not going to be able to make changes or edit the contents. This is probably the number one cause of Access Violation errors.

To get rid of them, you simply need to apply the correct attribute formation so that the file is accessible to your needs.

Next Step:

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

File / Folder Access Denied Errors

Posted by admin on 01 Jan 2008 | Tagged as: Access Denied, error, operating system

“Access Denied” errors are quite common on Windows XP, and indeed, the older versions of Microsoft’s operating system as well.

They can be quite diverse in their meaning, and equally confusing in terms of what is necessary to fix the problem. What does Access Denied mean? Well, besides the obvious of not being able to access said file, it typically implies that the source is locked, corrupt or unavailable at that present time.

Much depends on the context in which you’re receiving the error. Are you trying to access a webpage online? Some pages are locked on the Internet and a username and password are required, otherwise an Access Denied error will be returned. If you try to visit a secured page, or if you enter a wrong username and password combination, you will see an Access Denied message. Depending on the web browser that you’re using, this will usually be preceded by a login box. So you will know when you’re trying to access protected content.

Sometimes, however, the Access Denied error will spring up for no particular reason when you try to access files on your local hard disk. Once again, we must take the situation I to perspective of what you are trying to do.

Are you trying to rename or move a file that is already open? Are you trying to write to a file which is read-only? Both of these scenarios could potentially lead to an Access Denied message.

If a file is opened, it will be locked from many of the basic Windows commands. You can’t rename a file while it’s already in use. Close the file and try accessing it again. This should fix the problem. The same situation applies to system services which are required for other programs to operate.

If you open up Windows Task Manager and attempt to shut down a service which is critical to the way that the system functions, you will receive the error. And in cases like that, your access is usually denied for a reason.

You may have seen an error like the one below:

“Folder is not accessible. Access is denied.”

This is a problem which stems from re-installing the operating system and trying to access a folder which was created on a NTFS file system in a past installation. For example, if you re-installed your My Documents folder to a different volume, you will find an Access Denied error when you try to access it on the new system.

The solution is to turn off Simple File Sharing – an option which is set to on by default on Windows XP systems. To do this, you should go to My Computer, followed by the Tools tab. Under the View tab on Folder Options, you will have the chance to enable or disable the Simple File Sharing System. Set it to Off.

Once complete, you can right click on the problematic folder and alter the settings through the Properties tab.

Go to Security, then Advanced, and Owner. Now you simply need to ensure that your current user group has access to the folder. Save the changes where necessary and exit. The folder should now be accessible.

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

16-bit Errors

Posted by admin on 01 Jan 2008 | Tagged as: error, operating system

If you receive one of the error messages below when trying to install a DOS based or Windows 16 bit application, it’s likely that one of three essential Windows files has become corrupt or deleted altogether.

16-bit MS-DOS Subsystem

path to the affected program

C:\Winnt\System32\config.nt The system file is not suitable for running MS-DOS and Microsoft
Windows applications. Choose ‘Close’ to terminate the application.

16-bit MS-DOS Subsystem

path to the affected program

config.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose ‘Close’ to terminate the application.

16-bit MS-DOS Subsystem

path to the affected program

C:\Windows\System32\Autoexec.nt The system file is not suitable for running MS-DOS and Microsoft Windows applications. Choose ‘Close’ to terminate the application.

The files at the root of the problem are shown below.

  • Config.nt
  • Autoexec.nt
  • Command.com

If you’re suffering from the problem, you’ll no doubt be pleased to know that there is a fairly straightforward fix which eliminates the compatibility issue under most circumstances.

  • Go to Start, then Run and type “C:\Windows\Repair
  • Locate the Autoexec.nt file, right click it and select Copy.
  • Go back to Start, then Run, now type %windir%\system32 followed by clicking OK.
  • When the System32 folder opens, paste the Autoexec.nt file inside using CTRL and V.

This very quick fix should clear up most issues with 16 bit applications, both DOS based and those that run via Windows.

We should make it clear that this is only a common error on Windows XP systems. It’s unlikely that you will encounter it on the older models, as full support was enabled for 16 bit programs. But as that technology becomes slowly out of date, you can expect to see a few more problems arising.

So how do the core files become corrupt? Well, it could be through an accidental deletion from an inexperienced user, or it could be the result of a more damaging incident – such as the spreading of a virus or a worm.

Many viruses, particularly the more damaging breed, will attack the System32 folder as it holds some files which are critical to the functionality of a system. Unfortunately that can mean an easy corruption of the aforementioned files that we’ve discussed, particularly autoexec.nt.

Be sure to equip your system with the latest anti-Virus software and this will act as a good barrier between your critical files, and the grasp of a malicious hacker. Viruses aren’t the only reason behind file corruptions, of course. Spyware and malware can mess with the integrity of your files by writing files messily to the hard drive.

It’s a good idea to run regular system scans to weed out the corrupted files and to draw attention to any bad directories. Thankfully, the Windows Repair utility makes it quite easy to deal with 16 bit errors. If you’re running applications in a 16-bit environment and receiving the errors at the top of the page, you should check your core files before running a full virus scan. The error itself may sound somewhat optional, but it will always result in the program being terminated – whether you choose to close it or not.

Error 0×800CCC92

Posted by admin on 01 Jan 2008 | Tagged as: 0x800CCC92, outlook express, server, error

The error, 0×800CCC92, seen above, is quite confusing in the sense that it stems from a fault on Microsoft’s part. Of course, Microsoft isn’t the most reputable company around for releasing error-free software, but the 0×800CCC92 is unique in the way that it affects one program, and is caused by another.

The two programs at the root of the problem are Microsoft Exchange Server 2000 and Microsoft Outlook Express. The problem itself is caused when trying to retrieve mail from the server in Outlook Express. You will be faced with an error indicating an incorrect password or a fault with the login details. Of course, this is a red herring and has nothing to do with the real problem, which is actually a fault in Exchange Server.

Outlook Express and Exchange Server work in tandem, sharing functions and system resources.

You will receive the error at the top of the page when trying to access a POP email server, but we should point out that the error will vary if you are trying to use an Internet Messaging Protocol (IMAP). In this case, it will be shown as below:

Header download for the ‘Inbox’ folder did not complete. Could not download new messages from the IMAP server.

Account: ’storedriver3 (2)’

Server: ’storedriver3′

Protocol: IMAP

Server Response: ‘Unrecognized internal error: 0×800cce21′

Port: 143

Secure(SSL): No

Error Number: 0×800CCCD2

In either case, the source of the error is the collision between the two aforementioned programs. While it’s perfectly possible to uninstall Microsoft Exchange Server and fix the problem, such measures aren’t particularly desirable or indeed, necessary.

Microsoft has released a patch for Exchange Server which overwrites a key function and allows the two programs to work in tandem, without the inconvenience of the 0×800CCC92 error. It’s rare that you’ll receive the error at all since the more recent products have been fixed. But if you’re using older software, it’s still an issue.

The patch is included in Microsoft Exchange 2000 Server Service Pack 2, and after installing, the error will disappear and allow full functionality of both applications. The Service Pack is free to download from the Microsoft website, although you will have to search through the archives to obtain the fix as it slowly becomes more obsolete with the arrival of Vista and a whole new generation of Microsoft apps.

Thankfully the new versions of Outlook Express and Exchange Server return no such error. As a general rule, it’s a good idea to keep up to date with all of the Service Packs that Microsoft releases for its existing products. Not only will they clear up existing errors like the 0×800CCC92, but they will patch up security weaknesses too. Visit the Microsoft website to obtain the latest Service Pack to get rid of the error, and you should find that its possible to retrieve your email without fault from both the POP and IMAP servers.

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

0×0eedfade Error

Posted by admin on 01 Jan 2008 | Tagged as: blue screen of death, 0x0eedfade, error, operating system, windows

There has been much debate over the cause of the 0×0eedfade error, and many different scenarios have been reported where the error is seen.

Some users suffer from a module box error when closing Internet Explorer, others have noted instances where the error has disabled the operating system completely and forced a restart. Of course, restarting the computer might regain control temporarily, but when the error strikes again, you’re stuck in a vicious circle.

It’s generally perceived that the error is caused by malicious third party content such as spyware and adware. These redundant files do little or nothing to advance our experience on the computer, but they can cause a great deal of collisions in the way that the system operates.

The first port of call should be to rid your computer of any unsolicited third party content. Spyware is notorious for running in the background and avoiding detection by the naked eye. Yet it can reduce the performance of a system by a considerable margin. It also opens the computer to a new range of virus attacks.

However, spyware removal tools aren’t a foolproof solution. They can potentially damage what’s known as the Winsock stack, and this will lead to more problems and inevitably – more errors.

You can download special Winsock fix utilities which will repair the stack and, rather surprisingly, fix a lot of additional errors in the process. When combining it with a registry cleaner, you can weed out all of the corrupt files and reorganize your system so that any viruses or lingering spyware apps can be taken care of.

If a Winsock patch doesn’t get rid of the 0×0eedfade error, move on to the spyware removal software. There are plenty of free versions on the market and they take care of most third party content. We should stress that it’s extremely important to have sufficient anti-Virus protection on your system, at all times.

Viruses are capable of disabling Windows, particularly if you get one which attacks the boot sector. They also make the blue screen of death a recurring sight, and errors like the 0×0eedfade are known to arise from such infiltrations.

Even if you have a professional standard anti-Virus suite installed, don’t let that lure you in to a false sense of security. Some viruses are now so sophisticated that they can be designed to slip through the net of specific anti-Virus software. The best way to tackle this is to use two separate packages. With the combined technology, you should be able to sniff out all of the bad files.

There is no agreed explanation for when and where the 0×0eedfade error will appear. It is often seen as a third party error. A fault which appears after you’ve installed certain commercial packages (or uninstalled them rather). The most commonly documented problem is with Internet Explorer and an error which forces the system to restart. The toolbar is also disabled, which gives the distinct impression that it’s a virus at fault.

To avoid such problems, run regular scans of your hard drive. Keep a backup of the registry, and clean it once per month. Finally, be sure that you use proper anti-Virus protection when accessing the Internet. This should save you the headache and frustration of a blue screen and repeated 0×0eedfade errors!

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

Windows Error Message 0×0000007b

Posted by admin on 01 Jan 2008 | Tagged as: blue screen of death, 0x0000007b, error, operating system, windows

The 0×0000007B error usually appears during the start up of Windows, or when trying to install a fresh copy of the Operating System. The error is typically displayed in the way seen below.

STOP: 0×0000007B (parameter1, parameter2, parameter3, parameter4)
INACCESSIBLE_BOOT_DEVICE

It all sounds pretty daunting, but the inaccessible boot device hint tells us much about how to fix the problem itself.

The issue stems from one of three causes.

You could be suffering from a virus on the boot sector. These are particularly devastating viruses because they render an operating system useless and can prohibit any kind of access to the OC controls. In situations such as that where the damage is severe, you will need to repartition your hard drive and proceed with a complete re-install of Windows.

It may be possible to get rid of the virus if you have access to an anti-Virus control suite, and the system is functional enough to allow you to use it. Run a complete scan and remove the viruses individually, combining protection utilities where appropriate to ensure that all of the bad files are dealt with.

Alternatively, the fault could potentially lie with the boot controller. Every time your operating system is loaded, the boot controller loads up device drivers which run through the process of initiating the rest of the software. If the device drivers become corrupt or are removed altogether, you will receive a 0×0000007B error, probably amongst others too.

A registry cleaning utility will go a long way to ensuring that your device drivers are kept in tact. Remember that all the information to these drivers is stored in that one registry. If a virus or manual change alters the registry in a bad way, you can be faced with no end of problems. For that reason, it’s a good idea to keep a backup of a working registry at all times. If you’re faced with the device errors, you can reset the registry and regain control of the system.

The error is occasionally born from a collision with the IRQs and port allocations. This is more of a hardware issue, or at least, an issue with the way that your devices have been configured. To fix the problem, you’ll need to enter the device manager and ensure that different devices aren’t stealing the same IRQ line. If you have collisions, Windows will be thrown off and the errors will appear.

0×0000007B errors are often quite intimidating to receive. The blue screen of death isn’t a pleasant sight for any Windows user, but the persistent nature of the error can make it hard to fix. If you’re suffering from a boot sector virus – probably the least wanted reason for this error – you’ll need to reformat before you can begin to use Windows properly again.

So naturally, it’s a wise idea to stay up to date with the best anti-Virus protection. Make sure that you’re protected from the latest and obscurest threats. Also, keep a registry cleaning utility handy and put it to use once a month to clear up any of those potentially debilitating device driver errors.

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

« Previous Page