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

Nguyên văn bởi SombreNote:

LoginId:0ab59be4487d0303f4fcb39f58f23046
EpicAccountId:

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

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


Was there any conclusion on this? I just started playing the game and I am getting this error around every 3 minutes.

This usually indicates there are problems with the way software was installed on your machine.

Examples include issues with Windows itself. Problems with how a graphics driver was installed, etc.

There are way to diagnose and fix this but many are reluctant to admit they have an issue and refuse to do the necessary work to fix the issue. Instead they tend to try and blame Ghost Ship Games, which leads to nothing as again... The issue isn't the game... It's the user's PC.

If you are having this issue and are willing to do your part and fix issues on your PC, just add me on steam and let me know. I can walk you through a troubleshooting process.

[Sunshine.]

so uhm... I started the game today and I found out that I have (-) credits... idk what does that mean though... if I sell any resources it goes a little low (like I would pay a credit) xdd and after I restarted the game resources didn't returned back but the (-) credits restarted and returned to the start value ;w; pls help

[SombreNote]

Nguyên văn bởi The Exile:

This usually indicates there are problems with the way software was installed on your machine.

Examples include issues with Windows itself. Problems with how a graphics driver was installed, etc.

There are way to diagnose and fix this but many are reluctant to admit they have an issue and refuse to do the necessary work to fix the issue. Instead they tend to try and blame Ghost Ship Games, which leads to nothing as again... The issue isn't the game... It's the user's PC.

If you are having this issue and are willing to do your part and fix issues on your PC, just add me on steam and let me know. I can walk you through a troubleshooting process.

I fixed the problem by moving my monitor cable from my GeForce GTX 750 Ti to my GeForce GTX 650 Ti. Both were installed, it was just that the game didn't like one of my graphics cards. The other graphics card has no issues otherwise, so it would be "blame the user" bias point to it as the problem.

"There are way to diagnose and fix this but many are reluctant to admit" Nope. I was just lucky to have another card.

[The Exile]

Nguyên văn bởi SombreNote:

"There are ways to diagnose and fix this but many are reluctant to admit their PC is the problem."
- The Exile

Nope. I was just lucky to have another card.

Lol.

[Harlequin]

So if I have checked all solutions for the "Waiting for Steam to load" screen and nothing works is there any unusual idea someone can come up with? This ♥♥♥♥ is pissing me of pretty badly. I am far beyond being upset with DRG already.

[SN3AKYP3T3]

I am having a very strange crashing issue with Deep Rock Galactic . It seems to happen quicker with graphics on ultra . I will be running around in the main lobby and randomly my pc will shut off and will not power back on until I’ve cycled off the power supply switch for about 10 seconds. I have verified all drivers up to date , uninstalled any 3rd party programs that could possibley cause it , ( afterburner , antivirus ,Nvidia ansil/overlays, even steam overlay ). Added Realtek driver fix to the game directory, launch on dx12, removed OC settings on CPu , memory integrity check pass, game file integrity good, re installed on different ssd you name it . Cpu runs at 30% memory 20% GpU 40-60%. PC specs are as follows

Windows 10
Ryzen 1800x
Msi 3080 suprim x ( 3 pin)
Team Group 16x2 3200Mhz Night Hawk memory
TT 850w gold psu
Msi x370 gaming carbon pro
Water cooled cpu ,
great airflow , low temps ( nothing above 61deg c)

I love this game I want to keep playing it but it just won’t stop crashing and locking up my PC ! No error reports and event viewer shows *pc not powered down correctly ( not exact terms sorry )

Please help! Thanks

[The Exile]

Nguyên văn bởi SN3AKYP3T3:

my pc will shut off and will not power back on until I’ve cycled off the power supply switch for about 10 seconds.

Add me on steam. I can help you out.

[Nosteru]

Nguyên văn bởi The Exile:

Nguyên văn bởi SN3AKYP3T3:

my pc will shut off and will not power back on until I’ve cycled off the power supply switch for about 10 seconds.

Add me on steam. I can help you out.

Dear Exile,

You seems a very helpful lad here.
I pulled one of my RL friend into this awesome game to we play together. Sadly his game crash totaly randomly. We tried the solutions here but it just reduced the crash frequency but not removed the issue.
Please if you may take a look on this crashreport I made by his problem:
https://steamcommunity.com/app/548430/discussions/2/3017941618719314295/

Many thanks in advance if you willing to help us!

[Creamy Mouth Surprise]

What about this? The game is unplayable as of late on my PC. I was running my overclocks before and the game was fine. Occasional crash every 3-4 hours. Now I am lucky if I get 3-4 minutes before it crashes. This is the error I get.


