How To Fix Xlive.dll Not Found or Missing Errors

Xlive.dll Error Messages

There are several different ways that xlive.dll errors can show up on your computer. Here are some of the more common ways that you might see xlive.dll errors:

• "Xlive.dll Not Found"
  
• "This application failed to start because xlive.dll was not found. Re-installing the application may fix this problem."
  
• "Cannot find [PATH]\xlive.dll"
  
• "The file xlive.dll is missing."
  
• "Cannot start [APPLICATION]. A required component is missing: xlive.dll. Please install [APPLICATION] again."

Xlive.dll error messages might appear while using or installing certain programs, when Windows starts or shuts down, or maybe even during a Windows installation.
The context of the xlive.dll error is an important piece of information that will be helpful while solving the problem.

Cause of Xlive.dll Errors

Xlive.dll errors are caused by situations that lead to the removal or corruption of the xlive DLL file.
In some cases, xlive.dll errors could indicate a registry problem, a virus or malware issue or even a hardware failure.

How To Fix Xlive.dll Errors

Important: Do not download xlive.dll from a "DLL download" website. There are many reasons why downloading a DLL file is a bad idea. If you need a copy of xlive.dll, it's best to obtain it from its original, legitimate source. Note: Start Windows in Safe Mode to complete any of the following steps if you're unable to access Windows normally due to the xlive.dll error.

1. Download Games for Windows Live. The xlive.dll file is included in this download from Microsoft and installing it will likely replace the xlive.dll file, fixing this problem.
   
2. Restore xlive.dll from the Recycle Bin. The easiest possible cause of a "missing" xlive.dll file is that you've mistakenly deleted it.
   If you suspect that you've accidentally deleted xlive.dll but you've already emptied the Recycle Bin, you may be able to recover xlive.dll with a free file recovery program.
   Important: Recovering a deleted copy of xlive.dll with a file recovery program is a smart idea only if you're confident you've deleted the file yourself and that it was working properly before you did that.
   
3. Run a virus/malware scan of your entire system. Some xlive.dll errors could be related to a virus or other malware infection on your computer that has damaged the DLL file. It's even possible that the xlive.dll error you're seeing is related to a hostile program that's masquerading as the file.
   
4. Use System Restore to undo recent system changes. If you suspect that the xlive.dll error was caused by a change made to an important file or configuration, a System Restore could solve the problem.
   
5. Reinstall the program that uses the xlive.dll file. If the xlive.dll DLL error occurs when you use a particular program, reinstalling the program should replace the file.
   Important: Try your best to complete this step. Reinstalling the program that provides the xlive.dll file, if possible, is a likely solution to this DLL error.
   
6. Update the drivers for hardware devices that might be related to xlive.dll. If, for example, you're receiving a "The file xlive.dll is missing" error when you play a 3D video game, try updating the drivers for your video card.
   Note: The xlive.dll file may or may not be related to video cards - this was just an example. The key here is to pay very close attention to the context of the error and troubleshoot accordingly.
   
7. Roll back a driver to a previously installed version if xlive.dll errors began after updating a particular hardware device's driver.
   
8. Run the sfc /scannow System File Checker command to replace a missing or corrupt copy of the xlive.dll file. If this DLL file is provided my Microsoft, the System File Checker tool should restore it.
   
9. Install any available Windows updates. Many service packs and other patches replace or update some of the hundreds of Microsoft distributed DLL files on your computer. The xlive.dll file could be included in one of those updates.
   
10. Test your memory and then test your hard drive. I've left the majority of hardware troubleshooting to the last step, but your computer's memory and hard drive are easy to test and are the most likely components that might cause xlive.dll errors as they fail.
    If the hardware fails any of your tests, replace the memory or replace the hard drive as soon as possible.
    
11. Repair your installation of Windows. If the individual xlive.dll file troubleshooting advice above is unsuccessful, performing a startup repair or repair installation should restore all Windows DLL files to their working versions.
    
12. Use a free registry cleaner to repair xlive.dll related issues in the registry. A free registry cleaner program may be able to help by removing invalid xlive.dll registry entries that might be causing the DLL error.
    Important: I rarely recommend the use of registry cleaners. I've included the option here as a "last resort" attempt before the destructive step coming up next.
    
13. Perform a clean installation of Windows. A clean install of Windows will erase everything from the hard drive and install a fresh copy of Windows. If none of the steps above correct the xlive.dll error, this should be your next course of action.
    Important: All the information on your hard drive will be erased during a clean install. Make sure you've made the best attempt possible to fix the xlive.dll error using a troubleshooting step prior to this one.
    
14. Troubleshoot for a hardware problem if any xlive.dll errors persist. After a clean install of Windows, your DLL problem can only be hardware related.
    

How To Fix STOP 0x0000007B Errors

STOP 0x0000007B Error Messages

The STOP 0x0000007B error will always appear on a STOP message, more commonly called a Blue Screen of Death (BSOD). One of the errors below or a combination of both errors may display on the STOP message:

• "STOP: 0x0000007B"
  
• "INACCESSIBLE_BOOT_DEVICE"

The STOP 0x0000007B error may also be abbreviated as STOP 0x7B but the full STOP code will always be what's displayed on the blue screen STOP message.
If Windows is able to start after the STOP 0x7B error, you may be prompted with a Windows has recovered from an unexpected shutdown message that shows:
Problem Event Name: BlueScreen BCCode: 7b

Cause of STOP 0x0000007B Errors

