CE-108255-1 - keep crashing when I load into a online game

Hi,

this is my 3rd day with issue. Reported via PS every time it crashes. Updated, cleared cache, rebuilt DB, disabled 120Hz/VRR, tried performance mode, no SSD/USB, new internet, new untouched UT lineup. 

I crash right to the PS home screen every time after the crash.

I can get into RTG just fine. Only thing that works in the game for me and gives me this specific CE code.

dbaber17​ CE errors are PS errors, not Xbox errors. Xbox would have an entirely different error code. You may crash in the same mode or at the same point in the game, cutscene, etc., but if you are on a different platform, we have to set it as a different platform with their information.

Are you getting an error code, or does it just crash to the main menu, or does it go to the dashboard?

I’m having this same issue on Xbox. Game crashes randomly during RTG, Dynasty any Gabe mode offline or online. I’ve cleared reserved space and cache, uninstalled, reset nothing helps. Will there be a fix or some update for this issue? It’s ridiculous!!!

Mines does the same thing 

Mine will crash right before the teams make the entrance to the field.

Teaglin1993​ Hey,

Can you try these for me?

• Clear the PS5 system cache in Safe Mode.
• Disable 120 Hz Output and VRR temporarily.
• Try Performance Mode instead of Resolution Mode.
• If you're using an external drive, move the game back to the internal SSD.
• Disconnect any unnecessary USB devices while testing.
• Test the connection to the game on a hotspot from a mobile device.
• IF you can, go into UT and generate a new lineup with no special or upgraded players.

Hey, folks

I can definitely understand how frustrating this one is, especially after already working through many of PlayStation's recommended steps. The team is aware that some players are experiencing crashes, but they occur in different modes and for different reasons.

PS identifies it as an application error, so it is quite generic.

A few additional things that have helped some PS5 players:

• Make sure both the game and PS5 system software are fully up to date.
• Clear the PS5 system cache in Safe Mode.
• Disable 120 Hz Output and VRR temporarily.
• Try Performance Mode instead of Resolution Mode.
• If you're using an external drive, move the game back to the internal SSD.
• Disconnect any unnecessary USB devices while testing.
• IF you can, go into UT and generate a new lineup with no special or upgraded players.
  
  

I can see several of you have already tried reinstalling the game, rebuilding the database, restoring licenses, and restarting the console, so thanks for confirming those steps. One question that may help us compare reports: does the crash occur at roughly the same point in every game (such as when switching from offense to defense), or does it occur randomly regardless of mode or situation?

Same error 

Every time I play any game mode in College Football 27, the game crashes in the middle of a game and returns the error code CE-108255-1. I've attached a screenshot of the error below.

I've already tried every troubleshooting step I could find, including:

• Deleting and reinstalling the game
• Restarting and resetting my PlayStation
• Rebuilding the database
• Restoring licenses
• Contacting PlayStation Support

Unfortunately, none of these steps have resolved the issue, and PlayStation Support wasn't able to provide a solution.

Has anyone else experienced this issue or found a fix? Any suggestions would be greatly appreciated.

Every time I play any game mode in College Football 27, the game crashes in the middle of a game and returns the error code CE-108255-1. I've attached a screenshot of the error below.

I've already tried every troubleshooting step I could find, including:

• Deleting and reinstalling the game
• Restarting and resetting my PlayStation
• Rebuilding the database
• Restoring licenses
• Contacting PlayStation Support

Unfortunately, none of these steps have resolved the issue, and PlayStation Support wasn't able to provide a solution.

Has anyone else experienced this issue or found a fix? Any suggestions would be greatly appreciated.