User:ItsCrocoSwine/3DS Error toolkit

Key information

This page lists possible causes and fixes of Luma3DS exception screens, ErrDisp screens, stock error codes, and bootROM errors. They are not applicable to every situation, but cover most common known issues.

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.

On both stock and custom firmware, apps can cause error codes if they run into a non-fatal issue.
In the below tables, error codes are separated into sets by their section (e.g. 007-XXXX) and then sorted within their sets in ascending order by their result code (e.g. XXX-2001).

Not all 3DS error codes are known or understood, and it is unlikely all codes will ever be documented in full due to Nintendo failing to document many of them.

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.

Known errors

---

Arm9Arm11ErrDispError codesBootROM

Error On Boot

Exception Type	Problem & Solution
Any	Files on the SD are corrupted. To fix, verify that your SD card is not faulty. If it is verified working, make a backup of all intact files, format the SD card, and try booting again.
	A system save located on the NAND in [1:]/data has a problem.
	System-unique files are missing from the NAND in [1:]/rw/sys.
data abort	The shared2 folder in [2:] SYSNAND TWLN is missing. To fix, create this folder.
	System titles have been deleted. To fix, perform a Safe Mode update. If this does not work, perform a CTRTransfer.
prefetch abort (kernel panic)	The console likely has a hardware issue.
prefetch abort (svcBreak)	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.
	If none of the above fixes worked, perform a Manual CTRTransfer.
undefined instruction	The console likely has a hardware issue, or corrupted sysmodules. Try performing a CTRTransfer to see if it resolves the issue.

Error During Use

Exception Type	Problem & Solution
data abort	Files on the SD are corrupted. To fix, verify that the SD card is not faulty. If it is verified working, make a backup of all intact files, format the SD card, and try again.

Error On Boot

Current Process	Exception Type	Problem & Solution
gsp/i2c/mcu/pxi/spi	any	The console has a serious hardware issue that is likely not easily fixable. Run 3ds_hw_test. If the test returns zero errors detected, join the Nintendo Homebrew Discord and ask, in English, for help.
act	any	Your NNID(s)' stored data is misconfigured or being interfered with. To fix, if Pretendo is installed, turn it off by disabling Enable loading external FIRMs and modules on the Luma3DS configuration menu. If this does not help or Pretendo is not installed, then restore a NAND backup - especially if you recently tried to log out an NNID.
boss	data abort	Outdated firmware (11.16 or older): The current firmware version may be too old for SpotPass to work. Perform a Safe Mode update. If this does not work, you may require a CTRTransfer. Latest firmware (11.17): An outdated installation of NetPass is likely interfering with your console. To check this, do the following steps: Hold SELECT while powering on the console Within the Luma3DS configuration menu, disable Enable loading external FIRMs and modules Either press START or press A on the Save and exit option to save changes and exit the configuration menu If the issue stops after this, update Netpass via Universal-Updater (recommended) or go to the NetPass Website and follow the instructions there. Then, boot NetPass to update the patches. If this does not help, join the Nintendo Homebrew Discord or the NetPass Discord and ask, in english, for help.
camera	any	Potential hardware issues, or an instance of ShutTheCamUp is crashing. Look for and delete /luma/sysmodules/0004013000001602.ips and /luma/titles/0004013000001602/code.ips. If this fixed the issue, then update Luma3DS and reinstall the correct Old or New 3DS patch for ShutTheCamUp if you wish to continue using it. If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the Nintendo Homebrew Discord and ask, in English, for help.
cfg	any	Either the NAND config savegame or part of your console-unique file(s) is damaged. To fix, first boot into GodMode9, press R+A while the cursor is on the folder [1:]/data/<ID0>/sysdata/00010017, choose to Copy to 0:/gm9/out, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue. If this does not help, delete the newly created 00010017 and copy the backup into its place, run 3DS:ctrcheck, and replace any console-unique files marked as invalid or missing with the copies from the essentials.exefs backup inside [S:] SYSNAND VIRTUAL in GodMode9.
fs	any	Can be anything from SD card problems to hardware issues. Fault isolation will likely be required to find the true cause of this error. Start by doing ctrcheck and trying to trigger the error with the SD card removed from the console. If the error stops when the SD card is removed, reformat the SD card, and if that doesn't help, test it for hardware damage.
hid	any	Either an instance of rehid is crashing, or your console may have hardware damage. First look for and delete /luma/titles/0004013000001D02, /luma/titles/0004013000003302, /luma/sysmodules/0004013000001D02.cxi and /luma/sysmodules/0004013000003302.ips. If this fixed the issue, then update Luma3DS and reinstall the latest release of rehid to continue using it. If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. 3ds_hw_test or ctrcheck may help with fault isolation.
loader	prefetch abort (svcBreak)	The code or sysmodule patch Luma3DS tried to load is invalid or corrupt. To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in /luma/titles or /luma/sysmodules.) Alternatively, you may disable loading external FIRMs and modules as well as Enable game patching in the Luma3DS configuration menu.
menu	data abort	Broken HOME Menu theme. To fix, go into the folder sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/ and delete the folder matching your region, one of the following: USA: 000002cd EUR: 000002ce JPN: 000002cc
		Broken HOME Menu extra data. To fix, go into the folder sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/ and delete the folder matching your region, one of the following: USA: 0000008f EUR: 00000098 JPN: 00000082 KOR: 000000A9
		Broken HOME Menu application. 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, follow the directions on this page. If this occurs on boot, set Hbmenu autoboot in the Luma3DS configuration menu to 3DS, then follow the above instructions and turn Hbmenu autoboot back off once it has been removed. Ensure in sd:/luma/config.ini that hbldr_3dsx_titleid is set to 000400000d921e00 and boot.3dsx is in the root.
	prefetch abort (svcBreak)	If R5 contains D900458B: 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.
		System titles are missing. Perform a Safe Mode update. If you have a recent NAND backup, you could try restoring it instead with this guide