STOP 0x0000007B errors are caused by device driver issues (especially those related to hard drive and other storage controllers), viruses, data corruption, and sometimes even hardware failures.
If STOP 0x0000007B isn't the exact STOP code you're seeing or INACCESSIBLE_BOOT_DEVICE isn't the exact message, please check my Complete List of STOP Error Codes and reference the troubleshooting information for the STOP message that you are seeing.

How To Fix STOP 0x0000007B Errors

Note: Some of these steps may require you to access Windows via Safe Mode. If that's not possible then skip those steps.

1. Restart your computer if you haven't already done so. The STOP 0x0000007B blue screen error might be a fluke.
   
2. Did you just install or make a change to a hard drive controller? If so, there's a good chance that the change you made caused the STOP 0x0000007B error.
   Undo the change and test for the 0x7B blue screen error.
   Depending on what changes you made, some solutions might include:
   
   • Remove or reconfigure the newly installed hard drive controller.
   • Startup with Last Known Good Configuration to undo related registry and driver changes.
   • Use System Restore to undo recent changes.
   • Rollback hard drive controller device driver to version prior to your driver update.
3. Verify that the SCSI chain is correctly terminated, assuming you're using SCSI hard drives in your computer. Incorrect SCSI termination has been known to cause STOP 0x0000007B errors.
   Note: Most home computers don't utilize SCSI hard drives.
   
4. Verify that the hard drive is properly installed. An improperly installed hard drive could cause STOP 0x0000007B errors and other issues.
   
5. Verify that the hard drive is configured properly in BIOS. The STOP 0x0000007B error could occur if the hard drive settings in BIOS are incorrect.
   
6. Scan your computer for viruses. Certain viruses that infect the master boot record (MBR) or boot sector can cause STOP 0x0000007B errors.
   Important: Make sure your virus scanning software is updated and configured to scan the MBR and boot sector.
   
7. Update the drivers for your hard drive controller. If the drivers to your hard drive controller are outdated, incorrect, or corrupted then the STOP 0x0000007B error will likely occur.
   Note: If the STOP 0x0000007B error occurs during the Windows setup process and you suspect that the reason is driver related, be sure to install the latest hard drive controller driver from the manufacturer for use during the installation of the operating system.
   Note: This is a likely solution if the second hexadecimal number after the STOP code is 0xC0000034.
   
8. Change the SATA mode in BIOS to IDE mode. Disabling some of the advanced features of SATA drives in BIOS could stop the STOP 0x0000007B error from showing up, especially if you're seeing it in Windows XP or during a Windows XP installation.
   Note: Depending on your BIOS make and version, SATA mode may be referred to as AHCI mode and IDE mode may be referred to as either Legacy, ATA, or Compatibility Mode.
   Note: While not a common solution, you may also want to try the reverse - see if IDE mode is selected in BIOS and if so change it to AHCI, especially if you see the STOP 0x0000007B error in Windows 8, Windows 7, or Windows Vista.
   
9. Run chkdsk on your hard drive. If the boot volume is corrupted, the chkdsk command might repair the corruption.
   Important: You'll likely have to run chkdsk from the Recovery Console.
   Note: This will likely be the solution if the second hexadecimal number after the STOP code is 0xC0000032.
   
10. Perform an extensive test of your hard drive. If your hard drive has a physical problem, one very likely situation is the STOP 0x0000007B error you're seeing.
    Replace the hard drive if the diagnostics you complete suggest that there is a hardware problem with the drive.
    
11. Run the fixmbr command to create a new master boot record. A corrupted master boot record might be causing your STOP 0x0000007B error.
    Note: This will likely be the solution if the second hexadecimal number after the STOP code is 0xC000000E.
    
12. Clear the CMOS. Sometimes the STOP 0x0000007B error is caused by a BIOS memory issue. Clearing the CMOS could solve that problem.
    
13. Update your BIOS. In some situations, an outdated BIOS could cause a STOP 0x0000007B error due to incompatibilities with a hard drive controller.
    
14. Update the hard drive controller's firmware if possible. Just as with the BIOS in the previous step, an incompatibility could be causing the 0x7B error and a firmware update from the manufacturer may correct the problem.
    
15. Repair your Windows installation. If you've just replaced the motherboard in a computer without reinstalling Windows then this will likely fix your problem.
    Note: Sometimes a Windows repair will not fix a STOP 0x0000007B error. In those cases, a clean installation of Windows should do the trick.
    If you haven't just replaced your motherboard, a Windows reinstall probably will not fix your STOP 0x7B issue.
    
16. Perform basic STOP error troubleshooting. If none of the specific steps above help fix the STOP 0x0000007B error you're seeing, take a look at this general STOP error troubleshooting guide. Since most STOP errors are similarly caused, some of the suggestions might help.

Please let me know if you've fixed a blue screen of death with the STOP 0x0000007B STOP code using a method that I don't have above. I'd like to keep this page updated with the most accurate STOP 0x0000007B error troubleshooting information as possible

How To Fix Lame_enc.dll Not Found Errors

Lame_enc.dll Error Messages

Any error message involving a missing lame_enc.dll DLL file is referring to some issue that the program you are using is having with the LAME MP3 encoder.
The first error, generated by the Audacity software program, is by the far the most common simply because Audacity is the most common application that utilizes the LAME MP3 encoder.
If you're not using Audacity, your error message will be different and may appear more like the final two examples below:

• "Audacity does not export MP3 files directly, but instead uses the freely available LAME library to handle MP3 file encoding. You must obtain lame_enc.dll separately, by downloading the LAME MP3 encoder, and then locate this file for Audacity. You only need to do this once. Would you like to locate lame_enc.dll now?"
  
