How to Fix PS5 Error CE-108262-9 (Game Crash on Launch)
What CE-108262-9 means
Error code CE-108262-9 is the PlayStation 5's signal that something went wrong while the console was communicating with a game or its own system software. You will usually see it right after pressing play: the screen goes dark for a moment, the app fails to boot, and you are sent back to the home screen with the error code on display.
This code is a step above an ordinary crash. Sony's own guidance treats it as a possible problem with the system software or the application data itself — in other words, the console is reporting that it tried to read something and the data did not come back correctly. That does not automatically mean your PS5 is broken, but it does mean you should work through the fixes in order instead of just restarting once and hoping.
Where the game is installed matters more here than with most error codes. This error is frequently tied to games running from an external USB drive, especially one that is incompatible or starting to fail. If your game lives on an external drive, the storage step below is worth trying early — it resolves the error for a lot of people.
Common causes
- Corrupted game install or update: an interrupted download, a scratched disc, or a partially applied update can leave the game unreadable at launch.
- Broken database entries: over time the PS5's internal database can develop inconsistencies that stop apps from loading their data correctly.
- Failing or incompatible external USB drive: if the game runs from extended storage, a bad drive or a loose connection can trigger read failures on boot.
- Outdated system software or game version: mismatches between firmware and game patches are a known trigger for launch crashes.
- Interrupted system activity: power loss, overheating, or a crash during an update can leave system or application data in an unreadable state.
How to fix CE-108262-9 — step by step
Work through these fixes in order. Most people are fixed by step 4.
- Fully restart the PS5. Rest Mode does not count. Press the PS button on your controller to open the Control Center, go to Power, and choose Turn Off PS5. Wait about 30 seconds after the light goes out, then press the power button on the console to turn it back on. Try the game again before moving on.
- Update the game and the system software. On the PS5 home screen, highlight the crashing game, press the Options button, and choose Check for Update. Install anything it finds. Then go to Settings, then System, then System Software, then System Software Update, and install any console update. Sony regularly patches the read problems behind this code.
- Move the game to internal storage. If the game is on an external USB drive, go to Settings, then Storage, then Extended Storage. Highlight the game, press the Options button, and choose Move to Console Storage. If you cannot move it, safely disconnect the external drive instead and reinstall the game to internal storage. Test whether the error follows the game or stays with the drive.
- Rebuild the database in Safe Mode. Turn the PS5 fully off, then press and hold the power button until you hear a second beep (about seven seconds). Connect your controller to the console with a USB cable, press the PS button, and select Clear Cache and Rebuild Database from the Safe Mode menu. This repairs broken data entries and fixes read problems. It does not delete games or saves, though it can take a while on a full drive.
- Delete and reinstall the crashing game. If the error only affects one title, highlight it on the home screen, press Options, and choose Delete. Reinstall from your Game Library or from the disc, then install every update before launching. Save data is stored separately and is kept when you delete the game itself. A clean install rules out a corrupted game copy entirely.
- Reset the PS5 after backing up your saves. This is the last resort before considering a hardware fault. Upload your saves to cloud storage if you have PlayStation Plus, or copy them to a USB drive from Settings, then Saved Data and Game/App Settings. Then turn the PS5 off, boot into Safe Mode, and choose Reset PS5. Reinstall only the crashing game first and test it before restoring everything else.
Did this fix it? Quick checklist
- The game reaches its title screen without the error
- You can start a new game or load a save successfully
- Other games still launch normally after the rebuild
- No CE-108262-9 popup after restarting the console
If the error survives all six steps and appears across multiple games, the problem may be hardware-related — a failing internal drive is the most common suspect. Back up your saves and contact PlayStation Support with the error code, since it helps them diagnose the console quickly and check your warranty options.
Frequently asked questions
Is PS5 error CE-108262-9 a serious error?
It is more serious than a simple one-time crash because the console is reporting a read problem with its own system software or application data. Most cases are fixed at home with an update, a database rebuild, or a reinstall. Only when the error survives a full reset across multiple games is it likely a hardware issue.
Will rebuilding the database delete my games or saves?
No. Rebuilding the database only reorganizes the data on the drive so the PS5 can locate it properly. It does not delete games, apps, or save data. It is a safe, official maintenance option in the PS5 Safe Mode menu.
Can an external USB drive cause CE-108262-9?
Yes. This error is commonly linked to games running from an incompatible or failing external USB drive. Moving the game to the console's internal storage and testing it there is one of the fastest ways to confirm whether the external drive is the cause.
What should I do if CE-108262-9 happens in every game?
When the error affects every game, focus on console-wide fixes: update the system software, rebuild the database in Safe Mode, and as a last resort reset the PS5 after backing up your saves. If the error still appears after a reset, contact PlayStation Support, because a failing internal drive or another hardware fault is likely.