Atmosphere: Bug Report

Created on 21 Dec 2019 · 26Comments · Source: Atmosphere-NX/Atmosphere

What's the issue you encountered?
Atmosphere throws the following error when trying to boot from Hekate and Fusée:

A fatal error occurred when running Atmosphére.
Title ID: 010041544d530000
Error Desc: std::abort() called (0xffe)
[ Did you make any changes related to Atmosphère itself? ]

How can the issue be reproduced?
Boot to RCM
Launch Hekate
Boot Atmosphere through either fusèe-primary or emunand

Crash Report
Not a crash report but a Fatal Error:
https://github.com/jhawNS/66/blob/master/report_0000000005768c98.bin
System Firmware Version
9.1.0

Environment?
Bootloader: Hekate
Release: 0.10.1 (Official)
Additional Kips/Sysmodules: N/A
Homebrew Installed: N/A

Additional context?
This is happening after upgrading from 9.0.0 to 9.1.0 and then updating Atmosphere and Hekate to their latest versions.
I've had a hacked switch for a while now and this is the first time that upgrading has caused an issue.
I tried using hekate archive bit fix 、 fromat FAT32、changed memory card
didn't solve it.

Source

jhawNS

Most helpful comment

This is usually due to an archive metadata bit used by some OS’s that Horizon simply can’t deal with. Here’s how to fix it:

Get your switch in RCM mode.
Inject Hekate payload
Tap on "Tools" on top of the hekate screen.
Tap on "Archive Bit - AutoRCM" on the right bottom.
Tap on "Unset archive bit" button. This might take a while, be patient.

Manuel-Flores-F on 14 May 2020

😄1 👍1

All 26 comments

ams_mitm is throwing an abort. Dupe of #767?

fincs on 21 Dec 2019

ams_mitm is throwing an abort. Dupe of #767?
Different
I stopped while loading the atmosphere
not running games

jhawNS on 21 Dec 2019

I run into the same issue.
Is there any workaround?

webben-de on 21 Dec 2019

Having the same issue here, cant figure out how to fix it, tried the archive bit thing, no luck.
Really don't want to have to resort to empty nand backups.

ObscenityIB on 23 Dec 2019

Same problem here, AMS 0.10 is not running after updating to 9.1.0. Tried with and without Hetake 5.1.1, AMS 0.10.1... same result: black screen after displaying AMS logo : (

OddieBaSs on 23 Dec 2019

@webben-de @OddieBaSs
My solution was clearing out sdmc:/atmosphere/contents/ and replacing ONLY the stock contents and nothing additional.
I don't have any custom themes this time so I'm not sure what the source was.

ObscenityIB on 24 Dec 2019

What the......?

Masamune3210 on 24 Dec 2019

@webben-de @OddieBaSs
My solution was clearing out sdmc:/atmosphere/contents/ and replacing ONLY the stock contents and nothing additional.
I don't have any custom themes this time so I'm not sure what the source was.

I used this solution but it didn't work. :(

jhawNS on 24 Dec 2019

The trick is to run both of the following options. Not just one or the other.

CTCaer on 24 Dec 2019

👍1

The trick is to run both of the following options. Not just one or the other.

tried that, did absolutely nothing for me
this is a strange one, seems to be a different source for everybody but from the same result

ObscenityIB on 26 Dec 2019

If this doesn't fix it, it means that something in the now called contents folder is not compatible.
So step 2 is to delete that folder and put the one from the release manually. But you will probably need to run the archive bit options again after that. (Most OSes add the archive bits when a folder is created).

CTCaer on 26 Dec 2019

The trick is to run both of the following options. Not just one or the other.
I used this solution and replaced this folder "sdmc:/atmosphere/contents/"
but ...

Is there other workaround?

jhawNS on 26 Dec 2019

This console has a corrupted PRODINFO. Somehow the string conUrl": null, is being used as a serial number, which is obviously invalid. This causes an abort early in boot.

Un-corrupt your PRODINFO...?

SciresM on 30 Dec 2019

Feel free to talk to me on discord about wtf is going on with your console.

SciresM on 30 Dec 2019

Feel free to talk to me on discord about wtf is going on with your console.
Thank you,
What is your discord ID?

jhawNS on 30 Dec 2019

SciresM#0524

SciresM on 30 Dec 2019

@SciresM I am having the same error and I am trying to reach out to you on discord.

silentbomber25 on 30 Dec 2019

SciresM#0524

Hey Scires I am having a similar problem i sent you a request on discord if you are able to reach out

WhyNintendo on 29 Feb 2020

Hi SciresM#0524, also having the same problem

A fatal error occurred when running Atmosphère.
Title ID : 010041544D530000"
Error Desc : std::abort() called (0xffe)

Can you hint which things to check to fix this?
i'm also unable to send you a DM in Discord via SciresM#0524.

g2nd on 4 May 2020

Hi SciresM#0524, also having the same problem

A fatal error occurred when running Atmosphère.
Title ID : 010041544D530000"
Error Desc : std::abort() called (0xffe)

Can you hint which things to check to fix this?
i'm also unable to send you a DM in Discord via SciresM#0524.

Fixed it. Reason: updating firmware online changes the filesystem to FAT32. Had to use a FAT32 SD with Atmosphere. Once loaded, used ChoiDujourNX to downgrade back to 10.0.1 in Exfat format.

g2nd on 4 May 2020

ISSUE: Updated NSW to 10.0.2 via the internet

ERROR
A fatal error occurred when running Atmosphère.
Title ID : 010041544D530000"
Error Desc : std::abort() called (0xffe)

REASON: Updating Firmware online changes file system from Exfat to Fat32

SOLUTION:

Use and setup a fat32 SD card containing atmosphere.
Downgrade firmware to 10.0.1 using ChoiDujourNX using Exfat format. (I encountered error updating it to 10.0.2 Exfat so I had to downgrade).
Put back your old Exfat SD card that was working previous to the update.
Update firmware to 10.0.2 using ChoiDujourNX using Exfat format.
Done.

g2nd on 4 May 2020

Likely not an error with atmosphere if you used the online update. For some reason the switch didn't install the exfat fs driver when it updated, which made it fail to boot afterwards. Either install the exfat driver or format to fat32, which is recommended anyway as N's driver is hot garbage

Masamune3210 on 4 May 2020

Any solution?? I have the same fatal error, any channel in discord to fix this? Im Gnzloth#0220

Gnzloth on 9 May 2020

This is usually due to an archive metadata bit used by some OS’s that Horizon simply can’t deal with. Here’s how to fix it:

Manuel-Flores-F on 14 May 2020

😄1 👍1

I'm having this issue on Atmosphere 12, HOS 10.0.0

Did the archive bit fix with Hekate, didn't fix it. Tried an older version of Hekate in case there was some sort of issue with the new "all in one" bit fixer. Still no luck. I'm currently backing up my SD card, and will be formatting to FAT32 (from exFat) to see if that does anything.

Real stumped on this one. I don't recall changing anything, just found my switch in RCM one day and couldn't boot it. Here's the error dump if it helps.

report_0000000005ff1b1f.zip

Edit: Didn't realize this issue was closed, oops.

Anyway, switching to FAT32 worked. Looks like my girlfriend updated to 10.0.2 without realizing it, which is what caused the issue. Because I used ChoiDujourNX to install the ExFat driver, and never accepted the ExFat ToS with Nintendo, they didn't update the switch with ExFat support.