• "The LAME_ENC.DLL File Was Not Found"
  
• "Error loading lame_enc.dll"

Lame_enc.dll errors sometimes occur when the audio program you're using is first opened.
Other times, the lame_enc.dll error will show up when you attempt to save the audio project you're working on as an MP3 file.

Cause of Lame_enc.dll Errors

All lame_enc.dll errors are caused by either the missing component from the LAME MP3 encoder or some other issue that the audio program you're using is having with the LAME MP3 encoder.

How To Fix Lame_enc.dll Errors

Important Note: Do not download the lame_enc.dll DLL file individually from any "DLL download site." There are many reasons that downloading DLLs from these sites are never a good idea. There are a large number of sites offering the lame_enc.dll for download but there are few legitimate sites that I would recommend. Note: If you've already downloaded the lame_enc.dll file from one of those DLL download sites, remove it from wherever you placed it and continue with the following steps.

1. Close and reopen the audio program that generated the lame_enc.dll error. Audacity, or whatever audio program you're using, may be having a temporary problem that a restart might fix.
   
2. Download the latest LAME MP3 encoder package. The ZIP file at this Audacity-sanctioned site contains the latest version of the lame_enc.dll and related files.
   Note: The true source location for the LAME MP3 encoder is located at the LAME site on SourceForge.net but the files here are not readily usable by your audio program.
   
3. Extract the files from the ZIP file downloaded in Step 2.
   
4. Copy the lame_enc.dll file to whatever location your specific audio program requires.
   Note: Some programs don't require the lame_enc.dll file to reside in particular folders. Audacity, for example, only requires you to tell it where the lame_enc.dll file is - it doesn't care where.

Applies To

The lame_enc.dll error message applies to any audio program that utilizes the LAME MP3 encoder. Depending on what program you're using and what operating system you're running, you could see the lame_enc.dll error in Windows 8, Windows 7, Windows Vista, Windows XP, and older versions of Windows as well.
Some common software programs that use the LAME MP3 encoder and that might generate lame_enc.dll errors include Audacity, FFmpeg, VideoLAN, jRipper, CDex, LameDropXPd, DVDx, OmniEncoder, LAMEX, RazorLame, Audigrabber, RipTrax, WinAmp, UltraISO, TextAlound MP3, and many, many more.

How To Fix a 403 Forbidden Error

How You Might See the 403 Error

403 Forbidden error messages are sometimes customized by the websites they appear on but for the most part, you'll see them in one of the following ways:

• "403 Forbidden"
  
• "HTTP 403"
  
• "Forbidden: You don't have permission to access [directory] on this server."
  
• "Forbidden"
  
• "Error 403"
  
• "HTTP Error 403.14 - Forbidden"
  
• "Error 403 - Forbidden"
  
• "HTTP Error 403 - Forbidden"

The 403 Forbidden error displays inside the browser window, just as web pages do. 403 errors, like all errors of this type, might be seen in any browser on any operating system.
In Internet Explorer, a The website declined to show this webpage message indicates a 403 Forbidden error. The IE title bar should say 403 Forbidden or something similar.
403 errors received when opening links via Microsoft Office programs generate a Unable to open [url]. Cannot download the information you requested. message inside the MS Office program.
Windows Update may also report an HTTP 403 error but it will display as error code 0x80244018 or with the following message: WU_E_PT_HTTP_STATUS_FORBIDDEN.

Cause of 403 Forbidden Errors

The 403 Forbidden error is an HTTP status code that means that accessing the page or resource you were trying to reach is absolutely forbidden for some reason. In other words: "Go away and don't come back here."
Note: Microsoft IIS web servers provide more specific information about the cause of 403 Forbidden errors by suffixing a number after the 403 as in HTTP Error 403.14 - Forbidden which means Directory listing denied. You can see a complete list here.

How To Fix the 403 Forbidden Error

1. Check for URL errors and make sure you're specifying an actual web page file name and extension, not just a directory. Most websites are configured to disallow directory browsing so a 403 Forbidden message when trying to display a folder instead of a specific page is normal and expected.
   Important: This is, by far, the most common reason for a web site to return the 403 Forbidden error. Be sure you fully explore this possibility before investing time in the troubleshooting below.
   Tip: If you operate the website in question, and you want to prevent 403 errors in these cases, enable directory browsing in your web server software.
   
2. Clear your browser's cache. Issues with a cached version of the page you're viewing could be causing 403 Forbidden issues.
   
3. Log in to the website, assuming it's possible and appropriate to do so. A 403 Forbidden message could mean that you need additional access before you can view the page.
   Typically, a website produces a 401 Unauthorized error when special permission is required but sometimes a 403 Forbidden is used instead.
   
4. Clear your browser's cookies, especially if you typically log in to this website and logging in again (the last step) didn't work.
   Note: While we're talking about cookies, be sure you have them enabled in your browser, or at least for this website, if you do actually log in to access this page. The 403 Forbidden error in particular indicates that cookies may be involved in obtaining proper access.
   
5. Contact the website directly. It's possible that the 403 Forbidden error is a mistake, everyone else is seeing it too, and the website isn't yet aware of the problem.
   You can often find a website's contact information through a WHOIS search, using the domain name (e.g. mtv.com) as your search term.
   If an email address isn't listed, you might have luck emailing webmaster@website.com, replacing website.com with the actual website name. Another option is to contact the site via one of their social networking profiles.
   
