Gaming Mario 3D Allstars - Crashing issue

[mTilK]

Okay so here's my final report.
SXOS 3.0.4 BETA
FW 10.1.0

Once you have ran the title, You will get an error screen if trying to reload it; this will kick you out of the game entirely.

Same versions here, but run directly from XCI. And i get exactly the same issue with SM64.

 

[godreborn]

Humm.. I ran a Verify with NSCBuilder on the .nsp floating around and got this output; I really dunno what this means but usually i get NSP Safe as verdict, meaning I won't touch this copy yet.

***************
DECRYPTION TEST
***************
010049900F546000 - Content.PROGRAM
8ade91ccfae153c6c74c406c1dab9880.nca -> is CORRECT
010049900F546000 - Content.CONTROL
9fe3feaf6da10349d5ef8807e4bad863.nca -> is CORRECT
010049900F546000 - Content.MANUAL
17b3f11f774cb5939f3f13e82a61ad3f.nca -> is CORRECT
010049900F546000 - Content.MANUAL
2549c5272d0737c54a09636d35ea9fa4.nca -> is CORRECT
010049900F546001 - Content.PROGRAM
5977df9d4848858cbde157c6723dd1de.nca -> is CORRECT
010049900F546001 - Content.CONTROL
69a6b4c7d4d644ec47c140724910430f.nca -> is CORRECT
010049900F546001 - Content.MANUAL
3bfc1cab21c8dea97e245574f0f15251.nca -> is CORRECT
010049900F546002 - Content.PROGRAM
94b649803873ec7e230ccc709227377f.nca -> is CORRECT
010049900F546002 - Content.CONTROL
f3d6504a2c1426e6ab3a861f364dc203.nca -> is CORRECT
010049900F546002 - Content.MANUAL
c1d9a84f7b5649c1b3d44db402970846.nca -> is CORRECT
010049900F546003 - Content.PROGRAM
33b3271907e378d90579161a24261b9b.nca -> is CORRECT
010049900F546003 - Content.CONTROL
673446212a6849220956f2441676b471.nca -> is CORRECT
010049900F546003 - Content.MANUAL
c39bfc0119c36590ad12b02c2f72e2b7.nca -> is CORRECT
010049900F546000 - Content.META
bb5989a7f08ed3c25e4b1f44d6a16813.cnmt.nca -> is CORRECT

VERDICT: NSP FILE IS CORRECT

****************
SIGNATURE 1 TEST
****************
010049900F546000 - Content.PROGRAM
> 8ade91ccfae153c6c74c406c1dab9880.nca -> was MODIFIED
* NOT VERIFIABLE!!!

010049900F546000 - Content.CONTROL
> 9fe3feaf6da10349d5ef8807e4bad863.nca -> is PROPER
* ISGAMECARD WAS CHANGED FROM 1 TO 0

010049900F546000 - Content.MANUAL
> 17b3f11f774cb5939f3f13e82a61ad3f.nca -> is PROPER
* ISGAMECARD WAS CHANGED FROM 1 TO 0

010049900F546000 - Content.MANUAL
> 2549c5272d0737c54a09636d35ea9fa4.nca -> is PROPER
* ISGAMECARD WAS CHANGED FROM 1 TO 0

010049900F546001 - Content.PROGRAM
> 5977df9d4848858cbde157c6723dd1de.nca -> was MODIFIED
* NOT VERIFIABLE!!!

010049900F546001 - Content.CONTROL
> 69a6b4c7d4d644ec47c140724910430f.nca -> is PROPER
* ISGAMECARD WAS CHANGED FROM 1 TO 0

010049900F546001 - Content.MANUAL
> 3bfc1cab21c8dea97e245574f0f15251.nca -> is PROPER
* ISGAMECARD WAS CHANGED FROM 1 TO 0

010049900F546002 - Content.PROGRAM
> 94b649803873ec7e230ccc709227377f.nca -> was MODIFIED
* NOT VERIFIABLE!!!

010049900F546002 - Content.CONTROL
> f3d6504a2c1426e6ab3a861f364dc203.nca -> is PROPER
* ISGAMECARD WAS CHANGED FROM 1 TO 0

010049900F546002 - Content.MANUAL
> c1d9a84f7b5649c1b3d44db402970846.nca -> is PROPER
* ISGAMECARD WAS CHANGED FROM 1 TO 0

010049900F546003 - Content.PROGRAM
> 33b3271907e378d90579161a24261b9b.nca -> was MODIFIED
* NOT VERIFIABLE!!!

010049900F546003 - Content.CONTROL
> 673446212a6849220956f2441676b471.nca -> is PROPER
* ISGAMECARD WAS CHANGED FROM 1 TO 0

