Dolphin, the GameCube and Wii emulator - Forums

I Just updated to the latest WIP build and as soon as I go to edit my list of save files through the installed 4.3U System Menu, I get four consecutive error messages:

Invalid write to 0x0001000c, PC=0x815f7e54
Invalid write to 0x5234514d, PC=0x815f7e54
Invalid write to 0x0001000c, PC=0x8155a25c
Invalid write to 0x0001000c, PC=0x815f7e54

It then gives another massive set of errors when returning to the main menu that lead to a frozen black screen:

Invalid write to 0xa4780008, PC=0x815f7e54
Invalid write to 0xa4780008, PC=0x815c61c8
Unable to resolve write address 1d522da0 PC 815c61c8
Unable to resolve write address 1d522da4 PC 815c61c8
Unable to resolve write address 1d522dac PC 815c61c8
Unable to resolve write address 1d522da8 PC 815c61c8
Etc...

This happens with every Dolphin revision starting with 5.0-3463, my list of saves is wiped at this point too. If I roll back to 5.0-3449 I get my list back and these errors no longer occur...

Can anyone please help?

For any developer who wants to look into this: The likely commit in that range is 4d52df150bfb20f4892d364f00e52944ec3d3473.

Ouch. I think I see why: that's because Dolphin's NAND boot code is wildly inaccurate (to say the least) and does not set up everything properly. Your issue comes from the fact that we have become more accurate in other places.

Launch the system menu from emulation itself (e.g. go back to the Wii Menu from the Wii Menu) to work around this issue for now.

Edit: I have created an issue for this.

This is fixed in master now (>=5.0-3655). The underlying cause isn't and will be fixed in the future, but the issue shouldn't happen anymore.

Thanks a lot for looking into this.

Hey, this issue not only hasn't been resolved for me as of 5.0-4444 but now my save list is not just empty, it completely and utterly broken. I get the same error codes as I originally listed when accessing the save data, but now when I actually view it I have nothing but page after page of clone entries for one game, Klonoa.  

Different, more elaborate error codes when returning to the main menu though, and it still dies to a black screen:

Invalid write to 0x3c7e2e71, PC=0x815f7e54
Invalid write to 0x3c7e2e71, PC=0x81406ec4
Unknown Pointer 0x0ad6eee0 PC 0x81534418 LR 0x81534418
IOCTL_ES_READCONTENT - Bad destination
Invalid write to 0x3c7e2e71, PC=0x815f7e54
Invalid write to 0x3c7e2e71, PC=0x8151a060
Unknown Pointer 0x0ad5ed40 PC 0x81534418 LR 0x81534418
IOCTL_ES_READCONTENT - Bad destination
Invalid write to 0x3c7e2e71, PC=0x815f7e54
Invalid write to 0x3c7e2e71, PC=0x8151a060
etc..

That's weird... I cannot reproduce here. Could you send me the list of files that are in your NAND? The `tree /f` command should do that on Windows.

(06-21-2017, 12:23 AM)leolam Wrote: [ -> ]That's weird... I cannot reproduce here. Could you send me the list of files that are in your NAND? The `tree /f` command should do that on Windows.

I ran the command but i can't copy the entire list, command prompt doesn't keep track of that much data and cuts off the start...

Adding `> destination_text_file_name_here.txt` at the end of the command line (without the quotes, of course) should redirect the whole output to that text file.

(06-21-2017, 12:41 AM)leolam Wrote: [ -> ]Adding `> destination_text_file_name_here.txt` at the end of the command line (without the quotes, of course) should redirect the whole output to that text file.

Cheers, here's the info.