Panic

[seriouslyunderappreciated]

What's the issue you encountered?

Panic occurred while running Atmosphere. Title ID: 010041544D530000 ERROR: DABRT (0x101)

How can the issue be reproduced?

I wish I knew how to exactly reproduce the issue, but this crash DID happen under very similar circumstances twice across separate microSD cards, one of which is brand new, and the console was completely formatted (as in fresh sysnand) in between.

When I first opened a game (before it had created the initial save files) and quickly went back to the home menu before it actually had a proper chance to boot (during the very first second of booting the game I pressed the home button and closed it with X) I got the fatal error.

I tried to delete the existing save data after this to recreate the steps that led to the panic, but I can't reliably make it happen. It happened before and again under similar circumstances, but I can't say for sure if it's relevant.

Crash Report

report_d8dcf9dd.zip

System Firmware Version

18.0.1|AMS 1.7.0|E

Environment?

Hekate bootloader, latest official AMS (1.7.0 pre-release), no additional kips or sysmodules.

I have a folder for emuiibo with just amiibo files in it, but the actual emuiibo isn't installed, because I specifically wanted to rule out external causes of crash with a clean install of AMS on a new microSD and an EmuMMC made from a recently formatted SysNAND.

The EmuMMC is partition-based.

Additional Context

I should point out that this doesn't happen every time or even often, but it did happen before on my previous emunand on a previous microSD card, which is why I took steps to rule out culprits by not adding anything to AMS in this particular case.

I never had crashes or errors with AMS before updating from OFW 16.x.x to the latest OFW/AMS.

I do have romFS mods installed for BOTW/TOTK, but they're awfully simple edits I made to some weapons so they don't break by adding an indestructible property to them. Very small files.

I ran the archive bit fix from hekate but it didn't change anything so presumably that has nothing to do with this.

Neither the old 1TB Sandisk nor the brand new 512GB Samsung show damaged sectors, both cards were formatted (FAT32).

I have this on my default.txt hosts file:

127.0.0.1 receive-%.dg.srv.nintendo.net receive-%.er.srv.nintendo.net
127.0.0.1 *nintendo.*
127.0.0.1 *nintendo-europe.com
127.0.0.1 *nintendoswitch.*
95.216.149.205 *conntest.nintendowifi.net
95.216.149.205 *ctest.cdn.nintendo.net

[borntohonk]

When I first opened a game (before it had created the initial save files) and quickly went back to the home menu before it actually had a proper chance to boot (during the very first second of booting the game I pressed the home button and closed it with X) I got the fatal error.

I tried to delete the existing save data after this to recreate the steps that led to the panic, but I can't reliably make it happen. It happened before and again under similar circumstances

So basically, you take an IO hit from running emummc already, and you're trying to start a game, and before the game has started up and made its system save, you force the game into a paused mode by exiting to the home screen, and then you while having done that, close the game, and that forced the panic.

maybe don't do that? (the part where you open the game for barely a second, and then immediately exit to the home screen and closing the game)

[seriouslyunderappreciated]

When I first opened a game (before it had created the initial save files) and quickly went back to the home menu before it actually had a proper chance to boot (during the very first second of booting the game I pressed the home button and closed it with X) I got the fatal error. I tried to delete the existing save data after this to recreate the steps that led to the panic, but I can't reliably make it happen. It happened before and again under similar circumstances

So basically, you take an IO hit from running emummc already, and you're trying to start a game, and before the game has started up and made its system save, you force the game into a paused mode by exiting to the home screen, and then you while having done that, close the game, and that forced the panic.

maybe don't do that? (the part where you open the game for barely a second, and then immediately exit to the home screen and closing the game)

I also had a freeze during normal initial loading before this in my prior microSD. I'm not constantly doing what I described, that was just something I noticed happened twice and across both cards :)

And crucially, I never had any of these problems on prior OFW/AMS.

[masagrator]

maybe don't do that?

I am doing this pretty often and never had issue with it that was related purely to Atmosphere. Only in one case this was causing panic on my Switch - if I have SaltyNX enabled and I am booting Witcher 3. When I exit too fast, it causes fatal. This doesn't occur if SaltyNX is not running.

[seriouslyunderappreciated]

I wish I could say I'm running SaltyNX but no :(