010049900F546003 - Content.MANUAL
> c39bfc0119c36590ad12b02c2f72e2b7.nca -> is PROPER
* ISGAMECARD WAS CHANGED FROM 1 TO 0

010049900F546000 - Content.META
> bb5989a7f08ed3c25e4b1f44d6a16813.cnmt.nca -> needs RSV check
* CHECKING INTERNAL HASHES
- PFS0 hash is CORRECT
- HASH TABLE hash is CORRECT
- HEADER BLOCK hash is CORRECT
* INTERNAL HASHES MATCH
> bb5989a7f08ed3c25e4b1f44d6a16813.cnmt.nca -> was MODIFIED
* NOT VERIFIABLE!!!
VERDICT: NSP FILE COULD'VE BEEN TAMPERED WITH

nx info says that it's safe. however, I know the first dump was modified for some reason as it says in the nsp name. there's a second one or maybe it's the same in a dark place. I'm going to hex compare them to see if they're the same dump. I'm creating an nsz at this very moment of the first dump.

--------------------- MERGED ---------------------------

here's what I got from both downloads:

 

[Tumbleweed]

Good, that means the file I have is safe then... But probably with the same issue as everyone is reporting here...

 

[godreborn]

Good, that means the file I have is safe then... But probably with the same issue as everyone is reporting here...

someone told me that one, if not all, installers will tell you if something is unsafe or won't install something that is unsafe or something like that. never installed something, so I wouldn't know if that's true.

 

[Jayro]

When i exit SM64 using the - button to return to main title menu my Switch locks up completely.
The screen goes black and i have to force a reboot and inject payload again.
The crash only happens on SM64 the other games return to menu just fine.
I was wondering if this was a issue for everyone or just me.
Ive not updated my CFW or OFW in a little while which may be the issue ?

Yes, you want to be on 10.1.0 and the latest SX OS beta, v3.0.4

I'm using the XCI, the NSP kept crashing for me at game selection screen. The XCI works fine though.

 

[godreborn]

convert the nsp back to xci with nsc builder if that works. creating an xci from an nsp takes seconds unlike compressing them.

 

[Ace88]

Is it known why that error occurs?

 

[Ace88]

Just tried the game on AMS and after restarting it, i got a black screen and my switch doesnt turn on anymore. Can anybody help me :/ ?

Edit: got it restarted. The Switch crashes, after you have startet M64 and restart the game

 

[Don_Padoli]

sunshine and galaxy works fine,m64 crash the game

 

[DuveltjeDG]

It only crash when SM64 has started and go back to main menu. Also when you go to horizon close game and start. Only Galaxy and Sunshine work flawless. I’m on 10.1.1 and AMS 0.14.1.

 

[DiscostewSM]

Didn't pokemon (when it was leaked) cause crashing and such up until around the time it officially released?

 

[mrdude]

Didn't pokemon (when it was leaked) cause crashing and such up until around the time it officially released?

Why not try disabling your internet and change the date on your switch - then try it. That would give you the answer.

 

[Quarions]

guys just play the fan port of SM64... Why bother...

 

[naddel81]

guys just play the fan port of SM64... Why bother...

because V7 with HD textures stutters on switch

 

[Quarions]

because V7 with HD textures stutters on switch

like if the official port has better textures and run at 60 fps

 

[mrdude]

I've tried 2 different xci versions now: (both ones I tried were already trimmed or converted nsp files)

MD5: 47B0559D92B99C52DD7D1F818E0ED3FB - bad
MD5: C94438E5310012A70CF79CF99943553C - bad

As long as there no save file the 1997 version works - otherwise it crashes on 2nd load.

 

[Chrisssj2]

Loads of people are having this issue it seems, it's not just you. Seems to work fine on SXOS, but other CFW's it seems to crash, according to reports.

It is out SX OS, CFW of the year!!

 

[cashboxz01]

SX OS 3.0.4 w EmuNAND 10.1.0 here

• With the game installed to emunand, nothing gets past title screen, just crashes with error and back to home screen
• Then when game is selected and attempted to run it tries to check for data corruption.
  • XCI install of the game finds data corruption.
  • NSP install of the game finds no data corruption.
• Oddly enough, I have an SSD connected to the dock with the XCI and that works just fine

 

[Ace88]

Just updated AMS to 0.14.3 hoping it would help. (Switch Firmware still on 10.0.4) and now I can't start the game at all.

"Could not start the software.

Please try again from the HOME Menu"

any ideas what I could do?

 

[Essometer]

Just updated AMS to 0.14.3 hoping it would help. (Switch Firmware still on 10.0.4) and now I can't start the game at all.

"Could not start the software.

Please try again from the HOME Menu"

any ideas what I could do?

There are no sig patches currently available for 0.14.3. Downgrade Atmosphere to 0.14.2 and use the latest available sig patches.