< 3DS:Error screens
Revision as of 08:31, 25 September 2022 by Gruetzig (talk | contribs) (experienced that issue, and helpees had it too, removing the folder fixes it, so i guess its related to that)
This page lists possible causes of Luma3DS exception screens. They might not be applicable to every situation.
Arm9
On boot
- Files on the SD are corrupted.
- A system save inside
1:/data
has a problem. - Files in
1:/rw/sys
are missing.
Prefetch abort (svcBreak)
1:/private/movable.sed
is only 288 bytes, but its flag indicates otherwise.- SYSNAND CTRNAND has bad CMACs.
Data abort
- The
2:/shared2
folder is missing.
During use
- Files on the SD are corrupted.
Arm11
On boot
boss (0004013000003402), data abort
- Firmware version is too old to handle SpotPass. Perform a safe mode update.
fs (0000000000000000)
- Can be anything from SD card problems to hardware issues.
hid (0004013000001D02)
- Potential hardware problems.
- Broken HOME Menu theme.
- Broken HOME Menu extra data.
- Broken HOME Menu application.
- Broken f000000b folder in CTRNAND.
pm (0000000000000000), undefined instruction
- Outdated Luma3DS that does not support the current firmware version.
During use
loader (0000000000000000)
If the hexadecimal number next to R0 starts with 'C' or 'D', search for it in 3DS:Error_screens/Luma3DS_ErrDisp.