Approver
518
edits
User:ItsCrocoSwine/3DS Error toolkit (view source)
Revision as of 08:24, 13 November 2023
, 1 year agoslightliy larger images
m (smaller images) |
m (slightliy larger images) |
||
| Line 1,332: | Line 1,332: | ||
==Reading a Luma3DS exception screen== | ==Reading a Luma3DS exception screen== | ||
[[File:Luma3DS_exception.png|right| | [[File:Luma3DS_exception.png|right|300px]]A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows: | ||
* '''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: | ||
| Line 1,354: | Line 1,354: | ||
==Reading a Luma3DS ErrDisp== | ==Reading a Luma3DS ErrDisp== | ||
[[File:Luma3DS ErrDisp.jpg|right| | [[File:Luma3DS ErrDisp.jpg|right|300px]]With Luma3DS insa ErrDisp error has several parts, but only two of them help in finding its cause. They are as follows: | ||
* '''Process name:''' The part of the system that is triggering the error. Can be helpful if the error code is generic. | * '''Process name:''' The part of the system that is triggering the error. Can be helpful if the error code is generic. | ||
| Line 1,360: | Line 1,360: | ||
== Reading an error code == | == Reading an error code == | ||
[[File:3DS error code.jpg|right| | <span>[[File:3DS error code.jpg|right|300px]]An error code has two parts - the code itself, and its official description.<br> | ||
For this page, only the code matters | For this page, only the code matters</span> | ||
=Sources= | =Sources= | ||