ARK: Survival Evolved

ARK: Survival Evolved

View Stats:
Dracolyte Jun 13, 2022 @ 6:04am
Game crashes after launch (D3D Device lost, ERROR: 0x887A0007 -RESET)
Verified game files, all drivers are updated, but no matter what I do the game WILL CRASH about a minute or less after launching, always with the same error.

CRASH LOG:
LowLevelFatalError [File:E:\build\DevNext\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 201]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0007 - 'RESET')


VERSION: 346.11
KERNELBASE.dll!UnknownFunction (0x00007ff9e13cfa7c) + 0 bytes [UnknownFile:0]
ShooterGame.exe!FError::LowLevelFatal() (0x00007ff6128e20b5) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\misc\outputdevice.cpp:354]
ShooterGame.exe!TerminateOnDeviceRemoved() (0x00007ff612cbb820) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:214]
ShooterGame.exe!VerifyD3D11CreateTextureResult() (0x00007ff612cbbced) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:299]
ShooterGame.exe!FD3D11DynamicRHI::CreateD3D11Texture2D<FD3D11BaseTexture2D>() (0x00007ff612ccbe07) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11texture.cpp:710]
ShooterGame.exe!FD3D11DynamicRHI::RHICreateTexture2D() (0x00007ff612cb66f1) + 75 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11texture.cpp:1031]
ShooterGame.exe!FDynamicRHI::RHICreateTexture2D_RenderThread() (0x00007ff612d7f3b2) + 89 bytes [e:\build\devnext\engine\source\runtime\rhi\private\rhicommandlist.cpp:2004]
ShooterGame.exe!FTexture2DResource::InitRHI() (0x00007ff61339db72) + 38 bytes [e:\build\devnext\engine\source\runtime\engine\private\texture2d.cpp:1370]
ShooterGame.exe!FRenderResource::InitResource() (0x00007ff612d875e4) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderresource.cpp:32]
ShooterGame.exe!TGraphTask<`BeginInitResource'::`2'::EURCMacro_InitCommand>::ExecuteTask() (0x00007ff612d8bd0c) + 0 bytes [e:\build\devnext\engine\source\runtime\core\public\async\taskgraphinterfaces.h:895]
ShooterGame.exe!FNamedTaskThread::ProcessTasksNamedThread() (0x00007ff61284f0d8) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\async\taskgraph.cpp:939]
ShooterGame.exe!FNamedTaskThread::ProcessTasksUntilQuit() (0x00007ff61284e28d) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\async\taskgraph.cpp:680]
ShooterGame.exe!RenderingThreadMain() (0x00007ff612d85af9) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderingthread.cpp:265]
ShooterGame.exe!FRenderingThread::Run() (0x00007ff612d85ef0) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderingthread.cpp:385]
ShooterGame.exe!FRunnableThreadWin::Run() (0x00007ff612933636) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:73]
ShooterGame.exe!FRunnableThreadWin::GuardedRun() (0x00007ff6129334f8) + 8 bytes [e:\build\devnext\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:26]
KERNEL32.DLL!UnknownFunction (0x00007ff9e2ef244d) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ff9e3cadf88) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ff9e3cadf88) + 0 bytes [UnknownFile:0]

I have:
- Ryzen 3 2300X Quad-core
- Radeon RX 560 (2gb vram, getting 1660 super soon)
- 8gb RAM (Getting 16gb soon)

Help much appreciated, thanks in advance!

EDIT:
Ok so I have gotten it to work by doing this:
When you click play on Steam, select the DirectX 10 (low graphics) variant, and that seems to work fine for me with no crashes.
Last edited by Dracolyte; Jun 13, 2022 @ 6:56pm
Originally posted by retsam1:
Originally posted by Dracolyte:
Verified game files, all drivers are updated, but no matter what I do the game WILL CRASH about a minute or less after launching, always with the same error.

CRASH LOG:
LowLevelFatalError [File:E:\build\DevNext\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 201]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0007 - 'RESET')


