D3D Device Being lost

After buying a New GPU im was very happy to play CE now perfectly… than i have 6 Months gaming berak… i come back and this D3D Device Lost (INTERNAL ERROR) shoots me down… worked on this GPU and GPU Driver version fine @ may 2022.

im shure the problem is the VRAM Managing from the Client or the Engine… all ist fine if the GPU uses less than 10GB Vram. above 10GB instant crash.

the GPU works fine in UE4 and other UE Games. (with maximum 16GB Vram usage)

have tryed all things that google can find for me… nothing work.

I read the other Topics in this forum… Thanks for nothing :slight_smile: please switch the UE Version for the game. thanks or make it New and Use UE5… Its an Rare problem but save NOT a problem of the user systems. Happens ONLY in Conan Exiles

Not going to happen. I hope you will find a solution to your problem. Best of luck.

1 Like

then almost 5 years together come to an end. I’ve invested too much time in solving problems with this game, I was hoping that with 3.0 the beta would finally be over… apparently not

Hello @Winimarik!

Thank you for reaching out to us. Here are some ideas of what could impact or provide that error message. Please try the following:

  • Update Windows (no need to change to Win11 though, just update the current version you have)
  • Update Graphics Driver
  • Change to Default Graphics Card
  • Verify files in Steam
  • Disable NVIDIA Geforce/ AMD Radeon Experience Battery boost
  • Disabling Antivirus/Firewall Software
  • Turn off Overclocking and SLI Technology
  • Reduce PC’s energy consumption

Make sure to reach out if the issue still persists.

We hope this helps!

1 Like

im done. after a terrible night. tested ~50 driver versions. one from dez 2021 works…

1 Like

The problem still exists. Sad World…

You can solve it by setting the effect settings to medium or lower. It doesn’t look as nice anymore but it has already helped some players.

After a long period of testing we were able to narrow down the problem a little.
It’s because of about 90% of all mods that offer placebles, as soon as a placeble has been placed and you are nearby you immediately get the crash and the error message.
So far it has only occurred with newer AMD cards, I think from the RX6000+ onwards. A Vega56 or RX5700xt had no problems in our test. And the problem only exists in Conan countless other Unreal games run wonderfully. And no… before someone else comes up with some uninstall tips or something like that. It’s not a Windows or driver error… we have tested almost everything.

Sorry for that english :expressionless:

For amd processors, there is a docp setting in the bios that is often the culprit on the newer chipsets. It most likely is that and not the card itself unless the card is paired with an intel.

Thanks but that was also tested as well as most other overclocking and underclocking settings and over and undervolting. Also tested fresh windows with and without Adrenalin Software. Tested 6 different pcs in 4 different households. The only thing they have in common is an RX 6000 series or better. If you install an older RX there are no problems

Are you sure your psu isnt getting drug down since its only for certain graphics levels that it crashes? Maybe its either failing or underpowered.

Yes, a Rog Thor 850w is more than sufficient and my girlfriend has the 1100W and has the same problems.
So I think it’s not a power problem.

On my system and the highest settings Conan draws under 350W at 144fps and because the game isn’t optimized very well the graphics card gets bored in most areas, especially in player buildings, where the fps and power consumption drops significantly again.
Other Unreal games draws much more power without problems.

And it’s not the other hardware either the problems only appear after the graphics card upgrade.

Asus tuf x570 plus wifi
Ryzen 7 3700X
2x 1TB m.2
Win 11

Assim espero eu amo UE4 XD :star_struck:

Você pode estar frustrado por estar com uma ferrari andando mais lento que uma carroça por não saber configurar sua nova máquina… Se acalme e entenda sua GPU antes de jogar :thinking: :brazil:

That its hardware related isnt surprising as d3d is a hardware issue that impacts unreal at the base level. Its not conan; its the interplay of the hardware. There’s even a generic steam note on the subject because it happens across all unreal games if the hardware is acting up. There’s nothing in the game that can be patched to address it because its not a “CE” bug; its pure hardware and unreal, much like renderthread errors. Something in the hardware with those video cards and settings is the issue and the solution is contained there, either in a driver supplied by amd or interplay between the cpu, motherboard and video card.

Sounds logical.

