PS5 bf6 error code 0:85011S or 0:85008S
Hi All, I have been having issue on this for several days now but no resolution as of yet. Every time a login after 10-20 mins more or less, it will show this Error on PS5. I have done everything I could find over the NET including port forwarding, contacting my ISP, and changing my IP to Static but same issue. Im base in UK,
Battlefield 6 freezes the entire Windows system
Hello Battlefield Support, Battlefield 6 repeatedly causes a severe full-system freeze on my MSI Vector 16 HX AI A2XWIG. This is not a normal crash to desktop: the game first drops to only a few (2-6) FPS, then the entire Windows interface becomes unresponsive. The computer may remain in this state for several minutes before recovering, or it has to be restarted. System configuration: Laptop: MSI Vector 16 HX AI A2XWIG CPU: Intel Core Ultra 9 275HX GPU: NVIDIA GeForce RTX 5080 Laptop GPU, 16 GB Operating system: Windows 11 NVIDIA Game Ready Driver: 621.01 WHQL BIOS: E15M3IMS.118 Platform: Steam Graphics settings: Overkill preset (Any) Resolution: 2560 × 1440 Frame Generation: Off Ray Tracing: Off Incident: The problem occurs only in Battlefield 6. I have not observed the same behavior in other demanding games. HWiNFO evidence from the Battlefield 6 session (LOG1.CSV): Immediately before the freeze, at 21:57:06, the GPU was running at approximately 2377 MHz and consuming 146 W. At 21:57:10, the GPU clock suddenly dropped to approximately 180 MHz and power fell to 35.7 W. HWiNFO then stopped recording normally for 108.4 seconds. This was followed by additional logging gaps of approximately 71.1 and 62.6 seconds, confirming that the entire Windows system was unresponsive rather than only the game. The PCIe Recovery Count increased from 188 before the freeze to 191 during the incident. Maximum recorded temperatures were: CPU: 104°C GPU: 87.6°C GPU hotspot: 92.7°C GPU memory: 87°C Comparison test: I tested the latest Call of Duty: Modern Warfare 4 (Or Any Other game) using the same 2560 × 1440 resolution, Ultra graphics preset, Frame Generation disabled and Ray Tracing disabled (LOG2.CSV). Call of Duty remained completely stable for more than 16 minutes (Several Hours) despite placing an equal or greater load on the laptop: Average GPU load: approximately 95% Peak GPU power: approximately 197 W Maximum GPU temperature: 87.8°C Maximum CPU temperature: 104°C Maximum HWiNFO logging interval: approximately 1.25 seconds PCIe Recovery Count remained unchanged throughout the test Battlefield 6 therefore freezes even though the comparison game remains stable at practically identical temperatures and higher GPU load and peak power. This makes a general thermal or power limitation less likely. The sudden loss of GPU clock and power, long system-wide logging interruptions, and increase in the PCIe Recovery Count suggest a possible Battlefield 6/Frostbite/DirectX 12 interaction with the NVIDIA driver, leading to a GPU timeout or recovery event. Windows also recorded a LiveKernelEvent 141 on the same day, although I cannot confirm that the available entry corresponds to the exact 21:57 incident. I did not capture a normal Battlefield 6 APPCRASH or AppHang entry because Windows itself became unresponsive. Please escalate this as a full-system GPU hang rather than a standard application crash. Thank you.gun jammed
why is it when i shoot at certain players my gun fires 1 bullet and stops, or during sustained fire it'll stop firing halfway through the mag? i've tested it on all of the other modes and it hasn't happened once. it ONLY happens in the battle royale modes. i've built up a reflex of flicking my reticle off target and back on because it's the only thing that fixes the issue. also, it only happens in close range fights(10meteres or less) unless i'm using a sniper rifles. with sniper rifles it fires normally but will not zoom in if my reticle is on the players model. i have to again flick my reticle away from the player model and then zoom in and flick back on, so i don't use snipers anymore. from everything i've learned and experienced, it's tied to the reticle being on the player model and the only thing to reset it is to move your reticle off of the player model and back on. yes i have reinstalled and multiple times now have reset my settings because that is the only info i've been able to find. no i'm not forgetting to reload and no i'm not accidentally putting the rifle into semi. there's a reload bug too. it might look reloaded, you didn't swap and the animation played all the way through, but it isn't.
High ping in the game
High ping: 120-210-90. My internet speed is over 300 MB/s—all speed tests showed excellent results. I spent money on the game and can’t play it; it’s impossible. Forza Horizon 6 runs perfectly online—no problems at all. But as soon as I launch an EA game, I run into ping issues. I watched some videos on YouTube and noticed that people in Germany are also complaining about high ping, even though they have good internet. I wrote to EA support via online chat, and they promised to resolve the issue in German as soon as possible. I showed them all the screenshots as proof that my internet router is working fine.Battlefield 6 – Jet Third-Person Camera Stuttering with Classic Controls
Platform: PC Input device: Logitech G PRO X SUPERLIGHT 2 Game mode: Classic Jet Controls Issue: Vertical mouse movement causes camera stuttering in third-person view. I am experiencing an unusual camera issue when flying jets in Battlefield 6. When using Classic Jet Controls (Airplane Control Assists OFF), moving the mouse vertically causes the third-person camera to stutter or briefly freeze whenever I start moving the mouse again after stopping. Interestingly, horizontal camera movement works perfectly. The issue also appears to be speed-dependent: At low aircraft speeds, the camera sometimes works normally. At higher speeds, vertical camera movement starts stuttering. Reducing speed makes the camera smooth again. Troubleshooting already performed: I have tried the following without success: Reinstalled Battlefield 6. Tested with Raw Input ON and OFF. Changed mouse polling rate from 1000 Hz to 500 Hz. Tested different USB ports. Checked FPS – performance remains stable. Tested with a controller – camera movement is perfectly smooth. Tested first-person cockpit view – works perfectly. Tested helicopter third-person camera – works perfectly. Tested jet Freelook – works perfectly. The third-person camera should move smoothly when using vertical mouse input, regardless of aircraft speed. I played Battlefield 6 approximately four months ago, and everything was working perfectly with exactly the same settings and hardware. I returned to the game yesterday, and this issue appeared immediately, despite not changing any settings. This makes me suspect that a recent game update may have introduced this problem. I can provide a gameplay recording demonstrating the issue. Has anyone experienced the same problem? Is this a known bug with Classic Jet Controls?
FSR2 crashing game even if still disabled in settings
Game has been crashing on me, like 2 or 3 minutes after a game started, this is my rig: Processor 13th Gen Intel(R) Core(TM) i5-13600KF (3.50 GHz) Installed RAM 32.0 GB (31.8 GB usable) Graphics card NVIDIA GeForce RTX 5060 Ti (16 GB) Storage 1.73 TB of 2.73 TB used System type 64-bit operating system, x64-based processor Been running crash reports and all points to a FSR2 bug. Does anyone else has the same issue? What caused the crash? The crash is a null pointer write (0xC0000005): ExceptionCode: c0000005 (Access violation) Attempt to write to address 0000000000000000 AV.Type: Write AV.Dereference: NullPtr The faulting instruction: bf6!ffxFsr2ResourceIsNull+0x2ff9fd5 movntps xmmword ptr [rdx],xmm0 At the time of the crash: rdx = 0000000000000000 The game attempted: movntps [rdx], xmm0 which effectively became: movntps [0x0], xmm0 and immediately crashed. Why this is important The symbol name visible in the dump is: bf6!ffxFsr2ResourceIsNull and the stack is almost entirely inside that path: bf6!ffxFsr2ResourceIsNull bf6!ffxFsr2ResourceIsNull bf6!ffxFsr2ResourceIsNull ... That is extremely significant. FSR2 (AMD FidelityFX Super Resolution 2) resources are being referenced during the crash. The game is attempting to write to a resource pointer that is NULL. In plain English: Battlefield 6 tried to use an FSR2-related resource that didn't exist or had already been released. Another major clue Your dump shows: APPLICATION_VERIFIER_LOADED: 1 This means Application Verifier was still enabled when the crash occurred. The failure bucket confirms it: FAILURE_BUCKET_ID: INVALID_POINTER_WRITE_AVRF_c0000005_bf6.exe Notice: AVRF That's Application Verifier. Application Verifier intentionally catches invalid memory usage that might otherwise go unnoticed. What this means for your earlier testing You've already told me: FSR2 disabled DLSS enabled RTX 5060 Ti Driver 621.01 Crashes still occurring This dump suggests one of two things: Scenario 1 (more likely) Battlefield 6 still loads parts of the FSR2 code path internally even when DLSS is selected. Many Frostbite builds do this because: DLSS FSR2 XeSS share parts of the same temporal upscaling framework. So "DLSS enabled" does not necessarily mean FSR2 code is never loaded. Scenario 2 Corrupted shader cache or configuration data is causing a stale FSR2 resource reference. Typical symptoms: Crash during rendering Null GPU resource pointer Reproducible after graphics setting changes What I would do next 1. Remove Application Verifier completely Verify: appverif.exe or: gflags /p Battlefield 6 should not appear in either. If present: appverif /delete /for bf6.exe or through the Application Verifier GUI. Reboot afterward. 2. Delete the Battlefield 6 shader cache Delete any shader cache folders for Battlefield 6. Also clear: %LOCALAPPDATA%\NVIDIA\DXCache and %LOCALAPPDATA%\NVIDIA\GLCache then reboot. 3. Reset the BF6 graphics configuration Remove or rename the BF6 settings folder so the game regenerates it. This eliminates hidden FSR2-related settings left behind from previous configuration changes. 4. Disable all frame generation/upscaling temporarily For one test session: DLSS = Off FSR = Off XeSS = Off Frame Generation = Off Render at native resolution. If stability returns, you've confirmed the issue is in the upscaling pipeline. What the dump does NOT show I do not see evidence of: NVIDIA driver crash nvlddmkm.sys failure RTX 5060 Ti hardware fault DirectX device removed error Overclock instability RAM corruption The crash occurs before any of those indicators appear. My conclusion Based on this dump alone: Battlefield 6 crashed because an FSR2-related rendering resource pointer was NULL and the engine attempted to write through it. The instruction was: movntps [rdx], xmm0 with: rdx = 0 The evidence is strengthened by: bf6!ffxFsr2ResourceIsNull appearing as the faulting symbol and throughout the stack trace. The other thing that jumps out is that Application Verifier was still loaded, so I would make absolutely sure it has been completely removed before collecting the next crash dump. A post-Verifier dump will tell us whether this is a real engine bug or Application Verifier exposing a memory-management issue that normally stays hidden.