A fatal error occurred when running atmosphere что делать

Atmosphere-NX

locked as resolved and limited conversation to collaborators

Mar 23, 2020

You may also like…

• No one is chatting at the moment.

@

ZeroT21:

went there once, disneyland just ain’t for me

Today at 2:53 AM

What’s the issue you encountered?

Use newest ams release 1.4.0 on my Switch Lite. Then updated from firmware 14.1.2 to 15.0.1.
Boot with fusee.bin chainloaded with hekate.
I often get blackscreen after the Nintendo Logo. At the moment where the lock screen should pop up. There is only blackscreen with turned on backlight. I musst hold power off for 10 seconds to hard reset the Switch and try it again.

Sometimes it works and boots normaly.

If i downgrade back to 14.1.2 the Switch boots normaly each time. No more blackscreens.

Crash Report

N/A

System Firmware Version

15.0.1

Environment?

• Hekate as bootloader to chainload fusee.bin
• Latest official release
• No Homebrew
• emuMMC as partiton
• used clean SD with fat32

Smash Ultimate Crashing

I was adding mods to Smash Ultimate but I think I added too many and my game crashed.

I was just dragging and dropping mods over to my SD card like I usually do and the game crashed
I didn’t make any changes to Atmosphere

The issue can most likely be reproduced by adding a bunch of mods (Not sure in terms of GB storage) and see if the game will crash or not

The process is pretty much just adding a bunch of mods to your SD card and seeing what will happen in terms of crashing

Crash Report below

Link to the gist: https://gist.github.com/MikeyProHD/3d9d6cb750d537e91b33be4c52d88782

Switch ver 15.0.1

15.0.1

Atmosphere ver 1.4.1

Bootloader was fusee

No additional kips or sysmodules
SysNAND

Bug Report

What’s the issue you encountered?

emuMMC stops loading right after the Atmosphere splash screen with this notorious error message…

Panic occurred while running Atmosphere:
Title ID: 010000000000002B
Error: std::abort (0xFFE)

How can the issue be reproduced?

At first I start Hekate (using the RCMloader device) and from there I start Atmosphere either by script or by payload. It happens every time.

Crash Report

report_087eb780.zip

System Firmware Version

15.0.1

Environment?

• What bootloader (fusèe, hekate, etc) was Atmosphère launched by: Hekate 6.0.1
• Official release or unofficial build: Official release 1.4.1 (it first appeared with 1.4.0; update didn’t help)
• Do you have additional kips or sysmodules you’re loading: No
• Homebrew software installed: daybreak, dbi, ftpd, Goldleaf, NX-Shell, reboot_to_payload, Switch_90DNS_tester, Awoo-Installer, retroarch_switch, vgedit
• EmuMMC or SysNAND: emuMMC partition-based

Additional context?

I tried several (if not all) suggestions I could find (except setting all up from scratch), but nothing helped. Despite the familiar error message, this might be a new issue.
This whole thing came out of nowhere. One day I was suddenly unable to start any game. When I tried to reboot the Switch this error appeared.

Bug Report

i use a switch 1.0 whitout patch, hekate 6.0.1 abn firmware 15.0.1, I updated the switch with Atmosphère 1.4.1 a few days ago, I was using version 1.4.0 and I was playing the Kirby Forgotten Land game with my son, no game gave me a problem in 1.4.0, but I updated to 1.4.1, and I launched the game and it didn’t come in, it just told me to launch it from the menu, it was the only game that gave me an error, download sigpatches, change them, uninstall the game, download it again and nothing, then I changed to Atmosphère 1.4.0 As the last option and it worked as always. I hope you check that, regards

What’s the issue you encountered?

When I initialize my console (without deleting user data) through the maintenance mode on emunand, the OS crashes with error code 2005-0005.

How can the issue be reproduced?

Ensure you have the latest firmware and AMS.

Boot to emunand while holding down both the volume buttons.

Select «Initialize without deleting save data», or an option along the lines of.

Go through with the initialization.

Crash Report

