[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.

[Mort]

How do you help report a crash when the Ghost Ship Games Crash Reporter doesn't appear on game crash?

[The Exile]

Originally posted by Mort:

How do you help report a crash when the Ghost Ship Games Crash Reporter doesn't appear on game crash?

Post a step by step guide of what you did to get the game to crash without the crash reporter coming up and post a Dxdiag. Also, be willing to answer questions about your setup if the DXdiag results are not complete.

[Punished "Venom" Snake]

so can u help me to fix my cpu usage and lagging too?

[The Exile]

Originally posted by MX_MOHAMAD|TRADEIT.GG:

so can u help me to fix my cpu usage and lagging too?

I can try.

[ZenoCitium]

I am using a MacBook Pro (2019 16" with 8GB GPU) running Windows 10 through Boot Camp.

The game appears to be causing an issue that first makes the computer lose all audio, then a short time later the controls start bugging out (character moves erratically), and shortly after that the whole computer crashes.

This issue can occur after playing a couple missions, or I can go several hours with no issue... so not the most consistent of things.

The only thing consistent about it that I have noticed, is that the symptoms start immediately after the drop pod launches from the space station (once the animation starts of the drop pod flying through space). It is at this instant that the computer audio cuts completely (even microphone inputs, and affects other programs like Discord). I am able to play the level for maybe a couple minutes before the next symptoms kick in and the whole computer ultimately crashes instantly.

This game is quite enjoyable to play, but this issue definitely is making the experience frustrating. Any assistance would be greatly appreciated.

[The Exile]

Originally posted by ZenoCitium:

I am using a MacBook Pro (2019 16" with 8GB GPU) running Windows 10 through Boot Camp.

Just to be clear, you have one of these machines... Correct?

https://support.apple.com/kb/SP809?locale=en_US

and you are running the game in Windows 10 off the mac using the following method...Correct?

https://support.apple.com/en-us/HT201468

[ZenoCitium]

In response to your inquiry:

Yes, I do have one of the machines from the first link you provided.

Yes, I am running the game in Windows 10 using the method in your second link.

[[LUE]super_he_man]

I've been having my entire computer shutdown as well after launching the drop pod to start a mission. It's happened a few times now and I've just never had a game completely power down my whole machine like this when it errors out. hopefully it gets fixed.

[puentin2120]

So my Xbox 360 controller stopped working with the latest update. Tested and works with the rest of my Steam library. Did the normal device manager type uninstall--rediscover deal, still won't work. The strange thing is, it is working in the pause menu (full analog stick movement, buttons, etc). I've logged 220+ hours into the game and have dealt with the crashes, which isn't too terrible, but this one has me scratching my head. Any suggestions?? Update: re-downloaded Windows 7 64 bit driver for Xbox 360 controller; issue solved.

[The Exile]

Originally posted by puentin2120:

So my Xbox 360 controller stopped working with the latest update. Tested and works with the rest of my Steam library. Did the normal device manager type uninstall--rediscover deal, still won't work. The strange thing is, it is working in the pause menu (full analog stick movement, buttons, etc). I've logged 220+ hours into the game and have dealt with the crashes, which isn't too terrible, but this one has me scratching my head. Any suggestions?? Update: re-downloaded Windows 7 64 bit driver for Xbox 360 controller; issue solved.

FYI.

Windows 7 is no longer supported by Microsoft.

You need to update to Windows 10 or use an alternative such as a Linux distribution.

As time goes on you will begin to have more and more issues while using that operating system as all developers have to operate under the assumption that you have left that OS behind since it is no longer supported by Microsoft.

[puentin2120]

Originally posted by The Exile:

Originally posted by puentin2120:

So my Xbox 360 controller stopped working with the latest update. Tested and works with the rest of my Steam library. Did the normal device manager type uninstall--rediscover deal, still won't work. The strange thing is, it is working in the pause menu (full analog stick movement, buttons, etc). I've logged 220+ hours into the game and have dealt with the crashes, which isn't too terrible, but this one has me scratching my head. Any suggestions?? Update: re-downloaded Windows 7 64 bit driver for Xbox 360 controller; issue solved.

FYI.

Windows 7 is no longer supported by Microsoft.

You need to update to Windows 10 or use an alternative such as a Linux distribution.

As time goes on you will begin to have more and more issues while using that operating system as all developers have to operate under the assumption that you have left that OS behind since it is no longer supported by Microsoft.

Sorry, but I am not running Windows 7, I am running Win10 Pro 64. The USB driver for Xbox 360 on Windows 7 64 bit resolved the issue.

[The Exile]

Originally posted by puentin2120:

Originally posted by The Exile:

FYI.

Windows 7 is no longer supported by Microsoft.

You need to update to Windows 10 or use an alternative such as a Linux distribution.

As time goes on you will begin to have more and more issues while using that operating system as all developers have to operate under the assumption that you have left that OS behind since it is no longer supported by Microsoft.

Sorry, but I am not running Windows 7, I am running Win10 Pro 64. The USB driver for Xbox 360 on Windows 7 64 bit resolved the issue.

Ah, so you installed a Windows 7 driver, instead of just using the one in the Windows Update repository. Gotcha.

[The Exile]

Originally posted by Evil Hotdog:

Originally posted by LUEsuper_he_man:

I've been having my entire computer shutdown as well after launching the drop pod to start a mission. It's happened a few times now and I've just never had a game completely power down my whole machine like this when it errors out. hopefully it gets fixed.

Same thing happens here very occasionally, it happened about 4 or 5 times in almost 200 hours of gameplay, also during missions. This is the only program that has ever done this on any computer I owned. Temperatures of both cpu and gpu are below 70°C, PCH temperature never goes beyond 80°C when playing games so I don't think it could be that.

For more modern Nvidia graphics card 70°C causes the driver to throttle performance. 62°C is the limit in such scenarios with those select cards. All cards should be able to easily stay under 62°C as long as you make tweaks to the fan profile using a program like MSI Afterburner. Mind you, this will make your card louder due to the faster fan spinning but the card will also perform better as a result so it's just a trade off.

[The Exile]

Originally posted by Evil Hotdog:

Well, it's a six year old laptop, which always had these temperatures when gaming since the beginning, it's well below the throttling temperatures.

Telling me it's a six year old laptop tells me nothing about the computer Lol. For all I know you can be making it up.

The only way to verify your claims and get some sort of reliable data that will then allow others to provide you with some sort of assistance is for you to actually provide evidence of your machine and it's configuration. The only way to do that is with a Dxdiag. Even with a Dxdiag you can still fake that but, it's at least a better starting point vs...

" Well, it's a six year old laptop,which always had these temperatures when gaming since the beginning, it's well below the throttling temperatures."

Which tells us nothing about your machine or how you have it configured so we have no place to start troubleshooting.

Originally posted by Evil Hotdog:

It's pretty normal.

Says who? You? Some random dude on the internet? A mob of people who have no idea what they are talking about? Lol.

Temps like that are not normal. They are acceptable, sure, and won't cause damage to the GPU but, the driver will still throttle performance at those temperatures on certain laptops. Usually laptops have a bit more room to play with when it comes to temps, some don't, it really depends on the manufacturer of the laptop and how they have decided to configure the Nvidia/AMD part.

So what laptop do you have? What is your configuration in said laptop?
Provide a dxdiag so we can actually look at your PC in detail and give you possible explanations as to why you are seeing what you are seeing. Lol.

Also don't do this in this forum post, make a new one in the bugs section with requested info and provide a detailed account of the issue you are having. We can go from there.

[Evil Hotdog]

Originally posted by LUEsuper_he_man:

I've been having my entire computer shutdown as well after launching the drop pod to start a mission. It's happened a few times now and I've just never had a game completely power down my whole machine like this when it errors out. hopefully it gets fixed.

I've had the same issue. It only happens with this program,
during gameplay and upon loading a map.
Happened about 4 times in about 200 hours playing.

I closely monitored my system when this first happened.
It's not because of overheating, throttling issues, RAM shortage, windows errors or driver errors.

Just reporting the frequency of this issue happening.
Not looking for any help.
The game runs fine otherwise. It's great fun!