mario vs donkey kong mini land mayhem crash red screen
Game Console(s) used
- [ ] Nintendo DS
- [ ] Nintendo DS Lite
- [x] Nintendo DSi
- [ ] Nintendo DSi XL/LL
- [ ] Nintendo 3DS
- [ ] Nintendo 3DS XL/LL
- [ ] New Nintendo 3DS XL/LL
- [ ] Nintendo 2DS
- [ ] New Nintendo 2DS XL/LL
Launch Method
Sd card
Version used
v27.16.0 bootstrap 2.7.2
Game tested/used/applicable
mario vs donkey kong mini land mayhem
Expected Behavior
Go to the next screen
Actual Behavior
After completing a level I keep getting a red screen with an error
Steps to reproduce
Just complete a level
nds-bootstrap.ini
[NDS-BOOTSTRAP] DONORTWLONLY0_NDS_PATH = nand:/title/00030005/484e4b50/content/00000002.app USE_ROM_REGION = 1 DEBUG = 0 LOGGING = 0 B4DS_MODE = 0 ROMREAD_LED = 0 DMA_ROMREAD_LED = -1 PRECISE_VOLUME_CONTROL = 0 SDNAND = 0 MACRO_MODE = 0 SLEEP_MODE = 1 SOUND_FREQ = 0 CONSOLE_MODEL = 0 HOTKEY = 284 NDS_PATH = sd:/Roms/NDS/Mario vs. Donkey Kong - Mini-Land Mayhem! (Europe) (En,Fr,De,Es,It) (NDSi Enhanced).nds SAV_PATH = sd:/Roms/NDS/saves/Mario vs. Donkey Kong - Mini-Land Mayhem! (Europe) (En,Fr,De,Es,It) (NDSi Enhanced).sav RAM_DRIVE_PATH = sd:/null.img GUI_LANGUAGE = en LANGUAGE = -1 REGION = 2 DSI_MODE = 1 BOOST_CPU = 1 BOOST_VRAM = 0 CARD_READ_DMA = 0 ASYNC_CARD_READ = 0 DONOR_SDK_VER = 5 PATCH_MPU_REGION = 0 PATCH_MPU_SIZE = 0 FORCE_SLEEP_PATCH = 0 AP_FIX_PATH = HOMEBREW_ARG = APP_PATH = sd:/ROMS/NDS/DRMARI~1.NDS PRV_PATH = sd:/ROMS/NDS/SAVES/ GAME_SOFT_RESET = 1 SAVE_RELOCATION = 1 PHAT_COLORS = 0
Logs
/
Other notes
I only have this issue with the latest updates 27.16.0/2.7.2 and 27.15.1/2.6.2 If I roll back to my old update, 27.13.3/2.4.6 I no longer experience crashes (red screens) in Mario vs. Donkey Kong mini land mayhem.
Will you be available for future issues and/or replies?
Yes
Please test the versions in between 2.4.6 and 2.6.2, and find out which version has introduced the issue.
Strange things, I've tested every update now, and the problem hasn't reoccurred, even with the latest updates. I had already uninstalled Twighlightmenu beforehand, and it still happened. I can't reproduce it either. I'm glad it fixed itself in the meantime.