VERSION: 346.11
KERNELBASE.dll!UnknownFunction (0x00007ff9e13cfa7c) + 0 bytes [UnknownFile:0]
ShooterGame.exe!FError::LowLevelFatal() (0x00007ff6128e20b5) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\misc\outputdevice.cpp:354]
ShooterGame.exe!TerminateOnDeviceRemoved() (0x00007ff612cbb820) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:214]
ShooterGame.exe!VerifyD3D11CreateTextureResult() (0x00007ff612cbbced) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:299]
ShooterGame.exe!FD3D11DynamicRHI::CreateD3D11Texture2D<FD3D11BaseTexture2D>() (0x00007ff612ccbe07) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11texture.cpp:710]
ShooterGame.exe!FD3D11DynamicRHI::RHICreateTexture2D() (0x00007ff612cb66f1) + 75 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11texture.cpp:1031]
ShooterGame.exe!FDynamicRHI::RHICreateTexture2D_RenderThread() (0x00007ff612d7f3b2) + 89 bytes [e:\build\devnext\engine\source\runtime\rhi\private\rhicommandlist.cpp:2004]
ShooterGame.exe!FTexture2DResource::InitRHI() (0x00007ff61339db72) + 38 bytes [e:\build\devnext\engine\source\runtime\engine\private\texture2d.cpp:1370]
ShooterGame.exe!FRenderResource::InitResource() (0x00007ff612d875e4) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderresource.cpp:32]
ShooterGame.exe!TGraphTask<`BeginInitResource'::`2'::EURCMacro_InitCommand>::ExecuteTask() (0x00007ff612d8bd0c) + 0 bytes [e:\build\devnext\engine\source\runtime\core\public\async\taskgraphinterfaces.h:895]
ShooterGame.exe!FNamedTaskThread::ProcessTasksNamedThread() (0x00007ff61284f0d8) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\async\taskgraph.cpp:939]
ShooterGame.exe!FNamedTaskThread::ProcessTasksUntilQuit() (0x00007ff61284e28d) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\async\taskgraph.cpp:680]
ShooterGame.exe!RenderingThreadMain() (0x00007ff612d85af9) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderingthread.cpp:265]
ShooterGame.exe!FRenderingThread::Run() (0x00007ff612d85ef0) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderingthread.cpp:385]
ShooterGame.exe!FRunnableThreadWin::Run() (0x00007ff612933636) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:73]
ShooterGame.exe!FRunnableThreadWin::GuardedRun() (0x00007ff6129334f8) + 8 bytes [e:\build\devnext\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:26]
KERNEL32.DLL!UnknownFunction (0x00007ff9e2ef244d) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ff9e3cadf88) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ff9e3cadf88) + 0 bytes [UnknownFile:0]

I have:
- Ryzen 3 2300X Quad-core
- Radeon RX 560 (2gb vram, getting 1660 super soon)
- 8gb RAM (Getting 16gb soon)

Help much appreciated, thanks in advance!


Ok this has been discussed tons of times over the last 7 years. This is the infamous D3D crash error that plagues many UE4 games so take note of the next sentence:

There categorically and absolutely is -NO- fix for this error.

All you can do is limit the frequency of its occurrence. That is usually done by:

