Project

General

Profile

Actions

Emulator Issues #10377

closed

Bugs when viewing save data on wii menu

Added by EblfIYH over 7 years ago. Updated over 7 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

Wii Menu 4.3 NTSC-U

Game ID? (right click the game in the game list, properties, info tab)

0000000100000002

MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)

417358284cce02dbb0fed3ef30b0b59d

What's the problem? Describe what went wrong.

When trying to see saved data, there appears a window that says "Invalid write to 0x0001000c, PC=0x815f7e54" then "0x5238504d PC=same" and then the first message again and then something similar to first message. After skipping these messages the saved data can finally be seen but, sometimes they look duplicated or sometimes they are partly missing. Trying to exit will show other similar messages "Invalid write to 0x46520008, PC=0x813a7a14" and makes impossible return to Wii menu. Disabling Panic Handlers will make the process less frustrating but hangs the emulator when returning to Wii Menu.

What steps will reproduce the problem?

Open Wii Menu, then go to Settings > Data management > Saved Data > Games > Wii.

Which versions of Dolphin did you test on? Does using an older version of Dolphin solve your issue? If yes, which versions of Dolphin used to work?

Problem is from 5.0-3463 to 5.0-4607
Bug not present on 5.0

What are your PC specifications? (CPU, GPU, Operating System, more)

Don't think it's necessary but...
Intel Celeron G1610, Intel HD Graphics, Windows 10.

Is there any other relevant information? (e.g. logs, screenshots,
configuration files)

[Anything else here]

Actions #1

Updated by leoetlino over 7 years ago

Sounds like a bad NAND. Can you follow the instructions in this forum post?

Actions #2

Updated by leoetlino over 7 years ago

  • Status changed from New to Invalid

Closing as there is no response and the issue is known to be caused by bad setups.

Actions

Also available in: Atom PDF