[READ ME] Common Issues & How To Fix Them

[GSG Mark]

Attention, Miners!

Games that crash, won’t launch or suffer from stability issues are undoubtedly the most frustrating part of PC gaming. Although we strive to deliver a flawless gaming experience in the depths of Hoxxes IV, we can’t guarantee you won’t encounter a crash or stability issue at some point during your employment at Deep Rock Galactic. This is in part due to the iterative nature of game development in an early access stage but also because everyone has different hardware and PC specifications.

If you find yourself in an annoying predicament where the game crashes frequently, don’t panic! Take a deep breath and follow the steps below. More often than not we know a reliable solution to your problem.

• Step 1

  Restart your PC and ensure the crashes are consistent. This tried-and-true method for fixing things does sometimes work, as it's possible you're running into memory problems and just need to clean house. If it doesn't work, at least you've ruled out the easiest fix.
  
  

• Step 2

  If you're overclocking your CPU or GPU, stop it, at least for now. Even if every other game runs fine, it's best to rule out overclocking as a cause. You can always reinstate the overclock later.
  
  

• Step 3

  Copy the crash report, provided in the Ghost Ship Games Crash Reporter that appears when the game terminates. Paste it in a document and save it on your PC. Send and close the crash report. (Screenshot here!)[i.imgur.com]
  
  

• Step 4

  Take note of the first couple of lines in the crash report and look for its reference below. From a troubleshooting standpoint, these are the most important pieces of information you can gather in relation to your crash.
  
  

• Step 5

  Troubleshoot the issue using the most common workarounds detailed beneath the respective crash report. If the workarounds described here don't work, head back to the Bugs + Crashes subforum and search for your crash there.

If you encounter a crash that prevents the game from launching entirely, restart your PC. If that doesn’t resolve it, verify the integrity of the game files by right-clicking the game in your Steam Library > Properties > Local Files > Verify Integrity of Game Files. If that doesn't resolve it, run UE4PrereqSetup_x64.exe as Administrator located in steamapps\common\Deep Rock Galactic\Engine\Extras\Redist\en-us.

As a last resort, you can try to add "-dx11" to the launch options[media.discordapp.net] by right-clicking the game in your Steam Library > Properties > Launch Options. If that does not work, navigate to your GameUserSettings[cdn.discordapp.com] file, open it with any text editor (like Notepad) and set bPreferD3D12InGame to False instead of True.

🛠️ Common Crashes & How To Fix Them

💡 Are you experiencing a very particular issue? Check out community member Loan Ranger's extensive troubleshooting guide here:

https://steamcommunity.com/sharedfiles/filedetails/?id=2559182673

The crashes described below are the most common crashes reported by the Deep Rock Galactic community. Work your way through the steps beneath your respective crash and see if that restores your game to a playable state. If you are still experiencing crashes afterward, feel free to leave a reply on this topic and we'll assist you to the best of our ability.

Please be advised that some crashes may be related to Unreal Engine and thus not exclusive to Deep Rock Galactic. As such, it may be worth trying to boot up another game built on Unreal Engine (e.g. Fortnite, Mordhau) and see if your issue also occurs there.

igd10iumd64

This crash is one of the most frequent crashes we’re seeing and relates to an Intel Integrated HD graphics drivers issue, presumably inflicted by a faulty Windows update.

Access violation - code c0000005 (first/second chance not available)