1. Not playing the game beyond the means of your computer. (keeping drivers correctly up to date, not playing on a potato that isn't meant to play the game, not playing in settings above the limits of your graphic card, and the list goes on and on).

2. Not using broken and or abandoned modded content or combining mods not meant to work together.

3. No changing in game settings and ini files that also go beyond the capabilities of your rig. (Sort of point 1 but needed to be stated separately.


And the list goes on. Again this issue has occurred for years and Epic, the maker of the Engine has cited many many jira(error reports) on their website about it. Basically its a flaw of the engine that can't be resolved due to the variables that can seemingly trigger it.

Anyone telling you it can be "fixed" is incorrect. Do a search on here for D3D and you'll see many threads about this.
< >
Showing 1-13 of 13 comments
Whiplash711 Jun 13, 2022 @ 6:09am 
OS: Windows 7/8.1/10 (64-bit versions)
Processor: Intel Core i5-2400/AMD FX-8320 or better
Memory: 8 GB RAM
Graphics: NVIDIA GTX 670 2GB/AMD Radeon HD 7870 2GB or better
DirectX: Version 10
Storage: 60 GB available space

Keeping all that in mind you have an issue running Ark, not enough RAM. The game needs 8GB RAM you only have that. You are offering nothing for your Windows, Steam, security software to use. Though they take what they want and the game gets what is leftover.
As for that error though seems you are missing files. If integrity check did not work there are 2 other things to try. First is go in the install folder find the Application EXE that starts the game, delete it. Now do the integrity check again. Sometimes doing that can trigger Steam to find what is truely missing.
You other option is to reinstall the game. Note if you have a slow internet speed might want to install overnight when no one else uses the internet. So much data being downloaded can likely be an issue for slower connections.
Whiplash711 Jun 13, 2022 @ 6:13am 
Another tip if you can, look at the 2,000 series graphic cards. 3,000 series would be best. Reason is they already have the 4,000 series hitting the market. So games are going to move forward leaving the older cards in the dust. Now what you are looking at may benchmark well for todays games but what about next years games?
As for the RAM, it is sold in sticks of 8 or 16 I believe. I would get the 16GB if you can. Reason is more RAM is better. There are even some games that require 16GB RAM right now. So again that means you need to have more than not that amount.
RAM is very confusing when you are just learning. 20yrs ago I wasted so much money on PC games as I did not understand the specs and requirements. Did not understand that requiring 8GB RAM meant I needed to exceed that amount. So today I try to help others understand. I am far from an expert in PCs but these are lessons I learned the hard way.
Lori37 Jun 13, 2022 @ 6:15am 
OP, if I were you I would go for at least a 2060.... 1660 seems a bit old by now
Whiplash711 Jun 13, 2022 @ 6:17am 
I realize I posted a wall of text but this old dog learned a lot over the years, shared in that wall of text. Hope it can help others, as I know I would have left consoles a lot sooner if I understood more about PC gaming.
Dracolyte Jun 13, 2022 @ 6:18am 
Originally posted by Lori37:
OP, if I were you I would go for at least a 2060.... 1660 seems a bit old by now
Unfortunately it's what I can afford, and I don't really need max graphics or anything the newest games I'll play is Starfield and Elden Ring. It's a 1660 Super if that matters more too
Last edited by Dracolyte; Jun 13, 2022 @ 6:18am
Dracolyte Jun 13, 2022 @ 6:20am 
Originally posted by Whiplash711:
I realize I posted a wall of text but this old dog learned a lot over the years, shared in that wall of text. Hope it can help others, as I know I would have left consoles a lot sooner if I understood more about PC gaming.

No problem with that, thanks for the posts. If 8gb is the game's minimum, wouldn't the devs know that included windows and other processes? Also my issue is with the GPU, not the ram, but I'll try verifying the game files again with that method.
Lori37 Jun 13, 2022 @ 8:46am 
Originally posted by Dracolyte:

No problem with that, thanks for the posts. If 8gb is the game's minimum, wouldn't the devs know that included windows and other processes? Also my issue is with the GPU, not the ram, but I'll try verifying the game files again with that method.

Unfortunately with ARK, having low RAM is actually an issue with how the game will run.... 16 GB is minimum...
The author of this thread has indicated that this post answers the original topic.
retsam1 Jun 13, 2022 @ 9:21am 
Originally posted by Dracolyte:
Verified game files, all drivers are updated, but no matter what I do the game WILL CRASH about a minute or less after launching, always with the same error.

CRASH LOG:
LowLevelFatalError [File:E:\build\DevNext\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 201]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0007 - 'RESET')


VERSION: 346.11
KERNELBASE.dll!UnknownFunction (0x00007ff9e13cfa7c) + 0 bytes [UnknownFile:0]
ShooterGame.exe!FError::LowLevelFatal() (0x00007ff6128e20b5) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\misc\outputdevice.cpp:354]
ShooterGame.exe!TerminateOnDeviceRemoved() (0x00007ff612cbb820) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:214]
ShooterGame.exe!VerifyD3D11CreateTextureResult() (0x00007ff612cbbced) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:299]
ShooterGame.exe!FD3D11DynamicRHI::CreateD3D11Texture2D<FD3D11BaseTexture2D>() (0x00007ff612ccbe07) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11texture.cpp:710]
ShooterGame.exe!FD3D11DynamicRHI::RHICreateTexture2D() (0x00007ff612cb66f1) + 75 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11texture.cpp:1031]
ShooterGame.exe!FDynamicRHI::RHICreateTexture2D_RenderThread() (0x00007ff612d7f3b2) + 89 bytes [e:\build\devnext\engine\source\runtime\rhi\private\rhicommandlist.cpp:2004]
ShooterGame.exe!FTexture2DResource::InitRHI() (0x00007ff61339db72) + 38 bytes [e:\build\devnext\engine\source\runtime\engine\private\texture2d.cpp:1370]
ShooterGame.exe!FRenderResource::InitResource() (0x00007ff612d875e4) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderresource.cpp:32]
ShooterGame.exe!TGraphTask<`BeginInitResource'::`2'::EURCMacro_InitCommand>::ExecuteTask() (0x00007ff612d8bd0c) + 0 bytes [e:\build\devnext\engine\source\runtime\core\public\async\taskgraphinterfaces.h:895]
ShooterGame.exe!FNamedTaskThread::ProcessTasksNamedThread() (0x00007ff61284f0d8) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\async\taskgraph.cpp:939]
ShooterGame.exe!FNamedTaskThread::ProcessTasksUntilQuit() (0x00007ff61284e28d) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\async\taskgraph.cpp:680]
ShooterGame.exe!RenderingThreadMain() (0x00007ff612d85af9) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderingthread.cpp:265]
ShooterGame.exe!FRenderingThread::Run() (0x00007ff612d85ef0) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderingthread.cpp:385]
ShooterGame.exe!FRunnableThreadWin::Run() (0x00007ff612933636) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:73]
ShooterGame.exe!FRunnableThreadWin::GuardedRun() (0x00007ff6129334f8) + 8 bytes [e:\build\devnext\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:26]
KERNEL32.DLL!UnknownFunction (0x00007ff9e2ef244d) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ff9e3cadf88) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ff9e3cadf88) + 0 bytes [UnknownFile:0]