6. Contact your ISP if your still getting the 403 error, especially if you've contacted the website in question and they say everything is good on their end.
   It's possible that your public IP address, or your entire Internet Service Provider, has been blacklisted, a situation that could produce a 403 Forbidden error, usually on all pages on one or more sites.
   Tip: See my How To Talk To Tech Support for some help on communicating this issue to your ISP.
   
7. Come back later. Once you've verified that the page you're accessing is the correct one and that the HTTP 403 error is being seen by more than just you, just revisit the page on a regular basis until the problem is fixed.

How To Fix BOOTMGR is Missing Errors

BOOTMGR Error Message

There are few ways that the "BOOTMGR is missing" error may show up on your computer, with the first error I have listed being the most common:

• "BOOTMGR is missing
  Press Ctrl Alt Del to restart"
   
• "BOOTMGR is missing
  Press any key to restart"
   
• "Couldn't find BOOTMGR"

The "BOOTMGR is missing" error displays shortly after the computer is turned on, immediately after the Power On Self Test (POST) is complete. Windows has only initially started to load when the BOOTMGR error message appears.

Causes of BOOTMGR Errors

There are a number of possible causes for BOOTMGR errors, including the most common "BOOTMGR is missing" error message.
The most common reasons for BOOTMGR errors include corrupt and misconfigured files, hard drive and operating system upgrade issues, corrupt hard drive sectors, an outdated BIOS, and damaged or loose hard drive interface cables.
Another reason you might see BOOTMGR errors is if your PC is trying to boot from a hard drive or flash drive that is not properly configured to be booted from. In other words, it's trying to boot from a non-bootable source. This also would apply to media on an optical drive or floppy drive that you're trying to boot from.

Fixes for BOOTMGR Errors

1. Restart the PC. The BOOTMGR error could be a fluke.
    
2. Check your optical drives, USB ports, and floppy drives for media. Often times, the "BOOTMGR is Missing" error will appear if your PC is trying to boot to a non-bootable disc, external drive, or floppy disk.
   
   Note: If you find that this is the cause of your issue and it's happening regularly, you might want to consider changing the boot order in BIOS so the hard drive is listed as the first boot device.
    
3. Check the boot sequence in BIOS and make sure the correct hard drive or other bootable device is listed first, assuming you have more than one drive. If the wrong drive is listed first, you could see BOOTMGR errors.
   
   I know I sort of hit on this in the troubleshooting step above, but I wanted to call out specifically that you might have the wrong hard drive listed, as many BIOS/UEFI systems allow you to specify specific a particular hard drive to be booted from first.
    
4. Reseat all internal data and power cables. BOOTMGR error messages could be caused by unplugged, loose, or malfunctioning power or controller cables.
   
   Try replacing the PATA or SATA cable if you suspect it might be faulty.
    
5. Perform a Startup Repair of Windows. This type of installation should replace any missing or corrupt files, including BOOTMGR.
   
   Even though a Startup Repair is a common solution for BOOTMGR problems, don't worry if it doesn't fix your problem. Just continue troubleshooting - something will work.
    
6. Write a new partition boot sector to the Windows system partition to correct any possible corruption, configuration problem, or other damage.
   
   The partition boot sector is an important piece in the boot process so if there's any issue with it, you'll see problems like "BOOTMGR is Missing" errors.
    
7. Rebuild the Boot Configuration Data (BCD). Similar to the partition boot sector, a corrupted or incorrectly configured BCD could cause BOOTMGR error messages.
   
   Important: The following troubleshooting steps are much less likely to help fix your BOOTMGR problem. If you've skipped any of the above ideas then you may have overlooked a very likely solution to this problem!
    
8. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including BOOTMGR errors.
   
   Note: There's usually an Auto setting in BIOS for hard disk and optical drive configurations which is usually a safe bet if you're not sure what to do.
    
9. Update your motherboard's BIOS. An outdated BIOS version can sometimes cause the "BOOTMGR is Missing" error.
    
10. Perform a clean installation of Windows. This type of installation will completely remove Windows from your PC and install it again from scratch. While this will almost certainly resolve any BOOTMGR errors, it's a time consuming process due to the fact that all of your data must be backed up and then later restored.
    
    If you can't gain access to your files to back them up, please understand that you will lose them all if you continue with a clean installation of Windows!
     
11. Replace the hard drive and then install a new copy of Windows. If all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive.

BOOTMGR Errors Apply To

BOOTMGR issues apply to Windows 8, Windows 7, and Windows Vista operating systems only.
Windows XP does not utilize BOOTMGR. The equivalent function in Windows XP is NTLDR which produces the NTLDR is Missing error when there's a similar problem.

How To Fix Ntdll.dll Errors

Ntdll.dll Error Messages

There are many different ways that ntdll.dll errors may be displayed on your computer. Ntdll.dll errors can be caused by a number of different things which result in many different error messages, but some of the most common are listed below:

• "STOP: 0xC0000221 unknown hard error C:\Winnt\System32\Ntdll.dll"
   
• "STOP: C0000221 unknown hard error \SystemRoot\System32\ntdll.dll"
   
• "AppName: [PROGRAM NAME] ModName: ntdll.dll"
   
• "[PROGRAM NAME] caused a fault in module NTDLL.DLL at [ANY ADDRESS]"
   
• "Crash caused in ntdll.dll!"
   
• "NTDLL.DLL Error!"
   
• "Unhandled exception at [ANY ADDRESS] (NTDLL.DLL)"

Ntdll.dll error messages might appear before or after a program is used, while a program is running, when Windows is started or shutdown, or even during a Windows installation.

Cause of Ntdll.dll Errors

