TotK corrupted data at specific spot ingame

  • Thread starter Thread starter KatyS
  • Start date Start date
  • Views Views 6,066
  • Replies Replies 3

KatyS

New Member
Newbie
Joined
Jun 12, 2023
Messages
2
Reaction score
1
Trophies
0
Age
34
XP
49
Country
Germany
Hello,
my software is up-to-date (FW 16.0.3, Atmosphere 1.5.4, Hekate 6.0.5, newest sigpatches) and Tears of the Kingdom was running fine for like 4 hours on update 1.1.2.
However, whenever I try to enter the area around the tower south to the first tower you unlock, my game crashes and the game data becomes corrupt. THe only solution is to reinstall the game.
I tried NSPs from three different websites, used Tinfoil and DBI as installier, but the crash always persists at the exact same area ingame. It seems that I can explore the rest of the map without problems.
Does anybody have an idea what could cause this problem and how to fix it?
 
Hello,
my software is up-to-date (FW 16.0.3, Atmosphere 1.5.4, Hekate 6.0.5, newest sigpatches) and Tears of the Kingdom was running fine for like 4 hours on update 1.1.2.
However, whenever I try to enter the area around the tower south to the first tower you unlock, my game crashes and the game data becomes corrupt. THe only solution is to reinstall the game.
I tried NSPs from three different websites, used Tinfoil and DBI as installier, but the crash always persists at the exact same area ingame. It seems that I can explore the rest of the map without problems.
Does anybody have an idea what could cause this problem and how to fix it?
I've had that very same issue with BotW last year. The issue was a corrupted dump of the game. So just "make another backup" and you should be golden
EDIT: sorry, I've just now seen that you've actually tried multiple NSPs. If you still have them lying around, can you check their hashes and see if they might be the same? (multiple websites might host that same corrupted NSP)

Furthermore, you're running the game from your sd card, right? (emuMMC) Could you try a different SD card?
 
It was indeed a corrupted NSP. The file hashes confirmed that. I found another nsp with a different hash, and this seems to work for now.
 
  • Like
Reactions: MopSec
It was indeed a corrupted NSP. The file hashes confirmed that. I found another nsp with a different hash, and this seems to work for now.
I am running into the same problem as you did. For some reason, the same nsp file I use works fine in yuzu and doesnt crash. Maybe this is because yuzu doesn't check for corrupted data? Also how to I check the file hashes?
 

Site & Scene News

Popular threads in this forum