- Jun 26, 2020
- 12
- 21
Does your AMD showHey this was a surprising advice, thank you!
I'm on Win10, AMD gpu. DX11 seems to work, some UnrealEngine games seems to crash here when on DX12.
Also I had "Force randomization of images" Off already,
the "Randomize memory allocations" was On and I turned it off w/o restarting, and it seems at least I got to the menu with some rendering artefacts - still crashed tho.
Most of the research/possible fixed I found regarding the LowLevelFatelError where "device was removed" were mostly issues with MSI afterburning or having their GPU OC'd or they resolved it by underclocking it. Other's had their integrated and dedicated GPU showing up in device manger, disabling the integrated one and rebooting resolve it for some. Another resolution was adding an entry in your registry but I don't recall all the steps for that one. Another work around is running the game using DX11, you can see how to do that a few posts back. Then some fixed the issue by uninstalling the game and or GPU drivers, or rolling back to old drivers. There was a lot. Never actually came across an all around solution. I resolved it a while ago on either this game or another Unreal game by disabling my CPU display adapter in device manager I think. And also maybe a similar but slightly different error by following the user's post you quoted.how do I fix this, the game ran fine then crashed about 20 mins in and wont open now. I deleted the save file and reinstalled but the error still pops up but only for this game
It is shown in the Device manager.Does your AMD show
...
u need to turn off ALL programs with overlay. It's a microsoft bug.how do I fix this, the game ran fine then crashed about 20 mins in and wont open now. I deleted the save file and reinstalled but the error still pops up but only for this game
Adrenaline need's to close too and services.It is shown in the Device manager.
I don't have any GPU screen overlays.
The registry entry was some kind of delay - it just delays the crash, but does not help.
It is shown on different games since some time, so different GPU drivers were tested meanwhile.
It is really a baffling issue which I think it is related only to UE and DX12.
or sometimes helping PC reboot. I get this bug on all UE5 games, cuz they using DX12.It is shown in the Device manager.
I don't have any GPU screen overlays.
The registry entry was some kind of delay - it just delays the crash, but does not help.
It is shown on different games since some time, so different GPU drivers were tested meanwhile.
It is really a baffling issue which I think it is related only to UE and DX12.
Read the topic and run it on DX11. I think game running DXR.Totally unplayable for me. I have a I7-8086K + RTX 2060 and even if i set everything to the lowest i get 5 fps lol
Where do I look for the topic?Read the topic and run it on DX11. I think game running DXR.
same here, but windows 10Got error at start, all X64 MSVC++ installed WIn7 x64
Even with my specs being what they are:
Processor: AMD Ryzen 5 3600 6-Core Processor, 3.59 GHz
Installed RAM: 16.0 GB (15.9 GB usable)
System type: 64-bit operating system, x64-based processor, Windows 10
I still needed to turn all the settings down to Medium to even get semi-tolerable fps. I don't know if it's my gaming rig, or if this game is just not optimized as well as it could be. Regardless, I tried it out and played around the opening area for about ten minutes and enjoyed everything I saw. If the game can be optimized to run at a stable fps on High settings at 2160p, this might have the makings of something great.