mset	any	System Settings is broken in some way - this may indicate that the console has a hardware issue. To fix, perform a CTRTransfer, or a Manual CTRTransfer if that does not work. If neither of these work, the console has a serious issue. Join the Nintendo Homebrew Discord and ask, in English, for help.
ns	prefetch abort (svcBreak)	The Luma3DS configuration setting Hbmenu autoboot is set to boot to a title that does not exist. To fix, disable the option, install an application with the title ID in sd:/luma/config.ini, or change the set title ID to match an application that does exist.
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 using an external switch. New models do not have this switch 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. To fix, update CFW.

Error During Use

Current Process	Exception Type	Problem & Solution
3dsx_app	any	The .3dsx file that was most recently opened is corrupted. To fix, download a new copy of the .3dsx file. If this error happens when opening the Homebrew Launcher, download a new copy of boot.3dsx. If the error still happens, test the SD card for errors.
app CtrApp (any 3DS title)	prefetch abort (svcbreak)	The app most recently opened is out-of-region and relies on locale-specific data. Activate locale emulation for it.
	any	The app you most recently opened is attempting to load corrupt code, instructions, or patches. As this type of error can happen to nearly anything on the console, if your listed current process does not show up anywhere else under Arm11, it may help to follow these instructions anyway. First, turn off all game mods, cheat codes, plugins, and both the settings Game patching and loading external FIRMs and modules in the Luma3DS configuration menu to stop all external interference. If this fixes the issue, redownload all of those types of patches that you had enabled for the game(s) before turning them back on. If it does not fix the issue, check whether the game is the same region as the console and activate locale emulation if it is not. If the error continues after trying all of the above, 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.
