Resident Evil Requiem Errors: Fix Paths, and When to Ask for a Refund
Every documented Resident Evil Requiem error, the fix order that works, and how to tell a fixable bug from one that merits a refund.
Last updated 2026-09-25 · evergreen reference
This page lists the errors Resident Evil Requiem actually throws on PC and the order to fix them in. Start with verification and drivers, then move to the engine-specific causes. The point is to get you to a working game quickly — but also to tell you when you are done: if you have worked through this list and the game still will not run, that is the point at which a refund request is reasonable, and you should include what you tried when you contact the store.
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 to stop and request a refund
Drawing the line on unfixable problems.
Documented, acknowledged faults
If a fault is acknowledged by the developer as a known issue, say so in your refund request and include the crash pattern. Store refund windows are usually 14 days with under two hours of play, but documented technical faults that make a game unplayable are a valid reason to push past that — attach your crash logs and the steps you already tried.
What to include in the ticket
Include the full error text, when the problem began, whether it followed a patch or driver update, your hardware and driver versions, and the troubleshooting steps already attempted. A refund request with evidence is far more likely to be granted than one without.
Related pages
This is an independent player reference and is not official documentation for Resident Evil Requiem Errors: Fix Paths, and When to Ask for a Refund. GameFixPro 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.