Bloodborne Cusa00900 May 2026

Instead, they simply wrote:

“Failed to save game data. (CUSA00900)”

Another user, more pragmatic, noted that CUSA00900 only appeared on firmware 9.00—which was also the version that allowed PS4 jailbreaking. A few paranoid hunters speculated that Sony or FromSoftware had hidden a “trapping mechanism” for modders: a soft error that didn’t break the game, but slowly corrupted your emotional attachment to it. Sony eventually patched the 9.00 firmware’s save issues. Most players report that CUSA00900 has become rare—almost extinct. bloodborne cusa00900

For most PlayStation owners, an error code is an annoyance. A server timeout. A sync failure. You sigh, restart, and move on.

But not gone.

In other words, the game remembered you had progressed—but the console chose to forget.

But that’s the boring truth. The interesting truth is what happened when players started digging. In early 2022, a Reddit user posted: “CUSA00900 popped up right as I entered the Orphan of Kos arena. Then my save rolled back 6 hours.” Instead, they simply wrote: “Failed to save game data

But for Bloodborne hunters on the old PS4 firmware 9.00, CUSA00900 became something else entirely: a myth, a menace, and—depending on who you asked—a sign that the game itself was haunted. Let’s strip away the folklore for a moment. CUSA00900 is a region-specific title ID for the North American version of Bloodborne (the actual code is CUSA-00900 ). The error message usually appears when the PS4’s save-data auto-upload fails, often tied to corrupted system cache or a conflict with the console’s 9.00 firmware update—which, ironically, was supposed to improve stability.