Bug: Recurring EXCEPTION_ACCESS_VIOLATION Crashes Post-Sept 9-16 Hotfix
Bug #7304
Recurring EXCEPTION_ACCESS_VIOLATION Crashes Post-Sept 9-16 Hotfix
| Status: | Open |
| Priority: |
High |
| Added by: | Anonymous on September 15, '26 |
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: | |
| Actual Result: |
Game crashed to desktop with EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000000, while playing as Survivor. Part of the same recurring crash pattern already reported under bug #3135 — stack trace includes offsets +21104516 and +21081057 bytes, closely matching the previously reported crash location (+21464466 bytes).
|
| Expected Result: |
Game should continue running normally without crashing to desktop.
|
| Severity: |
Major
|
| Reproducibility: |
Frequently
|
| Platform: |
Epic
|
| Additional Notes & Comments: |
Additional crash addresses observed across sessions: 0x0000000000000078, 0x0000010000000000, 0x00000000006227b5, 0x0000000000000000 — all sharing closely matching top-of-stack offsets (+21464466 / +21104516 / +21081057 bytes). This is a daily recurring issue for me since I stream this game regularly, and the crash interrupts live broadcasts. Already reported under bug #3135 with full technical details (minidump, crash context, driver/system info). System: Windows 10 22H2, i5-9600K, GTX 1050 Ti (driver 582.66), UE 5.7.4 (Udon_HF2), D3D11. Happy to provide additional logs, VOD timestamps, or crash dumps if useful.
|
Steps to Reproduce
No steps to reproduce
Explanation
I wanted to follow up on this bug report because it's significantly affecting my ability to stream this game, which I do daily. The crash (EXCEPTION_ACCESS_VIOLATION, same recurring stack offset pattern: +21464466 / +21104516 / +21081057 bytes) has now happened multiple times across different sessions since the Sept 9-16 hotfix, cutting my live broadcasts mid-match in front of viewers.
I understand priority is based on how many players are affected and the technical severity, not individual requests, but I wanted to flag that this is a daily, recurring issue for me and likely for other content creators streaming the game as well. I've already provided full technical details (minidump, crash context, driver/system info) in bug #3135 and via in-game crash reports.
If there's any additional diagnostic information I can provide to help move this forward, I'm glad to share it. Thank you
Watchers
