Game crashes on any mode

Potential Fix for Connectivity & Crashes on PS5 (Error 0:85008S)

Hello,

From a broad point of view, the issue affects NFS (Network File System) unbound. I've analyzed your situation as a fellow player and community helper. Since the crash occurs after the Javelin anti-cheat and Launcher have successfully initialized, the issue likely lies in how the game client maintains its persistent connection or interacts with PS5 system settings.

Based on similar high-level incidents, please try the following steps in order of priority:

1. DNS Consistency & Network Conflicts

BF6 performs continuous DNS query checks during active sessions. If you are using a third-party VPN or have custom DNS settings (like Google DNS on the console but ISP default on the router), this can trigger a security disconnect.

Action: Temporarily disable any VPNs and set your PS5 DNS settings to "Automatic" to see if the 5-minute kick-out persists.

2. Peripheral Compatibility (The "I/O Conflict" Theory)

On PC, changing USB inputs mid-game can cause BSoDs. On PS5, certain third-party headsets or unlicensed controllers can cause system-level interrupts when the game engine hits a high load.

Action: Try launching the game with only a genuine DualSense controller connected (unplug any third-party USB dongles or headsets) to rule out hardware interrupts.

3. Security Thresholds (2FA & System Settings)

Sometimes, the PS5's internal security handshake conflicts with the game's own login verification during peak data transfer.

Action: As a test, if you have 2-Step Verification enabled, try toggling it off briefly (or ensuring your PSN and EA accounts are perfectly synced) to see if it stabilizes the session.

4. Error Code 0:85008S Insight

This specific code often points to a "Handshake Timeout" between the client and the backend. If your ISP is clear, the bottleneck is often local interference or a "double NAT" situation that only BF6’s netcode is sensitive to.

Please try these and let us know if you can stay in a match past the 10-minute mark!

Additional Advice

DNS Query Consistency: The fact that the player experienced similar symptoms in NFS Unbound is important. EA's Frostbite engine titles send frequent heartbeat packets, making them more sensitive to DNS inconsistencies than other games (such as Apex).

Peripheral Interrupts: The fact that the player crashes after 5-10 minutes may coincide with the controller's power-saving settings or the headset's communication refresh timing.

Error Code Analysis: 0:85008S is more likely to appear when the "session validity is lost" rather than from packet loss. Since Javelin (anti-cheat) is passed, it can be assumed that the "encrypted communication continuation" with the game server has failed.

It is recommended to strongly suggest "using a minimal configuration of peripherals (only a genuine controller)" in this case.

I hope this helps resolve the issue. If the aforementioned steps didn't resolve the 5-10 minute crash, please try these "Deep Dive" technical adjustments:

1. IP Reservation & DMZ (Rule out Firewall interference)

The PS5 might be experiencing a "Handshake Timeout" because your router's firewall is misinterpreting the game's security pings as a flood attack.

Step: Assign a Static IP to your PS5 via your router settings.

Step: Temporarily place that Static IP into the DMZ (Demilitarized Zone) of your router. This bypasses the router firewall entirely for the console. If the crashing stops, your router's SPI firewall was the culprit.

2. MTU (Maximum Transmission Unit) Adjustment

Standard MTU is 1500, but some ISPs/Network setups fragment EA's encrypted packets, causing the "0:85008S" error.

Step: Go to PS5 Settings > Network > Set Up Internet Connection > Advanced Settings.

Step: Change MTU from "Automatic" to 1473 or 1450. This often stabilizes connections that are prone to frequent "kicks."

3. Disable UPnP and Use Manual Port Forwarding

UPnP (Universal Plug and Play) can sometimes "forget" the open port mid-match, causing an immediate disconnect.

Step: Disable UPnP on your router.

Step: Manually forward the following ports for Battlefield 6 / PSN:

TCP: 1935, 3478, 3479, 3480

UDP: 3074, 3478, 3479, 3659, 49152 - 65535

4. Check for "Double NAT"

If you have a modem from your ISP and your own separate Wi-Fi router, you might have two firewalls active.

Action: Ensure your ISP modem is in "Bridge Mode," or connect the PS5 directly to the primary modem to test.

Please let us know if adjusting the MTU to 1473 changes the duration of your session—this is a common "silver bullet" for the specific error code you provided.