emuMMC broken after error – how to read fatal report / recover saves?

Hey folks,

I’ve been running Atmosphere 1.6.2 on emuNAND without issues for a while, but the other day, while launching a game, I got an error (didn’t screenshot it, unfortunately). Now, whenever I try to boot into emuNAND, I get this:

A fatal error occurred when running Atmosphere.

Program ID: 0100000000000005

Error Desc: std::abort() called (0xffe)

Report saved to /atmosphere/fatal_errors/report_0000000001023dd2.bin

Press POWER to reboot.

The sysNAND still works fine (it's untouched), and I also have a sysNAND backup from when I created the emuMMC (June 21). I know I could just reformat the SD and set up a new emuNAND, but I wanted to ask a few things before doing that:

• Is there a way to read the .bin crash report to figure out what happened?
• Any chance to recover or fix the broken emuNAND?
• If not, is there a way to recover the save files from it?
• Could I restore the sysNAND backup onto the crashed emuNAND? Would fuse mismatches be an issue like they are with sysNAND?

More info: Switch V1, unpatched, FW 17.0.1

Thanks a ton in advance for any help or pointers!