Bug: Post-Update Crash with EXCEPTION_ACCESS_VIOLATION after Hotfix 10.1.2
Post-Update Crash with EXCEPTION_ACCESS_VIOLATION after Hotfix 10.1.2
| Status: | Duplicate |
| Added by: | Anonymous on September 13, '26 |
| Reported for: | |
| Actual Result: |
Game crashes to desktop with EXCEPTION_ACCESS_VIOLATION after 25-30 minutes of normal play. Crash offset is identical every time: DeadByDaylight_EGS_Shipping.exe + 21464466 bytes. Memory addresses read differ each time (0x0000000000000078, 0x0000010000000000, 0x00000000006227b5) but the top stack frame offset is always the same, suggesting one recurring fault reached via different code paths.
|
| Expected Result: |
Game should continue running normally without crashing to desktop.
|
| Severity: |
Major
|
| Reproducibility: |
Frequently
|
| Platform: |
Epic
|
| Additional Notes & Comments: |
Additional crash addresses observed: 0x0000000000000078, 0x0000010000000000, 0x00000000006227b5 — all share the same top-of-stack offset (+21464466 bytes). System: Windows 10 22H2, i5-9600K, GTX 1050 Ti (driver 582.66), UE 5.7.4 (Udon_HF2), D3D11. Already verified game files, reinstalled clean, confirmed driver is current, ran sfc /scannow (no corruption), confirmed no third-party overlays loaded (checked minidump module list), corrected GameUserSettings.ini resolution/fullscreen conflicts. Happy to provide further logs if needed.
|
Steps to Reproduce
- 1. Launch Dead by Daylight and join a Trial (Survivor or Killer) 2. Play a normal match — not tied to one specific map 3. Continue playing normally (looping, healing, unhooking, chases, opening lockers, etc.) for roughly 25–30 minutes 4. Game crashes to desktop with EXCEPTION_ACCESS_VIOLATION 5. If possible, try a match with Killer 'The Judgment' using Divine Light power — crash onset lines up with the hotfix that introduced this killer
Explanation
The game was completely stable before the September 9-10, 2026 hotfix (10.1.2, which introduced/adjusted the Killer "The Judgment" and their power "Divine Light"). Right after this update, the game started crashing to desktop repeatedly during normal matches, with EXCEPTION_ACCESS_VIOLATION errors.
I've collected crash logs from multiple sessions, and every single one shows the exact same top-of-stack offset (DeadByDaylight_EGS_Shipping.exe + 21464466 bytes), even though the exact memory address being read is different each time. This strongly suggests one specific recurring bug in the game's code that's being reached through different gameplay situations, rather than random hardware or memory corruption.
I've already ruled out my own system as the cause: verified game file integrity, did a full clean reinstall, confirmed my GPU driver is current, ran a full Windows system file check (no corruption found), and confirmed via the crash dump's loaded module list that no third-party overlays (ReShade, Discord, OBS, etc.) were active at the time of the crashes.
Given the timing lines up exactly with the hotfix, I suspect this is related to the new Killer or their power, though I haven't been able to 100% confirm the Killer was present in every crashed match. Full technical details are in the sections below, and I've attached the minidump and crash context files.
Watchers
