[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.
EAAntiCheat.GameServiceLauncher.exe crashing Error code: c0000409 (7)
Hi, After updating BF6 to season 4 I started to experience crashes to the anticheat. I was able to launch game twiece (once after Windows and AMD driver update) and second one without any particular reason but I am now out of luck and it is no longer working. I tried to fix it with EAAntiCheat.Installer . Reinstalling, updating, deleting and checking the consistancy of the game files. I tied to delete eaanticheat files from several directories (thinking that there may be some collisions), edited the access level for this executable to read only. I uninstalled my graphics card driver and installed fresh once. And at the end I reinstalled whole game. Nothing helped and as I dont have tools and idea what could I do more about it (I tried to use procmon, but it wasnt helpful) I write this post here. Could you help me?
Battlefield 6 BSOD caused by EA Javelin AntiCheat (eaanticheat.sys)
Hello, I am experiencing a reproducible BSOD every time I launch Battlefield 6. The game never reaches the main menu. It crashes during the initial loading screen (black screen) shortly after EA AntiCheat starts. I checked everything except formatting pc or doing bios update (Cant do this cause of the manufacturer of my laptop doesnt shows motherboard manufacturer). Also did checkups with the help of ai like checking the debugs of dumpfiles, i attached them below. System CPU: Intel Core i7-11800H GPU: NVIDIA GeForce RTX 3060 Laptop Windows: 11 25H2 (Build 26100.x) Secure Boot: Enabled TPM: Enabled and ready UEFI: Enabled BSOD The Windows kernel dump consistently reports: Bug Check: PAGE_FAULT_IN_NONPAGED_AREA (0x50) Faulting module: eaanticheat.sys Failure Bucket: AV_eaanticheat!unknown_function The crash always occurs inside: eaanticheat.sys +0x1A4E317 The relevant instruction is: mov r9d,dword ptr [rbx+rax+8] The anti-cheat driver attempts to read invalid memory and Windows immediately bugchecks. EA GameService crash dump The EA GameService dump shows an independent crash: Process: eaanticheat.gameservice.exe Exception: 0xC0000005 (Access Violation) Fault: Attempt to read address: FFFFFFFFFFFFFFFF Stack: ntdll!RtlpCollectFreeBlocks ntdll!RtlpFreeHeap RtlFreeHeap eaanticheat.gameservice.exe This suggests GameService is attempting to free or access an invalid heap pointer before the kernel driver crashes. AntiCheat version GameService: Product: EA Javelin AntiCheat Internal Name: skyfall Version: 1.0.14592691 Timestamp: July 17, 2026 Kernel driver: eaanticheat.sys Timestamp: July 17, 2026 Troubleshooting already performed I have already tested the following without any change: Reinstalled Battlefield 6 Reinstalled EA App Repaired game files Updated NVIDIA driver Updated Intel chipset driver Updated Intel Management Engine Updated LAN driver Updated audio driver Disabled Hyper-V Disabled Memory Integrity Driver Verifier disabled Secure Boot enabled TPM enabled UEFI enabled Other games, including EA FC 26, run normally and do not trigger BSODs. The issue started after golmud railway update. Battlefield 6 worked correctly previously. The Windows kernel dump and the EA GameService dump both point to EA Javelin AntiCheat components rather than a random third-party driver. Thank you.
Should I be able to see previous ban appeal cases?
I have 2 closed cases on my account on my ban appeal. I haven't made any ban appeals in that span of time. In fact. I wasn't playing Battlefield in those months. When trying to view them. There is no information other than the date. I do not even know the nature of the appeals. Is this normal for closed cases? I am trying to figure out if someone else had access to my account. These 2 cases are a mystery to me. I've been trying to reach EA support through tickets and live chat (since June 19). But haven't been able to reach a human being. So I'm asking here.
Unknown Error 0:51009S:11468332130:1073807360Q
Whenever I launch the game I het Unknow Error 0:51009s:11468332130:1073807360q as it tries to connect to the servers. I have now been talking to support for 3+ hours and they told me to pos here as they have no fix for this 'bug' I did the entire slew of troubleshooting steps suggested. Game was working fine yesterday, no hardware or software changes since then.
Matchmaker constantly placing me with out of region players
Matchmaking keeps placing me with players from far East-Asia despite the fact that I am in England. I’m really not pleased about this and I mentioned it before in BF Labs. It has been weeks now and if this is what I am going to get for the rest of season 3, 4 and beyond then I am not going to be playing Battlefield 6, and before anyone says it doesn’t give an advantage that is not the point! It clearly causes the game to malfunction such that the shooting experience becomes inconsistent and you cannot compensate for it by changing how you play; near or far I’ve been blighted with 1 frame deaths, null shots, wonky third person animations that make the enemy players look like they have aimbots and received damage from players before they step around the corner. I can only imagine the same is happening for my opponents. If this isn’t to do with the networking modules in the software and more to do with something else in the game then so be it, but never have I heard anyone think that it is a great idea to go and encourage players of an FPS multiplayer game to play with others so far out of region by putting together a system that does that constantly or tolerates it through VPN use/network exploits, even temporarily this is unacceptable. Never did this happen with Battlefield 3 or Bad Company 2, never did I have this kind of experience when I played other online games. So why is this now the standard? Why is this considered acceptable practice for your paying customers and why should I spend my money on future Battlefield titles or even EA products in general? *Edit - here is a Reddit post that I made containing images showing the match up (I did not post the images here because of the name and shame policy): https://www.reddit.com/r/Battlefield/comments/1v5e5t2/the_state_of_battlefield_6_matchmaking_from/
Javline anticheat encountered error (7)(1053)
I am stuck with this error EA help desk said they can’t help I have tried whatever I saw online Windows update, Bios update, drivers update, reinstalling anti cheat multiple times, running them as administrator, reinstalling, moving save files locations I have ran out of options I could find I want to play this game Has anyone encountered this issues? If so how did you fix it? Any ideas?
Complete Audio Crash
BF6 Full Audio Crash Hey everyone, I’ve been dealing with a **persistent and fully reproducible system-wide audio crash** in *Battlefield 6*. After about **1–2 minutes of gameplay**, there’s a short **audio glitch/pop**, and then **all sound stops completely** — not only in the game, but across Windows. From that moment, Windows can’t output any sound at all, and I have to **reboot my PC** to get it back. # 🧠 My setup * **•Audio interface: Focusrite Scarlett 2i2 (tested 3rd & 4th Gen)** * •Driver: Focusrite USB ASIO (latest version 4.120.11) * •Routing: VoiceMeeter + OBS (for streaming) * •OS: Windows 11 (22H2) * •Battlefield 6: Latest release (issue also occurred in beta) # ⚙️ What I’ve already tried * •Updated Focusrite drivers and firmware * Switched between ASIO, WDM, and WASAPI drivers in VoiceMeeter * Forced all devices (VoiceMeeter + Focusrite) to 48 kHz sample rate * Disabled Spatial Audio and Dolby Atmos * Disabled Exclusive Mode on all playback devices — no sound at all * Re-enabled Exclusive Mode — sound works, but crash returns * Forced Battlefield output to “VoiceMeeter Input (VB-Audio VAIO)” instead of default * Tried launch options: -dx11 and -nosounddevicechange * Increased and decreased buffer sizes (128 → 512 samples) * Verified issue persists even with OBS and Discord closed # 🔍 Symptoms • Works fine for 1–2 minutes of gameplay • A single audio pop/crackle, then total silence • Sound devices disappear from Windows control panel • VoiceMeeter shows red “Device Lost” on Focusrite ASIO • Replugging the interface or restarting the audio engine does not help • Only a full reboot restores functionality # 🧩Osservation • Happens only in Battlefield 6 (no issues in other DX12/DX11 titles) • Same behavior was reported back in Battlefield 2042 with Focusrite hardware • Possibly linked to EA Anti-Cheat (kernel-level interference with audio drivers) • Appears right when Frostbite engine switches or reinitializes output devices • Occurs on both DirectX 11 and 12, with or without audio spatialization It seems the **Frostbite engine** is trying to change audio format or re-initialize the device dynamically, conflicting with **ASIO / exclusive-mode drivers**. This also happened in *Battlefield 2042*, but here it’s even worse — it kills the whole Windows audio stack until reboot. # 💡 What would help * Option to **disable device re-initialization / format switching** in game * A toggle to **force stereo 48 kHz shared mode** * Confirmation if EA Anti-Cheat or the new audio engine is interfering with USB driver stacks Is anyone else with a USB audio interface (Focusrite, Behringer, MOTU, etc.) experiencing this? Any workaround other than rebooting every time would be greatly appreciated. [CM: Moved from BF6 IT forums to EN. Please post in the right language boards]