The causes of ntdll.dll error messages can vary greatly. However, most ntdll.dll errors result from a corrupt or damaged version of the ntdll.dll file itself, corrupt hardware drivers, or issues between Windows and other programs. Ntdll.dll errors can sometimes mean that a piece of hardware in your computer is malfunctioning, but this is rare.

How To Fix Ntdll.dll Errors

1. Restart your computer. The ntdll.dll error you're receiving could be due to a one-time, temporary issue and a simple reboot may resolve the problem completely.
    
2. Reinstall the program if the ntdll.dll error only displays when you use a specific program.
   
   If the software program has any updates or service packs available, install them too. The software's programmers may have identified an issue with the program that caused the ntdll.dll error and then issued a patch for it.
   
   Note: Third party software programs that have been installed on your computer are almost always the cause of ntdll.dll errors. The remainder of these troubleshooting steps resolve ntdll.dll issues only rarely.
    
3. Check the Windows service pack level you're running and then check Microsoft's support site to see if there is a more recent service pack available for installation. Some issues that caused ntdll.dll errors have been corrected in these service packs from Microsoft.
    
4. Selectively disable Internet Explorer add-ons. If your ntdll.dll error is displaying when you start, run, or close Internet Explorer, an add-on may be causing the problem. Disabling each add-on, one by one, will determine which add-on is the culprit (if any).
   
   Note: As a workaround, assuming the ntdll.dll error really is Internet Explorer related, install and use a competing browser like Firefox.
    
5. Rename the NLSPATH system variable. If your Windows system does not have this environment variable, skip this step.
   
   Note: This is a troubleshooting step for this issue only. Be sure to set this path back to its original name if this does not resolve the ntdll.dll issue.
    
6. Disable Data Execution Prevention for Explorer.exe. As in the previous step, this is for troubleshooting the ntdll.dll issue only. If this doesn't resolve the problem, return the Data Execution Prevention settings to their previous settings.
    
7. Disable UAC. This is a workaround for some causes of ntdll issues, but could serve as a permanent solution if not using User Account Control is something you're comfortable with on your computer.
    
8. Update drivers for any hardware in your computer where updated drivers are available. Outdated drivers sometimes cause ntdll.dll errors.
    
9. Test your memory for damage. If you're receiving ntdll.dll messages, one possible cause could be a bad memory module in your system. Testing your memory will either identify a problem or clear your RAM of any responsibility.
   
   Replace your memory if it fails any of your tests.
    
10. Ntdll.dll errors could occur if you have an Iomega Zip drive on the same IDE cable as the hard drive inside your computer. If so, move the Zip drive to a dedicated IDE controller.
     
11. Replace the IDE cable connecting the hard drive to the motherboard. If this cable is damaged or malfunctioning, one symptom could be the ntdll.dll error you're seeing.
     
12. Repair your installation of Windows. If individual software reinstallations fail to resolve the problem, a repair installation of Windows will replace the ntdll.dll file.
     
13. Perform a clean installation of Windows. A clean installation will completely remove Windows from your PC and install it again from scratch. I don't recommend this option unless you've exhausted all previous troubleshooting ideas and you're comfortable that the ntdll.dll error is not caused by a single program (Step #2).
    
    Note: If a single program or plugin is causing the ntdll.dll error, reinstalling Windows and then reinstalling all of the same software may lead you right back to the same ntdll.dll error.
     
14. While extremely rare, if everything else has failed, including the clean installation from the last step, you could be dealing with a hardware issue with your hard drive.

How To Fix a 500 Internal Server Error

How You Might See the 500 Error

The 500 Internal Server Error message might be seen in any number of ways because each website is allowed to customize the message. Here are several common ways that you might see the HTTP 500 error:

• "500 Internal Server Error"
   
• "HTTP 500 - Internal Server Error"
   
• "Temporary Error (500)"
   
• "Internal Server Error"
   
• "HTTP 500 Internal Error"
   
• "500 Error"
   
• "HTTP Error 500"

500 Internal Server Error messages can show up in any browser in any operating system.
In Internet Explorer, the message The website cannot display the page often indicates an HTTP 500 Internal Server Error. A 405 Method Not Allowed error is another possibility but you can be sure by looking for either 500 or 405 in the IE title bar.
Most of the time, a 500 Internal Server Error displays inside the Internet browser window, just as web pages do.
When Windows Update reports an Internal Server Error, it appears as a WU_E_PT_HTTP_STATUS_SERVER_ERROR message or as the 0x8024401F error code.
When Google services, like Gmail or Google+, are experiencing a 500 Internal Server Error, they often report a Temporary Error (500).

Cause of HTTP 500 Errors

The 500 Internal Server Error is a very general HTTP status code that means something has gone wrong on the web site's server but the server could not be more specific on what the exact problem is.
Most of the time, "gone wrong" means an issue with the page or site's programming, nothing you have anything to do with.
Note: More specific information about the cause of a particular HTTP 500 error is often provided when it occurs on a server using Microsoft IIS software. Look for numbers after 500 as in HTTP Error 500.19 - Internal Server Error which means Configuration data is invalid. You can see a complete list here.

How To Fix the 500 Internal Server Error

Like I alluded to above, the 500 Internal Server Error is a server-side error, meaning the problem probably isn't with your computer or Internet connection but instead is a problem with the web site's server.
While not probable, it is possible that there's something wrong on your end and we'll look at some things you can try.

1. Reload the web page. You can do that by clicking the refresh/reload button, pressing F5, or trying the URL again from the address bar.
   
   Even if the 500 Internal Server Error is a problem on the web server, the issue may only be temporary. Trying the page again will often be successful.
   
   Note: If the 500 Internal Server Error message appears during the checkout process at an online merchant, be aware that duplicate attempts to checkout may end up creating multiple orders - and multiple charges! Most merchants have automatic protections from these kinds of actions but it's still something to keep in mind.
    