igd10iumd64
d3d11
dxgi
d3d11
d3d11
FSD_Win64_Shipping!FD3D11DynamicRHI::CommitRenderTargetsAndUAVs() [c:\p4\unrealengine\main4-21\engine\source\runtime\windows\d3d11rhi\private\d3d11commands.cpp:880]
FSD_Win64_Shipping!FD3D11DynamicRHI::RHISetRenderTargets() [c:\p4\unrealengine\main4-21\engine\source\runtime\windows\d3d11rhi\private\d3d11commands.cpp:1144]
FSD_Win64_Shipping!FD3D11DynamicRHI::RHIBeginDrawingViewport() [c:\p4\unrealengine\main4-21\engine\source\runtime\windows\d3d11rhi\private\d3d11viewport.cpp:623]
FSD_Win64_Shipping!FRHICommandListExecutor::ExecuteInner() [c:\p4\unrealengine\main4-21\engine\source\runtime\rhi\private\rhicommandlist.cpp:577]
FSD_Win64_Shipping!FRHICommandList::BeginDrawingViewport() [c:\p4\unrealengine\main4-21\engine\source\runtime\rhi\private\rhicommandlist.cpp:1486]
FSD_Win64_Shipping!FSlateRHIRenderer::DrawWindow_RenderThread() [c:\p4\unrealengine\main4-21\engine\source\runtime\slaterhirenderer\private\slaterhirenderer.cpp:829]
FSD_Win64_Shipping!TGraphTask<TEnqueueUniqueRenderCommandType<`FSlateRHIRenderer::DrawWindows_Private'::`29'::SlateDrawWindowsCommandName,<lambda_9609773cc530bfaa1bbe99d6670154e1> > >::ExecuteTask() [c:\p4\unrealengine\main4-21\engine\source\runtime\core\public\async\taskgraphinterfaces.h:844]
FSD_Win64_Shipping!FNamedTaskThread::ProcessTasksUntilQuit() [c:\p4\unrealengine\main4-21\engine\source\runtime\core\private\async\taskgraph.cpp:574]
FSD_Win64_Shipping!RenderingThreadMain() [c:\p4\unrealengine\main4-21\engine\source\runtime\rendercore\private\renderingthread.cpp:333]
FSD_Win64_Shipping!FRenderingThread::Run() [c:\p4\unrealengine\main4-21\engine\source\runtime\rendercore\private\renderingthread.cpp:467]
FSD_Win64_Shipping!FRunnableThreadWin::Run() [c:\p4\unrealengine\main4-21\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:76]

🔧 How To Fix

• Step 1
  First of all update your Intel HD graphics drivers, directly from Intel[downloadcenter.intel.com]. If you find that the versions of the latest driver on the website and that of the driver installed on the computer are the same, I would suggest you uninstall and reinstall the current version of display driver to try and fix the issue.
  
  
• Step 2
  Restart your PC and boot up the game again. Are the crashes still occurring? If not; fantastic! If the crashes have not been resolved, resume with step 3.
  
  
• Step 3
  Uninstall Intel HD graphics drivers and use normal drivers instead.

Unreal Engine is exiting due to D3D device being lost

This crash log indicates GPU issues, often related to overheating.

LowLevelFatalError [File:Unknown] [Line: 200] Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG')