Will upload later

System Firmware Version

15.0.1

Environment?

• What bootloader (fusèe, hekate, etc) was Atmosphère launched by: Hekate
• Official release or unofficial build: Official
• Do you have additional kips or sysmodules you’re loading: Teknik kips, missioncontrol, sys-clk, sysdvr
• Homebrew software installed: Inapplicable
• EmuMMC or SysNAND: Partition based EmuMMC

Hello! i had to create a new account just to report this since im not seeing any..
but after installing Atmosphere 1.4.1 , a LOT of games such as FE Three Houses, Skyward Sword, Hollow Knight, Mario All Stars, DQ Builders 2 , from what i tested ALL crash and say the game cannot run. I thought it was Atmosphere mods in Three Houses and Skyward swords, but i removed mods there and nothing. Hollow Knight, Mario etc on my Switch have no mods…

Message says : «Could not start software , please try again from Home menu». (sorry i dont know how to attach screenshots on github)

Some other games like Astral Chain, FE Engage (not surprisingly- even with the mods) do work well on 1.4.1 .. so im not sure what’s going on with all the others.

I did update Fusee as well as instructed. After testing and failing , i reverted back to 1.4.0 that i had and everything works just like before.
Please if this can be addressed/ fixed. Thanks!

Bug Report

What’s the issue you encountered?

After the console was on sleep, I turned it on and launched a game. Then threw me the following message:

A fatal error occurred when running Atmosphere
Program ID: 010000000000002b
Error Desc: std:: abort() called (0xffe)

Report saved to /atmosphere/fatal_errors/report_000000000b38548a.bin
Press POWER to reboot.

After three reboots getting the same message, I read a thread where the solution posted was to delete the ‘contents’ folder inside Atmosphere folder which worked. After this, I updated Atmosphere to 1.2.6.

However, today happened the same. After Sleep mode, launched a game and it happened again. Inject payload didn’t work either.

How can the issue be reproduced?

After sleep mode, launch a game. Reboot with the power button will put the message in a loop. Inject payload does not work

Crash Report

report_000000000b38548a.zip

System Firmware Version

EmuMMC firmware version 13.2.1

Environment?

• What bootloader (fusèe, hekate, etc) was Atmosphère launched by:
  Fusee
• Official release or unofficial build:
  Official release version 1.2.6 (I updated atmosphere thinking that perhaps an update could solve the issue)
• Do you have additional kips or sysmodules you’re loading:
  None (contents folder was erased)
• Homebrew software installed:
  EdiZon, Emuiibo, Amiigo, Goldleaf, JKSV (but they were already installed more ago than a month before the crash and was working properly)
• EmuMMC or SysNAND:
  EmuMMC partition-based

Additional context?

I don’t remember having done anything outside normal usage before the crash appeared; it started to appear suddenly.

Feature Request

What feature are you suggesting?

Overview:

• Now that qemu-virtual board target is added, what about supporting running whole Atmosphère with GUI as a virtual machine on arm chips?

Smaller Details:

• Maybe virtio-gpu-gl-pci and virtio-gpu support

Nature of Request:

What component do you feel this would best fit within?

Kernel

Why would this feature be useful?

Hello,

I recently got my Nintendo Switch fixed at a repair shop because the fan was not working. After they fixed it I tested my switch in CFW and my switch would constantly crash with the atmosphere error code 2002-3502. After some research, I figured out that it was an SD card reader issue. I went back to the repair shop and told them that they broke the sd card board while trying to replace the fan and they fixed it. After I got my switch back I tried to load up Atmosphere and I got a new error

ProgramID: 010000000000002B
Error Desc: std::abort() called (0xffe)

Now I can’t load into CFW at all and I have no idea on how to fix it. I have read multiple forums about this issue but none of them have a conclusive answer on how to fix this issue.

Bug Report

What’s the issue you encountered?

Updated AMS fom 1.4.0 to 1.4.1
While booting up the Switch, the AMS Logos appear but the Switch Logo doesn’t.
Screen stays black, Switch has to be turned off hard.
Falling back to AMS 1.4.0, everything works fne again