2. Clear your browser's cache. If there's a problem with the cached version of the page you're viewing, it could be causing HTTP 500 issues.
   
   Note: Internal Server Errors are not often caused by caching issues but I have, on occasion, seen the error go away after clearing the cache. It's such an easy and harmless thing to try so don't skip it.
    
3. Delete your browser's cookies. Some 500 Internal Server Error issues can be corrected by deleting the cookies associated with the site you're getting the error on.
   
   After removing the cookie(s), restart the browser and try again.
    
4. Troubleshoot as a 504 Gateway Timeout error instead.
   
   It's not very common, but some servers produce a 500 Internal Server Error when in reality the more appropriate message based on the cause of the problem is 504 Gateway Timeout.
    
5. Contact the website directly. Chances are good that the website administrators already know about the 500 error but if you suspect they don't, letting them know helps both you and them (and everyone else).
   
   The best way to find contact information for a website is through a WHOIS search, using the domain name (e.g. facebook.com) as your search term.
   
   If an email address isn't listed, try webmaster@website.com, replacing website.com with the actual website name. Sending a message to the site via their social networking profile is another good idea.
    
6. Come back later. The 500 Internal Server Error message is one of the most common HTTP error messages seen when checking out during an online purchase so sales are often disrupted. This is usually a great incentive to resolve the issue very quickly.
   
   Even if you're getting the 500 error on a site that doesn't sell anything, like YouTube or Twitter, as long as you've let them know about the problem, there's little more you can do than wait it out.

How To Fix Ieframe.dll Errors

Ieframe.dll Error Messages

Ieframe.dll errors are fairly varied and really depend on the cause of the problem. A few of the more common ieframe.dll related errors are shown here:

• "Res://ieframe.dll/dnserror.htm#"
  
• "File Not Found C:\WINDOWS\SYSTEM32\IEFRAME.DLL"

Most ieframe.dll "not found" or "missing" type of errors occur when using Internet Explorer or while using Visual Basic.
The "Res://ieframe.dll/dnserror.htm" and related messages are much more common and appear in the Internet Explorer browser window itself.

Cause of Ieframe.dll Errors

The ieframe.dll DLL file is related to Internet Explorer. In many cases, the installation of Internet Explorer causes ieframe.dll errors to appear. Other causes include viruses, certain Windows Updates, incorrect firewall settings, outdated security software applications, and more.

How To Fix Ieframe.dll Errors

Important Note: Do not, under any circumstances, download the ieframe.dll DLL file individually from any "DLL download site." There are many reasons that downloading DLLs from these sites are never a good idea. Note: If you've already downloaded ieframe.dll from one of those DLL download sites, remove it from wherever you placed it and continue with the following steps.

1. Restart your computer unless you've already done so. The ieframe.dll error might be a fluke and a simple restart could clear it up completely.
   
2. Install the latest version of Internet Explorer. No matter if you're missing ieframe.dll or if you're receiving a browser error message about it, reinstalling or updating to the latest version of Internet Explorer has resolved many user's issues with ieframe.dll.
   
3. Using Visual Basic? If so, change the reference for Microsoft Internet Controls from the existing ieframe.dll to shdocvw.ocx. Save your project and then reopen it.
   
4. Restart your router, switch, cable/DSL modem and anything else that's used to communicate to the Internet or other computers on your network. There may be an issue in one of these pieces of hardware that a simple restart could solve.
   
5. Scan your entire computer for viruses. Sometimes, the ieframe.dll error will show up when your computer is infected with certain kinds of viruses. Use your antivirus software to do a complete system scan for virus infections.
   
6. Disable Windows Firewall if you have another firewall installed. Running two firewall applications at the same time can cause problems.
   Note: Even if you're positive that the Windows firewall is disabled, check again. Some Microsoft security updates have been known to re-enable the firewall automatically even if you have an existing firewall enabled in another security software program.
   
7. Update all non-Microsoft firewall and other security software on your computer. Certain security updates from Microsoft have been known to cause issues with security software from other vendors that those vendors are responsible for resolving. Check their websites for updates or service packs and install any that are available.
   Note: If you're already running a fully updated version of your security software, try uninstalling and then reinstalling the software instead. A clean installation may stop that nagging ieframe.dll error message.
   
8. Install any available Windows updates. It is true that some previous updates from Microsoft may actually cause some ieframe.dll errors, but installing more recent updates, especially those to the Windows Update software itself, may help resolve the problem.
   
9. Clear the temporary Internet files in Internet Explorer. Some ieframe.dll issues may have to do with problems accessing existing temporary Internet files.
   
10. Increase the frequency that Internet Explorer checks for new versions of web pages. If the default setting is too infrequent and there are issues with certain pages, you may see ieframe.dll and related errors.
    
11. Disable Internet Explorer add-ons one by one. One of your installed add-ons might be causing the ieframe.dll issue. Selectively disabling them will show you which one, if any, is causing problems.
    
12. Set Internet Explorer security options back to their default levels. Some programs, even some updates from Microsoft, will sometimes make automatic changes to your Internet Explorer security settings.
    Incorrect or overprotective security settings can sometimes cause ieframe.dll issues. Returning these settings to their default levels may correct your issue.
    
