TL;DR
- The most common GPU crash error is: “Unreal Engine is exiting due to D3D device being lost (Error: 0x887A0006 – HUNG)”
- Switch to DirectX 11 first — add
-dx11to your Steam launch options. This fixes most GPU crash cases fast. - AMD users: disable Anti-Lag and the in-game overlay in AMD Adrenalin software before anything else.
- Turn off every overlay — Steam, Discord, Nvidia App, AMD Adrenalin, Afterburner, OBS. All of them.
- Clear your DirectX Shader Cache through Windows Disk Cleanup.
- Reset all overclocks and undervolts to stock, even ones that are stable in other games.
- If crashes happen after 20–30 minutes, check GPU temperature and VRAM usage — heat and VRAM overflow are two of the most common causes.
- Do a clean GPU driver reinstall using DDU if nothing else works.
The GPU crash in Hell Let Loose Vietnam is one of the most reported PC issues since launch. It usually shows up as a sudden black screen, a desktop return with no warning, or the error message “Unreal Engine is exiting due to D3D device being lost.” Some players crash every match. Others get 20–30 minutes before it hits. The cause is almost always one of a small number of things: DirectX compatibility, overlays conflicting with the rendering pipeline, GPU temperature, VRAM running out, or an overclocked component cracking under sustained 50v50 load. This guide works through every fix in order, starting with the ones that solve it most often. For broader crash issues beyond the GPU, the Hell Let Loose Vietnam crash fixes guide covers other crash types including startup crashes and Easy Anti-Cheat issues. The official developer launch page at hellletloose.com also lists confirmed AMD GPU workarounds directly from Expression Games.
What the GPU Crash Error Actually Means
When you see this error:
LowLevelFatalError [File:Unknown] [Line: 198]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 – ‘HUNG’)
It means the GPU stopped responding to DirectX commands for long enough that Windows gave up waiting and terminated the process. Error code 0x887A0006 specifically means the GPU was “HUNG” — it locked up mid-render. The less common 0x887A0005 means “REMOVED” — the device was physically lost or reset.
Both are GPU-level failures, not game-side bugs. The game triggers the situation but the actual failure happens at the driver or hardware layer. That is why fixes involve DirectX version, drivers, overlays, and hardware stability rather than in-game settings alone.
With DX12 this error often crashes silently — no popup, just a return to desktop. With DX11 the error message appears. If your crashes leave no popup at all, you are likely on DX12 and the same fixes apply.
Fix 1: Switch to DirectX 11
This is the fix that works for the most people and takes thirty seconds to try. DirectX 12 offers better CPU threading on paper, but its implementation in this game causes GPU hangs on a wide range of hardware — both AMD and Nvidia. DX11 is more stable for most players right now.
In Steam, right-click Hell Let Loose: Vietnam, select Properties, and find the Launch Options field in the General tab. Type this and close the window:
-dx11 -USEALLAVAILABLECORES -malloc=system
Launch the game and play a full match. If it does not crash, leave this in place until a patch improves DX12 stability. If you want to try DX12 again later, swap -dx11 for -dx12. The -USEALLAVAILABLECORES and -malloc=system additions help CPU scheduling and memory allocation — they are safe on all hardware and have helped some players even when the DirectX version was not the core issue.
Fix 2: Disable All Overlays
Overlays inject code directly into the game’s rendering pipeline. In Unreal Engine 5, this causes conflicts that show up as GPU hangs — particularly under the heavy load of a full 50v50 server. This is one of the most overlooked fixes and one of the most effective.
Turn off every overlay you have running:
- Steam Overlay: Right-click the game in your library → Properties → General → uncheck “Enable the Steam Overlay while in game”
- Discord Overlay: Discord Settings → Game Overlay → toggle off “Enable in-game overlay”
- Nvidia App / GeForce Experience: Open the app → Settings → toggle off in-game overlay
- AMD Adrenalin In-Game Overlay: AMD Software → Settings → General → disable In-Game Overlay
- MSI Afterburner / RivaTuner Statistics Server: Close both entirely from the system tray
- OBS, Overwolf, Twitch Studio: Close these fully while testing — do not just minimize them
Test the game with all of them off. If the crash stops, re-enable them one at a time to find which one is responsible. Many players find Discord or the Nvidia overlay is the culprit.
Fix 3: AMD-Specific Settings (AMD GPU Owners)
AMD GPU owners have had more GPU crashes than Nvidia users in Hell Let Loose Vietnam, and the developers confirmed this on launch day. Beyond the DX11 switch above, two AMD-specific settings are directly linked to crashes in this game.
Disable AMD Anti-Lag
Radeon Anti-Lag has been connected to GPU crashes and a white flickering visual bug on the ground in Hell Let Loose Vietnam. Open AMD Software: Adrenalin Edition, go to Gaming, and find Hell Let Loose: Vietnam in your game list. Toggle Anti-Lag off. If there is no per-game profile for it, disable it in the Global Graphics settings instead. Apply and restart the game.
Disable the AMD In-Game Overlay
The AMD Adrenalin in-game overlay hooks into the rendering pipeline in a way that conflicts with this game. Go to AMD Software → Settings (gear icon in the top right) → General → turn off In-Game Overlay. This is separate from the overlay toggle inside the Gaming section — make sure you hit both.
Try a Previous AMD Driver Version
Not every new AMD driver is stable with every game. If you installed the latest driver and crashes started or got worse, try rolling back to the previous version. On AMD’s download page at amd.com/support, scroll down to find previous driver versions. Do a clean install using DDU (covered below in Fix 7) before installing an older version.
Fix 4: Clear the Shader Cache
A corrupted shader cache is one of the quieter causes of GPU crashes — nothing about your setup looks broken, but the game loads bad shader data and hits a rendering error mid-match. It is especially common after a game update or a partial download.
Open the Windows Start menu and search for Disk Cleanup. Run it on your system drive (usually C:). Check the box for DirectX Shader Cache and clear it. Restart your PC before launching the game again. Expect the first match to have some shader compilation stutters — this is normal as the cache rebuilds cleanly.
Nvidia users can also clear Nvidia’s own shader cache separately. Close all Nvidia apps and services through Task Manager first, then navigate to C:\Users\[your username]\AppData\Local\NVIDIA (AppData is a hidden folder — enable Show Hidden Items in File Explorer to find it) and delete the contents of the cache folders inside. Restart and relaunch.
Fix 5: Remove Overclocks and Undervolts
This is the fix players resist the most, and it is also one of the most effective. Overclocked GPUs, undervolted GPUs, and XMP/EXPO RAM profiles that are stable in every other game often fail under the specific combined load of a 100-player Unreal Engine 5 match with dense jungle foliage, vehicle physics, and helicopter rendering all running simultaneously.
If you are using MSI Afterburner, AMD Adrenalin overclocking tools, or any GPU utility with a custom frequency or voltage profile — reset everything to stock and close the software. Also check your RAM settings in BIOS. If XMP or EXPO is enabled at an aggressive profile, try disabling it or stepping down to a lower frequency profile.
Test the game completely stock. If the crashes stop, you have your answer. You can then re-introduce overclocks gradually to find the stability limit this specific game requires.
A particularly important note for Nvidia users: some RTX cards that have been running for several years have dried thermal paste between the die and cooler. Sustained high-temperature loads under this game’s demand can push those cards into thermal throttling or hard crashes that present as D3D errors. If your card is several years old and crashes always happen after a similar amount of play time, heat is worth investigating.
Fix 6: Check GPU Temperature and VRAM Usage
Two hardware-level causes show up as GPU crashes: overheating and running out of VRAM.
GPU Temperature
Download GPU-Z or use MSI Afterburner’s on-screen display to monitor your GPU temperature during a match. A GPU consistently above 85–90°C will trigger thermal throttling and eventually a driver timeout crash. Hell Let Loose Vietnam’s dense jungle rendering is more GPU-demanding than most games at equivalent settings.
If temperatures are high: check that your GPU fans are spinning and that the cooler is not clogged with dust. Clean the heatsink with compressed air. Make sure your PC case has adequate airflow — side panels fully on, no cables blocking fans. If the card is several years old and you have never repasted it, dried thermal paste is a legitimate cause of these temperature crashes.
You can also set a more aggressive manual fan curve in MSI Afterburner: set fans to 80–100% speed at 70°C rather than letting the automatic curve react slowly. This keeps temperatures lower during sustained load.
VRAM Overflow
When the game tries to use more VRAM than your GPU physically has, Windows starts offloading to system RAM. This causes severe stutters followed by a D3D device crash. It is common on 6GB and 8GB VRAM cards running Texture Quality at High or Ultra.
To check if this is your issue, lower Texture Quality one step, then lower Shadow Quality to Medium or Low. These two settings have the largest impact on VRAM usage. If crashes stop after lowering them, VRAM was the cause. Check the best PC settings guide for recommended settings by VRAM tier.
Fix 7: Change the TDR Delay in Windows Registry
Windows has a Timeout Detection and Recovery (TDR) system that monitors how long the GPU takes to respond to commands. If the GPU takes too long — even during a brief but legitimate rendering spike — Windows kills the process and you get the D3D crash. Increasing the TDR delay gives the GPU more time before Windows decides it has hung.
This is a registry edit — follow the steps carefully. Press Win + R, type regedit, and press Enter. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers
Right-click in the right panel, select New → DWORD (32-bit) Value. Name it TdrDelay. Double-click it, select Decimal, and set the value to 8. Click OK and restart your PC.
This does not fix the underlying cause of GPU spikes but it stops Windows from killing the game during brief spikes that the GPU would have recovered from on its own. It is particularly useful for players who crash during heavy combat moments like helicopter attacks, artillery, or large firefights.
Fix 8: Clean GPU Driver Reinstall with DDU
A clean driver reinstall removes every trace of old driver files that standard updates leave behind. These leftover files can conflict with new drivers in ways that cause D3D crashes specifically under UE5 games without causing any problems elsewhere. This is the nuclear option but it has a high success rate for persistent crashes.
Download Display Driver Uninstaller (DDU) from guru3d.com. Before running it, download your target GPU driver from nvidia.com/drivers or amd.com/support so you have it ready to install afterward.
Boot Windows into Safe Mode: go to Settings → System → Recovery → Advanced Startup → Restart Now → Troubleshoot → Advanced Options → Startup Settings → Restart, then press 4. In Safe Mode, run DDU, select your GPU manufacturer, and choose Clean and Restart. After Windows restarts normally, install the GPU driver you downloaded. Do not install any optional companion utilities during the install — keep it to the driver only. Restart after installation and test the game.
Fix 9: Switch to Windowed Fullscreen Mode
Some players find that exclusive fullscreen mode triggers GPU crashes that stop when they switch to Windowed Fullscreen (also called Borderless Window). Exclusive fullscreen gives the game more direct control over the display, which can amplify driver conflicts.
In the game’s Video settings, change the display mode to Windowed Fullscreen. The visual difference is negligible in most cases and it removes one potential cause of the D3D crash without affecting gameplay.
Fix 10: Verify Game Files and Update Visual C++ Redistributables
Missing or corrupted game files can cause GPU crashes because the engine tries to load a rendering asset that is broken. In Steam, right-click the game → Properties → Installed Files → Verify integrity of game files. Wait for it to complete and replace anything it finds.
Also make sure your Visual C++ Redistributables are current. These are runtime libraries that Unreal Engine 5 relies on for rendering operations. Download the latest x64 packages from Microsoft’s Visual C++ Redistributables page. Install both the x64 and x86 versions, restart, and test.
Still Crashing After All of This?
If you have worked through every fix above and still get D3D crashes consistently, the most useful thing you can do is report it properly. The developers are actively tracking crash data. When you report, include your exact GPU model, driver version, whether you are on DX11 or DX12, how long before the crash happens, and what is on screen when it hits (heavy combat, helicopter pass, specific map). Reports with this detail help Expression Games identify which hardware configurations still need patches.
Submit reports through the official Team17 support page at support.team17.com or post on the Hell Let Loose: Vietnam Steam discussions in the Report a Problem section. Other players often find GPU-specific workarounds that are not in official documentation, and checking discussions for your exact GPU model is worth doing before giving up.
For other types of crashes — startup failures, Easy Anti-Cheat errors, or crashes with no error message — the full crash fixes guide covers those separately.