How can the issue be reproduced?

N/A

Crash Report

No report was created

System Firmware Version

15.0.1

Environment?

• Tried Fusee and Hekate
• Official release
  • AMS 1.4.1, Hekarte 6.0.1
• additional kips or sysmodules: don’t know
• Homebrew software installed: [ * ]
• EmuMMC on partition

Additional context?

N/A

Bug Report

What’s the issue you encountered?

I’ve unpacked FE:Engage and modded a file inside it.
I placed the modded file under atmospherecontentsTITLEIDromfsData... like what I did to other games, and atmosphere crashed.
Further testing showed that even without modding the file it would cause a crash.

How can the issue be reproduced?

1. Unpack Fire Emblem: Engage.
2. Choose a file at random. For example, romfsDataStreamingAssetsaaSwitchfe_assets_gamedataperson.xml.bundle. No need to modify this file.
3. Copy the unchanged file to atmospherecontents .
4. Run the game. Atmosphere crashed.

A fatal error occured when running Atmosphere.
Error Desc: Data Abort (0x101)

Crash Report

It’s a binary file so I converted it to base64: https://gist.github.com/ayssia/fd0f4901740362030c8587e46e89e393

System Firmware Version

15.0.1

Environment?

Hekate 5.9.0 with Official Atmosphere 1.4.0, SysNAND. Test with all kips/sysmodules disabled.

Additional context?

I guess the crash is caused by too many files in the unpacked game, there are ~178,000 files.

Bug Report

What’s the issue you encountered?

When I try to access the Chapter II in the game Unravel Two the game crashes.
I’m about sure that it’s not new. I’ve noticed this problem for some time now but just reported right now…

How can the issue be reproduced?

Just try to enter the Chapter II in the game Unravel Two

Crash Report

01674159053_0100e5d00cc0c000.zip

System Firmware Version

15.0.1

Environment?

• Atmisphère 1.4.0 with Hekate 6.0.1
• Only Tesla enabled at sysmodules
• I’m also using EmuMMC

Additional context?

• No additional context

Bug Report

What’s the issue you encountered?

How can the issue be reproduced?

Crash Report

System Firmware Version

15.0.1

Environment?

• What bootloader (fusèe, hekate, etc) was Atmosphère launched by: hekate
• Official release or unofficial build:
  • [ Official release version 14.0.1 (or) unofficial build ]
  • [ If using an unofficial build, include details on where/how you acquired the build. ]
    • [ Ex: Self-compilation ]
    • [ Ex: Kosmos’ distribution of Atmosphère ]
• Do you have additional kips or sysmodules you’re loading: sys-clk, Mission Control, ldl_mitm
• Homebrew software installed: [ * ]
• EmuMMC or SysNAND: EmuMMC, File based
  • [ If using an EmuMMC, include whether it’s partition-based or file-based. ]

Additional context?

• Additional info about your environment:
• [ Any other information relevant to your issue. ]

Hi!

I tried installing Atmosphere on a Switch Lite (which has a SX Lite chip) and I get the following error message on boot:

A fatal error occurred when running Fusée.
Abort called, lr=0x40012b5b

Press POWER to reboot.

The boot process is SX OS boot menu => Payloads => «hekate.bin» => Payloads => «fusee.bin»
And then I get this error.

I don’t get why, and I haven’t found any help online. Do you have any idea of what could be causing this?

Thanks in advance for your help!

Bug Report

What’s the issue you encountered?

I wanted to play a game with mods so installed mods in atmosphere. Didn’t work. Wiped the SD and only installed the master still the same error.

How can the issue be reproduced?

Crash Report

No existing

System Firmware Version

I’m on firmware 15.0.1

Environment?

Using only atmosphere (the master file with everything) and TegraRCMGui with the fusee.bin from the same release.

Additional context?

It isn’t my first time jailbreaking

Bug Report

