3DS:Error screens/Luma3DS exception screen: Difference between revisions

Line 5:

[[File:Luma3DS_exception.png|center]]

* '''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 card.

**'''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.

**'''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 more often related to broken software or user data.

* '''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~~:

* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [ARM9 https://developer.arm.com/documentation/ddi0201/d] and [ARM11 https://developer.arm.com/documentation/ddi0360/f) CPUs, as follows:

**'''data abort''': ~~Oftentimes~~ related to ~~a broken mod or~~ broken HOME Menu data. ~~Occasionally~~ related to ~~custom firmware data being broken~~.

**'''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.

**'''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''': Caused by an attempt to execute an invalid CPU instruction. Often related to conflicts between CFW and other software.

**'''undefined instruction''': ~~Usually either~~ a ~~broken piece of~~ software (if not on boot) or outdated <code>boot.firm</code> (if on boot).

**'''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually terminating code because it matched a pre-defined condition. Often related to errors in NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]

*'''Fault status:''' ~~Why the system is causing the~~ exception. ~~Normally~~ not ~~helpful except~~ for ~~developers~~.

**'''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable fatal error and forcibly shutting down to avoid damage. Can be related to any of several things, but hardware issues are the most likely.

**'''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software not having the required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).

*'''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.

*'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:

**'''fs''': The filesystem, i.e. either the SD card or the NAND.

Line 132:

Line 134:

<h5>app/CtrApp</h5>

* The app you last opened is trying to use broken software.

* If not <code>prefetch abort (svcBreak)</code>: The app you last opened is trying to use broken software.

** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.

**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

* If <code>prefetch abort (svcBreak)</code>: The app you are trying to open is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>

Line 147:

Line 150:

<h5>Kujira/Joker/niji_loc</h5>

* The app you last opened has an issue of some kind.

** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|~~force~~ the game ~~to use the correct region~~.]]

** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]

*** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

@@ Line 5: / Line 5: @@
 [[File:Luma3DS_exception.png|center]]
 * '''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 card.
+**'''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
-**'''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 more often related to broken software or user data.
-* '''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:
+* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [ARM9 https://developer.arm.com/documentation/ddi0201/d] and [ARM11 https://developer.arm.com/documentation/ddi0360/f) CPUs, as follows:
-**'''data abort''': Oftentimes related to a broken mod or broken HOME Menu data. Occasionally related to custom firmware data being broken.
+**'''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
-**'''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''': Caused by an attempt to execute an invalid CPU instruction. Often related to conflicts between CFW and other software.
-**'''undefined instruction''': Usually either a broken piece of software (if not on boot) or outdated <code>boot.firm</code> (if on boot).
+**'''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually terminating code because it matched a pre-defined condition. Often related to errors in NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
-*'''Fault status:''' Why the system is causing the exception. Normally not helpful except for developers.
+**'''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable fatal error and forcibly shutting down to avoid damage. Can be related to any of several things, but hardware issues are the most likely.
+**'''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software not having the required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
+*'''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
 *'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
 **'''fs''': The filesystem, i.e. either the SD card or the NAND.
@@ Line 132: / Line 134: @@
 <h5>app/CtrApp</h5>
-* The app you last opened is trying to use broken software.
+* If not <code>prefetch abort (svcBreak)</code>: The app you last opened is trying to use broken software.
 ** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
 **: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
+* If <code>prefetch abort (svcBreak)</code>: The app you are trying to open is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.
 <h5>GARDEN</h5>
@@ Line 147: / Line 150: @@
 <h5>Kujira/Joker/niji_loc</h5>
 * The app you last opened has an issue of some kind.
-** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|force the game to use the correct region.]]
+** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]
 *** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.