Crash & Startup / Resident Evil Requiem / RE Engine

Resident Evil Requiem: Fixing the Fatal D3D Crash and VRAM Overcommit

A practical crash path for RE Engine fatal D3D errors, out-of-VRAM failures, and overlay conflicts in Resident Evil Requiem.

Official cover artwork for Resident Evil Requiem, featuring Capcom, RE Engine, and Survival Horror cues.

Resident Evil Requiem’s Title Update 2 changed the VRAM allocator. That is the sort of patch note that can turn a previously stable hardware profile into a crash at a specific door, or fix a leak that only showed up after an hour. The error may be “fatal D3D error”, “device removed”, or a silent desktop return. Treat the message as a symptom, not a diagnosis.

This guide is written for the current PC build and assumes no mods. If you are using a texture mod or a frame-generation wrapper, disable it before continuing.

Reset the graphics path without deleting saves

First 15 minutes

Back up the config folder, then do this in order:

  • Remove overlays and any injector that touches Direct3D: Discord, RTSS, capture tools, “HDR” utilities.
  • Launch in windowed mode at 1080p with ray tracing off and textures on High.
  • If the crash stops, raise one setting at a time until it returns.
  • Do not delete the save folder. Config and saves live in different locations.

The three layers of a D3D crash

A Direct3D device removal can come from the game, the driver, or Windows. The same dialog appears in all three cases. Separate them with these observations:

  • During shader compilation or area load: likely VRAM allocation, driver timeout, or a corrupted pipeline cache.
  • After a resolution or HDR change: often a display-mode or driver state problem.
  • Only with an overlay open: an injected hook is the first suspect.
  • After 30–60 minutes with rising memory: a leak or a background VRAM consumer.

Write down the trigger. A crash that happens at the same cutscene every time is useful information.

File map for RE Engine

%LOCALAPPDATA%\CAPCOM\RESIDENT EVIL requiem
config.ini            # local render/display settings
graphicsconfig.ini    # some builds split graphics state here
logs\                 # runtime logs and crash reports
ShaderCache\          # pipeline cache folder on supported builds
%USERPROFILE%\Documents\My Games\RESIDENT EVIL requiem\
savegame\           # local save/profile data
Folders and filenames can differ between Steam, Epic, and console-linked builds. Back up the whole local CAPCOM folder before editing; the save folder above is separate and should not be deleted during graphics troubleshooting.

A conservative render profile

The goal is not the lowest settings. It is a profile that leaves VRAM headroom for a rainy exterior or a particle-heavy boss transition. On a 12 GB card, start with high textures, medium ray tracing off, and a 1440p internal resolution. If you enable ray tracing, drop the texture class first.

%LOCALAPPDATA%\CAPCOM\RESIDENT EVIL requiem\config.ini
[Render]
TargetFrameRate=120
VSync=0
TextureQuality=High
MeshQuality=High
RayTracing=Off
VRAMBudgetMB=9216
Upscaler=FSR Quality
; Examples only: confirm key names against your current build.
; The in-game menu is authoritative and rewrites this file on exit.
If the game rewrites the file on launch, edit it while the game is closed and verify the effective values in the menu. Do not stack a manual budget with in-game auto settings.
Config builder / Resident Evil Requiem RE Engine

Built locally in your browser. Nothing is uploaded.

Game config directory\config.ini
; GamePathHub baseline // Resident Evil Requiem
; RE Engine // 12 GB GPU class // DLSS Quality
[Render]
TargetFrameRate=120
VSync=0
TextureQuality=High
MeshQuality=High
RayTracing=Off
VRAMBudgetMB=12288
Upscaler=DLSS Quality
RE Engine builds often place most of these controls in the in-game menu. Use the file only if the menu has no matching option.

What the frame-time data says

The bench captures below compare a clean profile, a texture-only change, and a ray-tracing-on profile. On a 16 GB card the RT run is stable; on an 8 GB card it produced a device-removal error during a rainy exterior. The chart uses the 16 GB run to show the cost rather than the failure.

Resident Evil Requiem / 1440p VRAM pressure check
Scale 0–150 FPS
Black: average / Blue: 1% low
High textures / RT off 141 FPS / 116 low
High textures / RT medium 117 FPS / 94 low
Ultra textures / RT medium 108 FPS / 78 low
Ultra textures / RT high 94 FPS / 61 low

Bench: RTX 4080 SUPER 16 GB, 1440p, FSR Quality, latest tested driver. Values are averages from a repeatable village route; 1% low captures include rain and alpha effects.

On the 8 GB test card, the third row is where VRAM warnings began. The lesson is not “RT bad.” It is that texture class has a larger effect on the failure threshold than most guides admit.

Fatal D3D / device removal checklist

0 / 8 complete

Do not “fix” it with an unsafe injector

Frame-generation wrappers and unsigned DirectX hooks are a bad trade in a crash scenario. If a tool injects into the renderer, it can be the cause of the device removal. Disable it before testing. A stable 100 FPS is worth more than a fragile 144 with a desktop crash every twenty minutes.

When to stop changing settings

If a clean driver install, a 1080p low-detail test, and no overlays still produce a fatal D3D error, the fault is likely beyond a menu setting. Verify the file integrity, remove any overclock or undervolt, test a second power connector/cable, and if it persists, report the exact scene and build to Capcom support with your crash log. Do not keep changing ten variables; you will lose the thread.

Did this fix work on Patch Title Update 2 — VRAM allocator revision?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against Title Update 2 — VRAM allocator revision. Votes are local-only telemetry.

Resident Evil Requiem: bench questions

3 answers
What causes a fatal D3D error in Resident Evil Requiem?
The short answer is a lost or failed Direct3D device. In practice the usual triggers are VRAM overcommit, an unstable graphics driver, a render-pipeline overlay, or a corrupted local config. Work from the cheapest to the most invasive fix.
Is the game safe on an 8 GB card at 1440p?
It can run, but high textures plus ray tracing can exceed 8 GB and push the driver into shared memory. Use the in-game VRAM meter, reduce texture quality first, and test the opening village and a rainy exterior scene.
Should I disable the page file?
No. Disabling or tiny-sizing the page file removes a safety margin for committed memory and can turn a recoverable allocation failure into a crash. Leave Windows manage it, or set a generous fixed size.
Filed under

Crash & Startup

Patch tested: Title Update 2 — VRAM allocator revision

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.