Well, as long as only a handful of players encounter this problem, fixing it won’t be a big priority. But since more players are upgrading their PCs every day, a small bug like this can end up making a lot of noise if you don’t take care of it quickly. And I think that the impetus here lies with FC as it doesn’t appear anywhere else in this form.

When you recieve D3D crash, check your event log.

If you recieve following warning “display driver nvlddmkm stopped responding and has successfully recovered”, open your bios settings and turn off XMP.

XMP/D.O.C.P is off. And there are no Windows or driver errors in the logs. As I said, the whole thing only comes from the engine and only in Conan.
Here is the conan log after the effect settings are increased, which causes the crash.

[2023.10.01-12.38.52:981][554]LogConsoleManager:Warning: Setting the console variable 't.MaxFPS' to '0' with 'SetByGameSetting' was ignored as it is lower priority than the previous 'SetByCode'. Value remains '144'
[2023.10.01-12.38.52:981][554]LogConsoleManager:Warning: Setting the console variable 'r.VolumetricFog' to '1' with 'SetByScalability' was ignored as it is lower priority than the previous 'SetByCode'. Value remains '1'
[2023.10.01-12.38.52:981][554]LogConsoleManager:Warning: Setting the console variable 'r.MotionBlurQuality' to '4' with 'SetByScalability' was ignored as it is lower priority than the previous 'SetByCode'. Value remains '0'
[2023.10.01-12.38.53:277][561]LogD3D11RHI:Error: Direct3DDevice->CreatePixelShader( (void*)CodePtr, CodeSize, NULL, Shader->Resource.GetInitReference() ) failed 
 at C:\B\tech_exiles\code\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Shaders.cpp:179 
[2023.10.01-12.38.53:278][561]LogWindows: Windows GetLastError: Der Vorgang wurde erfolgreich beendet. (0)
Script stack log empty!

[2023.10.01-12.39.12:580][561]LogMemory: Platform Memory Stats for WindowsNoEditor
[2023.10.01-12.39.12:580][561]LogMemory: Process Physical Memory: 5236.01 MB used, 5519.56 MB peak
[2023.10.01-12.39.12:580][561]LogMemory: Process Virtual Memory: 14119.38 MB used, 14122.16 MB peak
[2023.10.01-12.39.12:580][561]LogMemory: Physical Memory: 14452.75 MB used,  34606.65 MB free, 49059.41 MB total
[2023.10.01-12.39.12:580][561]LogMemory: Virtual Memory: 20202.93 MB used,  34606.65 MB free, 134217728.00 MB total
[2023.10.01-12.39.12:586][561]LogWindows: Windows GetLastError: Der Vorgang wurde erfolgreich beendet. (0)
[2023.10.01-12.39.12:586][561]LogWindows:Error: === Critical error: ===
[2023.10.01-12.39.12:586][561]LogWindows:Error: Fatal error: [File:C:\B\tech_exiles\code\Engine\Source\Runtime\RenderCore\Private\RenderingThread.cpp] [Line: 805] 
[2023.10.01-12.39.12:586][561]LogWindows:Error: Rendering thread exception:
[2023.10.01-12.39.12:586][561]LogWindows:Error: Fatal error: [File:C:\B\tech_exiles\code\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 181] 
[2023.10.01-12.39.12:586][561]LogWindows:Error: Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0020 - 'INTERNAL_ERROR')
[2023.10.01-12.39.12:586][561]LogWindows:Error: !0x0000000000000000
[2023.10.01-12.39.12:614][561]LogExit: Executing StaticShutdownAfterError
[2023.10.01-12.39.12:763][561]LogWindows: FPlatformMisc::RequestExit(1)
[2023.10.01-12.39.12:763][561]Log file closed, 10/01/23 14:39:12

Enable it.

I had to smile at first when I read that because I didn’t know what it was supposed to do in this case, but ok, I turned it on and checked whether it was running.
Started the game.
Joined Server.
Increased the effect settings.

So what happens if you do it in an empty single player game? Crashes on servers are common. DOCP being on is step one tho.

A new save game has already been created without success.
It crashes in single player and on the server as soon as you get close to a placeble which triggers the error “I think as soon as it is rendered”.
And there are quite well-known placebles such as: the workbenches from Shanie’s. Stuff from some other mods are also affected by this.