[9950X3D dual-CCD X3D] Javelin prevents core parking — still unresolved

Hi,

I wanted to bring this up since it is sill unresolved. EA_Rtas​ EA_Leeuw​ 

System:

- CPU: AMD Ryzen 9 9950X3D (dual-CCD: CCD0 = 3D V-Cache, CCD1 = frequency)

- GPU: NVIDIA RTX 4080

- RAM: 32 GB DDR5-6000 (EXPO)

- Board: ASUS ROG STRIX B850-E GAMING WIFI (latest AGESA)

- OS: Windows 11 Pro, Balanced power plan, Xbox Game Bar "Remember this is a game" enabled, AMD chipset driver installed, BIOS CPPC/Preferred Cores = Driver

The problem:

On dual-CCD X3D CPUs, Windows + the AMD 3D V-Cache Optimizer are supposed to

park the non-cache CCD (CCD1) for games so the title runs on the V-Cache die

(CCD0) for best performance. This works correctly in the BF6 MENU/LOBBY — only

CCD0 is active, exactly as intended.

As soon as I load into a multiplayer match, CCD1 becomes active and the game

runs across BOTH CCDs. Core parking no longer engages. This behavior is tied to

the Javelin anti-cheat, which only runs in multiplayer — the single-player

campaign parks correctly. The same behavior is reported across other EA titles

using Javelin, and across multiple X3D CPUs (7950X3D, 9900X3D, 9950X3D).

Why it's still not "solved":

- The standard, AMD-recommended setup (chipset driver, CPPC=Driver, Balanced

power plan, Game Bar tagging) does NOT fix it in multiplayer — Javelin overrides

the scheduler at a low level.

- The only "workarounds" are unacceptable for a shipping AAA title:

* Third-party affinity tools (e.g. Process Lasso) are ignored/reset AND risk a

false-positive anti-cheat ban, so they are not a real option.

* Disabling CCD1 in BIOS "works" but cripples the CPU for everything else and

causes system instability for some users.

* user.cfg thread-count tweaks give inconsistent results and don't reliably

keep the game on CCD0.

Impact:

Measured/community-reported ~5-10% FPS loss in CPU-bound scenes, plus higher

CCD1 temperatures and power draw — the opposite of how an X3D chip is designed

to behave in games.

Request to EA:

This is a software/anti-cheat scheduling conflict, not an end-user hardware or

config problem. Please work with AMD so Javelin respects the OS/AMD core-parking

behavior for dual-CCD X3D CPUs (or provide an officially supported way to pin BF6

to the V-Cache CCD without triggering anti-cheat). A large and growing number of

X3D owners are affected. Could we please get an official status update on whether

a fix is in progress?

Thank you.