Emulator

Game Name?

Luigis's Mansion (Gamecube)

Game ID? (right click the game in the game list, Properties, Info tab)

GLME01

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

6e3d9ae0ed2fbd2f77fa1ca09a60c494

What's the problem? Describe what went wrong.

When i saving game and rebooting game, memorycard needs to be formnated (in game and in GC menu, memorycard A)

What steps will reproduce the problem?

At first, the game was saved normally, then, having already reached the ghosts, which 50 pieces need to be caught, each save breaks memory card A.
5.0-19864

Is the issue present in the latest stable version?

N/A

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

[Attach any fifologs if possible, write a description of fifologs and screenshots here to assist people unfamiliar with the game.]

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

[PC specs here]
Windows 11 Build 23516.1000 | RTX 2060 | Ryzen 7 2700X

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

Save State and 2 memory card (breaked and working) included in archive and save Card A (25MB)
Link : https://mega.nz/file/XwsQHazQ#M9L4DihNeBK2duKl_YoiQCOvwS3HAob_V_cpzo5t1k8

Does this problem happen when not using savestates?

JosJuice wrote in #note-2:

Does this problem happen when not using savestates?

Just now checked, without saving the state everything works.

The fix has yet to be merged. I'll just mark it as related, but I would expect the mentioned PR to fix this issue as well.
https://github.com/dolphin-emu/dolphin/pull/9027

I must have made a mistake somewhere, because I was looking at a PR that was merged in 2020 when I reopened this issue. I'll let you decide how to handle this.