search

Atmosphere-NX / Atmosphere

Atmosphère is a work-in-progress customized firmware for the Nintendo Switch.
GNU General Public License v2.0
15.01k stars 1.24k forks source link

Fatal error ocurred when running Atmosphére #010041544d530000 #813

Closed DreamDevourer closed 4 years ago

DreamDevourer commented 4 years ago

Bug Report [Fatal Error Ocurred when running Atmosphére.]

Title ID: 010041544d530000 Error Desc: std::abort() called (0xffe)

Press POWER to reboot.

What's the issue you encountered?

I was in version 9.0.1, but when I had updated to the 9.1.0 using ChoiDujourNX, the Atmosphere stop working, I formated my SD (from ExFat) to FAT32 but that not worked,I've tried to use chmod and chflags, but nothing works. But the Update was sucessfully, because I tested using sxos, but I prefer Atmosphere...

I not changed anything in the atmosphere folder and a have tried a clean installation with only Atmosphere.

How can the issue be reproduced?

Just injecting the Atmosphere payload 10, 10.1 or 10.2
the issue happens after the White Icon splash screen

Crash Report

Report from fatal_errors folder: https://1drv.ms/u/s!AkqmmjrMDNW3kjBzgA-0J1QUB90x?e=pgxhS3

System Firmware Version

9.1.0 and Atmosphére 10, 10.1 & 10.2

Environment?

Additional context?

When I have tried with clean Atmosphere installation the report was the same, but the some description was in Bold and Yellow.

Ness-666 commented 4 years ago

I am having the exact same issue, the only thing I thing that I can think of is that i had removed my prod.info and since then lost my back up. Not sure if that would effect it though.

SciresM commented 4 years ago

This is a corrupt prodinfo problem -- your PRODINFO somehow has non-ascii characters in the serial number.

This currently isn't supported by Atmosphere.

Manuel-Flores-F commented 4 years ago

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.

Barkermush commented 4 years ago

I'm getting this exact same problem. It was fine until I updated from 10.0.1 to 10.0.2. I updated atmosphere, I've formatted the memory card and tried a clean install but I'm still getting this error.

I think I might have to try a full nand backup too, as I don't seem to be getting anywhere.

SciresM commented 4 years ago

"same problem" probably not. literally any error in ams.mitm generates this symptom to user. Upload your report binary.

Barkermush commented 4 years ago

Ah I never knew that, thanks. I will do that now.

Barkermush commented 4 years ago

"same problem" probably not. literally any error in ams.mitm generates this symptom to user. Upload your report binary.

Sorry to be a pain but do you have a link to something showing how to get the 'binary report' had a look on hekate and can't see anything for that.

The only stuff I can dump to my sd card is 'console info/soc info.. Ipatches & bootrom.. fuses' etc

SciresM commented 4 years ago

When an error occurs, a report is saved in /atmosphere/fatal_errors

Barkermush commented 4 years ago

When an error occurs, a report is saved in /atmosphere/fatal_errors

Thanks. Uploaded the error report below:

Barkermush commented 4 years ago

report_0000000005fb318e.zip

Barkermush commented 4 years ago

When an error occurs, a report is saved in /atmosphere/fatal_errors

Wow, I have managed to sort it. After looking at some other threads, I needed to format the sd card to fat32 (need to download a 3rd party app to do this, as Win10 as no fat32 option)

Never had a problem with atmosphere and exfat from 8.00 patches up until this 10.0.2 patch. This is the first time I have needed to have my sd card in fat32 format.

Ah well, just glad I didn't have to do a full nand :D

yokanes commented 4 years ago

Hi friends! i have the same issue . When the switch forced to update my atmosphere dosent work. I have a micro sdxc 128gb and when i inject the payload of version 0.14.4 of atmosphere, appears this text :

A fatal error ocurred when running atmosphere. itittle ID: 010041544d530000 error desc: std::abort() called (0xffe) Report saved to /atmosphere/fatal_errors/report_00000000559655.bin

Press POWER to reboot.

report_0000000005996855.bin.zip

I though is a problem with my micro sdxc 128 gb and decided bought a new micro sd xc of 256 gb and make the same steps for the new micro sdxc of 256 gb and the same issue appears again. Can u help me?

SciresM commented 4 years ago

@yokanes run the archive bit fixer in hekate.

yokanes commented 4 years ago

How can i run it the archive? i dont know what is hetake , i cant enter on cfw

yokanes commented 4 years ago

100% completed the fixed. Problem solved !!

U are the f***ing master !!

