Error Codes (Xbox)
From Wiki-Scene
|
Error codes appear after the console has run through it's boot sequence, just before the dashboard is loaded. They are located in the top left corner of a screen advising the user that "your xbox requires service".
As a general rule it's just about always possible to fix a console displaying error codes, though the difficulty depends on which code is being displayed. Note that the original 1.0 consoles display the service screen without the error code.
It is recommended to read through all of these regardless of whether your console is functioning correctly or not, if only because you'll know what not to do if you wish to keep it that way.
Of special note in regards to this is error 16. If your console is displaying ANY error code, it is recommended to leave it connected to mains power to prevent an error 16 occuring (Doesn't have to be turned on).
Error 05
HDD not locked
As part of the Xbox security system programmed into the BIOS (Xbox) the console will not boot without a locked hard drive.
Those using a flashed TSOP or a modchip can typically bypass this error code and so use unlocked drives with their system. People without such mods will need to lock the drive using the system's EEPROM data.
Error 06
Unable to access locked HDD
The attached hard drive is locked, but it's using a passcode the system does not recognise. This usually occurs if you try to transfer a locked drive from one console to another, or you've locked the drive manually but using an incorrect passcode.
The only way to bypass an error 06 is to find a way to unlock the drive, either using the EEPROM data from the console it was locked to, or via the master passcode.
Note that once unlocked, the console will revert to an error 05 unless it has a flashed TSOP or a modchip installed.
Error 07
HDD time out
The hard drive is incorrectly connected, or faulty. In many cases reseating the IDE cable is enough to fix the problem.
Faulty DVD drives have been known to cause this error (as they share the IDE cable with the HDD), and in some more serious cases the issue may lay with the Xbox motherboard. You may also see an 07 if your power supply unit is failing (and hence unable to activate the drive).
You can test whether the drive itself is at fault by connecting a different one that you know to be functional. If you don't get an error 07 with that, likely the original drive has given up the ghost.
Error 08
No HDD detected
Very similar to error 07.
Error 09
Invalid HDD parameters
A hard drive is detected, but does not appear to be compatible. A rather uncommon error that sometimes occurs for the reasons listed against error 07.
Error 10
DVD drive time out
The DVD drive is incorrectly connected, or faulty. In many cases reseating the cables connected to the device is enough to fix the problem.
In some more serious cases the issue may lay with the Xbox motherboard. You may also see an 10 if your power supply unit is failing (and hence unable to activate the drive).
You can test whether the drive itself is at fault by connecting a different one that you know to be functional. If you don't get an error 10 with that, likely the original drive has given up the ghost.
Error 11
No DVD drive detected
Very similar to error 10.
Many people disconnect their DVD drive intentionally when hotswapping and then do the switch when this error appears.
Error 12
Invalid DVD drive parameters
A DVD drive is detected, but does not appear to be compatible. A rather uncommon error that sometimes occurs for the reasons listed against error 10.
Error 13
Dashboard launch failure
The hard drive is otherwise readable, but the dashboard is not. 99% of the time this is caused by the dashboard's XBE file being non-existant (for example, the user has deleted it).
Those using a flashed TSOP or a modchip can typically just insert a boot disc such as Slayers or AID and install a new one.
Softmod users will need to repeat the process they originally used to modify the console. Note that the system should still be capable of booting game discs, so if an autoinstaller was used it should be simple to get things up and running again.
Unmodded users (or softmodded users unaware of how their console was originally modified) can attempt to restore the Microsoft Dashboard using the update feature built into most Xbox Live compatible games.
If all else fails, a hotswap can be used to access the drive and repair the damage.
Error 14
Error loading dashboard
Very similar to error 14 though hardly ever seen.
Error 16
Clock cannot be set
The Xbox keeps track of the time while the console is turned off, and even uses a capacitor to hold a backup charge should the mains power be disconnected entirely. However, if the system is unplugged and the capacitor fully drained (a process which takes roughly three hours), the console will forget the time and prompt the user for it on the next startup.
If, however, the console can't access the Microsoft Dashboard in order to do so, the system will display an error 16. Unlike an error 13 it will not boot retail game discs in this state.
Those using a flashed TSOP or a modchip will typically find that their modifed BIOS prevents this error from appearing. The same is also true for newer softmods (which in fact require parts of the MS Dash in order to work), provided they themselves are functioning correctly.
If, on the other hand, the system IS displaying this error, it can be tricky to work out the initial cause (as it over rides any of the other error codes). Most often it is originally due to an error 13 (which is in turn most often due to user error!), and hence fixable using the process of hotswapping to restore a working softmod.
Error 20
The dashboard attempted to load and failed
A very uncommon error, thought to be about equal to error 21.
Error 21
General software malfunction
Perhaps the only error that can be displayed after the dashboard has successfully loaded, this can be roughly described as a "non-specific" crash related to whatever program was running at the time.
Often if a specific program is producing this error on a regular basis, re-copying it or clearing the system's cache files will fix the problem.
For example, if a system boots up to an error 21, make sure the dashboard (and softmod, if you're using one) is correctly installed.
