How to Fix: Resident Evil Requiem Fatal D3D Error

Quick Fix

Most players fix this by turning off Ray Tracing and Frame Generation first, since those are the most reported culprits:

1. Disable Ray Tracing. Go to Options → Display/Graphics and turn Ray Tracing off entirely.
2. Disable Frame Generation (DLSS/FSR FG). Turn this off in the same graphics menu.
3. Revert any GPU overclock. Reset your card to stock clocks and voltages, even if it is only factory-overclocked.
4. Update or clean-install your GPU driver. Use the latest driver from NVIDIA/AMD, doing a clean install if possible.

Step-by-Step Guide

What this error means

The 'Fatal D3D Error' in Resident Evil Requiem is a crash in Capcom's RE Engine where Windows' DirectX component loses contact with your graphics card. It commonly appears with a code such as Fatal D3D Error (24, DXGI_ERROR_DEVICE_REMOVED, 0x887a0005), sometimes followed by DeviceRemovedReason (0x887a0006). Other variants players report include DXGI Error Device Removed, E_ACCESSDENIED, 0x80070005, and E_OUTOFMEMORY. In plain terms: the GPU driver crashed or the graphics device was reset mid-game, forcing the game to abort. This is not unique to Requiem — Capcom's previous RE Engine games, like Monster Hunter Wilds and Dragon's Dogma 2, have experienced the same Fatal D3D error message, suggesting an engine-level sensitivity to certain GPU settings rather than one single bug.

The error can be caused by several different things, so work through the fixes below in order — most people are fixed by the first two or three.

Fix 1: Turn off Ray Tracing and Frame Generation

Community reports consistently point to ray tracing and frame generation features as the biggest trigger.

1. Disable Ray Tracing. One affected player confirmed turning OFF Ray Tracing fixed it, though there are graphical artifacts happening sometimes as a side effect, meaning you may still need to restart occasionally even with it off.
2. Disable Frame Generation. Another user reported that turning OFF framegen seems to have fixed the issues, managing to play about 3 hours without the game crashing.
3. Note the likely cause. As one Steam thread summarized, there are different Fatal d3d errors that many players are experiencing, and the most likely culprits are NVIDIA DLSS, Frame Generation, and Reflex in most cases.
4. If you play with path tracing enabled, try dropping to standard ray tracing or off entirely before testing again.

Fix 2: Revert any GPU overclock

1. Reset your GPU to stock settings. If you have overclocked your graphics card or if it is factory overclocked, then revert it to its default clocks and voltages.
2. Also check memory clocks specifically. One report notes if you have a factory overclock on your GPU or are manually pushing your memory clocks, dial them back, since the RE Engine is incredibly sensitive to unstable memory frequencies, and reducing memory clock by even 100MHz can be the difference between a hard crash and a smooth playthrough.
3. Use your GPU vendor's tool (MSI Afterburner, NVIDIA app, AMD Adrenalin) to reset to factory defaults, then relaunch the game.

Fix 3: Clean-install your GPU driver

1. Uninstall your current driver using a tool like Display Driver Uninstaller (DDU) in Safe Mode, or use the 'clean install' option in the NVIDIA/AMD installer.
2. Install the latest driver from NVIDIA or AMD's official site. Community advice explicitly recommends to clean install GPU drivers, preferably the latest ones.
3. Note: one player reported that a normal driver update alone did not resolve it — driver update didn't help — so if a simple update fails, try the full clean-install/reinstall route instead.

Fix 4: Lower texture quality if you have 8GB VRAM or less

1. Lower Texture Quality. Turn off Ray Tracing or lower Texture quality setting for GPUs with 8 GB or less VRAM, since this specific fix targets the Device Removed variant of the error.
2. One user with a 10GB card confirmed lowering textures from high to normal seemed to do the trick, having not been in the red with a 10gb 3080 but close to it.
3. Open Task Manager or an overlay like MSI Afterburner during gameplay to check if VRAM usage is maxing out before a crash.

Fix 5: Remove third-party overlays and injectors

1. Uninstall ReShade or similar injectors. Some sources report the game aggressively rejects ReShade injection, causing an immediate crash on startup, so remove it entirely if installed.
2. Disable other overlays such as Discord, GeForce Experience/NVIDIA app overlay, or RGB software overlays temporarily to rule them out.

Fix 6: Check for corrupted or missing game/system files

1. Verify game file integrity through Steam (right-click the game → Properties → Local Files → Verify Integrity of Game Files) or the equivalent option on your storefront.
2. Install Visual C++ Redistributables. Missing VC++ 2019/2022 runtime libraries can cause startup crashes; download the latest redistributables from Microsoft's official site.
3. Check for a rogue hid.dll. Some crash guides note a fake hid.dll placed in your Steam root folder can interfere with DirectX initialization — check C:\Program Files (x86)\Steam\ for a suspicious hid.dll and remove it if it does not belong there.

Fix 7: When to look elsewhere for help

1. If crashes persist after all the above, it may be a driver-level incompatibility that only Capcom or NVIDIA/AMD can patch — check for a day-one or post-launch stability patch, since Capcom typically issues fixes within the first couple weeks of a major release.
2. If your hardware is genuinely unstable (crashes across multiple other demanding games too, not just this one), consider stress-testing your GPU and RAM, as this could point to a hardware or PSU issue rather than a game bug.
3. Report the exact error code (the numbers in parentheses) on the official Resident Evil Requiem Steam discussions or Capcom support if none of these steps work, since different sub-codes (E_OUTOFMEMORY vs DEVICE_REMOVED vs E_ACCESSDENIED) can have different root causes.

Platform note: These fixes apply to the PC version of Resident Evil Requiem on Windows. If you are on console, this specific 'D3D' error does not apply, since Direct3D is a Windows-only graphics API.