Contact game developer, it’s there responsibility to give you support of published game. D3D Internal Error suggest there something with either DirectX or Driver, that all that can be deduced from this. D3D simply tells UE4 that internal error happened and UE4 just say “ok bye bye” and simply aborts. Call stack you posted is useless without debug symbols which game developer has.
You may try to download Ue4 editor with debug symbols (it’s in installation options) run some demos and see if crashes too, it will give more readable call stack and we may able to deduce something more out of it.
If you run on laptop common D3D crash cause with UE4 is automatic GPU switching between CPU-integrated GPU and seperate GPU.
If you OC CPU you may want to try to run it in normal stack clock and see what happens.