FSD_Win64_Shipping!FDebug::AssertFailed() [c:\p4\unrealengine\main4-21\engine\source\runtime\core\private\misc\assertionmacros.cpp:417]
FSD_Win64_Shipping!TerminateOnDeviceRemoved() [c:\p4\unrealengine\main4-21\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:213]
FSD_Win64_Shipping!VerifyD3D11Result() [c:\p4\unrealengine\main4-21\engine\source\runtime\windows\d3d11rhi\private\d3d11util.cpp:249]
FSD_Win64_Shipping!FD3D11DynamicRHI::GetQueryData() [c:\p4\unrealengine\main4-21\engine\source\runtime\windows\d3d11rhi\private\d3d11query.cpp:141]
FSD_Win64_Shipping!FD3D11DynamicRHI::RHIGetRenderQueryResult() [c:\p4\unrealengine\main4-21\engine\source\runtime\windows\d3d11rhi\private\d3d11query.cpp:55]
FSD_Win64_Shipping!FetchVisibilityForPrimitives_Range<1>() [c:\p4\unrealengine\main4-21\engine\source\runtime\renderer\private\scenevisibility.cpp:854]
FSD_Win64_Shipping!FetchVisibilityForPrimitives() [c:\p4\unrealengine\main4-21\engine\source\runtime\renderer\private\scenevisibility.cpp:1402]
FSD_Win64_Shipping!OcclusionCull() [c:\p4\unrealengine\main4-21\engine\source\runtime\renderer\private\scenevisibility.cpp:1566]
FSD_Win64_Shipping!FSceneRenderer::ComputeViewVisibility() [c:\p4\unrealengine\main4-21\engine\source\runtime\renderer\private\scenevisibility.cpp:3058]
FSD_Win64_Shipping!FDeferredShadingSceneRenderer::InitViews() [c:\p4\unrealengine\main4-21\engine\source\runtime\renderer\private\scenevisibility.cpp:3380]
FSD_Win64_Shipping!FDeferredShadingSceneRenderer::Render() [c:\p4\unrealengine\main4-21\engine\source\runtime\renderer\private\deferredshadingrenderer.cpp:610]
FSD_Win64_Shipping!RenderViewFamily_RenderThread() [c:\p4\unrealengine\main4-21\engine\source\runtime\renderer\private\scenerendering.cpp:2957]
FSD_Win64_Shipping!TGraphTask<`FRendererModule::BeginRenderingViewFamily'::`20'::EURCMacro_FDrawSceneCommand>::ExecuteTask() [c:\p4\unrealengine\main4-21\engine\source\runtime\core\public\async\taskgraphinterfaces.h:829]
FSD_Win64_Shipping!FNamedTaskThread::ProcessTasksUntilQuit() [c:\p4\unrealengine\main4-21\engine\source\runtime\core\private\async\taskgraph.cpp:574]
FSD_Win64_Shipping!RenderingThreadMain() [c:\p4\unrealengine\main4-21\engine\source\runtime\rendercore\private\renderingthread.cpp:333]
FSD_Win64_Shipping!FRenderingThread::Run() [c:\p4\unrealengine\main4-21\engine\source\runtime\rendercore\private\renderingthread.cpp:467]
FSD_Win64_Shipping!FRunnableThreadWin::Run() [c:\p4\unrealengine\main4-21\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:76]

🔧 How To Fix

• Step 1
  Head into the in-game Options and try to limit your FPS in the 60 - 120 range or enable Vsync. Some players have reported that allowing the FPS of the game to spool into higher ranges can cause crashes for some GPUs.
  
  
• Step 2
  Update your graphics drivers if Step 1 yields no success. Still crashing? Proceed to step 3.
  
  
• Step 3
  Perform a clean uninstall of the game and delete all residual files and folders related to Deep Rock Galactic on your PC.
  
  
• Step 4
  Reinstall the game.

Unhandled exception

This crash has many manifestations but is most commonly related to your graphics card drivers.

Unhandled exception

nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
nvwgf2umx
kernel32
ntdll

🔧 How To Fix

• Step 1
  Perform a clean uninstallation of your GPU drivers. We recommend this tool[www.guru3d.com] as long as the guidelines for recommended usage are followed.
  
  
• Step 2
  Reinstall the latest GPU driver for your graphics card.

You do not have any debugging symbols required to display the callstack for this crash

This crash log relates to the game engine Deep Rock Galactic runs on.

You do not have any debugging symbols required to display the callstack for this crash

🔧 How To Fix

• Step 1
  Install the Epic Games Launcher
  
  
• Step 2
  Open up the Epic Games Launcher
  
  
• Step 3
  Click on the yellow and black downward arrow beside Launch
  
  
• Step 4
  Click on Options
  
  
• Step 5
  Make sure that there is a check-mark beside 'Editor symbols for debugging' and press Apply

⏳ Waiting For Steam To Load

Occasionally, a connection issue between Steam and the game may be preventing you from playing. This is indicated by a loading screen with the text "Waiting for Steam to load".[i.imgur.com]

First of all; try to restart your PC. If that doesn't resolve it, end all Steam related processes via the Task Manager and restart Steam. Ensure Steam isn't at fault by messaging someone on your friends list. Did your friend receive your chat message? Perfect. You have a connection to Steam. Boot up the game and see if your issue has been fixed.

If that doesn't resolve it head into the quarantine settings of your anti-virus and restore all DRG-related files that may have been caught in the quarantine. Closing your anti-virus or adding an exception for the game in the settings is rarely sufficient. You must ensure that no DRG related files have already been isolated in the quarantine.