Hi folks, I was just updating my switch to FW 15.0.1. And wanted to update the CFW as well. Unfortunately, Atmosphere no longer works since the update. First I had the problem (0xffe) which I fixed afterwards. Then I uploaded a new fusee file where it said at the first launch that the fusee primary was missing. I then used another payload from Atmosphere and Hekate which was only called Fusee. As a result, Atmosphere crashed again and again with the error code «a fatal error occurred while running Fusee. Incorrect version (program=0xd40bf51f, mtc=0xb6b6ac70. But I have the latest version of Fusee in the folder and I have updated all the other folders like Atmosphere and Hekate. And there is nothing in the Atmosphere Content folder either.

Please help, thank you.

Feature Request

What feature are you suggesting?

Overview:

• Delete contents/0100000000001000 folder if it exists before rebooting to prevent custom Horizon themes from crashing switch

Nature of Request:

• Addition
  • After performing a successful update within Daybreak, automatically delete contents/0100000000001000 prior to rebooting console.

What component do you feel this would best fit within?

• Troposphère(I think, searched the Repo for Daybreak but didn’t find much)

Why would this feature be useful?

• A large number of users regularly get stuck after system update and ask for help on Reddit, Discords etc.
• The folder will always need to be deleted after an OS update, so automatically removing it if it exists wouldn’t cause any issues.
• Would reduce user confusion/users incorrectly blaming Atmosphere

Bug Report

What’s the issue you encountered?

I’ve unpacked FE:Engage and modded a file inside it.
I placed the modded file under atmospherecontentsTITLEIDromfsData... like what I did to other games, and atmosphere crashed.
Further testing showed that even without modding the file it would cause a crash.

How can the issue be reproduced?

1. Unpack Fire Emblem: Engage.
2. Choose a file at random. For example, romfsDataStreamingAssetsaaSwitchfe_assets_gamedataperson.xml.bundle. No need to modify this file.
3. Copy the unchanged file to atmospherecontents .
4. Run the game. Atmosphere crashed.

A fatal error occured when running Atmosphere.
Error Desc: Data Abort (0x101)

Crash Report

It’s a binary file so I converted it to base64: https://gist.github.com/ayssia/fd0f4901740362030c8587e46e89e393

System Firmware Version

15.0.1

Environment?

Hekate 5.9.0 with Official Atmosphere 1.4.0, SysNAND. Test with all kips/sysmodules disabled.

Additional context?

I guess the crash is caused by too many files in the unpacked game, there are ~178,000 files.

Bug Report

What’s the issue you encountered?

I’ve been playing the game for some time now today and it’s crashed twice.

How can the issue be reproduced?

I don’t think it’s easily reproducible, but: first was when skipping a cutscene in-game when joining a friend and the other when collecting a spirit.

Crash Report

01673902526_0100c52011460000.log

01673900103_0100c52011460000.log

System Firmware Version

15.0.1

Environment?

• I am launching official atmosphere 1.4.0 with Hekate.
• No additional KIPs or sysmodules loaded
• No homebrew software «installed».
  • The only apps I have downloaded to execute on hbmenu via title takeover are:
    • ftpd, Checkpoint, Reboot to Payload and LÖVE Potion
• EmuMMC or SysNAND: SysNAND

Additional context?

The game itself is up-to-date (0.20.0.209642 from its details on the HOME Menu).

What’s the issue you encountered?

when booted into atmosphere a lot of files are created in the erpt_reports folder even when i am not doing anything

How can the issue be reproduced?

launch atmosphere and wait for a couple minutes and check the sd card erpt_reports folder, there will be a lot of files causing it to hit the FAT limit of 16383 files in that folder and making the switch completely unusable (games load noticably slow and homebrew works extremely badly)

Crash Report

N/A

System Firmware Version

15.0.1

Environment?

• hekate (launching atmosphere using fusee.bin)
• Official release version 1.4.0
• Do you have additional kips or sysmodules you’re loading: N/A
• Homebrew software installed: N/A
• SysNAND

Additional context?

N/A