Bug: Game Crashes with EXCEPTION_ACCESS_VIOLATION During Matches
270 °C
Bug #7255
Game Crashes with EXCEPTION_ACCESS_VIOLATION During Matches
| Status: | Open |
| Priority: |
Critical |
| Added by: | Anonymous on September 14, '26 |
| Assigned to: |
Unassigned
|
| Due date: | |
| Reported for: | |
| Actual Result: |
Client crashes to desktop with EXCEPTION_ACCESS_VIOLATION in DeadByDaylight-WinGDK-Shipping.exe, or (once) a named engine assertion in MaterialRenderProxy.cpp. Full crash logs and Reliability Monitor reports for all 4 occurrences are in Additional Notes below.
|
| Expected Result: |
Match should complete normally without the client crashing to desktop.
|
| Severity: |
Blocker
|
| Reproducibility: |
Always
|
| Platform: |
Windows Store
|
| Additional Notes & Comments: |
Related to existing tracked issue #3135 (same crash signature, still "Needs More Info"). Troubleshooting already completed without resolving it: verified/repaired game files, disabled all overlays (Xbox Game Bar, NVIDIA, Discord), confirmed GPU driver and Gaming Services current, enabled Resizable BAR in BIOS (increased time-to-crash but didn't eliminate it), cleared NVIDIA shader cache. Hardware: RTX 3080, i7-11700F, 32GB RAM, Alienware Aurora R16. Notable pattern: function offset +22597152 recurs in 2 of 4 crashes, +21103684 in 3 of 4, suggesting one specific reproducible bug rather than random corruption. Also flagging: repeated involuntary crashes have now resulted in a 48-hour leave-game ban, which I'm separately disputing with player support since the disconnects weren't voluntary.
|
Steps to Reproduce
- Launch Dead by Daylight via the Xbox app / PC Game Pass on Windows.
- Queue into and play a normal Killer match.
- Play as Jason and enter omnipresent evil. I have times I can go 10 seconds or 10 minutes into a game. This has been ongoing since the 9/1 update
Explanation
Game repeatedly crashes to desktop mid-match with EXCEPTION_ACCESS_VIOLATION (occasionally a named engine assertion instead), at unpredictable times ranging from 10 seconds to a full completed match. Four occurrences in the past 5 days on build 10.1.2, several sharing identical stack-trace offsets, indicating one reproducible underlying bug.
Watchers
Screenshots
None
Video Clips
None
Log Files
Log files are not visible to you
This project restricts log file visibility.
[ #1 ]
by
[ #2 ]
by
Loading comments...
Loading comments...
2 comments loaded
You need to join this project to comment on issues.
Join Project