Hello! Are you not able to access the HOME Menu after a long session playing Super Smash Bros 4, or when you made nice progress in Monster Hunter X or Pokemon Sun/Moon/US/UM when you realize this popped up:
"An error has occurred (ErrDisp)
Error type: generic
Proccess ID: 15
Proccess name: menu
Proccess title ID: 0x0004003000000f02 (Smash 4, in this case)
Address: 0x00230c80
Error code: 0xd8c3fbf3
Press any button to reboot"
Or how about you cannot access the HOME Menu at all because of a "logged" error? Well, that may mean the proccess ID described in the error is missing, or it got corrupted! This can happen when you go onto the Rosalina settings and tamper around with the ID, You downloaded Luna3DS or its boot proccess anywhere else other than AuroraWright's official Github, or what I fell to: The mod I was using for a game, froze the system completely and messed up the boot. It happens
Well, you are lucky, because I have a fix for it. The guide is so n00b proof, literally, nobody should come here asking for those issues again. Ready? Here it goes.
1: Go onto AuroraWright's Luma3DS Github page.
2: Download Luma3DS again. Not the updater. (or go to the .zip if you had the download saved)
3: drag the boot file to the root of the SD card. The boot file contains the proccess that you may have missed or that you made corrupt. Overwriting the old boot file with the one you just dragged will restore all proccess IDs, generic or logged.
4: hit the Select button while booting up and select "Show NAND or user string in System Settings" then press start.
Seriously, do not come back here with another ErrDisp issue again. I have provided you a fix for a little while. Go on, play your Smash Bros or Pokemon Sun for now.
"An error has occurred (ErrDisp)
Error type: generic
Proccess ID: 15
Proccess name: menu
Proccess title ID: 0x0004003000000f02 (Smash 4, in this case)
Address: 0x00230c80
Error code: 0xd8c3fbf3
Press any button to reboot"
Or how about you cannot access the HOME Menu at all because of a "logged" error? Well, that may mean the proccess ID described in the error is missing, or it got corrupted! This can happen when you go onto the Rosalina settings and tamper around with the ID, You downloaded Luna3DS or its boot proccess anywhere else other than AuroraWright's official Github, or what I fell to: The mod I was using for a game, froze the system completely and messed up the boot. It happens
Well, you are lucky, because I have a fix for it. The guide is so n00b proof, literally, nobody should come here asking for those issues again. Ready? Here it goes.
1: Go onto AuroraWright's Luma3DS Github page.
2: Download Luma3DS again. Not the updater. (or go to the .zip if you had the download saved)
3: drag the boot file to the root of the SD card. The boot file contains the proccess that you may have missed or that you made corrupt. Overwriting the old boot file with the one you just dragged will restore all proccess IDs, generic or logged.
4: hit the Select button while booting up and select "Show NAND or user string in System Settings" then press start.
Seriously, do not come back here with another ErrDisp issue again. I have provided you a fix for a little while. Go on, play your Smash Bros or Pokemon Sun for now.
Last edited by Inny74,