Deep Rock Galactic Known Issues, Glitches, Bugs, and Fixes

Deep Rock Galactic has a number of known issues and bugs that are plaguing the game including some for PC and others for consoles.

Ghost Ship Games has provided a list of all the known issues and their fixes. We have also added our own set of known issues based on the problems faced by the players so far.

All Deep Rock Galactic Known Issues, Glitches, Bugs, and Fixes

Deep Rock Galactic PC Known Issues and Fixes

Note: The details below are taken from the official guide.

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.

Deep Rock Galactic PS4/PS5 Known Issues and Fixes

Mutliplayer Not Working or Multiplayer Session Ended

If you are facing this problem on PS4 and PS5, check out this detailed guide to learn more about it. If you want to use a quick fix, try restarting your router according to the developers.