Re: cannot launch game, get splash screen then black box, THEN CRASH back to EA App

Hi there kind support person!

Had no issues with this until the Redsec/Season 1 update today. My game loads into the start screen but when I click start and begin the shader compilation process, my CPU usage spikes and slows the background video playback to a crawl while updating the progress bar very slowly until eventually it crashes my PC and then very slowly returns control back to me on the desktop. Search for "compilation" in the recent posts on the Battlefield subreddit and you'll see others are affected by this issue as well. Specs are below. Need a resolution for this, thanks!

Processor    AMD Ryzen 9 3900X 12-Core Processor 4.28 GHz

GPU AMD Radeon RX 7900 XT

Game installed on a Samsung SSD 990 PRO 4TB

RAM    16.0 GB

Windows 11

Hello,

I have the same issue with the difference that the game closes rather quickly instead of staying frozen : about 30s after being stuck on 39.06%, the game closes.

I also had no major issue in beta or since release (played just fine a few days ago, before the patch).

DxDiag given for comparison

Im having issues ever since the recent updates my shaders load to 56.55% then throws me back to my desktop saying its an issues on their end and to try again in a little while, ive tried again after 15 hours for my shaders to shoot instantly to 56.55% and throws me vck to desktop this time without the error. ive repaired the files and still no luck so i decided to unistall the game just in case the files have corrupted and it wont unistall via the EA app nor can io deleted it from my settings, can anyone give me any advice why this is happening?

The exact same here as well, same number of 39.06%. I've seen somewhere that it may be tied to AMD graphics card. I am running a 5700XT.

im getting to 56.55% before it closes to desktop, i downloaded redsec on steam to have the same issue, 3 files where corruted tried to unitall the game and not having no luck via the EA app nor via my computer 

I am not, so the problem might not be related to the brand of GPU :/

ive had the same issue since the recent updates via the EA app and even steam, i got 3 corrupted files, EA app wont allow me to unistall the game and nor can i unistall it via my actual computer. dosnt matter how many times i repair the files still get the same results. i get an error message saying its an issue on their end and to try again in a little while, i debating getting a refund tbh 

inertiaoa​ Nicola931​ Greeds96​ fecba08​ 

This fixed it on my machine: had to specifically delete the shader cache files from my Battlefield 6 folder in local app data (C:\Users\[Username here]\AppData\Local\Battlefield 6\cache). Go to windows explorer, search for %appdata%, go back one folder to the main appdata folder, then go the Local folder, then open Battlefield 6 folder. Delete the files called 6803938.PcDx12, cache.manifest and gpustats.dat then try running the game again. My shaders compiled way quicker and then I loaded in without any issues.

Haven't tested super thoroughly but this lets you load in so that's reason enough to pop champagne lmao. Godspeed y'all!

inertiaoa​ Nicola931​ Greeds96​ fecba08​ 

FIXED IT, here's what worked for me: try deleting your shader cache files from your Battlefield 6 folder in App Data.

The direct file path to it in Windows is C:\Users\[Your Windows Username Here]\AppData\Local\Battlefield 6\cache or you can go into File Explorer and type %appdata% into the search bar, go back one folder to the main AppData folder and then open the Local folder, then open the Battlefield 6 folder and in the cache folder: delete 6803938.PcDx12, cache.manifest, and gpustats.dat. I play using DirectX 12 so the file names might be slightly different if you play using DX11 but delete all of those and then try loading game again.

For me, the shader comp was then way quicker and I could load into the game without any issues. Played a bit of Redsec and haven't had any more trouble so give this a try! Godspeed y'all!

JamesGang95​ I tried this and it didn't work

Still having the same issue after trying everything...

I'm having the same exact issue, tried the fix mentioned below but it didnt work. 

and I dont think EA has any knowledge about this issue, I dont see any fix .

Negative effect for me😅😭