[GH-ISSUE #3367] [GAME BUG]: Driveclub save data corruption #1037

New issue

Closed

opened 2026-02-27 21:09:35 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 21:09:35 +03:00

Owner

Originally created by @kalaposfos13 on GitHub (Aug 2, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3367

Checklist (we expect you to perform these steps before opening the issue)

I have searched for a similar issue in this repository and did not find one.
I am using an official build obtained from releases or updated one of those builds using its in-app updater.
I have re-dumped the game and performed a clean install without mods and the issue is still present.
I have disabled all patches and cheats and the issue is still present.
I have all the required system modules installed.

Describe the Bug

For some reason, PROFILE/sce_sys/param.sfo has been wiped to 0 bytes for the second time now for me (I for some reason still have a backup of my old bricked save, and after I looked into what went wrong when my save had issues again I found out that said backup had the same problem), leading to a crash in trying to parse its header (you can't really read 8 bytes from an empty file)

Reproduction Steps

I have no idea what caused these two instances of the corruption, but it is possible to manually reproduce it by wiping savedata/1/CUSAXXXXX/PROFILES/sce_sys/param.sfo yourself, or doing this with any param.sfo in any save.

Specify OS Version

Arch Linux

CPU

Intel 12700h Laptop CPU

GPU

nVidia 3060 Laptop GPU

Amount of RAM in GB

32 GB

Amount of VRAM in GB

6 GB

Log File

Since I fixed my issue by copying another param.sfo from another save, I can only provide a log with a manually broken save, plus this isn't really useful either, as the important part would be to learn what causes this in the first place.
callstack.txt
CUSA00003.log

Originally created by @kalaposfos13 on GitHub (Aug 2, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3367 ### Checklist (we expect you to perform these steps before opening the issue) - [x] I have searched for a similar issue in this repository and did not find one. - [ ] I am using an official build obtained from [releases](https://github.com/shadps4-emu/shadPS4/releases) or updated one of those builds using its in-app updater. - [ ] I have re-dumped the game and performed a clean install without mods and the issue is still present. - [x] I have disabled all patches and cheats and the issue is still present. - [x] I have all the required [system modules](https://github.com/shadps4-emu/shadPS4/wiki/I.-Quick-start-%5BUsers%5D#4-adding-modules) installed. ### Describe the Bug For some reason, PROFILE/sce_sys/param.sfo has been wiped to 0 bytes for the second time now for me (I for some reason still have a backup of my old bricked save, and after I looked into what went wrong when my save had issues again I found out that said backup had the same problem), leading to a crash in trying to parse its header (you can't really read 8 bytes from an empty file) ### Reproduction Steps I have no idea what caused these two instances of the corruption, but it is possible to manually reproduce it by wiping savedata/1/CUSAXXXXX/PROFILES/sce_sys/param.sfo yourself, or doing this with any param.sfo in any save. ### Specify OS Version Arch Linux ### CPU Intel 12700h Laptop CPU ### GPU nVidia 3060 Laptop GPU ### Amount of RAM in GB 32 GB ### Amount of VRAM in GB 6 GB ### Log File Since I fixed my issue by copying another param.sfo from another save, I can only provide a log with a manually broken save, plus this isn't really useful either, as the important part would be to learn what causes this in the first place. [callstack.txt](https://github.com/user-attachments/files/21557881/callstack.txt) [CUSA00003.log](https://github.com/user-attachments/files/21557919/CUSA00003.log)

kerem closed this issue

2026-02-27 21:09:36 +03:00

kerem commented

2026-02-27 21:09:36 +03:00

Author

Owner

@StevenMiller123 commented on GitHub (Aug 2, 2025):

This is an invalid report due to reasons you seem to know already.
Please redump/uninstall mods at the minimum.

It would also be helpful if you sent a log containing a test run where the game actually saved data, so we can identify more places where this corruption could occur.

@StevenMiller123 commented on GitHub (Aug 2, 2025): This is an invalid report due to reasons you seem to know already. Please redump/uninstall mods at the minimum. It would also be helpful if you sent a log containing a test run where the game actually saved data, so we can identify more places where this corruption could occur.

kerem referenced this issue

2026-02-27 21:14:21 +03:00

[PR #1037] [MERGED] core/memory: Fix sceKernelMTypeProtect setting VMA type #1895