Approver, confirmaccount
398
edits
3DS:Error screens/Luma3DS exception screen (view source)
Revision as of 03:55, 24 November 2022
, 2 years agominor wording fixes. also, i know my info's not perfect here, i just can't tell what parts are wrong. so, uh, have fun fixing my mistakes? i guess?
StarlitSkies (talk | contribs) (insert exception pic and how to read it - page WIP removed, and now i'm going to figure out how to overhaul the formatting of this page. i'll be back with that in a few days lmao) |
StarlitSkies (talk | contribs) m (minor wording fixes. also, i know my info's not perfect here, i just can't tell what parts are wrong. so, uh, have fun fixing my mistakes? i guess?) |
||
| Line 1: | Line 1: | ||
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues. | This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues. | ||
==Reading a Luma3DS exception screen== | ==Reading a Luma3DS exception screen== | ||
A Luma3DS exception has | A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows: | ||
[[File:Luma3DS_exception.png|center]] | [[File:Luma3DS_exception.png|center]] | ||
* '''Processor:''' What part of the system is causing the exception. The two processors are: | * '''Processor:''' What part of the system is causing the exception. The two processors are: | ||
**'''Arm9:''' The 'security processor' of the system. These exceptions usually result from errors in NAND data or hardware faults in either the 3DS or its SD. | **'''Arm9:''' The 'security processor' of the system. These exceptions usually result from errors in NAND data or hardware faults in either the 3DS or its SD. | ||
**'''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are often related to broken software or user data. | **'''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are often related to broken software or user data. | ||
* '''Exception type:''' How the system is causing the exception. These are often too broad | * '''Exception type:''' How the system is causing the exception. These categories are often too broad to be helpful, but three of them are more precise: | ||
**'''data abort''': Oftentimes related to a broken mod or broken HOME Menu data. Occasionally related to custom firmware data being broken. | **'''data abort''': Oftentimes related to a broken mod or broken HOME Menu data. Occasionally related to custom firmware data being broken. | ||
**'''prefetch abort (svcBreak)''': Oftentimes an issue with data on the NAND, even when Arm11. Can also happen when launching an out-of-region game. | **'''prefetch abort (svcBreak)''': Oftentimes an issue with data on the NAND, even when Arm11. Can also happen when launching an out-of-region game. | ||
**'''undefined instruction''': Usually either a broken piece of software (if not on boot) or outdated <code>boot.firm</code> (if on boot). | **'''undefined instruction''': Usually either a broken piece of software (if not on boot) or outdated <code>boot.firm</code> (if on boot). | ||
*'''Fault status:''' Why the system is causing the exception. Normally not helpful for | *'''Fault status:''' Why the system is causing the exception. Normally not helpful except for developers. | ||
*'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Common or unique processes are as follows: | *'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Common or unique processes are as follows: | ||
**'''hid''': Potential hardware problems. | **'''hid''': Potential hardware problems. | ||
| Line 19: | Line 19: | ||
*'''R0''': Usually just internal data that's not worth reading. There are two notable exceptions, however: | *'''R0''': Usually just internal data that's not worth reading. There are two notable exceptions, however: | ||
**'''Arm11 loader exception''': If R0's contents start with a C or D, R0 is an error code. This code usually gives the exact cause of the issue. | **'''Arm11 loader exception''': If R0's contents start with a C or D, R0 is an error code. This code usually gives the exact cause of the issue. | ||
**'''Arm11 pm exception''': If R0's contents are <code>E0E01BF5</code>, <code>boot.firm</code> is too outdated to work. | **'''Arm11 pm exception''': If R0's contents are <code>E0E01BF5</code>, <code>boot.firm</code> is guaranteed to be too outdated to work. | ||
==Known Errors== | ==Known Errors== | ||