Last but not least, running dedicated servers for other games can be the cause of a connection conflict. Close any dedicated servers that may be running in the background and see if that fixes your issue. This has for instance been the case for players running Mordhau servers and Conan Exiles servers.

⏳ Network & Connection Issues

Some players report unusual connection issues that manifest themselves by preventing players from joining or hosting servers on the server list, causing random, unexplainable loss of connection to games mid-mission or weird in-game behavior like no weapons, the inability to jump, clipping into terrain, etc.

If you are a victim to these symptoms, forcing your PC to reset your IP stack/network adapter can alleviate the problem:

🔧 How To Fix

• Step 1
  Right-click your network adapter and select ‘Properties’. Disable ‘IPv6’.
  
  
• Step 2
  Run Command Prompt as administrator. Command Prompt is most easily be located by searching for ‘cmd’ in the Windows Start Menu.
  
  
• Step 3
  Enter the following commands in the Command Prompt.
  Type netsh int ip reset then press Enter.
  Type netsh winsock reset then press Enter.
  
  
• Step 4
  Finally, restart your PC.

Miscellaneous Common Issues

• Nvidia Ansel is notorious in the community for causing performance issues. Try to update Nvidia Ansel. If that doesn’t work, disable it completely.
  
  
• If you are running a PC configuration with AMD FX Series components and/or Realtek Audio, refer to the following Steam Topic for help:
  https://steamcommunity.com/app/548430/discussions/2/1729827777339086202/
  
  
• Disable 'Anti-Lag' in the AMD Radeon™ Software
  
  
• If the game refuses to launch entirely even after reinstalling, try to download DirectX directly from Microsoft's website.
  https://www.microsoft.com/en-ca/download/details.aspx?id=35
  https://www.microsoft.com/en-us/download/details.aspx?id=34429
  
  
• If your game refuses to launch entirely even after reinstalling and downloading DirectX, try to add "-dx12" to the launch options by right-clicking the game in your Steam Library > Properties > Set Launch Options.
  
  
• If the game crashes on startup, try to add "-regenerateinis" to the launch options by right-clicking the game in your Steam Library > Properties > Set Launch Options. Beware that this launch option will reset all options to their defaults.
  
  
• Are you suffering from unresponsive mouse clicks? Change your game to fullscreen and your native resolution. That should do the trick.
  
  
• Are you not hearing your friend's voice communication in-game? Head to Windows Sound Settings, select Sound Control Panel, right-click your preferred output device, and select Set as Default Communication Device.

[The Exile]

⸸𝔻έⓐ𝒹мᵃ𝓷⸸ の投稿を引用：

...

Post a DXdiag my guy.

[Arem the Red]

I kind of gave up with the game the other night, but thought I'd throw this onto this thread on the chance someone such as The Exile has some advice. Been repeatedly encountering the EXCEPTION_ACCESS_VIOLATION type errors during multiplayer. In particular I recall it happened twice at the time when a detonator boss enemy died and then the instant the large explosion happens, the game would crash to this type of error. Could not pin down what occurred at the other times this would happen.
Recently did a hardware upgrade (Jan). I've tried various things, but nothing seemed to stick and I continue to encounter the error with varied codes after it (...00005, ...0008, ...fffff)
DXdiag here.
https://pastebin.com/5j2YcVV6

I hope it's not something like needing to forcefully underclock my RAM in BIOS or something...but I'll listen to anything offered so hopefully I won't be left out the next time friends want to play together.
Thanks

[The Exile]

Arem the Red の投稿を引用：

...

Add me as a friend or create a thread and message me the link to the thread. I will help you troubleshoot.

[The Exile]

Arem the Red の投稿を引用：

DXdiag here.
https://pastebin.com/5j2YcVV6

A couple of issues that are immediately apparent.

1. You are using BIOS instead of UEFI and chances are that BIOS is out of date.
2. Windows 10 OS is out of date. You are using 21H2 when 22H2 is the latest.

3. Your graphics card drivers are out of date.

You are on ...

31.00.12029.10015

The latest are...

31.0.14043.1000

4. Chipset drivers are out of date.