cam qtm	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.
fs	any	Could be an SD card problem, minor NAND problem, hardware issue, or anything in between. fault isolation will likely be required to find the true cause of this error. Start by doing ctrcheck and trying to recreate the error without the SD card inserted. If the error stops after the SD card is removed, reformat the SD card, and if that doesn't help, test it for hardware damage.
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.
loader	undefined instruction	The app most recently opened is trying to load invalid, missing, or corrupt data. If the value of R0 starts with C or D, it is an error code, and has a chance of being an error code if the value starts with E or F. A large number of such error codes can be found at this page, but here are the most common values seen in this error: D9004587: When trying to open a game: The game is corrupted, or its seed is not imported. To fix: Follow the corrupted games guide C8804478: If trying to open the Homebrew Launcher: boot.3dsx is missing from the root of your SD card. To fix: Download the latest Homebrew Launcher from here C88044AB: If trying to open the Homebrew Launcher: Your SD card either is not properly inserted, or cannot be read by the console. To fix: Try to reinsert the SD more firmly, and check whether its data can be read on boot. If it can't, then reformat the SD. D96077FA/FFFFFFFF: The .3dsx that Luma3DS tried to load is corrupted. To fix, redownload the app you are trying to launch. If this happens when you try to open the Homebrew Launcher itself, see the error above. Most of the other possible error codes that can appear here are listed on the ErrDisp page.
	prefetch abort (svcBreak)	The LayeredFS or sysmodule patch Luma3DS tried to load is invalid or corrupt. To fix: Re-download any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in /luma/titles or /luma/sysmodules.) Alternatively, you may disable loading external FIRMs and modules as well as Enable game patching in the Luma3DS configuration menu.
mset	any	If not occurring in Nintendo DS Profile: System Settings is broken in some way - this may indicate that the console has a hardware issue. To fix, perform a CTRTransfer, or a Manual CTRTransfer if that does not work. If neither of these work, the console has a serious issue. Join the Nintendo Homebrew Discord and ask, in English, for help. If occurring in Nintendo DS Profile: Your NVRAM either is corrupted or is suffering from hardware damage. Run ctrcheck - if its results do not include Critical: NVRAM is inaccessible, then follow the Fix NVRAM guide.
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	any	The software you have launched may be missing required files. If the value in R0 is E0E01BF5, this is extremely likely to be the cause.
pxi	any	Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.
swkbd	any	The software keyboard is broken in some way - this may indicate that the console has a hardware issue. To fix, perform a CTRTransfer, or a Manual CTRTransfer if that does not work. If neither of these work, the console has a serious issue. Join the Nintendo Homebrew Discord and ask, in English, for help.

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: mcu	Some piece(s) of hardware related to power or the battery is damaged. First, check if your console's charging LED (the orange one) repeatedly turns on and off on its own while a cable is inserted. If it does, this is a sign of a faulty charger port, which may be contributing to the errors and should be fixed before any other troubleshooting. Once the charger port is verified intact, any other causes are likely deeper within the motherboard. Dissassembling and carefully analyzing the console will likely be necessary to find these issues, and even then, they may not be practical to fix.
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.

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.
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 are specifically getting 0xc8804471 when opening an out-of-region game, it means it needs locale emulation to function properly. 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.
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, Lazarus3DS, or the nim module errors, 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.
0xC8A04573	Your SD card is formatted strangely. To fix, reformat the SD card. If this does not work, test the SD card for errors.
0xC8A0802B	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. rebuild title.db and then try again. Open GodMode9, go into the file path [A:] SYSNAND SD/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.
0xC8A11BEF	Occurs when attempting to use DLP services with an out-of-region game. This issue is not fixable currently.
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 is happening when launching a cartridge, especially if the error code is 0xC960454?, delete any updates or DLC to see if the cartridge works as they could be corrupt or faulty. If this succeeds, reinstall them from eShop and ensure the cartridge still works. 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.
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.
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.
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.

Error Codes