I have gotten rid of my overclocks on my GPU (not my CPU yet since it's more intensive). I a running the PBO2 with the latest Bios from MSI and as I said before I have no issues with other games/apps.

Deep Rock seems to crash every 3-4 minutes. Sometimes it even crashes with a full screen of death and once even no BSOD but the entire system restart. All the crashes/errors register on "BlueScreenView.exe" but I am not sure what to do with that info. This is the type of error I typically get.

LoginId:73ff25c64553a3fcfb4119b5ba08d533
EpicAccountId:109a124bf18243828079238f169e1fa0

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x24c79860

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 only thing that seems to change is the following line in there errors:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x8b3c0458
Another one:

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x24c79860

After some searching, I was pointed to Memory/RAM issues and I happen to have another set of 8x2 Ram. I tested with the new ram with the same issues.

Also ended up doing a Memtest86 for about 12 hours overnight with 0 errors being displayed.

What are my next steps? Removing the overclocks on my CPU? The issue wasn't as present before, but I did have a few crashes in December as well from the start when I bought my game. About one every 2-3 hour gaming session.

Hoping to get some insight on what the possible issues/causes and fixes are. Thanks all in advance.

[SN3AKYP3T3]

Nguyên văn bởi Nosteru:

Nguyên văn bởi The Exile:

Add me on steam. I can help you out.

Dear Exile,

You seems a very helpful lad here.
I pulled one of my RL friend into this awesome game to we play together. Sadly his game crash totaly randomly. We tried the solutions here but it just reduced the crash frequency but not removed the issue.
Please if you may take a look on this crashreport I made by his problem:
https://steamcommunity.com/app/548430/discussions/2/3017941618719314295/

Many thanks in advance if you willing to help us!

I did a fresh install of windows and didn't install any driver but my AMD chipset and Nvidia drivers. Still Crashed. No memory issues, no system 32 corruption no hardware issues. The only fix I found is to cap the FPS at 60. For some reason the gpu runs away on me and hard crashes the PC. The Exile is very knowledgeable and can probably help you, however for me, the only fix was the fps cap.

[Nosteru]

Nguyên văn bởi SN3AKYP3T3:

Nguyên văn bởi Nosteru:

Dear Exile,

You seems a very helpful lad here.
I pulled one of my RL friend into this awesome game to we play together. Sadly his game crash totaly randomly. We tried the solutions here but it just reduced the crash frequency but not removed the issue.
Please if you may take a look on this crashreport I made by his problem:
https://steamcommunity.com/app/548430/discussions/2/3017941618719314295/

Many thanks in advance if you willing to help us!

I did a fresh install of windows and didn't install any driver but my AMD chipset and Nvidia drivers. Still Crashed. No memory issues, no system 32 corruption no hardware issues. The only fix I found is to cap the FPS at 60. For some reason the gpu runs away on me and hard crashes the PC. The Exile is very knowledgeable and can probably help you, however for me, the only fix was the fps cap.

Somehow when first time he set the FPS cap to 60 and even vsync enabled the game stopped crashing for a while. We were happy that found an easy fix. However the crash started later. It is totaly random. Sometimes we can finish two or three mission, play for like 2 hour. Other times he crashing repeatedly. Once he even crashed on the RIG when just watching his Perks (eg very low graphic demand time).
Yes Exile tried to help us, but my friend dont want to go trough this deep repair procedure, like windows repair, even reinstall as otherwise his system run fine without other anomalies, except DRG crash what is silly random. Atm we try to find another easier accesible solution to fix the issue.

[Harlequin]

lol cant even report a freaking crash cuz this great game wont let me get behind the "waiting for bs"-screen and i get zero help from devs. ♥♥♥♥ game XD

[The Exile]

Nguyên văn bởi Harlequin:

lol cant even report a freaking crash cuz this great game wont let me get behind the "waiting for bs"-screen and i get zero help from devs. ♥♥♥♥ game XD

If you crash and you don't get an engine prompt of the crash, then the issue is entirely related to your operating system or some issue with your hardware, not the game or game engine. There are fixes that you can apply to fix whatever is broken with your system but, no patch the dev makes for the game will fix issues with your OS or how poorly your system is maintained. That is something that is entirely your responsibility. I have offered to help people with these issues and many have had their issue solved by working with me. I have yet to have you reach out to me for help.

One thing that won't help, and this is a certainty, is you talking trash about the devs or the game they've put together. Cursing at them on this forum for something that isn't even in the realm of their responsibility... It just isn't helpful.

Have you provided a DXdiag?
Have you created a separate forum post asking Mark or Bjorn for help and providing them your DXdiag so they can try to help you troubleshoot your issue?
Have you provided them an idea of how you have your home network setup?
Have you provided them a YouTube video of what happens to you?
Both Nvidia and AMD have internal H.264 encoders in all of their modern graphics cards. All of these modern graphics cards can record video of your gameplay with little to no effort on your part. These recordings can be uploaded to YouTube and the link to the video can be posted in a forum post. Stuff like that would be very helpful in diagnosing your issue and helping you with a solution.

If your answer is no to all of these questions... You aren't doing your part in looking for help from them. They don't know who you are, what system you have, how it's setup, and there are so many factors that could lead to the problems you are having that it's impossible for them to diagnose and help you with just...

"i get zero help from devs. **** game XD"

Do your part and you will get the help you need. Attack the game and devs irrationally and illogically... and well... There isn't much they can do for you if that is how you are going to go about "getting help".

[/* ToAsT */]

Looking for some assistance from you guys if you can help. Apologies if I missed a recommended step from the previous posts.

I've been struggling with the "Unreal Engine is exiting due to D3D device being lost" issue ever since I swapped my video card from an MSI Radeon R9 390 to a Sapphire Pulse RX 5600 XT a few weeks ago. This is the exact same card that I installed on a new build for my partner and she hasn't had any of these issues. Any game I've tried that uses the unreal engine will crash within about 30 seconds of starting, including Deep Rock Galactic. I also tried Fortnite and a couple other games, which also crash. I can't return the video card for a refund and I don't want to go back to my old card (which worked but was at its end of life). I found a way to prevent the crashing, but I don't understand why it resolves it, and this likely isn't a proper workaround for other games that might be affected by this issue (see further below). Posting the dxdiag text here pushes me way over the limit so I placed a copy here: https://pastebin.com/m23TXZBi

Other tech details:
CPU: Intel Core i5-6600K CPU @ 3.50GHz
Motherboard: MSI Z170A GAMING M5
32GB RAM

What I tried (following the troubleshooting issues in the first post and others related to this issue):
- Restarted multiple times. I'm not overclocking anything. Temps are fine (and much lower than my R9 390 in the same games) according to GPU-Z and AMD Performance tab.
- I used DDU to completely remove my drivers twice (once before switching cards and again to see if it would resolve this issue. This made no difference.
- Verified the integrity of the game files. Later I completely uninstalled DRG via Steam. Deleted the associated folders that I could find. Reinstalled. Same issue.
- I tried the latest recommended AMD drivers as well as the latest non-recommended (beta?) ones from early this year. No change.
- Modified the registry to add TdrDelay=10 but that just caused my game to freeze longer before crashing.
- Changed the resolution, different window modes, set an FPS Limit of 60, disabled AA. Still crashes.
- I can't copy the text from the crash reporter because the crash completely locks up my display until I kill the DRG process (which also closes the crash reporter). Is there another way to obtain the text there? Either way, it's the same "Unreal Engine is exiting due to D3D device being lost" as mentioned before.
- Cleared DirectX Shader cache files using Disk Cleanup.
- I don't have integrated graphics installed or enabled on my motherboard BIOS or within WIndows 10.

***What (almost) resolved it***:
- I added -dx12 flag on startup to DRG. No crashes since, although I've only played in-game for about 20 mins. Still, it's far better than a crash in the first 30s.
- Similarly, forcing DirectX 12 (Beta) in Fortnite resolved the crashing there too.
**EDIT**: This was only a temp fix - it would just take longer to crash.

I don't believe this issue is due to overheating. It's a brand new card, I've used it in several other non-unreal engine games that have pretty good but not great graphics (e.g., Green Hell) without any crashes. I'm worried that this issue will happen in other DirectX 11 Unreal engine games that I haven't played in a while but that don't have a DirectX 12 option :(.

Is it possible some DirectX 11 settings / drivers / cache are looking for my older card? I never forced DirectX 12 in any of my games while using the R9 390 to my knowledge.

Again, a link to the dxdiag information: https://pastebin.com/m23TXZBi

[The Exile]

Nguyên văn bởi /* ToAsT */:

...

As I've previously stated. It's best to create a separate post in the crash+bug forum here on Steam than it is to post to this post.

However...

I will try to help you as best as I can.

After reviewing your data, it seems like your issue is related to your BIOS.

You are using a vastly outdated BIOS that did not have that graphics card in mind when it was released. This is probably the cause of all your issues.

You need to update to BIOS 7977v1I.

US Link:
https://us.msi.com/Motherboard/support/Z170A-GAMING-M5

This is not optional either. This BIOS update also addresses several key Intel Microcode Vulnerabilities that you need to be protected from.

Far to often people fail to update their BIOS on their motherboard, thinking they don't have to, and well that is just vastly incorrect. You need to update. Updates are put out for a reason and it's often security or compatibility related.

Update your BIOS and re-install your video drivers with the latest one's from AMD's website. That should do the trick. Assuming there are no other issues with Windows or the hardware itself and how it's installed.