This page lists possible causes and fixes of Luma3DS exception screens, and Luma3DS ErrDisp screens. They are not applicable to every situation, but cover most common known issues.
Known errors
In the following lists, the file prefixes on file paths refer to the starting location. sd:/ refers to the SD card, and numbers in the format of [X:] refer to GodMode9's drive numbers.
If your ErrDisp displays one of the processes in the first table, you do not need to look up its error code in the second one. The solutions for these processes are almost always the same.
If the below fixes do not solve your issue or you are unsure of what to do, join the [Nintendo Homebrew Discord] for further assistance.
The system movable, [1:]/private/movable.sed, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
To fix, boot into GodMode9 and select SYSNAND CTRNAND, then go into the private folder. Inside this folder, you will see a file named movable.sed. Select it, and under the options menu, select Show in Hexeditor. Green-colored numbers will appear in the middle of the screen - press A and then unlock writing to sysNAND (lvl2). At the beginning of the file, look for the set of numbers 53 45 45 44 00 01. Once you find these numbers, hold A and press D-PAD DOWN while the 01 value is highlighted to change it to 00. Press B, then A, then B to save changes and exit from the hexeditor, then press START to reboot your console.
SYSNAND CTRNAND has bad CMACs.
To fix, press R+A on the SYSNAND CTRNAND drive and Fix CMACs for drive. The console will act like it has been formatted after this, and this is intended.
Potential hardware problems, or an outdated version of Rehid.
First look for and delete /luma/titles/0004013000001D02 and /luma/titles/0004013000003302. If these dont exist, or you've never downloaded Rehid, it's likely hardware issues.
To fix, either perform a Safe Mode update, attempt to enter System Settings before the crash occurs and delete the application in Data Management, or reformat the SD card.
prefetch abort
An installation of menuhax is conflicting with the custom firmware.
To fix, place the menuhax67_installer.3dsx file from [this download] into sd:/3ds, run it through Homebrew Launcher, and choose REMOVE.
prefetch abort (svcBreak)
The f000000b folder in SYSNAND CTRNAND is broken, its exact location being at [1:]/data/<ID0>/extdata/00048000/f000000b.
To fix, backup f000000b by pressing R+A while highlighting it, then selecting Copy to 0:/gm9/out. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
ns
prefetch abort (svcBreak)
The Luma configuration setting Autoboot Homebrew is set to boot to a title that does not exist.
To fix, disable the option or install an application that matches the title ID set in sd:/luma/config.ini.
nwm
any
The WiFi chipset's hardware is damaged or dead.
To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.
pm
undefined instruction
The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are E0E01BF5.
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, perform a CTRTransfer. Otherwise, if it is a 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.
GARDEN
any
Animal Crossing's game data or savedata is having issues.
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 may be faulty. If it is a 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 the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.
fs
any
Can be anything from SD card problems to hardware issues.
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, force the game to use the correct region.
If the error yet still happens, then the game itself is likely faulty. If it is a 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.
loader
undefined instruction
The app you last opened has an issue. If the contents of R0 start with C or D, R0 is an error code.
Most of the possible error codes for this are also listed on this page.
mset
any
System Settings is broken in some way - this may indicate that the console has a hardware issue.
If neither of these work, the console has a serious issue. Join the [Nintendo Homebrew Discord] and ask, in English, for help.
nwm
any
The WiFi chipset's hardware is damaged or dead.
To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.
qtm cam
any
The camera's hardware is damaged or dead.
To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.
ErrDisp
Process Name
Problem & Solution
process: cam process: qtm
Your camera's hardware is damaged or dead.
If the error code is 0xF96183FE, you can open sd:/luma/config.ini and set the variable enable_safe_firm_rosalina to 1 to bypass this error.
Otherwise, to fix, replace the camera with a new one. To avoid the error until then or if you cannot get a new camera, disconnect the camera.
process: kernel
Your system software is having a strange issue.
To fix, diagnose further by reading the contents of the file sd:/luma/errdisp.txt. If you do not understand this file, join the [Nintendo Homebrew Discord] and explain your issue there.
process: nwm
Your WiFi chipset's hardware is damaged or dead.
To fix, replace the WiFi chipset with a new one. To avoid this error until then or if you cannot get a new chipset, disable WiFi on the 3DS and do not turn it back on.
If your 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on may allow you to access Rosalina before it can crash.
process: mcu
Something related to power or the battery is having issues.
To fix, check if your charger repeatedly disconnects and reconnects while it is inserted. If this is the case, you have a faulty charger port and need to replace it.
If this is not the case, you have a deeper hardware issue that may not be fixable.
In the following table, when ? is in an error code, it is a wildcard. This means any character can be in its position and the error code will remain the same.
Error Code
Problem & Solution
card removed
Your SD card is faulty, or debris is interfering with its connection to the 3DS.
To fix, clean the SD card and the SD reader in the 3DS with isopropyl alcohol. If this does not work, test the SD card for errors.
0xC86044D2
Your NAND does not have enough free space available.
To fix, join the [Nintendo Homebrew Discord] and explain your issue in detail. Deleting files from the NAND without guidance is likely to cause additional issues.
0xC8804478
The app you tried to open or system software it relies on is missing.
If this occurs when you open any DS game or DS Download Play, follow TWLFix.
If this occurs after doing a manual CTRTransfer or Lazarus3DS, check in GodMode9 whether the file path 1:/private/movable.sed exists. If it does not, you will need to manually restore movable.sed from a backup. Join the [Nintendo Homebrew Discord] and ask for help with this.
0xC8804464 0xC8804471 0xC8804497 0xC88044A?
Some dependency of the app you are trying to open does not exist.
Ensure your SD is inserted, especially if the code is C88044AB specifically. If it is, ensure you have all of the necessary files for what you are trying to do. If you do have the files and it is happening to a digital title, do a Safe Mode update. If you do have the files and it is happening to a cartridge, either your 3DS or the cartridge likely has a hardware issue.
If this happened while installing an application, your title.db does not exist or is corrupted.
To fix, follow one of the two following sets of instructions. The second one will delete all installed games/apps as a side effect, but is significantly faster and simpler.
Open GodMode9, go into the file path 1:/dbs/ and delete any existing title.db, then press R+Y, choose Create a dummy file, and name this file title.db - leave the file size at 0. Once the file is created, press START to reboot, go into System Settings -> Data Management -> Nintendo 3DS -> Software, and choose Yes if a prompt about management information appears.
0xC92044EB 0xC92044FA 0xC960454?
Your SD card is set to read-only or is faulty.
To fix, make sure the slider on the left side of the SD card is pushed up, use a different SD adapter if you are currently using one, and test the SD for errors if it is not read-only.
If the error still happens, the SD card is likely faulty. If it is also read-only, it has permanently protected itself to prevent data corruption. Either way, back up its contents and get a new SD.
0xD8E0806A
You have developer UNITINFO enabled and are trying to install a retail game.
To fix, go into the file sd:/luma/config.ini and set the variable use_dev_unitinfo to 0.
0xD860446?
You are attempting to use more processing power than the console currently has available.
To fix, ensure you are not using a mod that is designed for an emulator rather than native hardware. If you are using such a mod, either toggle off any "Extra RAM" setting or use a different mod.
0xD900458?
The app you tried to open, its savedata, or an update file for it is corrupted.
To fix, if it is a 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.
0xF9605002
If attempting to use any camera features, your camera hardware is damaged or dead.
Reading a Luma3DS exception screen
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:
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.
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 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.
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 boot.firm (if on boot).
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. Some examples of processes are as follows:
fs: The filesystem, i.e. either the SD card or the NAND.
menu: Data that is opened either as a part of the HOME Menu or at the same time as it.
loader: The service that opens apps, meaning the app you last tried to open has an issue.
nwm: Networking services, almost always WiFi.
ns: The Nintendo User Interface Shell, which handles all apps/processes/services in 3DS mode.
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 pm exception: If R0's contents are E0E01BF5, boot.firm is guaranteed to be too outdated to work.
Reading a Luma3DS ErrDisp
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.
Error code: The specific reason the error occurred. This is almost always the most helpful part of the error.
