
Starfield was supposed to be getting a second life on PS5. Instead, Sony players are beta-testing a port that crashes so often it’s turning a “soft relaunch” into yet another Bethesda tech drama.
On paper, April 7 should have been the redemption arc. Starfield finally hit PS5 and PS5 Pro. The massive Free Lanes update dropped at the same time, overhauling systems with things like an in‑space cruise mode, the Anchor Point station, tougher elite enemy variants and meaningful outpost improvements. On top of that, the Terran Armada DLC landed as a $10 incursion‑style campaign with a new robot companion, late‑game combat and new ship toys.
Reviewers like Mortismal Gaming were clear: the free update does more to fix Starfield’s pacing and world than the paid DLC does to expand it. This was Bethesda trying to do what CD Projekt did with Cyberpunk – patch, overhaul, then relaunch on new hardware with a better story to tell.
Instead, PS5 forums and subreddits filled up with something Bethesda really didn’t need more of: crash reports. Not occasional bugs. We’re talking repeated hard crashes to the PS5 home screen, system error messages, short freezing spells during busy scenes and – in the nastier cases – saves that won’t load or quest chains that can’t be progressed because the game dies mid‑mission.
According to coverage from Eurogamer, Push Square and German outlet PlayCentral, this isn’t isolated to some edge case. Base PS5 and Pro, digital and physical copies, vanilla base game and players who immediately bought Terran Armada – all of them are in the mix. The day‑one PS5 patch didn’t make the wave go away.
So the “Starfield 2.0” moment that was supposed to win over a fresh console audience is, for a decent chunk of PS5 owners, boiling down to: pay full price, download tens of gigabytes, then pray the game doesn’t throw an error when you fast travel.
Here’s where it gets more specific – and more awkward for Sony as much as Bethesda.
Push Square and other outlets have been testing different visual setups, and the pattern they (and a lot of players) keep coming back to is this: the crashes on PS5 Pro get worse when you lean into the console’s premium features.
That means graphics modes, frame‑rate caps, and particularly the PS5 Pro’s PSSR 2 upscaler – exposed in console settings as “Enhance PSSR image quality”. When that’s turned on and the game is running in the enhanced mode, Starfield seems far more likely to fall over for some users. Turn off the PSSR enhancement, or cap your frame rate at 60fps instead of going uncapped, and suddenly some players can run long sessions without a single crash.

Internal testing write‑ups and community reports converge on roughly the same workaround:
Do that, and a lot of people stop crashing. Don’t do that, and it’s error codes every couple of missions.
Two big caveats here. First, this isn’t a guaranteed fix – base PS5 players without PSSR 2 at all are still reporting crashes and brief freezes. Second, no one on the outside has the engine‑level visibility to say “this is definitely the cause”. Right now it’s correlation, not confirmed fault.
But from the outside, it looks like a perfect storm. You’ve got:
If you were designing a scenario most likely to expose edge‑case engine bugs, this would be it. Starfield already launched on PC and Xbox with a reputation for being “Bethesda‑stable” – playable, but creaky around the edges until enough patches and mods landed. Building a complex PS5 build and a major systems revamp at the same time always looked ambitious. Now we’re seeing the bill.
Predictably, the next step after “my game keeps crashing” is “do I get my money back?” And that’s exactly where PS5 players are heading.
Eurogamer highlights players who describe the PS5 version as “unplayable” and are contacting Sony support for digital refunds – sometimes for the full game, sometimes for the new Terran Armada DLC on top. Those reports line up with what’s happening on social channels and forums: people stuck in crash loops on main quests, or watching the game die every 20–30 minutes, are not just waiting politely for Patch 1.01.
The uncomfortable bit for Bethesda is that, on console, you don’t have the PC safety net. There’s no quick mod that disables a specific feature, no .ini hack to force‑lock the game to a safer path. If a build is broken on your platform, your choices are: hope for a patch, or ask for a refund.
Sony, famously, is stricter than Valve when it comes to digital refunds, and historically hasn’t loved setting precedents here. But that stance already bent once for Cyberpunk 2077, where Sony went as far as temporarily pulling the game from the store. Starfield isn’t at that level of catastrophe – yet – but a steady flow of players arguing they can’t finish what they paid for puts the pressure in the same direction.
And remember the timing: PS5 players are not just buying a late port of last year’s Xbox/PC release. They’re buying into Starfield at the post‑Free‑Lanes, post‑expansion price point, with marketing that frames this as the definitive, upgraded experience. Drop £70+ on that, maybe another £10 for Terran Armada, and being told “just turn off the premium visual feature your console shipped with” is a hard sell.

This is the bit the PR teams hate to hear: the existence of a community workaround doesn’t change the consumer rights situation. If your game crashes frequently in normal use with default or marketed settings, then from a buyer’s perspective it’s not fit for purpose. It doesn’t matter that a subreddit found a combination of toggles that makes it mostly OK.
FinalBoss // Gear
Level up your setup
01Best-selling Xbox Series X|S gameson Amazon→02Xbox controllerson Amazon→03Top-rated gaming headsetson Amazon→04Discounted game keyson Kinguin→Affiliate links · As an Amazon Associate, FinalBoss earns from qualifying purchases.
Get access to exclusive strategies, hidden tips, and pro-level insights that we don't share publicly.
Ultimate Gaming Strategy Guide + Weekly Pro Tips
To be fair, Bethesda has clearly been putting in the work on Starfield since its original release. Free Lanes is a serious swing at fixing the most boring parts of space travel and combat. Earlier on other platforms, the Shattered Space expansion and major feature patches showed a studio that knows the launch reception wasn’t good enough and is trying to build a longer tail for the game.
But you don’t get infinite chances to re‑launch the same RPG. Xbox and PC players already lived through “it’ll be better in a year”. PS5 players only arrive once. If the first impression is a wall of error codes and “this quest always crashes here”, a lot of them won’t be back when the inevitable “now it’s finally ready” trailer hits.
And the silence is doing Bethesda no favours. As of mid‑April, there’s no detailed, public acknowledgement of the specific PS5/PS5 Pro crash patterns, no clear statement along the lines of: “yes, we see the PSSR 2 issues, we’re working with Sony, hotfix incoming, here’s what to toggle in the meantime.”
That vacuum gets filled by frustration and worst‑case assumptions. Is this a PS5‑specific optimisation miss? Is it Free Lanes’ new systems interacting badly with Sony’s hardware? Is it the PSSR 2 path needing deeper engine integration? We don’t know – and that’s exactly the point. If Bethesda wants to keep Starfield alive as an evolving platform across three ecosystems, clear technical communication is no longer optional.
The irony is that beneath all this, there’s finally a version of Starfield that people who bounced off at launch might actually like. Better travel flow, stronger late‑game combat from Terran Armada, more reason to care about outposts and ship builds. But all of that is downstream of a basic question PS5 users have to ask: “Does it run without wrecking my evening?”
Starfield’s big PS5 arrival – bundled with the Free Lanes overhaul and Terran Armada DLC – is being dragged down by widespread crashes, freezes and some progression‑breaking bugs on both PS5 and PS5 Pro. Community testing and early coverage strongly suggest the PS5 Pro’s PSSR 2 upscaler and aggressive performance modes are making things worse, leading to unofficial “turn this off” workarounds and growing calls for refunds. The real test now is whether Bethesda and Sony treat this as a teething issue they move quickly and transparently to fix, or just another chapter in the long, slow “we’ll patch it later” saga that players are increasingly tired of funding.