Just to throw in my two cents here, because I have experienced this same problem, but only with one game - Toy Story 3. NTSC game on an NTSC console, running system menu 4.2, you can see my post from two weeks ago or so on it here:
http://gbatemp.net/t278201-corrupt-sys-men...ing-toy-story-3
I just wonder after reading everything if it isn't a system menu issue... ie: I wonder if I was on 4.3 if it would not work just fine. Also, I don't have to unplug mine from the wall, simply reboot and system menu error screen goes away. Maybe this helps...
I've tried Tory Story 3. I Also am able to get the message with this game!
QUOTE(Captain_N @ Mar 1 2011, 06:36 AM) I have read the topic in its entirety and i got a question : how can any game or usb loader write to the ios unless it was programed to do so by an update or .dol. all a game does is read the ios when you play it not write it.
I wonder if its that the nand chip is failing? A failing nand chip will cause file corruption.
does the event happen when you use a loader that does not write to the play log?
If you dont get any corruption when the play log is not being updated then guess what its the playlog update.
Lets think about all the things that get written to NAND when we play a game,
(not including updates)
1) title tmd data base gets updated when the game is first run.
2) a folder for the games save gets created.
3) save games get written to the game save folder
4) message board may get written to(like how mario galaxy 1 sends screen shots to message board)
5) Play log gets updated
6) if the game has a channel then it will create/update channel data(mario kart/wii fit)
7) there is prob other stuff feel free to add
all said i dont know how a game can change an ios file unless the game updated the wii or had a dol that tells it to do that.
This seems to be a real problem. and there has to be a logical reason why this is happening