13. Move the IE Temporary Internet Files Folder to its Default Location in Windows XP. If the Temporary Internet Files folder in Internet Explorer has been moved from its original location, plus both Protected Mode and the Phishing Filter are enabled, the ieframe.dll error will occur.
    
14. Disable the Phishing Filter in Internet Explorer. This isn't a great long term solution if you don't have another phishing filter installed, but disabling IE's phishing filter has been known to correct ieframe.dll issues in some situations.
    
15. Disable Protected Mode in Internet Explorer. The Protected Mode feature in Internet Explorer can, in some very specific situations, be involved in generating an ieframe.dll error message.

Applies To

The ieframe.dll error message applies to Internet Explorer on any of Microsoft's operating systems that support any version of the browser, including Windows 8, Windows 7, Windows Vista, and Windows XP.

How To Fix NTLDR is Missing Errors

NTLDR Error Messages

There are few different ways that the "NTLDR is missing" error may present itself, with the first listing being the most common:

• "NTLDR is missing
  Press any key to restart"
   
• "NTLDR is missing
  Press Ctrl Alt Del to restart"
   
• "Boot: Couldn't find NTLDR
  Please insert another disk"

The "NTLDR is missing" error displays very shortly after the computer is first started, immediately after the Power On Self Test (POST) is complete. Windows XP has only initially begun to load when the NTLDR error message appears.

Causes of NTLDR Errors

There are a number of possible causes for NTLDR errors, including the most common "NTLDR is missing" error message.
The most common reason for this error is when your PC is trying to boot from a hard drive or flash drive that is not properly configured to be booted from; in other words, it's trying to boot from a non-bootable source. This also would apply to media on an optical drive or floppy drive that you're trying to boot from.
Other possible causes include corrupt and misconfigured files, hard drive and operating system upgrade issues, corrupt hard drive sectors, an outdated BIOS, and damaged or loose IDE cables.

How to Fix NTLDR Errors

1. Restart the PC. The NTLDR error could be a fluke.
    
2. Check your floppy and optical (CD/DVD/BD) drives for media and disconnect any external drives. Often times, the "NTLDR is Missing" error will appear if your PC is trying to boot to a non-bootable floppy disk, CD/DVD/BD, or external hard drive or flash drive.
   
   Note: If you find that this is the cause of your problem and it's happening a lot, you might want to consider changing the boot order in BIOS so the hard drive with Windows installed is listed first.
    
3. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including NTLDR errors.
   
   Note: There is usually an Auto setting for hard drive and optical drive configurations in BIOS which is usually a safe bet if you're not sure what to do.
    
4. Restore the NTLDR and ntdetect.com files from the Windows XP CD. Restoring these two important system files from the original Windows XP CD may do the trick.
    
5. Repair or replace the boot.ini file. This will prevent the NTLDR error if the cause of the problem is a boot.ini file that is not configured properly for your Windows XP installation.
    
6. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the "NTLDR is Missing" error.
    
7. Repair the Windows XP master boot record. NTLDR error messages may also appear if the master boot record is corrupt.
    
8. Reseat all internal data and power cables. NTLDR error messages could be caused by loose or malfunctioning IDE cables.
   
   Try replacing the IDE cable cable if you suspect it might be faulty.
    
9. Update your motherboard's BIOS. Occasionally, an outdated BIOS version can cause the "NTLDR is Missing" error.
    
10. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.
     
11. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch. While this will almost certainly resolve any NTLDR errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.
    
    If you can't gain access to your files to back them up, understand that you will lose them all if you continue with a clean installation of Windows XP.
     
12. Replace the hard drive and then perform a new installation of Windows XP. If all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive.

NTLDR Errors Apply To

This issue applies to the Windows XP operating system, including Windows XP Professional and Windows XP Home Edition.
Windows 8, Windows 7, and Windows Vista utilize BOOTMGR, not NTLDR.

How To Fix Missing Hal.dll Errors in Windows XP

Hal.dll Error Message

There are few different ways that the "missing or corrupt hal.dll" error may present itself, with the first listing being the most common:

• "Windows could not start because the following file is missing or corrupt: <Windows root>\system32\hal.dll. Please re-install a copy of the above file."
  
• "<Winnt_root>\System32\Hal.dll missing or corrupt: Please re-install a copy of the above file."
  
• "Cannot find \Windows\System32\hal.dll"
  
• "Cannot find hal.dll"

The "missing or corrupt hal.dll" error displays shortly after the computer is first started. Windows XP has not yet fully loaded when this error message appears.
Windows 8, 7, & Vista: Hal.dll errors in Windows 7, Windows 8, and Windows Vista are often a different issue entirely. See How To Fix Hal.dll Errors in Windows 7, 8, and Vista for help.

Cause

Causes of the "missing or corrupt hal.dll" error include, naturally, a damaged hal.dll DLL file or a hal.dll file that has been deleted or moved from its intended location.
Additional causes may include a damaged or missing boot.ini file or possibly a physically damaged hard drive.

Hal.dll Error Troubleshooting

1. Restart the PC. The hal.dll error could be a fluke.
   
2. Check for proper boot order in BIOS. You might see the hal.dll error if the boot order in BIOS is first looking at a hard drive other than your main hard drive.
   Note: If you've recently changed your boot order or recently flashed your BIOS, this may be what's causing your problem.
   
3. Run Windows XP System Restore from a command prompt. If this doesn't work or you're receiving the hal.dll error message before you're able to complete this process, move on to the next step.
   
4. Repair or replace the boot.ini file. This will work if the cause of the problem is actually Windows XP's boot.ini file and not the hal.dll file, which is often times the case.
   Note: If repairing the boot.ini does correct the hal.dll issue but the problem reappears after a reboot and you've recently installed Internet Explorer 8 in Windows XP, uninstall IE8. In this specific situation, IE8 could be the root cause of your hal.dll problem.
   