I have:
- Ryzen 3 2300X Quad-core
- Radeon RX 560 (2gb vram, getting 1660 super soon)
- 8gb RAM (Getting 16gb soon)

Help much appreciated, thanks in advance!


Ok this has been discussed tons of times over the last 7 years. This is the infamous D3D crash error that plagues many UE4 games so take note of the next sentence:

There categorically and absolutely is -NO- fix for this error.

All you can do is limit the frequency of its occurrence. That is usually done by:

1. Not playing the game beyond the means of your computer. (keeping drivers correctly up to date, not playing on a potato that isn't meant to play the game, not playing in settings above the limits of your graphic card, and the list goes on and on).

2. Not using broken and or abandoned modded content or combining mods not meant to work together.

3. No changing in game settings and ini files that also go beyond the capabilities of your rig. (Sort of point 1 but needed to be stated separately.


And the list goes on. Again this issue has occurred for years and Epic, the maker of the Engine has cited many many jira(error reports) on their website about it. Basically its a flaw of the engine that can't be resolved due to the variables that can seemingly trigger it.

Anyone telling you it can be "fixed" is incorrect. Do a search on here for D3D and you'll see many threads about this.
Dracolyte Jun 13, 2022 @ 10:28am 
Originally posted by retsam1:
Originally posted by Dracolyte:
Verified game files, all drivers are updated, but no matter what I do the game WILL CRASH about a minute or less after launching, always with the same error.

CRASH LOG:
LowLevelFatalError [File:E:\build\DevNext\Engine\Source\Runtime\Windows\D3D11RHI\Private\D3D11Util.cpp] [Line: 201]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0007 - 'RESET')


VERSION: 346.11
KERNELBASE.dll!UnknownFunction (0x00007ff9e13cfa7c) + 0 bytes [UnknownFile:0]
ShooterGame.exe!FError::LowLevelFatal() (0x00007ff6128e20b5) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\misc\outputdevice.cpp:354]
ShooterGame.exe!TerminateOnDeviceRemoved() (0x00007ff612cbb820) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:214]
ShooterGame.exe!VerifyD3D11CreateTextureResult() (0x00007ff612cbbced) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:299]
ShooterGame.exe!FD3D11DynamicRHI::CreateD3D11Texture2D<FD3D11BaseTexture2D>() (0x00007ff612ccbe07) + 0 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11texture.cpp:710]
ShooterGame.exe!FD3D11DynamicRHI::RHICreateTexture2D() (0x00007ff612cb66f1) + 75 bytes [e:\build\devnext\engine\source\runtime\windows\d3d11rhi\private\d3d11texture.cpp:1031]
ShooterGame.exe!FDynamicRHI::RHICreateTexture2D_RenderThread() (0x00007ff612d7f3b2) + 89 bytes [e:\build\devnext\engine\source\runtime\rhi\private\rhicommandlist.cpp:2004]
ShooterGame.exe!FTexture2DResource::InitRHI() (0x00007ff61339db72) + 38 bytes [e:\build\devnext\engine\source\runtime\engine\private\texture2d.cpp:1370]
ShooterGame.exe!FRenderResource::InitResource() (0x00007ff612d875e4) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderresource.cpp:32]
ShooterGame.exe!TGraphTask<`BeginInitResource'::`2'::EURCMacro_InitCommand>::ExecuteTask() (0x00007ff612d8bd0c) + 0 bytes [e:\build\devnext\engine\source\runtime\core\public\async\taskgraphinterfaces.h:895]
ShooterGame.exe!FNamedTaskThread::ProcessTasksNamedThread() (0x00007ff61284f0d8) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\async\taskgraph.cpp:939]
ShooterGame.exe!FNamedTaskThread::ProcessTasksUntilQuit() (0x00007ff61284e28d) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\async\taskgraph.cpp:680]
ShooterGame.exe!RenderingThreadMain() (0x00007ff612d85af9) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderingthread.cpp:265]
ShooterGame.exe!FRenderingThread::Run() (0x00007ff612d85ef0) + 0 bytes [e:\build\devnext\engine\source\runtime\rendercore\private\renderingthread.cpp:385]
ShooterGame.exe!FRunnableThreadWin::Run() (0x00007ff612933636) + 0 bytes [e:\build\devnext\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:73]
ShooterGame.exe!FRunnableThreadWin::GuardedRun() (0x00007ff6129334f8) + 8 bytes [e:\build\devnext\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:26]
KERNEL32.DLL!UnknownFunction (0x00007ff9e2ef244d) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ff9e3cadf88) + 0 bytes [UnknownFile:0]
ntdll.dll!UnknownFunction (0x00007ff9e3cadf88) + 0 bytes [UnknownFile:0]

