UPDATE: Upon further investigation, we are happy to say that no members of the Dead by Daylight forums had their data compromised in the breach over the past weekend. All passwords have been reset as a precautionary measure, please be sure to update your password as soon as possible using the password reset button.

Sorry for any confusion this may have caused!
We have updated our Forum Rules. Please take a moment to read through them: https://forum.deadbydaylight.com/en/discussion/87004/
This section is used to report issues on PC specifically.

*** Please use the search box in upper right to see if your bug has already been reported first! ***

If this is an issue that occurs on all platforms, please post your report in the most fitting category instead.

When reporting a bug, please use the following template:

Description of the issue:
Steps to reproduce (if possible):
How often does this occur:

Please be sure to attach any screenshots, videos, or logs (if on PC) that you may have if you believe they could help us find the issue.

crash upon launching killer lobby

powerbatspowerbats Member Posts: 7,071

I'd just finished a killer match and went to launch another killer lobby when it immediately crashed me to the desktop.

Access violation - code c0000005 (first/second chance not available)

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 12431419 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 12431545 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 12431545 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 12431545 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 12737740 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 12644384 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 12743930 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 12809440 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 12808186 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 17989693 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 17987357 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 11139255 bytes
DeadByDaylight_Win64_Shipping {0x0000000000000000} + 11097820 bytes
kernel32 {0x0000000000000000} + 77876 bytes
ntdll {0x0000000000000000} + 463985 bytes

There was about 5-10 seconds or so from the time I left the post game lobby to launching another one when it crashed so not sure if that helps any. @MandyTalk

Comments

  • MandyTalkMandyTalk Mod, Co-ordinator Posts: 4,207

    @powerbats I've brought it up with the team, as you've seen yourself there've been a few reports made recently of the same thing. Will let you know as soon as I hear anything - I've had it too as a survivor, crashed with same error message when in the loading screen.

  • MandyTalkMandyTalk Mod, Co-ordinator Posts: 4,207

    @powerbats are you using reshade or sweetfx by any chance? I've heard these can cause the same error message.

  • powerbatspowerbats Member Posts: 7,071

    @MandyTalk said:
    @powerbats are you using reshade or sweetfx by any chance? I've heard these can cause the same error message.

    What are those from? I might be without knowing it.

  • MandyTalkMandyTalk Mod, Co-ordinator Posts: 4,207

    They are overlays to improve graphics on the games

  • powerbatspowerbats Member Posts: 7,071

    @MandyTalk said:
    They are overlays to improve graphics on the games

    I don't use either of those but do use Steam overlay which I know caused FPs issues or used to in some games before.

    I also use GeFore Experience but don't use it to launch the game and the settings aren't any different.

  • MandyTalkMandyTalk Mod, Co-ordinator Posts: 4,207

    When it happens again, I need the .log file from immediately after the crash if that's possible?

  • powerbatspowerbats Member Posts: 7,071

    @MandyTalk said:
    When it happens again, I need the .log file from immediately after the crash if that's possible?

    Will do

  • MandyTalkMandyTalk Mod, Co-ordinator Posts: 4,207

    Thank you @powerbats it's appreciated <3

Sign In or Register to comment.