Bug: Game Crashes Post-September 9-10 Hotfix with EXCEPTION_ACCESS_VIOLATION
Game Crashes Post-September 9-10 Hotfix with EXCEPTION_ACCESS_VIOLATION
| 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. Crash addresses read differ (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 across different sessions (for reference, in case they help correlate with other reports): - 0x0000000000000078 - 0x0000010000000000 - 0x00000000006227b5 All three crashes share the identical top-of-stack offset: DeadByDaylight_EGS_Shipping.exe + 21464466 bytes. System specs at time of crash: - OS: Windows 10 22H2 (Build 19045) - CPU: Intel i5-9600K - GPU: NVIDIA GeForce GTX 1050 Ti (4GB VRAM), Driver 582.66 - Engine Version: UE 5.7.4 (Udon_HF2 build) - RHI: D3D11 Troubleshooting already completed without resolution: - Verified game files via Epic Games Launcher - Ran sfc /scannow (no corrupted system files found) - Cleared DirectX shader cache - Full clean uninstall + reinstall - Confirmed GPU driver is current for this legacy GPU branch - Confirmed no third-party overlays/injected DLLs present at crash time (checked minidump module list directly — no ReShade, Discord, OBS, RTSS, etc.) - Corrected resolution/fullscreen mode settings in GameUserSettings.ini Happy to provide any further logs or information needed to help track this down. Thank you for looking into it.
|
Steps to Reproduce
- 1. Launch Dead by Daylight and join a Trial (Survivor or Killer) 2. Play a normal match — crash is not tied to one specific map or action 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 لو طلعتلك خانة ثانية رقم 2، زيد عليها: "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
Screenshots
None
Video Clips
None
Log Files
Log files are not visible to you
This project restricts log file visibility.