Low level fatal error d3d

trying to launch game from Epic Launcher. The Prelaunch/ splash screen appears (prior to the shader Claptrap fill screen) Then it crashes.

You watching: Low level fatal error d3d

Top of the window“The Ue4-OakGame Game has craburned and will certainly close”

“LowLevelFatalError Device-> CreatePipelineState

then lists the remainder. height being Kernelbase.dll, the rest being Borderlands3exe! unknownFunction

I tried to google this however came up brief on answers.

DX12 updated, Drivers Updated, Game Uninstalled-Remounted and also proved via Epic Launcher, also updated the BIOS in situation that was the problem.

Windows 10 machine, Ryzen 7 3700 x 8 core, AMD Radeon RX5700 XT

Skimmer (Skimmer) August 11, 2020, 8:59pm #2

I obtained the exact same crash message last night. Cannot launch the game without obtaining the error. I also restarted, uninstalled/reset up BL3, showed via Epic Launcher.

I am likewise making use of AMD Radeon RX5700XT.


Skimmer (Skimmer) August 13, 2020, 6:51pm #10

I swapped graphics cards to watch if that made a difference and also I’m no longer having the concern. I’m now making use of nVidia RTX 2060 SUPER. Seems favor the AMD Radeon RX5700 XT is the culprit. Best of luck refixing your worry.

MojaveMuse (Mojave Muse) August 13, 2020, 8:47pm #11

If I had one to swap would have done so.


Dirges (Dirges) August 14, 2020, 10:18am #12

Today I initially got 2 crashes in game saying memory accessibility violation… Rebooted and also currently I’m obtaining the same thing at the initially splash display screen.


Using a GTX1080 with 451.67 vehicle drivers. Steam variation.

See more: How To Password Protect External Hard Drive Without Encryption

…Did a tiny even more digging and also this crash can have actually somepoint to do with Directx 12 and the fix might be to readjust the game’s ini settings to use Directx 11. (Kind of a no duh minute looking back at the error window… “EngineSourceRuntime D3D12 RHPrivateWindowsWindows D3D12 PipelineState.cpp:725”) You have the right to adjust the setting in the GameUserSetting.ini file situated at C:UsersAdministratorDocumentsMy GamesBorderlands 3SavedConfigWindowsNoEditor

Look for “PreferredGraphicsAPI” and also adjust it from DX12 to DX11, don’t forobtain to conserve.

…Seems to have worked. But running it in DX11 I had actually some significant structure skipping… I feel that DX12 might still need to be repaired. I’ve discovered some indevelopment that might help to deal with it. It requires downloading and install Windows Media Creation Device from Microsoft and downloading and install Windows 10 ISO and also running the setup.exe from there and also selecting the repair alternative.

…So I repaired Windows and tried Borderlands 3 in DX12 aacquire, no error popped up but the game would never fill previous the splash display. So I deleted everything situated in the C:UsersAdministratorDocumentsMy GamesBorderlands 3Saved (copying the SaveGames folder to an additional folder) and also the game started best up.

Somepoint in the config folder had to have been corrupted and also deleting every little thing in that folder compelled the game to redevelop those documents and played for around an hour through no issues, seems to have actually worked… Hope my journey have the right to aid others.


yeah, Official assistance just gained to me this morning informing me to do so…

computer system just Greened out through a tone and also shut down. so that was a fun all brand-new error.

also running the game Remnant which is likewise a UE4 game I think caused it to crash out so I think its somepoint in dispute between the engine and also the card.

update 1: underclocking the card in settings along with the rollearlier to DX11 appeared to obtain me secure sufficient to launch the game and play through Carnivora and also the Agonizer 5000; however as quickly as I exited the software application recollection to default…aacquire. (been a constant struggle to save settings)

additionally added more fans to case to boost flow as the present heatwave can be effecting points.

See more: Simple Scan No Scanners Detected, Scanninghowto

I have actually an Asrock Challenger version of the 5700 xt, that might be appropriate to obtaining to the bottom of points too.