lordelan commented 3 years ago

The archive bit fixer in hekate doesn't do the job for me unfortunately. (finished with total of 0 set/unset) I'm in an emuMMC on 11.0.0 and am getting the same error message as OP. Please let me know what's the problem: reports.zip

lordelan commented 3 years ago

Further info: All I did is install Fizeau (color adjustment homebrew) from the appstore nx. It told me that it needs newest Atmosphère, so I updated Atmosphère. That brought me to the error screen. I deleted Fizeau and reverted back to the old Atmosphère folder (since I set up a completely new SD card I luckily had a backup of the exact content from 1 day before on my PC). Oddly (and that's really odd) it still gives me that error.

SciresM commented 3 years ago

@lordelan you have an incomplete atmosphere directory. One of fusee-secondary.bin, sept/payload.bin, or stratosphere.romfs is missing.

lordelan commented 3 years ago

@SciresM You're right. By restoring my old Atmosphère backup I forgot to also take the "old" corresponding sept folder.

That still confuses me why the new Atmosphère version wasn't booting. Are your findings that you just wrote the same for all three included log files?

SciresM commented 3 years ago

All three reports describe identical "file not found" crashes.

lordelan commented 3 years ago

Okay, gotta do another update later on and take care everything works out. Thanks. :)

ImanCol commented 3 years ago

Hekate fixed this problem with their formatting systems by resizing the MicroSD. It is recommended to have less than 900MB of files for you to restore while formatting.

nota-debug commented 3 years ago

me too as well it happened when my little brother updated my switch and it been happening before 19.4.0 prelease of atmosphere. i tries the bitarchive method formatting it and downloading 19.5.0. I will post the report below. please help me.

nota-debug commented 3 years ago

report.zip

Unlashjen24 commented 3 years ago

Hi all, ive just started getting a similar error too, everything was working just fine after I updated my atmosphere and hekate to the latest versions and I was testing some tesla cheats and I was trying to make it so the cheats didn't auto activate on startup of the application and now im getting this error, I'd really appreciate the help report_00000000064c2d3e.zip

Zylder commented 3 years ago

I have the same problem.

Hekate was successfully installed, however when launching Atmosphere it crashes on this error.

Atmosphere is at version 12.1.0

I've tried several times, but so far nothing.

masagrator commented 3 years ago

Atmosphere is at version 12.1.0

This is not Atmosphere version, this is HOS version

KTVX94 commented 3 years ago

report_0000000006a8f6af.zip

I tried updating Atmosphere, Hekate and the Switch's OS in an attempt to dump it into the emu eMMC. First time doing it so I might have made some silly mistake. In theory they should all be the latest versions (Hekate 5.6.0, Atmosphere 1.0.0 and Switch 12.1.0). As with everyone else, Atmosphere crashes after the first 2 intro screens.

GormAuslander commented 3 years ago

im getting this error when I launch smash bros, after updating to atmo 1.2.2 and installing the latest smash update

ghost commented 3 years ago

Please update your ARCropolis, Training Modpack, and Skyline. Those cause the issue. Also, fill out the issue template next time please (this helps the devs help you!)

On Nov 1, 2021, at 6:22 PM, Jason Summer @.***> wrote:

 im getting this error when I launch smash bros, after updating to atmo 1.2.2 and installing the latest smash update

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

SciresM commented 3 years ago

(also, don't comment on resolved issues from 2020).

ghost commented 3 years ago

(also, don't comment on resolved issues from 2020).

my bad! I got an email notification for this and assumed that it was a new issue--I should've looked at the issue number.

GormAuslander commented 3 years ago

(also, don't comment on resolved issues from 2020).

my bad! I got an email notification for this and assumed that it was a new issue--I should've looked at the issue number.

You are a saint, and I apologize for the incorrect error report

SciresM commented 2 years ago

@BeckysFootSlave commenting as a non-maintainer on this stuff on closed issues from two years ago is really not necessary. I can handle it.

HeikesFootSlave commented 2 years ago

Sorry! Didn't looked at timestamp! Deleted

AndyII-II commented 3 months ago

I am having the same error. Archive fix doesn't help.

Panic occured while running atmosphere. Title id: 010041544D530000 Error: std: : abort <0xFFE> Report saved to atmosphere/fatal_errors/report_03d34dfe9.bin Press POWER to continue.

I don't see 03d34dfe9 file in fatal errors folder, so there is all i have ZIP_-_WinRAR.zip

I get this error only when boot atmosphere. Stock works. Also works another sd card with atmosphere.