Bug: Random Crashes at Code Offset +21439522 Despite Configuration Changes
Bug #6546
Random Crashes at Code Offset +21439522 Despite Configuration Changes
| Status: | Duplicate |
| Added by: | Anonymous on August 27, '26 |
| Reported for: | |
| Actual Result: |
game crashes and closes out, bringing up error report screen.
|
| Expected Result: |
Game finishes as normal
|
| Severity: |
Blocker
|
| Reproducibility: |
Frequently
|
| Platform: |
Epic
|
| Additional Notes & Comments: |
All overlays have been turned off. Using a 4k tv as monitor. This just started with the Judgement update. Its not letting me see which log files uploaded successfully, so let me know if you need more.
|
Steps to Reproduce
- No fixed repro steps
- crash occurs randomly during normal matches, not tied to any specific action.
Explanation
Crash: same code offset, random address each time. Ruled out: driver frame-gen (AMD Fluid Motion Frames 2.1, AMD FSR Frame Generation), in-game FSR, exclusive vs windowed fullscreen, all overlays (Adrenalin metrics overlay, Discord) — all disabled/tested individually, crash persists under every configuration. All crashes trace to the same code offset (+21439522) in DeadByDaylight_EGS_Shipping, reached via different call paths (RenderThread 0 and various Background Worker threads), each time dereferencing a different invalid address (0x8, 0xFFFFFFFFFFFFFFFF, 0x100000, 0x0000030003000002) — consistent with a race condition or uninitialized read rather than a fixed trigger. Occurred in 5 separate sessions. Hardware: AMD Ryzen 7 9800X3D, AMD Radeon RX 9070 XT (16GB VRAM), 32GB RAM, Windows 11 25H2. Platform: Epic Games Store client.
Watchers
Screenshots
Video Clips
None
Log Files
Log files are not visible to you
This project restricts log file visibility.