Game crash, can't play, during this BP event

Options
Magor57
Magor57 Member Posts: 5

Platform: PC

Type of Bug: Game crash

Description: When I try to start the game, it crashes, I get blackscreen and a error report. Everytime the same

Expected result: Uhh, for the game to start to I can play?

Actual result: Game crash

Reproduction rate: 100%

System Specs (PC only): Intel i7-8700k 3.70 GHz, Geforce GTX 980, 16GB Ram, SSD....

Description of the error report: START

Assertion failed: [File:Unknown] [Line: 198] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0020 - 'INTERNAL_ERROR')


DeadByDaylight_Win64_Shipping {0x0000000000000000} + 25327097 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 25073690 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 24830071 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 24829816 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 29637364 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 29642646 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 29643743 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 29600907 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 35190731 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 35181399 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 40378236 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 40386633 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 24136899 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 35475826 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 35478984 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 25361339 bytes

DeadByDaylight_Win64_Shipping {0x0000000000000000} + 25350204 bytes

kernel32 {0x0000000000000000} + 97236 bytes

ntdll {0x0000000000000000} + 446161 bytes


END.

I need this fixed ASAP, as I am loosing out on the bloodpoints right now. I decided to come back to the game after a year or so and I can't even start it?

0
0 votes

Not a bug · Last Updated

This isn't a bug, this is an issue with your GPU or GPU drivers. Please refer to the technical support subforum for more information.

This discussion has been closed.