[BUG] Strikepoint win condition broken after Blastpoint update (1.3.2.0)**
**Platform:** PC / Xbox Series X|S / PS5 (observed cross-platform) **Mode:** Strikepoint **Update:** 1.3.2.0 (Blastpoint, June 9) **Summary:** Since the Blastpoint update, Strikepoint round win logic is incorrect. The objective capture state appears to override elimination outcomes. **Observed behavior:** 1. A team that touches the objective (capture progress as low as ~1%) and then wipes ON the point is awarded the round win anyway. 2. Rounds have been awarded to the wrong team even after a full enemy squad elimination. **Expected behavior:** Round win requires either (a) full capture of the objective, or (b) eliminating/downing the entire enemy squad — per pre-update rules. **Impact:** This removes the elimination win condition in practice and forces every round into a rush to the center point. Tactical play (holds, route denial, revive plays) is no longer rewarded. The mode is effectively unplayable as designed. **Repro rate:** Consistent across matches since the update. Requesting acknowledgment and a hotfix or rollback of the Strikepoint scoring change. If this was an intentional design change, please communicate that — but as shipped it reads as broken capture/win logic.873Views16likes46CommentsOuroboros gun sticker unavailable after Gauntlet Tier One Operator 5 completed
Ouroboros (Gauntlet Tier One Operator Challenge 5 reward) weapon sticker will not unlock. In Loadouts → Select Sticker → Ranked, the tile is locked and shows “Currently Unavailable.” The weapon preview can temporarily show the multi card art on the gun, but the sticker cannot be equipped. Challenge 5 shows complete. Restart, extra matches, and rechecking Challenges / Loadouts did not grant it. Reproduced on Xbox Series X, PS5, and PC. Related: https://forums.ea.com/idea/battlefield-6-bug-reports-en/ouroboros-stickers-missing---challenge-5-completed/1358865692Views1like4CommentsBATTLEFIELD 6 SEASON 5
ADDITIONAL TECHNICAL REQUIREMENTS – Beyond Bug Fixes: Technical Transparency, Quality Assurance and Long-Term Game Stability This additional report expands on the technical concerns already submitted regarding Battlefield 6 Season 5. Fixing individual bugs is important, but the development team should also address the underlying processes that allow technical problems to return after major updates. The goal should not simply be to repair the current version. The goal should be to establish a more reliable technical foundation for Battlefield 6. 1. PERFORMANCE REGRESSION MONITORING Every major update should be compared against previous versions. The development team should monitor: Average FPS. 1% low FPS. Frame-time consistency. CPU and GPU utilization. VRAM and RAM consumption. Loading times. Shader compilation. Performance during large-scale destruction. Performance during extended multiplayer sessions. A new update should not introduce measurable performance regressions without investigation and communication. 2. CROSS-PLATFORM PERFORMANCE EQUALITY Xbox, PlayStation and PC should receive dedicated optimization and validation. The objective is not identical graphical settings across different hardware. The objective is consistent gameplay quality, responsive controls and reliable performance within each platform's technical capabilities. 3. HIT REGISTRATION TRANSPARENCY The development team should provide more information about server-side hit registration and synchronization. A dedicated investigation should examine: Server processing delays. Client/server synchronization. Hit confirmation inconsistencies. Packet loss. Latency fluctuations. Network interpolation. Lag compensation. Players need confidence that their actions are accurately represented by the game servers. 4. VISUAL COMPETITIVE READABILITY Visual fidelity should never compromise competitive visibility. Investigate excessive darkness, lighting inconsistencies, visual clutter, smoke density, explosion effects and enemy visibility. Players should be able to identify relevant combat information without removing the visual atmosphere that defines Battlefield. 5. WEAPON BALANCE AND DAMAGE CONSISTENCY Investigate weapon behavior across different network conditions. Review: Damage consistency. Bullet registration. Recoil behavior. Weapon spread. Attachment functionality. Animation synchronization. Differences between weapon statistics and actual in-game behavior. Weapon balancing should be based on measurable gameplay data rather than isolated impressions. 6. ANTI-CHEAT AND COMPETITIVE INTEGRITY Continue improving anti-cheat detection while minimizing false positives. Investigate suspicious gameplay patterns, cheating reports and competitive integrity across all platforms. Players should have confidence that matches are decided by skill rather than unfair external advantages. 7. PATCH VALIDATION AND REGRESSION TESTING Before releasing an update, the development team should validate: Every multiplayer map. Every major game mode. Weapon functionality. Vehicle functionality. Respawn and revive systems. Audio and HUD. Network synchronization. Performance under maximum combat intensity. A fix should not introduce another problem in an unrelated system. 8. PUBLIC TECHNICAL ISSUE TRACKER I strongly recommend that EA maintain a regularly updated public tracker containing: Confirmed issues. Issues currently under investigation. Issues awaiting a fix. Fixed issues. Platform-specific problems. Known workarounds. Relevant patch numbers. This would significantly improve communication between developers and the community. 9. COMMUNITY-BASED REPRODUCTION AND VALIDATION The community should have a clear way to submit reproducible technical reports. Useful information includes: Platform. Game version. Map and game mode. Approximate time of occurrence. Reproduction steps. Video evidence. Network conditions. Whether the problem occurs consistently. Developers could use this information to identify patterns and prioritize fixes. 10. FINAL REQUEST Battlefield 6 deserves a long-term technical improvement strategy. The community does not expect every problem to be resolved immediately. However, it deserves transparency, measurable improvements and consistent communication. Please consider establishing a permanent technical quality program for Battlefield 6, with platform-specific performance validation, regression monitoring, server analysis and a public issue-tracking process. The objective is not simply to release more content. The objective is to build a Battlefield experience that remains stable, optimized, competitive and reliable throughout every season. Content attracts players. Technical quality earns their confidence and keeps the community engaged. Thank you for considering this additional feedback.40Views0likes2CommentsBATTLEFIELD 6 – SEASON 5
COMPREHENSIVE CROSS-PLATFORM TECHNICAL AUDIT AND PERFORMANCE INVESTIGATION Xbox Series X|S | PlayStation 5 | PlayStation 5 Pro | PC Report date: October 31, 2026 Game version: Season 5 – Siege of Vegas Report category: Technical Issues, Performance, Stability and Constructive Community Feedback 1. INTRODUCTION – THE CURRENT STATE OF SEASON 5 I am submitting this technical report to highlight the problems affecting Battlefield 6 following the release of Season 5. Battlefield 6 has the potential to become one of the best large-scale FPS experiences available. However, the current technical situation raises important concerns regarding performance consistency, visual quality, server reliability, hit registration, audio, gameplay systems and overall stability. These concerns should not be interpreted as an attack against the development team. The purpose is to provide structured, constructive feedback that can help identify technical weaknesses and establish clear priorities for future updates. A major seasonal update should improve the overall experience without introducing regressions into systems that previously worked correctly. The problems described below combine officially acknowledged issues, recent community reports and technical areas that deserve further investigation. Not every reported issue has been independently confirmed across all platforms. 2. PERFORMANCE AND FRAME RATE – ALL PLATFORMS Platforms: Xbox Series X|S, PS5, PS5 Pro and PC. Performance consistency is one of the most important requirements in a competitive FPS. The following problems deserve investigation: Unexpected FPS drops during intense firefights. Frame-time instability and inconsistent frame pacing. Micro-stuttering during movement, aiming and camera rotation. Performance degradation during explosions, smoke, destruction and large-scale battles. Sudden performance drops after respawning. Performance inconsistencies between maps. Possible performance regressions following seasonal updates. Inconsistent CPU and GPU utilization. Potential memory management and asset streaming problems. Why this matters A game can display a high average FPS while still feeling unstable. Frame-time spikes can produce visible interruptions, negatively affecting aiming precision, movement and reaction time. Competitive gameplay requires consistent frame delivery, not simply a high FPS number displayed on screen. Requested improvements Investigate frame-time consistency across all platforms. Compare performance before and after Season 5. Optimize CPU and GPU workloads. Investigate memory allocation and asset streaming. Improve performance during destruction-heavy encounters. Validate performance across every multiplayer map and game mode. Ensure that performance improvements do not reduce visual quality unnecessarily. 3. GRAPHICS, TEXTURES AND VISUAL FIDELITY Platforms: Xbox, PlayStation and PC. Visual consistency is essential to Battlefield's immersive experience. The following areas deserve technical investigation: Delayed texture loading. Objects and environmental details appearing at low resolution before becoming sharp. Buildings, vegetation and environmental assets loading inconsistently. Texture streaming interruptions during fast movement. Visual pop-in at medium and long distances. Inconsistent shadow quality. Lighting transitions that make visibility unpredictable. Possible visual artifacts following updates. Inconsistent image quality between different graphics configurations. Excessive visual noise during explosions and environmental effects. Lighting and visibility Lighting should create atmosphere without compromising gameplay readability. Certain environments, especially darker maps and nighttime combat scenarios, deserve additional testing. Players must be able to distinguish enemies, environmental objects and movement without visual interference caused by excessive darkness, inconsistent exposure or poorly balanced effects. Requested improvements Review lighting and exposure calibration. Improve texture streaming and loading priorities. Optimize shadow rendering. Investigate visual artifacts and object pop-in. Improve visibility in dark environments. Preserve visual fidelity across performance modes. Test long-distance visibility and object rendering. 4. NETCODE, HIT REGISTRATION AND SERVER PERFORMANCE Platforms: Xbox, PlayStation and PC. One of the most frustrating problems reported by players is inconsistent hit registration. Community reports describe situations where shots appear to connect but do not produce the expected hit confirmation. Areas requiring investigation include: Hit registration inconsistencies. Delayed hit markers. Inconsistent damage confirmation. Possible discrepancies between client-side and server-side results. Network interpolation and reconciliation. Rubber-banding. Packet loss. Latency fluctuations. Inconsistent synchronization between players. Why this matters In a competitive FPS, players need confidence that the actions they perform are accurately represented by the server. When the visual feedback and server-confirmed outcome appear inconsistent, the player loses confidence in the game's combat system. This directly affects competitive integrity. Requested improvements Conduct a detailed netcode investigation. Analyze server-side hit registration. Improve synchronization between clients and servers. Review interpolation and lag compensation. Improve network diagnostics. Investigate regional matchmaking and latency distribution. Provide clearer information about server performance. Importantly, hit registration problems should not automatically be attributed to internet connections. Server processing, client synchronization and network conditions must be investigated separately. 5. AUDIO SYSTEM AND SOUND POSITIONING Platforms: Xbox, PlayStation and PC. Audio is fundamental to situational awareness. The Season 5 launch was followed by an officially acknowledged issue that could cause audio to cut out until the game was restarted. A hotfix was released to address that particular problem. However, audio quality deserves broader ongoing testing. Areas to investigate: Temporary audio interruptions. Missing or delayed sound effects. Inconsistent directional audio. Footstep localization. Difficulty distinguishing nearby and distant sounds. Audio masking during explosions. Inconsistent environmental sound levels. Synchronization between visual events and sound effects. Requested improvements Review the spatial audio system. Improve directional sound accuracy. Investigate audio prioritization during intense combat. Test audio consistency across different headsets and platforms. Ensure that critical gameplay sounds remain distinguishable. Players should be able to make reliable decisions using audio information. 6. RESPAWN, REVIVE AND GAMEPLAY SYSTEMS Several gameplay systems deserve particular attention. Officially acknowledged issues include reports of revive prompts failing to appear or activate in Battle Royale modes. Vehicle health regeneration has also been under investigation. Additional community feedback concerns inconsistent respawn behavior. Areas requiring investigation Revive prompts failing to appear. Revive interactions not activating correctly. Delayed interaction responses. Players experiencing abnormal respawn states. Respawn positioning inconsistencies. Vehicle health regeneration taking longer than intended. Inconsistent interaction detection. Requested improvements The development team should review the complete interaction process, from the initial player input to server confirmation. Respawn and revive systems must be reliable because they directly influence squad coordination, match flow and competitive fairness. 7. MAP STABILITY – VEGAS STRIP AND AREA 51 The introduction of new maps should expand the experience without compromising stability. An October 22 hotfix specifically addressed stability improvements on Vegas Strip and Area 51. This demonstrates why map-specific technical validation is important. Areas to investigate: FPS consistency in different map sectors. Texture streaming during rapid movement. Environmental asset loading. Performance around destruction-heavy areas. Lighting consistency. Collision detection. Object interaction. Audio propagation. Map-specific crashes and freezes. The development team should conduct separate performance tests for every map rather than relying exclusively on overall game benchmarks. 8. PC-SPECIFIC PERFORMANCE AND STABILITY PC players operate across a wide variety of hardware configurations. This creates additional optimization challenges. Recent community reports describe performance degradation following Season 5 updates, including lower FPS and frame-time instability. Additional reports describe crashes and complete system freezes. These reports require investigation and should not be considered confirmed universal defects. Areas requiring investigation CPU utilization and scheduling. GPU utilization. VRAM consumption. System RAM consumption. Shader compilation. Shader cache behavior. DirectX-related stability. Driver compatibility. Upscaling technologies. Frame generation compatibility. EA AntiCheat compatibility. Full system freezes. Crashes to desktop without error messages. Requested improvements Test different NVIDIA and AMD GPU generations. Investigate performance regressions following game updates. Review shader compilation and cache behavior. Test multiple CPU configurations. Investigate crashes occurring during matches. Improve error reporting. Validate graphics settings and upscaling technologies individually. Publish recommended configurations for different hardware levels. Performance optimization should not depend on owning the newest or most expensive hardware. 9. PLAYSTATION-SPECIFIC INVESTIGATION PS5, PS5 Digital Edition and PS5 Pro. Community reports on the EA Forums include: FPS drops. Stuttering. Delayed texture loading. Black screens. Unexpected crashes. Performance problems during gameplay. These reports do not establish that every PlayStation player is affected, but they justify further investigation. Requested tests Compare PS5 and PS5 Pro performance. Compare performance before and after Season 5. Test both visual and performance modes. Investigate texture streaming. Examine crashes during multiplayer sessions. Test prolonged gameplay sessions. Validate performance after respawning. Console players should receive a stable and consistent experience without having to rely on repeated troubleshooting. 10. XBOX-SPECIFIC INVESTIGATION Xbox Series X and Xbox Series S. Xbox deserves a dedicated technical validation process rather than being treated as an extension of PC testing. Areas requiring investigation: FPS consistency. Frame-time stability. Texture streaming. Memory management. Lighting and visual effects. Audio consistency. Matchmaking stability. Crashes and unexpected disconnections. Performance differences between Series X and Series S. The Series X and Series S have different hardware capabilities. Optimization should account for those differences while preserving stable gameplay. I also request confirmation that Xbox-specific regression tests are included in the quality assurance process before future seasonal updates are released. 11. USER INTERFACE, HUD AND GAMEPLAY FEEDBACK The interface is not merely decorative. It communicates important gameplay information. Community reports following the Season 5 update mention interface problems and delayed or inconsistent visual feedback. Areas requiring investigation: HUD elements disappearing or displaying incorrectly. Delayed notifications. Hit indicator inconsistencies. Scoreboard updates. Minimap visibility. Interaction prompts. Menu navigation. Incorrect or delayed gameplay notifications. The team should prioritize interface reliability because players depend on immediate and accurate information during combat. 12. MATCHMAKING, SERVER REGIONS AND COMPETITIVE FAIRNESS Matchmaking quality is another important part of the overall experience. Areas requiring continuous monitoring: Excessive matchmaking waiting times. Players being placed on distant regional servers. Unstable latency. Inconsistent lobby population. Unbalanced team composition. Unexpected disconnections. Competitive penalties resulting from technical failures. A fair matchmaking system should consider latency, regional availability and competitive balance. Ranked penalties should also be reviewed when a disconnect is demonstrably caused by a game or server failure. 13. QUALITY ASSURANCE AND UPDATE VALIDATION One of the most important recommendations is to strengthen regression testing. Every seasonal update should undergo comprehensive validation before release. A recommended testing process should include: Performance validation Frame-time measurements. CPU and GPU performance. Memory consumption. Long-duration gameplay testing. Visual validation Texture loading. Lighting. Shadows. Environmental rendering. Visibility at different distances. Network validation Server synchronization. Hit registration. Packet loss scenarios. Regional latency. Gameplay validation Respawn. Revive. Vehicle interactions. Weapon attachments. Matchmaking. Platform validation Xbox Series X. Xbox Series S. PlayStation 5. PlayStation 5 Pro. Different PC hardware configurations. A successful update should improve existing systems without introducing new regressions. 14. PRIORITY LEVELS FOR FUTURE FIXES I recommend the following order of priorities: Priority 1 – Critical Game crashes and freezes. Severe FPS drops. Hit registration inconsistencies. Server synchronization problems. Match disconnects. Priority 2 – High Texture streaming. Lighting and visibility. Audio positioning. Respawn and revive failures. Map stability. Priority 3 – Medium HUD and interface inconsistencies. Delayed notifications. Environmental rendering. Minor visual artifacts. Priority 4 – Continuous improvement Graphics optimization. Performance scaling. Matchmaking refinement. Audio improvements. Cross-platform quality assurance. 15. WHY FIXING THESE ISSUES WILL IMPROVE BATTLEFIELD 6 Resolving these problems would produce benefits beyond simply eliminating bugs. It would: Improve competitive fairness. Increase player confidence in hit registration. Deliver smoother gameplay. Improve visual consistency. Strengthen immersion. Reduce frustration caused by crashes and disconnects. Improve squad coordination. Increase the accessibility of stable performance across hardware configurations. Improve player retention. Strengthen the Battlefield community's confidence in future updates. A technically stable game is also a more enjoyable game. New content is important, but technical quality is what keeps players coming back. 16. REQUEST TO DICE AND ELECTRONIC ARTS I respectfully request that the development team: Acknowledge the main technical concerns raised by the community. Publish an updated list of known issues. Identify which problems are confirmed, under investigation or resolved. Provide more transparent information about planned fixes. Investigate platform-specific performance regressions. Improve cross-platform testing. Prioritize critical gameplay and server issues. Continue monitoring community feedback after every patch. I also encourage the team to communicate which fixes are already implemented and which still require additional development. Players appreciate transparency, even when a problem cannot be resolved immediately. 17. FINAL STATEMENT – CONSTRUCTIVE FEEDBACK FROM THE COMMUNITY Battlefield 6 has the foundation to become an exceptional FPS. Its large-scale battles, environmental destruction, maps, vehicles, squad mechanics and overall gameplay identity provide something special within the FPS genre. However, technical consistency must remain a priority. The community is not asking for perfection overnight. We are asking for consistent improvements, transparent communication and a development process that protects the quality of the game. A new season should represent progress, not introduce new frustrations into systems that were previously working. I hope this report reaches the appropriate technical and development teams and contributes to a more stable, optimized and competitive Battlefield 6 across Xbox, PlayStation and PC. The objective is simple: make Battlefield 6 technically stronger, more consistent and worthy of the community that continues to support it. Thank you to the Battlefield development team for reviewing this feedback. #Battlefield6 #Season5 #DICE #EA #Performance #Optimization #HitRegistration #Netcode #Xbox #PlayStation #PC #TechnicalIssues #CommunityFeedback45Views0likes0Comments[CRASH] bf6.exe+0xC7F667 ACCESS_VIOLATION, 100% reproducible offset
Battlefield 6 Crash Report - ACCESS_VIOLATION at bf6.exe+0xC7F667 === SUMMARY === Battlefield 6 crashes reproducibly with an access violation (0xC0000005) inside the game's own executable, at a stable code offset. The failure is a null pointer dereference - the game dereferences an object reference that is 0 without validating it. Four crashes across two separate dates land in the same code region, indicating a deterministic code defect rather than flaky hardware. === ENVIRONMENT === Game build: Steam appid 2807960, buildid 26003479 (updated 2026-10-23 17:59) Game exe: F:\SteamLibrary\steamapps\common\Battlefield 6\bf6.exe (198,225,256 bytes) GPU: NVIDIA GeForce RTX 5060 Laptop GPU (8 GB) Driver: 32.0.16.1714 (NVIDIA, 2026-09-17) CPU: AMD Ryzen 9 8940HX OS: Windows 10 Home China, 25H2, Build 26200.9457 Laptop: ASUS TX Gaming FA608PM, BIOS FA608PM.311 (2026-01-20) Renderer: DirectX 12 === CRASH DETAILS === ExceptionCode : 0xC0000005 (ACCESS_VIOLATION) ExceptionAddress : 0x0000000140C7F667 Faulting module : bf6.exe (base 0x0000000140000000, offset +0x00C7F667) Faulting thread : 33520 (0x82F0) Access type : read Faulting address : 0x00000000000FAFF5 Register state at fault: RIP : 0x0000000140C7F667 RSP : 0x000000007DD7F0A0 RBP : 0x000000007DD7F0F0 RAX : 0x00000000000FAFCD RCX : 0x0000000D96A6CDB8 RDX : 0x0000000D96A6CD88 Interpretation: RAX holds a near-zero value (0xFAFCD). The fault occurs at RAX + 0x28 -> 0xFAFF5, which matches the reported faulting address exactly. A near-null base register with a small struct offset is the signature of a null / invalid object pointer being dereferenced: Object* obj = container[index]; // returns null obj->member = ...; // deref at obj + 0x28 -> crash No bounds-check or null-check occurs between the load and the dereference. Validating the pointer before use would prevent the crash. A secondary pointer (RCX/RDX, both 0x0D96A6xxxx) appears to be a valid heap access, suggesting the code is iterating a container or array and one entry has become invalid. === CRASH HISTORY - SAME CODE REGION, REPRODUCIBLE === 2026-10-25 17:43:28.601 | bf6.exe+0xC7F667 | thread 0x82F0 2026-10-25 17:43:36.681 | bf6.exe+0xC7F667 | thread 0x82F0 2026-10-09 23:14:04.024 | bf6.exe+0xC76F37 | thread 0x239C 2026-10-09 23:14:12.095 | bf6.exe+0xC76F37 | thread 0x239C On 2026-10-25 the game crashed twice within 8 seconds at the identical offset and on the identical thread. The 2026-10-09 pair is likewise identical to itself, about 34 KB from the 10-25 offset - the same call path, shifted by a code change. Determinism is the key signal: hardware faults (VRAM errors, unstable memory, driver defects) produce scattered crash sites. Every observed crash here lands on the same handful of instructions. This is characteristic of a code defect, not a hardware failure. === SYMPTOM === 1. In-game, the rendered scene freezes on its last frame. 2. Camera / view rotation still responds to mouse input - implying the input and camera-update threads remain alive. 3. After several seconds, the game terminates to desktop. This matches a render/draw-submission thread faulting while the input thread continues to run, followed by the built-in crash handler writing the dump and exiting. === POSSIBLE CONTRIBUTING FACTORS (not root cause) === These are not claimed as root cause - the crash is in game code - but they may lower the threshold for hitting the unguarded dereference: - Frame generation. All three FG backends ship in the game directory: nvngx_dlssg.dll (DLSS FG), amd_fidelityfx_framegeneration_dx12.dll (FSR FG), libxess_fg.dll (XeSS FG). Frame generation introduces additional per-frame objects and latency; an object not yet initialized when dereferenced would produce exactly this fault signature. - Ray tracing enabled at time of crash. - Third-party kernel driver present: WinRing0_1_2_0 (C:\Program Files (x86)\LeiGod_Acc\resources\leishenSdk\datacenter\fps_monitor\driver\WinRing0x64.sys, OpenLibSys.org, 2026-08-13). Windows event log shows repeated service startup failures for this driver (2026-10-04, 2026-10-20). - Virtual display adapter: GameViewer Virtual Display Adapter v15.6.5.1990, which expands the DX12 adapter enumeration. - Game updated on 2026-10-23 17:59 (buildid 26003479), two days before the latest crashes. Possible regression. === STEPS ALREADY TAKEN === 1. Uninstalling the third-party accelerator and removing WinRing0x64.sys; disabling the GameViewer virtual display adapter. 2. Disabling all frame generation (DLSS FG / FSR FG / XeSS FG), keeping DLSS upscaling only; disabling ray tracing; clearing the shader cache. 3. If still crashing: clean driver reinstall via DDU with a previous stable branch. === REQUEST === 1. Please use the internal symbol table to map bf6.exe+0xC7F667 (and +0xC76F37) to the containing function - this should identify the exact subsystem without further guesswork. 2. Audit that call site for missing null validation on the dereferenced object. 3. Confirm whether this is a known regression introduced in buildid 26003479. === ATTACHED FILES === CrashDump_2026.10.25_17.43.28.601.mdmp (5,621,202 bytes) CrashDump_2026.10.25_17.43.36.681.mdmp (5,671,933 bytes) CrashDump_2026.10.09_23.14.04.024.mdmp (5,398,082 bytes) CrashDump_2026.10.09_23.14.12.095.mdmp (5,430,245 bytes) All dumps contain full ThreadList (183 threads), ModuleList (189 modules), HandleData, and Exception streams.11Views0likes0Comments[CRASH] bf6.exe+0xC7F667 ACCESS_VIOLATION, 100% reproducible offset
《战地6》崩溃报告 - ACCESS_VIOLATION bf6.exe+0xC7F667 === 摘要 === 《战地6》在游戏自身可执行文件中存在访问违规(0xC0000005)且代码偏移量稳定,可复现地崩溃。失败的原因在于空指针去引用——游戏在没有验证的情况下去引用了为0的对象引用。两个不同日期的四起崩溃发生在同一代码区域,表明是确定性代码缺陷,而非硬件故障。 === 环境 === 游戏构建:Steam appid 2807960,buildid 26003479(更新于 2026-10-23 17:59) 游戏exe:F:\SteamLibrary\steamapps\common\Battlefield 6\bf6.exe(198,225,256字节) 显卡:NVIDIA GeForce RTX 5060 笔记本显卡(8 GB) 驱动:32.0.16.1714(NVIDIA,2026-09-17) CPU:AMD Ryzen 9 8940HX **bleep**作系统:Windows 11 家庭中国版,25H2,构建号26200.9457 笔记本:华硕TX Gaming FA608PM,BIOS FA608PM.311(2026-01-20) 渲染器:DirectX 12 === 事故详情 === 例外代码:0xC0000005(ACCESS_VIOLATION) 例外地址:0x0000000140C7F667 故障模块:bf6.exe(基准0x0000000140000000,偏移+0x00C7F667) 故障线程:33520(0x82F0) 访问类型:已读 故障地址:0x00000000000FAFF5 寄存器故障状态: 安息:0x0000000140C7F667 RSP:0x000000007DD7F0A0 RBP:0x000000007DD7F0F0 RAX:0x00000000000FAFCD RCX:0x0000000D96A6CDB8 RDX:0x0000000D96A6CD88 解读: RAX值近乎零(0xFAFCD)。故障发生在RAX + 0x28 -> 0xFAFF5处,这与报告的故障地址完全匹配。一个带有小结构偏移量的近空基寄存器是被取消引用的空/无效对象指针的签名: Object* obj = container[index];返回空 obj->成员 = ...;在OBJ处deref + 0x28 -> crash 加载和去引用之间不发生边界检查或空检查。在使用前验证指针可以防止崩溃。 一个次级指针(RCX/RDX,均为0x0D96A6xxxx)似乎是有效的堆访问,表明代码正在迭代容器或数组,且其中一个条目变得无效。 === 崩溃历史 - 相同代码区域,可复现 === 2026-10-25 17:43:28.601 |bf6.exe+0xC7F667 |线0x82F0 2026-10-25 17:43:36.681 |bf6.exe+0xC7F667 |线0x82F0 2026-10-09 23:14:04.024 |bf6.exe+0xC76F37 |线程0x239C 2026-10-09 23:14:12.095 |bf6.exe+0xC76F37 |线程0x239C 2026年10月25日,游戏在8秒内两次以相同的偏移量和相同的线程崩溃。2026-10-09 的通话对同样与自身相同,距离 10-25 偏移约 34 KB——同一呼叫路径,但因代码变更而偏移。 确定性是关键信号:硬件故障(显存错误、内存不稳定、驱动缺陷)会导致零散的崩溃点。这里观察到的每一次坠毁都落在同样的几条指令上。这是代码缺陷的特征,而非硬件故障。 === 症状 === 1. 在游戏中,渲染的场景在最后一帧会冻结。 2. 摄像机/视角旋转仍响应鼠标输入——这意味着输入线程和摄像机更新线程依然活跃。 3. 几秒后,游戏会切换到桌面。 这与渲染/绘制-提交线程错误相匹配,输入线程继续运行,随后内置崩溃处理程序写入转储并退出。 === 可能的促成因素(非根本原因)=== 这些不被认为是根本原因——崩溃是游戏代码——但它们可能会降低触发无保护去引用的阈值: - 帧生成。游戏目录中所有三个FG后端都发货:nvngx_dlssg.dll(DLSS射击)、amd_fidelityfx_framegeneration_dx12.dll(FSR射击)、libxess_fg.dll(XeSS射门)。帧生成引入了额外的每帧对象和延迟;未初始化的对象在被取消引用时会产生完全相同的错误签名。 - 在事故发生时启用光线追踪。 - 第三方内核驱动:WinRing0_1_2_0 (C:\Program Files (x86)\LeiGod_Acc\resources\leishenSdk\datacenter\fps_monitor\driver\WinRing0x64.sys,OpenLibSys.org,2026-08-13)。Windows 事件日志显示该驱动程序的服务启动多次失败(2026-10-04,2026-10-20)。 - 虚拟显示适配器:GameViewer 虚拟显示适配器 v15.6.5.1990,扩展了 DX12 适配器枚举。 - 游戏更新于2026-10-23 17:59(buildid 26003479),比最新崩溃早两天。可能是倒退。 === 已采取的步骤 === 1. 卸载第三方加速器并移除WinRing0x64.sys;禁用GameViewer虚拟显示适配器。 2. 禁用所有帧生成(DLSS FG / FSR FG / XeSS FG),仅保留 DLSS 升频;禁用光线追踪;清除着色器缓存。 3. 如果还是崩溃:通过DDU重新安装驱动,使用之前稳定的分支。 === 请求 === 1. 请使用内部符号表将 bf6.exe+0xC7F667(和 +0xC76F37)映射到包含的函数——这样可以准确识别子系统,无需额外猜测。 2. 审计该调用站点是否缺少对被引用对象的空验证。 3. 确认这是 buildid 26003479 中引入的已知回归。 === 附件文件 === CrashDump_2026.10.25_17.43.28.601.mdmp(5,621,202字节) CrashDump_2026.10.25_17.43.36.681.mdmp (5,671,933 字节) CrashDump_2026.10.09_23.14.04.024.mdmp (5,398,082 字节) CrashDump_2026.10.09_23.14.12.095.mdmp (5,430,245 字节) 所有转储都包含完整的 ThreadList(183 个线程)、ModuleList(189 个模块)、HandleData 和 Exception 流。46Views0likes1CommentInvisible player cards and weapons images while in game
I play on xbox series s and I cannot see any in game ui icons like weapon images, player names or player cards. this bug started with season 5 and all my friends on xbox series s have the exact same issue I tested it on ps5 and it works fine. How can we fix this Added screenshots12Views0likes0CommentsOpen Series: incorrect APAC region blocks PT player from joining EMEA team
Hello, I’m helping my friend ze_maximoPT resolve a region mismatch that prevents him from joining an EMEA team in the REDSEC Open Series. He is Portuguese and lives in Portugal. His Battlefield Esports registration correctly shows “Europe, Middle East, and Africa” and “Portugal”. However, Battlefy identifies his account as “Asia Pacific” and blocks him from accepting our team invitation. On 13 October, Battlefield support confirmed that his region had been corrected to Europe, but the error persists. We have contacted both Battlefy support and the Battlefield competition support Discord. Each has referred us to the other, leaving the issue unresolved. Could an EA moderator please escalate this to the appropriate technical or esports team to investigate why the two systems show different regions? EA ID: ze_maximoPT Team: XIII LUSITAN PT Correct region: EMEA Incorrect region displayed by Battlefy: Asia Pacific We can provide further information privately if needed. Thank you.17Views0likes0Comments