001 - Online Services
0102	Unexpected disconnection from network services.	Nintendo Support Page
0112	Friends server connection timed out.	Nintendo Support Page
0302	Unable to connect to the server.
0502	Cannot connect to online services, or unexpectedly disconnected from them.
0718	The Friends List is already full.
0720	Generic error code.
0721	Online access is restricted by Parental Controls.
0724	Your Personal Mii is missing.
0725	Your ability to register friends is restricted by Parental Controls.
0726	Your notification settings for the Friends List are not yet configured.
0803	Cannot connect to authentication servers.	Server Status and Maintenance
0811	Online play servers under maintenance.	Server Status and Maintenance
002 - Account Related Errors
0100	The online service is unavailable.
0101	Network has high traffic or is down.
0102	Account permanently banned.
0107	Account temporarily banned.
0109	Possible corrupted data.
0110	The online service is no longer available.
0111	The online service is unavailable.
0119	Friend module outdated, system update required.
0120	This game/title is outdated, and must be updated before use.
0121	Invalid LocalFriendCodeSeed SEED signature - the file is possibly modified.
0123	This specific game cartridge is banned from online play.
3503	Service under maintenance.
34xx	Server returned a 4xx HTTP error.	Server Status and Maintenance
35xx	Server returned a 5xx HTTP error.	Server Status and Maintenance
003 - Network Connection Errors
0200	Wireless connections are disabled.
0299	Wireless connections are disabled.
0300	The EULA for your region has not been accepted.
0399	The accepted EULA version is too low.
0400	Your ability to do this is restricted by Parental Controls.
1000	No Access Point found.
1004	No Access Point found with USB Connector.
1099	Could not find an Access Point with the entered SSID.	Nintendo Support Page
1100	The encryption key is incorrect.
1101	Access Point password incorrect or it has a incompatible configuration.
1102	Unable to connect to Access Point due to incorrect Security Setting.
1104	Unable to connect to Access Point with USB Connector.
1200	Connection refused, as it would give this device the same IP address as another device in the network.
1300	Incorrect Access Point configuration.
1400	Incorrect security key.
1402	Unable to connect to the internet with this Access Point.
2000	Incorrect security key or DNS.
2001	DNS resolution error. If you are using a custom DNS server, recheck its settings.
2100	Network may be busy or have other connection problems.
2200	Unable to connect to the Proxy Server.
3000	There was an issue with authentication.
3305	This service is not available in your location.
3405	Generic communication error.
4000	Generic communication error.
4100	Generic communication error.
005 - Network Installation Management
2008	eShop download failed or the title's ticket is invalid. Delete the ticket in FBI and install it from a legitimate source like the eShop or (if it's a cart dump) from the game's cartridge.	Nintendo Support Page
2037	The server is undergoing maintenance.
2038	A system update is required to use this service.
2043	A system update is required to use this service.
2056	Not enough space on the SD Card.
2061	Unable to access the SD Card.
2062	Not enough space in the System Memory.
2068	The server is undergoing maintenance.
2069	The software is corrupted.
4017	This activation code is not recognized.
4040	eShop connection timeout.	Nintendo Support Page
4069	eShop is unavailable. If the issue persists, the SD might need to be replaced.	Nintendo Support Page
4240	Cannot connect to eShop servers.	Nintendo Support Page
4305	Generic connection timeout error, could also mean that you are unable to download software from the eShop.	Nintendo Support Page
4320	Generic error, only displays when formatting the console or performing a system transfer.	Nintendo Support Page
5403	Transfers are currently prohibited.
5404	The transfer limit has been reached.
5542	Maximum Funds reached.
5546	Unable to purchase more items.
5568	This activation code cannot be used with your account.
5593	Unable to transfer specific software.
5602	eShop title(s) from another region are linked to this console. This is caused by a region change.
5644	Unable to use this credit card with this specific system.
5670	You are unable to view your account's activity at this time.
5687	Generic eShop connection issue error.	Nintendo Support Page
5704	Generic eShop connection issue error.	Nintendo Support Page
5804	This number has expired.
5811	This activation code has expired.
5815	This activation code has already been used.
5941	The entered login details are incorrect.
5942	Name was not registered due to a connection error.
5948	Your eShop funds are already over the maximum value.
5958	Unknown eShop error, usually seen on region-changed consoles.
5964	Your NNID is banned from accessing the eShop. Contact Nintendo Support if this is a mistake.
5989	You cannot link your Club Nintendo account to more than eight Nintendo 3DS systems.
6402	The entered login details are incorrect.
6403	Unable to register the entered username.
6499	The Club Nintendo servers are undergoing maintenance, so your name couldn't be registered.
6501	This credit card cannot be used.
6503	The entered credit card number is incorrect.
6504	You must enter the three-digit security code.
6507	The entered credit card details are incorrect.
6511	This credit card cannot be used.
6514	The entered expiry date for this credit card is incorrect.
6519	The entered address does not match the credit card's billing address.
7545	eShop is unavailable. If the issue persists, the SD might need to be replaced.	Nintendo Support Page
7550	eShop is unavailable. If the issue persists, the SD might need to be replaced.	Nintendo Support Page
8025	eShop is unavailable. If the issue persists, the SD might need to be replaced.	Nintendo Support Page
8026	eShop is unavailable. If the issue persists, the SD might need to be replaced.	Nintendo Support Page
8029	eShop is unavailable. If the issue persists, the SD might need to be replaced.	Nintendo Support Page
006 - Matchmaking Errors
0102 - 0111	Application errors.	Pretendo Documentation
0112	Connection timed out.	Pretendo Documentation
0113 - 0116	Application errors.	Pretendo Documentation
0301	Connection could not be established.	Pretendo Documentation
0302	Authentication failed.	Pretendo Documentation
0303 - 0311	Application/Server Communication Errors.	Pretendo Documentation
0329	The server is undergoing maintenance.
0332	Closed ports while attempting matchmaking.
0347	This online service is discontinued.
0501	May indicate that the network is blocking traffic necessary for Online Play.	Nintendo Support Page
0502	May indicate that the network is blocking traffic necessary for Online Play.	Nintendo Support Page
0503 - 0511	Communication Errors.	Pretendo Documentation
0520	Unable to connect to the Internet.
0612	Network is not optimal for peer-to-peer connections, possibly due to your network's NAT type.	Nintendo Support Page
0617	Generic error message.
0620	Generic communication error.
0623	Unable to connect due to outdated software.
0721	Your ability to do online interactions is restricted by Parental Controls.
0800	Unable to connect to authentication servers during the matchmaking process.	Nintendo Support Page
0811	Service unavailable due to maintenance.	Nintendo Support Page
0817	This online service is discontinued.
0899	Unable to connect to authentication servers during the matchmaking process.	Nintendo Support Page
007 - eShop API Errors
0200	Could not access the SD Card.	Nintendo Support Page
1221	The used download code is only redeemable in its relevant software, not in the eShop.	Nintendo Support Page
2001	Error when attempting to access the eShop with a region-changed console. Change back to the original region or restore a NAND backup made before the change to fix.
2100	Connection to eShop timed out, often caused by slow download times.	Nintendo Support Pageor Server Status and Maintenance
2640	Cannot connect to eShop/CDN servers.	Server Status and Maintenance
2670	Error while attempting to connect.	Nintendo Support Page
2705	Cannot connect to Nintendo servers.	Server Status and Maintenance
2720	eShop SSL error.
2913	The server is probably down. Try again later.	Nintendo Support Page
2916	Unknown cause, typically displayed when attempting to download a title from the eShop.	Nintendo Support Page
2920	eShop download failed or invalid title ticket. Delete the ticket in FBI and install it from a legitimate source like the eShop or (if it's a cart dump) from the game's cartridge.	Nintendo Support Page
2924	The language or region setting in your profile (not the same as the console's region) is not supported by the eShop.
3049	The eShop is currently under maintenance.	Server Status and Maintenance
6106	Occurs when attempting to re-download software from the eShop with an invalid or fake ticket active.
009 - eShop Application
1000	A system update required. Check 3DS:Is it safe to update?
1001	The eShop is currently under maintenance.	Server Status and Maintenance
1002	This service cannot be used in your region.
1003	The system's country setting and the eShop's country setting do not match.
1004	The content of this code has already been acquired.
1006	The selected downloadable items cannot be purchased together.
1100	The Add Funds function is not available in your selected region.
1200	This Activation Code has already been used.
1201	The entered code is not recognized.
1202	The entered activation code is not recognized.
1203	This card is not valid on 3DS Systems.
1205	This activation code is not valid in your region.
1206	This code cannot be used here.
1299	The entered number is invalid.
1302	Failed to enter the correct PIN.
1303	Failed to authenticate the stored credit card's information. The information has been deleted.
1304	The entered credit card cannot be used.
1305	Credit card payments cannot be accepted at this time.
1313	The entered address is incorrect.
1350	The entered value exceeds your balance limit.
1351	The balance limit has been reached.
2001	Error when attempting to access the eShop with a region-changed console. Change back to the original region or restore a NAND backup made before the change to fix.
2410	This service has been discontinued.
2705	Often caused by network timing out or losing connection with the eShop.	Nintendo Support Page
2913	eShop or in-game DLC failed to download (or the server is down).	Nintendo Support Page
2916	Unknown cause, typically displayed when attempting to download a title from the eShop.	Nintendo Support Page
2920	eShop download failed or invalid title ticket. Delete the ticket in FBI and install it from a legitimate source like the eShop or (if it's a cart dump) from the game's cartridge.	Nintendo Support Page
2923	Unable to use a function that requires Internet Services.	Nintendo Support Site
2924	Your language or region setting (not console region) is not supported by the eShop.
2995	The used download code is incorrect, not yet activated, expired, entered in the wrong place, or only usable in a different region.	Nintendo Support Site
2996	The item from the entered code is not currently being distributed.
4100	The SD Card's data limit has been reached.
4072	The SD Card may not be inserted.
4074	Could not access the SD Card.
4075	The SD Card's software management data is corrupted.
4077	Download refused due to insufficient space on the SD Card.
4079	Unable to access the SD Card.
4998	The local version of this content is newer than the version you are trying to download. Unknown what causes this.
6106	An AM error occurred in NIM. Likely a bad ticket.
8001	Authentication failed.
8002	The service has expired.
8101	The save data is unusable, as DLC required for it is missing.
8102	Not enough free space to complete this process.
8111	The DLC is corrupted.
8201	Your access to the eShop is restricted by Parental Controls.
8301	The 3DS User Agreement has to be accepted.
8401	Corrupted update data. Delete it and reinstall.
9001	The download was stopped due to low battery.
9002	The entered number is invalid.
9003	The entered Password is invalid.
011 - eShop Site
24xx	Server returned a 4xx HTTP error.	Server Status and Maintenance
25xx	Server returned a 5xx HTTP error.	Server Status and Maintenance
3010	The server timed out due to inactivity.
3021	eShop title not found (wrong region or non-existent).
3136	eShop currently unavailable. Try again later.
5998	eShop is currently under maintenance.	Nintendo Support Page
6901	Console permanently banned (this is always displayed in Japanese).
012 - Old 3DS Browser Errors
1004	The SSL connection failed.
1032	The file cannot be loaded.
1506, 1509 - 1511	Certificate Errors.	Pretendo Documentation
014 - Data Transfer Errors
0013	The System Transfer failed due to an invalid language setting.
0016	The consoles have the same movable.sed. Format the target console and try again.
0062	An error occurred during the System Transfer. Move closer to the router and try again.	Nintendo Support Page
022 - More Account Errors
1001	Unable to find the specified user.
1021	There is no NNID linked to this system.
1022	The entered NNID is already linked to the system.
2452	Tried to access the eShop with UNITINFO patch enabled. Turn this off in Luma's configuration file, sd:/luma/config.ini.
2458	The HTTP client was not authorized to make the request.
2482	The game server requested could not be found.
2484	The game server ID and title ID were not linked, or the request did not send a game server ID.
2501	The entered NNID is already linked to another system. Could be caused by a System Transfer (which transfers all associated NNID's, whether linked or not), restoring the Source System's NAND, and then attempting to use applications that require an NNID.
2502	The NNID can't be used because it does not match the region setting of the system.
2503	The network Service Agreement is not yet accepted.
2511	A System Update is required (displayed by Miiverse).
2512	A software update is required to use this title's online services.
2571	This NNID is already in use.
2572	NNID contains text that can't be used.
2573	The entered password can't be used.
2574	The entered nickname can't be used.
2575	The entered email address is incorrect.
2576	The entered NNID can't be used.
2577	Your password cannot be identical to your NNID.
2578	The entry contains characters that can't be used.
2579	You can't use more than one punctuation character in your NNID.
2580	You can't use punctuation as the first or last character of your NNID.
2581	You can't use more than six numbers in your NNID.
2582	Your entry contains characters that cannot be used.
2583	Your password must contain characters from at least two of the following categories: letters, numbers and punctuation.
2584	You can't use the same character three or more times in a row.
2585	The email address you entered can't be used.
2586	The domain name of the e-mail address you entered may be incorrect.
2587	The NNID you entered already exists.
2591	NNID is already linked to another system. Could be caused by a System Transfer (which transfers all associated NNID's, whether linked or not), restoring the Source System's NAND, and then attempting to use applications that require an NNID.
2592	The limit for linking this NNID has been reached.
2593	The entered NNID cannot be used because it has not yet been confirmed by a parent/guardian.
2594	Parental Controls restrictions must be set up first.
2595	You have not registered a Mii.
2611	The entered password is incorrect.
2612	The entered email address is incorrect.
2613	The entered information is incorrect.
2613	Incorrect email or password when attempting to link an existing NNID. Can also happen if the NNID is already linked to a system, or when attempting to download a title from the eShop without having a linked NNID on the console.
2631	The NNID you are trying to use has been deleted or can't be used for a system transfer. A transferable NNID will only work on the target system.	Nintendo Support Page
2632	The NNID has been changed.
2633	This NNID has been temporarily locked due to too many password attempts. Try again later.
2634	The NNID is not correctly linked to the system. To fix this, follow these steps, reboot the console, and try to sign into the NNID again.	Said Steps
2643	The session has expired.
2662	You can't perform this operation several times in a row.
2672	Use of credit card has been stopped.
2673	The entered credit card cannot be used.
2674	Check the credit card's number and enter it again.
2675	Check the credit card's expiration date and enter it again.
2676	Check the credit card's PIN and enter it again.
2677	The entered information is not correct.
2679	The entered credit card is expired.
2801	Online Services cannot be used.
2802	The entered NNID cannot be used.
2803	Online Services cannot be used.
2812	Console has been permanently banned by Nintendo for playing Pokémon Sun & Moon online before the release date.
2815	Console has been permanently banned from accessing Miiverse by Nintendo.
2881	The server is undergoing maintenance.
2882	This online service has been discontinued.
2884	This online service is not available in your country of residence.
2911	Your ability to do online interactions has been restricted by Parental Controls.
5363	The NNID settings failed to load due to an invalid language setting.
5515	The network timed out.
5531	Cannot connect to account servers.	Server Status and Maintenance
026 - Account/eShop?
24xx	Server returned a 4xx HTTP error.	Server Status and Maintenance
25xx	Server returned a 5xx HTTP error.	Server Status and Maintenance
3221	Failed to unlink the NNID during formatting. Try again.
3278	eShop gift cards cannot be used on the 3DS eShop. Add funds through the website or Nintendo Switch.
032 - New 3DS Browser Errors
1006, 1035	Unable to display the page.
1208	Address not supported.	Nintendo Support Page
1820	The Internet Browser cannot confirm the security of the website. Note that the 3DS Internet Browser is fairly old and does not contain certificates for certain issuers, namely Let's Encrypt, so it may show this issue for some websites that work fine on a modern device.
090 - In-Game Specific Errors
0212	The game is permanently banned from Pokémon Global Link for using altered or illegal save data.

BootROM

Error	Description
00F800FE 00000000 00000000 00000200 00000000	Error when having SD-card reader connected to NAND during boot.
00F800FE 00000000 00000000 00000400 00000000	NAND not found error (?)
00F800FE FFFFFFFF FFFFFFFF 00000080 00800000	NAND error when DAT1 was used as DAT0.
00F800FE FFFFFFFF FFFFFFFF 00000005 00800000	NAND error when DAT2 was used as DAT0.
00F800FE FFFFFFFF FFFFFFFF 00000005 00000000	NAND error when DAT3 was used as DAT0.
00F800FF F8F8FFFF FFFFFFFF 00000000 00000000	Both the firm0 and firm1 partitions are corrupt (failed signature checks).
00F800FF DEDEFFFF FFFFFFFF 00000000 00000000	Both the firm0 and firm1 partitions are corrupt (possibly related to certain flags missing?)
00F800FF CFCFFFFF FFFFFFFF 00000000 00000000	Both the firm0 and firm1 partitions are corrupt
00F800EE FFFFFFFF FFFFFFFF 00000000 00000000	NCSD header in sector 0 is corrupt (failed signature check).

Reading error screens

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 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 more often related to broken software or user data.
• Exception type: The type of fault that caused the exception. These categories correspond to the ARM exceptions for the ARM9 and ARM11 CPUs, as follows:
  • 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: Caused by an attempt to execute a CPU instruction that was marked as invalid. Often related to conflicts between CFW and other software.
  • prefetch abort (kernel panic): Caused by Kernel9 detecting an unrecoverable error and forcibly halting to avoid causing damage. Can be related to any of several things, but hardware issues are the most likely.
  • prefetch abort (svcBreak): Caused by either Process9 or homebrew software manually halting because it tripped a pre-defined error condition. Often related to damage to NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't locale emulated.
  • undefined instruction: Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software missing its required files (if not on boot) or an outdated boot.firm (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.
  • loader: The service that opens apps, meaning the app most recently opened has an issue.
  • menu: Data that is opened either as a part of the HOME Menu or at the same time as it.
  • ns: The Nintendo User Interface Shell, which handles all apps/processes/services in 3DS mode.
  • nwm: Networking services, almost always Wi-Fi.
• Registers (R0-R12/SP/LR/PC/CPSR/FPEXC): Usually just internal data that's not worth reading, though R0 is the most likely of them to contain useful data. There are certain notable exceptions that aren't mentioned in the list of known errors, however:
  • If the value 000400?? (the ? marks can be any number) appears in any of the registers, it likely refers to the first half of a title ID - check the value of the register after it to ensure this. If it is a title ID, it can be used to narrow down the original cause of an error.
  • If the value of any register starts with the letter C, D, E, or F (even if it isn't in R0) and doesn't look completely random, it may be an error code - this is more likely if the value starts with C or D. You may want to check it manually, as if it is an error code, it can likely help in troubleshooting.

Reading a Luma3DS ErrDisp

A Luma3DS 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.

Reading an error code

An error code has two parts - the code itself, and its official description.

For this page, only the code matters

Reading boot9strap LED status codes

Booting your console while holding X+START+SELECT, or if either FIRM file is corrupt, the notification LED will display a color indicating the status of the FIRMs located at sdmc:/boot.firm and nand:/boot.firm. Refer to the following table for their status:

Color	SD FIRM	CTRNAND FIRM
Green	Loaded	-
Yellow	Missing	Loaded
Orange	Corrupt	Loaded
White	Missing	Missing
Magenta	Missing	Corrupt
Red	Corrupt	Corrupt/Missing

In addition, the LED will blink if booting from ntrboot
NOTE: A red LED status can also occur if the NAND firm is missing rather than corrupt.

Sources

3DS:Error codes
3DS:Error screens/Luma3DS exception screen
3DS:Error screens/Luma3DS ErrDisp
3DS:Boot9strap
boot9strap GitHub
3dbrew:Bootloader

This page is up to date as of 04:08, 12 July 2024 (UTC)