Game crashes because of something about d3d device and lost island?

[TheFigureInTheStreetlight]

Ark will load properly, but when I join the server I play on, the game will be extremely laggy, and will crash with the error message in the post anywhere from 0 to 60 seconds after I have entered the server. It tends to crash sooner rather than later. I've had this problem twice before and the problem went away after a few hours. The problem comes and goes, with no apparent reason for why it starts or stops. For some reason the error message mentions lost island even though I'm playing on the island. The error does not occur if I use the dx10 graphics, but these are worse than ARK mobile's graphics and I will not play with these graphics, and the game is still laggy and textures/models do not load. The problem does not occur frequently, but because I can't play for hours after seeing the error message, and because the problem may be more frequent in the future, I am posting it here. I hope someone can help me because from what I see, no one who has had the same problem has ever said they've fixed it.
Things I have tried to do:

verify integrity of game files

update graphics driver (no update found)

uninstall and reinstall lost island

run game through steam

run game with this command -dx12 (pulls up a different error message and does not load game)

run game with this command -opengl4 (pulls up a different error message and does not load game)

turning off battery boost in nvidia geforce experience

The error message is:

LowLevelFatalError [File:F:\build\LostIsland Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 201] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG')
VERSION: 355.5 KERNELBASE.dll!UnknownFunction (0x00007ffb403006bc) + 0 bytes [UnknownFile:0]
renderer\private\deferredshadingrenderer.cpp:668]
ShooterGame.exe!FError::LowLevelFatal) (0x00007ff6c9c14435) + 0 bytes [f:\build\lostisland\engine\source\runtime\core\private\misc\output device.cpp:354] ShooterGame.exe!Terminate OnDeviceRemoved) (0x00007ff6c9fee0e0) + 0 bytes [f:\build\lostisland\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:214] ShooterGame.exe!VerifyD3D11Result() (0x00007ff6c9fee2ec) + 0 bytes [f:\build\lostisland\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:250] ShooterGame.exe!FD3D11DynamicRHI::GetQueryData() (0x00007ff6c9fdda43) + 0 bytes [f:\build\lostisland\engine\source\runtime\windows\d3d11rhi\private\d3d11query.cpp:153] ShooterGame.exe!FD3D11DynamicRHI::RHIGetRenderQueryResult() (0x00007ff6c9fdd7e7) + 24 bytes [f:\build\lostisland\engine\source\runtime\windows\d3d11rhi\private\d3d11query.cpp:65] ShooterGame.exe!FetchVisibilityForPrimitives_Range<1>0 (0x00007ff6cb28f73e) + 23 bytes [f:\build\lostisland\engine\source\runtime\renderer\private\scenevisibility.cpp:710] ShooterGame.exe!FetchVisibilityForPrimitives() (0x00007ff6cb26b9b4) + 0 bytes [f:\build\lostisland\engine\source\runtime\renderer\private\scenevisibility.cpp:1224] ShooterGame.exe!Occlusion Cull) (0x00007ff6cb26bd93)+ 19 bytes [f:\build\lostisland\engine\source\runtime\renderer\private\scenevisibility.cpp:1286] ShooterGame.exe!FSceneRenderer::ComputeViewVisibility) (0x00007ff6cb271c3a) + 0 bytes [f:\build\lostisland\engine\source\runtime\renderer\private\scenevisibility.cpp:2973] ShooterGame.exe!FDeferredShadingSceneRenderer::InitViews) (0x00007ff6cb272a0b) + 0 bytes [f:\build\lostisland\engine\source\runtime\renderer\private\scenevisibility.cpp:3234] ShooterGame.exe!FDeferredShadingSceneRenderer::Render() (0x00007ff6cb18b6f5) + 0 bytes [f:\build\lostisland\engine\source\runtime ShooterGame.exe!RenderViewFamily_RenderThread() (0x00007ff6cb2699df) + 0 bytes [f:\build\lostisland\engine\source\runtime\renderer\private\scenerendering.cpp:1164] ShooterGame.exe!TGraphTask< FRendererModule::BeginRenderingViewFamily :: 26::EURCMacro_FDrawSceneCommand>::ExecuteTask() (0x00007ff6cb2814c2) + 12 bytes ShooterGame.exe!FNamedTaskThread::ProcessTasks NamedThread0 (0x00007ff6c9b80ad8) + 0 bytes [f:\build\lostisland\engine\source\runtime\core\private\async\taskgraph.cpp:939] ShooterGame.exe!FNamedTaskThread::ProcessTasks UntilQuit) (0x00007ff6c9b7fc8d) + 0 bytes [f:\build\lostisland\engine\source\runtime\core\private\async\taskgraph.cpp:680] ShooterGame.exe!RenderingThreadMain) (0x00007ff6ca0b8449) + 0 bytes [f:\build\lostisland\engine\source\runtime\rendercore\private\renderingthread.cpp:265] ShooterGame.exe!FRenderingThread::Run) (0x00007ff6ca0b8840) + 0 bytes [f:\build\lostisland\engine\source\runtime\rendercore\private\renderingthread.cpp:385] ShooterGame.exe!FRunnableThreadWin::Run) (0x00007ff6c9c65d56) + 0 bytes [f:\build\lostisland\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:73] ShooterGame.exe!FRunnableThreadWin::GuardedRun() (0x00007ff6c9c65c18) + 8 bytes [f:\build\lostisland\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:26] KERNEL32.DLL!UnknownFunction (0x00007ffb41b526bd) + 0 bytes [UnknownFile:0]
[f:\build\lostisland\engine\source\runtime\core\public\async\taskgraphinterfaces.h:871]
ntdll.dll!UnknownFunction (0x00007ffb42d8dfb8) + 0 bytes [UnknownFile:0] ntdll.dll!UnknownFunction (0x00007ffb42d8dfb8) + 0 bytes [UnknownFile:0]

[retsam1]

If you'd searched, the d3d issue has been discussed for many years now. It is an issue with the Unreal Engine 4 by Epic and is not limited to Ark. It has no fix. Again, there is No fix for it. All you can do is limit the chances of it occurring, primarily by playing UE4 games within the limitations of your comp.

With that said then:

1. Go to the steam help menu, click system information, and copy paste all that info here so we can more accurately see what steam detects for your computer and any potential discrepancies.

2. If you are using modded content, list all mods by name and in their load order.

3. Do not overclock, use msi afterburner, 3rd party graphic enhancers etc, They are known issue makers.

4. Do not use launch commands like you were mentioning. Some are obsolete and can actually cause more issues(as you discovered...)

5. The server you play on that you mention.... is it an official or unofficial server?

Start with that info and lets see from there.