Skip to content

[BUG]: Memory Card Crashes in Windows #12658

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
xfechx opened this issue May 13, 2025 · 13 comments · May be fixed by #12694
Open

[BUG]: Memory Card Crashes in Windows #12658

xfechx opened this issue May 13, 2025 · 13 comments · May be fixed by #12694

Comments

@xfechx
Copy link

xfechx commented May 13, 2025

Describe the Bug

I am having crashes while saving game data (overwrtting slot game save) using a folder type memory card that I have been using for years (cross-save) between devices.

In Linux this is not happening, but anytime I want to save game progress in windows to that memory card (overwritting a save file from a game), the game crashes.

Here is the log

emulog.txt

Reproduction Steps

Saving a game like usual, under a 'folder-type' memory card.

Expected Behavior

Saving and continuing game, however game crashes when saving.

PCSX2 Revision

V2.3.343

Operating System

Windows 11

If Linux - Specify Distro

No response

Logs & Dumps

emulog.txt

@RedDevilus
Copy link
Contributor

Failed to open CHD 'F:\Games\PS2\Crash Twinsanity (USA) (v2.00).chd': invalid file

Are you sure the game is still there and also check if there are no permission issues.

Maybe try this below for that game:

How To Verify Your Games
From the game list, right click on your game and go to Properties. Then, in the Summary tab click Verify.

If the status is bad, follow the disk dumping guide to make a fresh copy.

@xfechx xfechx closed this as completed May 13, 2025
@xfechx
Copy link
Author

xfechx commented May 13, 2025

It still showing the same error when all files are ok, please check the updated log file

@xfechx xfechx reopened this May 13, 2025
@xfechx
Copy link
Author

xfechx commented May 13, 2025

Please check the new updated log, still having the same issue, the bad chd file had nothing to do with the bug.

@RedDevilus
Copy link
Contributor

[   38.6689] Reopening GS with existing device
[   76.0562] OSD [MemoryCardSave0]: Memory Card 'Mcd001.ps2' was saved to storage.
[   77.9235] FolderMcd: Writing data for slot 0 to file system...

Hmm at a glance I don't see where it's breaking.

@xfechx
Copy link
Author

xfechx commented May 13, 2025 via email

@RedDevilus
Copy link
Contributor

Oh, yeah using dropbox can cause permission changes or problems with wrong saves/ broken saves on Windows. People using something like syncthing and having cold saves (whenever emulator is fully closed and then synced up in cloud) is safer.

Makes sense as to why it works fine on Linux but not Windows. I don't think we can really fix this besides making a way to connect to cloud only after everything safe or a built-in save sync.

@xfechx
Copy link
Author

xfechx commented May 13, 2025 via email

@RedDevilus
Copy link
Contributor

I remember there is a different issue where PCSX2 doesn't release the lock handler properly and then doesn't save correctly, it's been an issue that can come up randomly. It can be totally fine at times and you probably got unlucky.

@xfechx
Copy link
Author

xfechx commented May 13, 2025 via email

@RedDevilus
Copy link
Contributor

What should I try?
I have had this issue since yesterday and I have tried many times with the
same issue.

You could join the Discord and see if there are ways to alleviate the issue somewhat. Because it's kinda both Windows and PCSX2 not liking it.

@xfechx
Copy link
Author

xfechx commented May 13, 2025

OK, it seems to be resolved by going to Dropbox for Windows application, and then under preferences > account, pressing ALT will show "Fix Permissions" and "Reset File System warnings" buttons, pressed those two and now the problem is fixed.

So the problem was dropbox file permissions, because now it saves without issues, for new saves and overwriting.

@xfechx xfechx closed this as completed May 13, 2025
@xfechx
Copy link
Author

xfechx commented May 13, 2025

So further testing, and I am still having the same issue.

@lightningterror
Copy link
Contributor

Can you try #12694 if it fixes the crash?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants