Difference between revisions of "Fatal Error"
From xboxdevwiki
(Be more precise with HDD and DVD errors) |
(Added note about lack of error code display in kernel 3944) |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
− | These are the errors which will be displayed [[File:Fatal_Error_13.png|300px|thumb|right|Fatal Error 13 being displayed]] | + | These are the errors which will be displayed [[File:Fatal_Error_13.png|300px|thumb|right|Fatal Error 13 being displayed]]. |
+ | |||
+ | Kernel version 3944 is the only known official kernel which doesn't show an error code in the corner{{FIXME|reason=Does it still pulse the hardware pin? does it still set error code in the SMC?}}. | ||
Checked after cold-boot, in this particular order{{FIXME|reason=We should split this into larger blocks, like HDD initalization, DVD initialization, .. and then explain the steps in each}}: | Checked after cold-boot, in this particular order{{FIXME|reason=We should split this into larger blocks, like HDD initalization, DVD initialization, .. and then explain the steps in each}}: | ||
Line 6: | Line 8: | ||
!Value (2 digit decimal) | !Value (2 digit decimal) | ||
!Step / Condition | !Step / Condition | ||
+ | <!-- | ||
+ | |||
+ | IDE / Harddive initialization | ||
+ | |||
+ | --> | ||
|- | |- | ||
|07 | |07 | ||
Line 30: | Line 37: | ||
|08 | |08 | ||
|Setting Harddrive device parameters failed | |Setting Harddrive device parameters failed | ||
+ | <!-- | ||
+ | |||
+ | IDE / DVD Drive initialization | ||
+ | |||
+ | --> | ||
|- | |- | ||
|10 | |10 | ||
Line 42: | Line 54: | ||
|11 | |11 | ||
|DVD Drive ATAPI identify device command failed | |DVD Drive ATAPI identify device command failed | ||
+ | <!-- | ||
+ | |||
+ | XBE Loader | ||
+ | |||
+ | --> | ||
+ | |- | ||
+ | |05 | ||
+ | |Harddrive not locked; Not reported if either: | ||
+ | * XBE is allowed to run from unlocked HDD | ||
+ | * Xbox is in manufacturing region | ||
+ | * Kernel is made for Chihiro | ||
+ | * Kernel is made for XDK | ||
+ | |||
|} | |} | ||
Line 64: | Line 89: | ||
|04 | |04 | ||
|RAM bad | |RAM bad | ||
− | |||
− | |||
− | |||
|- | |- | ||
|13 | |13 |
Latest revision as of 15:24, 2 November 2018
These are the errors which will be displayed .Kernel version 3944 is the only known official kernel which doesn't show an error code in the corner[FIXME].
Checked after cold-boot, in this particular order[FIXME]:
Value (2 digit decimal) | Step / Condition |
---|---|
07 | Harddrive never left busy state (after reset from cold-boot) |
09 | Setting Harddrive PIO mode failed |
09 | Setting Harddrive DMA mode failed |
08 | Harddrive ATA identify device command failed |
09 | Harddrive is too small for cache partitions |
06 | Unable to unlock Harddrive |
08 | Harddrive ATA identify device after unlock command failed |
08 | Setting Harddrive device parameters failed |
10 | DVD Drive never left busy state (after reset from cold-boot) |
12 | Setting DVD Drive PIO mode failed |
12 | Setting DVD Drive DMA mode failed |
11 | DVD Drive ATAPI identify device command failed |
05 | Harddrive not locked; Not reported if either:
|
Additional error codes, or no precise order known[FIXME]:
Value (2 digit decimal) | Generic meaning |
---|---|
00 | No error (used internally to clear error flags from EEPROM) |
01 | |
02 | EEPROM Checksum failure |
03 | |
04 | RAM bad |
13 | Dashboard broken, while Kernel/LaunchDataPage reason == 0 (MainMenu)
|
14 | Dashboard broken, while Kernel/LaunchDataPage reason == 1 (Error)
|
15 | |
16 | Dashboard settings error[citation needed] |
17 | |
18 | |
19 | |
20 | Dashboard failed to launch, but DVD security check was successful |
21 | Used to manually display fatal error after reboot (on purpose) |