5. Write a new partition boot sector to the Windows XP system partition. If the partition boot sector has become corrupt or isn't properly configured, you may receive the hal.dll error.
   
6. Recover data from any bad sectors on your hard drive. If the physical part of your hard drive that stores any part of the hal.dll file has been damaged, you're likely to see errors like this.
   
7. Restore the hal.dll file from the Windows XP CD. If the hal.dll file is truly the cause of the problem, restoring it from the original Windows XP CD may do the trick.
   
8. Perform a repair installation of Windows XP. This type of installation should replace any missing or corrupt files. Continue troubleshooting if this does not resolve the issue.
   
9. Perform a clean installation of Windows XP. This type of installation will completely remove Windows XP from your PC and install it again from scratch.
   Note: While this will almost certainly resolve any hal.dll errors, it is a time consuming process due to the fact that all of your data must be backed up and then later restored.
   Important: If you can't gain access to your files to back them up, you should understand that you will lose them all if you continue with a clean installation of Windows XP.
   
10. Test the hard drive. If all else has failed, including the clean installation from the last step, you're most likely facing a hardware issue with your hard drive but you'll want to test it to be sure.
    If the drive fails any of your tests, replace the hard drive and then complete a "new" installation of Windows XP.

How To Fix a 404 Not Found Error

How You Might See the 404 Error

404 Not Found error messages are frequently customized by individual websites, so keep in mind that the 404 error may show up in just about any way imaginable depending on what website it's shown from.
Here are some common ways in which you might see the HTTP 404 error displayed:

• "404 Error"
   
• "404 Not Found"
   
• "Error 404"
   
• "The requested URL [URL] was not found on this server."
   
• "HTTP 404"
   
• "Error 404 Not Found"
   
• "404 File or Directory Not Found"
   
• "HTTP 404 Not Found"
   
• "404 Page Not Found"

404 Not Found error messages can appear in any browser and in any operating system. Most 404 Not Found errors display inside the Internet browser window just as webpages do.
In Internet Explorer, the message The webpage cannot be found usually indicates an HTTP 404 Internal Server Error but a 400 Bad Request error is another possibility. You can check to see which error IE is referring to by checking for either 404 or 400 in the title bar.
404 errors received when opening links via Microsoft Office applications generate a The Internet site reports that the item you requested could not be found (HTTP/1.0 404) message inside the MS Office program.
When Windows Update produces a 404 error, it appears as a code 0x80244019 or as the message WU_E_PT_HTTP_STATUS_NOT_FOUND.

Cause of HTTP 404 Errors

A 404 error is an HTTP status code that means that the page you were trying to reach on a website couldn't be found on their server.
Technically, an Error 404 is a client-side error, implying that the error is your mistake, either because you typed the URL in wrong or the page has been moved or removed from the website and you should have known.
Another possibility is if a website has moved a page or resource but did so without redirecting the old URL to the new one. When that happens, you'll receive a 404 error instead of being automatically routed to the new page.
Note: Microsoft IIS web servers sometimes give more specific information about the cause of 404 Not Found errors by suffixing a number after the 404 as in HTTP Error 404.3 - Not Found which means MIME type restriction. You can see a complete list here.

How To Fix the 404 Not Found Error

1. Retry the web page by pressing F5, clicking the refresh/reload button, or trying the URL from the address bar again.
   
   The 404 Not Found error might appear for several reasons even though no real issue exists, so sometimes a simple refresh will often load the page you were looking for.
    
2. Check for errors in the URL. Often times the 404 Not Found error appears because the URL was typed wrong or the link that was clicked on points to the wrong URL.
    
3. Move up one directory level at a time in the URL until you find something.
   
   For example, if www.web.com/a/b/c.htm gave you the 404 Not Found error, move up to www.web.com/a/b/. If you get nothing here (or an error), move up to www.web.com/a/. This should lead you toward what you're looking for or at least confirm that it's no longer available.
   
   Tip: If you have moved all the way up to the website's homepage, try to run a search for the information you're looking for. If the site doesn't have a search function, try navigating to the page you want using category links to dig deeper into the site.
    
4. Search for the page at a popular search engine. It's possible that you simply have the entirely wrong URL in which case a quick Google or Bing search should get you where you want to go.
   
   If you do find the page you were after, update your bookmark or favorite to avoid the HTTP 404 error in the future.
    
5. Clear your browser's cache if you have any indication that the 404 Not Found message might just be yours. For example, if you can reach the URL from your phone but not from your tablet, clearing the cache on your tablet's browser might help.
   
   You might also consider clearing your browser's cookies, or at least the one(s) involved with the website in question, if clearing the cache didn't work.
    
6. Change the DNS servers used by your computer but usually only if an entire website is giving you a 404 error, especially if the website is available to those on other networks (e.g. your mobile phone network or a friend in another city).
   
   404's on an entire website isn't particularly common unless your ISP or government filters/censors websites. No matter the reason, if it does happen, giving another set of DNS servers a try is a good step to take. See my Public DNS Servers List for some alternatives.
    
7. Finally, if all else fails, contact the website directly. If they've removed the page you're after then the 404 error is completely legitimate and they should be able to tell you that. If they've moved the page, and are generating 404's instead of redirecting visitors to the new page, they might be very happy to hear from you.
   
   A WHOIS search, using the site's domain name (e.g. weather.com) as your search term, should give you some contact information.