5. Your windows error logs are tampered with. Every windows system has errors your just lists no data so either you altered something or your Windows installation is damaged and isn't doing what it should do.

[Arem the Red]

The Exile の投稿を引用：

Arem the Red の投稿を引用：

...

Made a separate thread. https://steamcommunity.com/app/548430/discussions/2/3830914462334218793/

[Tr4ct0r]

Fatal error: [File:Unknown] [Line: 684] pResource->Map(Subresource, pReadRange, reinterpret_cast<void**>(&pData)) failed at C:\BuildAgent\work\DRG-release\UnrealEngine\Engine\Source\Runtime\D3D12RHI\Private\D3D12RHIPrivate.h:1181 with error DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_HUNG

FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
kernel32
ntdll

[The Exile]

MARTIN の投稿を引用：

Fatal error: [File:Unknown] [Line: 684] pResource->Map(Subresource, pReadRange, reinterpret_cast<void**>(&pData)) failed at C:\BuildAgent\work\DRG-release\UnrealEngine\Engine\Source\Runtime\D3D12RHI\Private\D3D12RHIPrivate.h:1181 with error DXGI_ERROR_DEVICE_REMOVED with Reason: DXGI_ERROR_DEVICE_HUNG

FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
FSD_Win64_Shipping
kernel32
ntdll

https://steamcommunity.com/app/548430/discussions/2/3821910251186773790/

[Tr4ct0r]

https://pastebin.com/ABvvRATu

[The Exile]

MARTIN の投稿を引用：

https://pastebin.com/ABvvRATu

I made a thread for you MARTIN, I provided the link to it. Continue your posts there.

I will provide it to you one more time.

HELP FOR MARTIN :
https://steamcommunity.com/app/548430/discussions/2/3821910251186773790/

English to Polish
angielskiego do polskiego

Założyłem wątek dla Ciebie MARTIN, podałem link do niego. Kontynuuj tam swoje posty.

Dam ci to jeszcze raz.

POMOC DLA MARTYNA:
https://steamcommunity.com/app/548430/discussions/2/3821910251186773790/

Długie i krótkie to, co dzieje się w twoim przypadku, to...

Twój sprzęt komputerowy nie jest wystarczający do grania w tę grę, a awarie, które widzisz, są spowodowane tym, że silnik gry nie jest w stanie nadążyć za tym, co musi zrobić, aby utrzymać aplikację w czasie wykonywania.

Przykro mi, przyjacielu, potrzebujesz nowszego sprzętu komputerowego, który jest potężniejszy niż komputer z niższej półki, którego używasz do grania w Deep Rock Galactic na jakimkolwiek akceptowalnym poziomie.

[Barco Basurero Gaming]

I didn't have any problems besides only being able to play in safe mode until i decided to update my horribly outdated graphics. Then i started to have glitched textures covering my whole screen and more crashes

[Barco Basurero Gaming]

here's the pasterbin
https://pastebin.com/Ht7Pc8sy
I got this error out of nowhere while hanging out with the glitchy textures in the spacerig

[The Exile]

Fan Nº1 de Cloud Uzucraft の投稿を引用：

here's the pasterbin
https://pastebin.com/Ht7Pc8sy
I got this error out of nowhere while hanging out with the glitchy textures in the spacerig

You have the paste set to private so no one can see it's contents.

[Keksut]

i did the deep dive to its completion and didnt get my rewards. where are my matrix cores?

[Zot*]

Since 4 season I have been tormented by one bug. The bottom line is that my dwarf can get into textures of drop pod, supply pod, pipes, mule and others textures, making the mission impossible as I can't replenish ammo, unload, repair the pipe and so on. This is ♥♥♥♥♥♥♥♥♥!!!

[kkrwilson12]

I just got this a few weeks ago and I still can't get it to launch. I have a new lenovo tower (bought the game through the microsoft store for x box). I have AMD Ryzen 5 5600G with Radeon Graphics 3.90 GHz, 8GB installed RAM. I've tried re-installing and restarting. I read through this thread and didn't find anything helpful. It starts to load for 3 seconds and then pops up with Error: (0x0).