I have:
- Ryzen 3 2300X Quad-core
- Radeon RX 560 (2gb vram, getting 1660 super soon)
- 8gb RAM (Getting 16gb soon)

Help much appreciated, thanks in advance!


Ok this has been discussed tons of times over the last 7 years. This is the infamous D3D crash error that plagues many UE4 games so take note of the next sentence:

There categorically and absolutely is -NO- fix for this error.

All you can do is limit the frequency of its occurrence. That is usually done by:

1. Not playing the game beyond the means of your computer. (keeping drivers correctly up to date, not playing on a potato that isn't meant to play the game, not playing in settings above the limits of your graphic card, and the list goes on and on).

2. Not using broken and or abandoned modded content or combining mods not meant to work together.

3. No changing in game settings and ini files that also go beyond the capabilities of your rig. (Sort of point 1 but needed to be stated separately.


And the list goes on. Again this issue has occurred for years and Epic, the maker of the Engine has cited many many jira(error reports) on their website about it. Basically its a flaw of the engine that can't be resolved due to the variables that can seemingly trigger it.

Anyone telling you it can be "fixed" is incorrect. Do a search on here for D3D and you'll see many threads about this.

Ok so basically, I just have to turn the settings allllll the way down and hope it works? That sucks but I'll try it, praying it goes well lol
RadarScreen Jun 13, 2022 @ 6:02pm 
Why is my ARK folder 461 GB, when it only requires 61 GB????
retsam1 Jun 13, 2022 @ 6:04pm 
Originally posted by Dracolyte:

Ok so basically, I just have to turn the settings allllll the way down and hope it works? That sucks but I'll try it, praying it goes well lol

No because as I mentioned all the different variables that can potentially trigger it depend so specific to your case you'd need to provide more details of things that could be contributing factors. Turning everything low may but it may not reduce its frequency in your case but it may be excessive or may not be the main factor for you.
retsam1 Jun 13, 2022 @ 6:05pm 
Originally posted by RadarScreen:
Why is my ARK folder 461 GB, when it only requires 61 GB????

This has nothing to do with the OP and there are lots of thread discussing and explaining this.
Dracolyte Jun 13, 2022 @ 6:55pm 
Ok so I have gotten it to work by doing this:
When you click play on Steam, select the DirectX 10 (low graphics) variant, and that seems to work fine for me with no crashes.
< >
Showing 1-13 of 13 comments
Per page: 1530 50

Date Posted: Jun 13, 2022 @ 6:04am
Posts: 13