Resident Evil Requiem — Common Errors & How to Fix Them
The crashes and error messages players actually hit in Resident Evil Requiem, what causes each one, and the fix that works.
Last updated 2026-09-25 · evergreen reference
Below are the errors Resident Evil Requiem players report most often on PC, paired with the cause and the fix that actually resolves it. Resident Evil Requiem runs on the RE Engine, and several of these faults are engine-level rather than game-specific — which is why the same fix keeps appearing across different 2026 releases. Work through them in order: the cheap, reversible steps first, and the invasive ones (BIOS updates, clean driver installs, page file changes) only if the symptom matches.
The errors and their fixes
Symptom, cause, and the fix that resolves it.
“Out of Video Memory” or DXGI_ERROR_DEVICE_HUNG
**Cause:** Two different root causes get reported under the same message. On Intel 13th/14th-gen Core i7/i9 CPUs the crash happens during Oodle asset decompression and is CPU voltage instability, not VRAM. On other systems it is genuine VRAM exhaustion.
**Fix:** If the crash is during shader compilation before the main menu and you have a 13900K/14700K/14900K, update the motherboard BIOS to microcode 0x129/0x12B and load the Intel Baseline profile. If the crash is in-game or on fast scene changes, drop Textures from Ultra to High (saves roughly 2GB), disable ray tracing, and put the page file on an NVMe SSD.
Crash or hang during shader compilation
**Cause:** The RE Engine decompresses and compiles shaders on first launch; unstable CPUs fail in the Oodle decompression step.
**Fix:** BIOS microcode update per above. Then delete the shader cache under %LOCALAPPDATA%\Capcom\Resident Evil Requiem and clear Steam’s global shader pre-cache, and relaunch. Expect one to three minutes of recompilation.
Black screen with audio playing
**Cause:** A long-standing RE Engine fullscreen/HDR initialisation fault.
**Fix:** Press Alt+Enter to toggle windowed. If that fails, delete config.ini in the Capcom save folder to reset graphics, and disable HDR in Windows Display Settings before launching. RE Engine HDR init can black-screen certain monitors.
Mouse cursor stuck on screen
**Cause:** Known RE Engine input bug when switching between mouse/keyboard and controller.
**Fix:** In Options > Controls set the input mode explicitly to Keyboard/Mouse Only or Controller Only instead of auto-detect. If the cursor persists, Alt+Tab out and back in.
White dots along the bottom of the screen
**Cause:** A documented DLSS artifact at the lower presets.
**Fix:** Switch DLSS from Performance to Balanced or Quality.
FPS tanks in large open areas
**Cause:** The Mesh Quality setting is the single biggest offender in this port.
**Fix:** Set Mesh Quality to Low and Volumetric Lighting to Medium. On AMD cards also try disabling ReBAR.
Stutter when frame generation is on
**Cause:** Frame generation plus in-game V-Sync interacts badly, and frame generation itself costs 1.0–1.5GB of extra VRAM.
**Fix:** Disable in-game V-Sync and use NVIDIA Control Panel V-Sync instead, cap frames with RTSS below your refresh rate, and keep frame generation off entirely on 8GB cards.
Fix order if you do not know which one you have
Cheapest and most reversible first.
1. Verify and restart
Verify game file integrity through your launcher and restart the PC. This clears stuck background tasks and driver hooks, and repairs the corrupt downloads that launch-day server load makes common.
2. Drivers, cleanly
Install the latest GPU driver from the vendor site rather than Windows Update, and choose the clean-install option. Both NVIDIA and AMD ship game-ready drivers for major releases that fix compatibility outright.
3. Strip overlays and background hooks
Disable Steam, Discord, Xbox Game Bar, GeForce Experience and MSI Afterburner overlays, along with RGB utilities and hardware monitors. These inject code into the game process and are one of the most frequent crash triggers.
4. Rebuild the shader cache
Clear the DirectX shader cache from Windows Disk Cleanup and delete the game’s own shader cache folder, then let it rebuild. Corrupted shader caches cause crashes that look like hardware faults.
5. Only then touch hardware settings
Remove GPU and CPU overclocks including RAM XMP/EXPO, check temperatures, and if the crash pattern points to CPU instability rather than the GPU, update the motherboard BIOS before assuming your hardware is faulty.
When it is not your PC
Engine and patch bugs worth knowing about.
Known engine-level issues
Several Resident Evil Requiem faults trace back to the RE Engine rather than to your hardware — shader compilation crashes, overlay conflicts and memory leaks during long sessions are the recurring three. These get patched; the workarounds above exist to keep you playing until then.
Reporting it usefully
When you report a crash, include the exact error message, when it started, whether it followed a patch or driver update, your GPU model and driver version, and whether ray tracing, overlays or overclocks were enabled. That distinction is what separates a game bug from a system problem.
Related pages
This is an independent player reference and is not official documentation for Resident Evil Requiem. GameRulePro does not host or link to copyrighted assets. Modding guidance is for single-player use only — never use mods in online multiplayer. Verify current requirements, prices and policies with the publisher before acting.
Keep fixing
Can I run it? FPS calculator
Check whether your hardware, not the settings, is the limit.
Open →All fix & optimization guides
Every crash, black-screen and FPS guide we have published.
Open →Game database
System requirements and projected FPS for 335 titles.
Open →Release calendar
Launch dates and platforms for upcoming games.
Open →