No More Room in Hell 2No More Room in Hell 2

crash-fixes

title: "No More Room in Hell 2 Crash Fixes Tips & Strategies" description: "Fix crash fixes tips & strategies in No More Room in Hell 2 with our comprehensive troubleshooting guide. Solutions for common errors, crashes, and." keywords: ["NMRiH2", "No More Room in Hell 2", "fix", "error", "crash", "bug", "issue", "problem", "fixes"] date: "2026-08-16" lastModified: "2026-08-16" category: troubleshooting tags: [n mrih2, crash, fix, troubleshooting, guide]

Crash Fixes

No More Room in Hell 2 (NMRiH2) is a demanding cooperative survival horror game that pushes both hardware and software to their limits. While the tense atmosphere and hordes of zombies are part of the appeal, an unexpected crash can pull you right out of the experience. This guide compiles the most common crash scenarios, their root causes, and step-by-step fixes to get you back to the apocalypse.

Crash troubleshooting is rarely a one-size-fits-all process. The following sections are ordered from the simplest and most common solutions to more invasive ones. Always start by restarting your PC and updating your OS, then work through the remaining steps methodically. Git gud at fixing, not just surviving.

Common Crash Scenarios

NMRiH2 can crash in different ways. Knowing exactly when a crash happens is the first step toward solving it. Pay attention to the moment of failure—is it on boot, during a specific action, or randomly in the middle of a firefight?

Startup Crashes

Crashes that occur immediately after launching the game, before the main menu appears, are almost always related to missing or corrupted files, or severe API mismatches.

  • Symptoms: Game opens to a black screen, freezes, or immediately closes with an error dialogue.
  • Likely causes: Corrupted installation files, incompatible graphics API, or an outdated GPU driver that fails to initialize the renderer.
  • Primary fixes: Verify game files (see below), update your graphics driver (see below), and check that your system meets the [minimum requirements].

In-Game Crashes During Gameplay

These happen after you’ve successfully started a match. They may be random or tied to a specific event, such as when multiple explosions occur, a horde spawns, or you enter a new zone.

  • Symptoms: The game freezes for a few seconds, then returns to desktop without an error; or you get a "LowLevelFatalError" with a memory address.
  • Likely causes: Memory leaks, overheating, unstable overclocks, or driver timeouts.
  • Primary fixes: Enable VSync, cap your frame rate, disable overclocking, and check your memory usage (see memory section).

Action-Specific Crashes

Crashes that trigger only when you perform a certain action—like opening the inventory, using a specific weapon, or toggling a flashlight—point to a corrupted asset or a bug introduced by a recent patch.

  • Symptoms: The game reliably crashes when pressing a key, picking up an item, or interacting with a specific prop.
  • Likely causes: Corrupted local game files or missing shader caches.
  • Primary fixes: Verify integrity of game files, delete the shader cache in your install directory, or perform a registry reset (see below).

Tip: Before starting any in-depth troubleshooting, disable all background overlay programs (Discord, NVIDIA GeForce Overlay, MSI Afterburner, etc.). These inject software into the game process and can cause unpredictable crashes.

GPU / Driver-Related Crashes

Graphics card errors are the single largest category of crash causes in NMRiH2. The game relies heavily on modern rendering features like dynamic lighting and volumetric effects, which stress both the GPU hardware and its driver.

Identifying a GPU Driver Crash

  • The game freezes for a second, then minimizes to desktop.
  • An error message appears: "Display driver stopped responding and has recovered."
  • The Event Viewer shows an error with source nvlddmkm (NVIDIA) or amdkmdag (AMD).
  • Strange colored artifacts appear on screen before the crash.
  1. Update to the latest driver. Visit NVIDIA or AMD and download the current stable driver for your card. Do not use a Beta driver unless you are specifically testing a fix for a known issue.
  2. If you recently updated, roll back the driver. Sometimes a new driver introduces a regression. Roll back to the previous version via Device Manager (Properties > Driver > Roll Back Driver) and see if the crash persists.
  3. Disable GPU overclocking. Use MSI Afterburner or EVGA Precision to reset your clock speeds to stock. The same applies to factory-overclocked "OC Edition" cards—restore default memory and core offsets in the vendor software.
  4. Set the power management to "Prefer Maximum Performance." In the NVIDIA Control Panel or AMD Adrenalin settings, force the game profile to prefer maximum performance rather than optimal power. This prevents the GPU from downclocking mid-game, which can cause a timeout crash.
  5. Disable multi-display modes if you use more than one monitor. Outputting to a second monitor while a full-screen game is running can occasionally trigger misallocation of GPU resources. Try temporarily unplugging the extra display.
  6. Lower in-game graphics settings. Specifically reduce Shadows and Reflections to High, not Ultra. These are the most GPU-intensive settings and the most likely to cause a driver timeout on mid-range hardware.

Clean Graphics Driver Reinstall

If updating or rolling back doesn't work, a clean installation of the driver is the next step. This removes all traces of old driver files, which can conflict with new ones.

  1. Download the latest driver for your GPU from the manufacturer's website.
  2. Download and run Display Driver Uninstaller (DDU) in Safe Mode (recommended by most tech communities). Select "Clean and restart."
  3. After the restart, install your freshly downloaded driver with the "Clean Installation" option instead of "Express Installation."
  4. Reboot the PC again after the driver installation.
  5. Try launching NMRiH2.

Tip: If your system has both an integrated GPU (Intel or AMD APU) and a discrete GPU, ensure the game is using the correct one. In Windows Settings > Display > Graphics, set NMRiH2 to "High Performance" (your discrete GPU). Or force it in the NVIDIA Control Panel or AMD Software: Adrenalin Edition per-game profile.

Out-of-memory (OOM) crashes are common in games with long play sessions and massive zombie counts. NMRiH2 requires a great deal of RAM and VRAM, and bad memory management can lead to sudden termination.

Symptoms of Memory Crashes

  • An error message stating "Out of Video Memory" or "Ran out of memory."
  • The game stutters progressively over time, then crashes.
  • Windows reports "Low memory" even though nothing else is running.
  • The game crashes at the same point every time—usually when a lot of textures stream in.

Memory Fixes to Try

  1. Increase your Windows page file. By default, Windows manages this automatically. To set a custom size:
    • Press Win + R, type sysdm.cpl, go to Advanced > Settings > Advanced > Virtual Memory.
    • Uncheck "Automatically manage paging file size."
    • Select your system drive (the one with significant free space) and choose Custom size.
    • Set Initial size and Maximum size to 1.5 × your RAM size (e.g., for 16GB RAM, set 24576 MB).
    • Click Set, then OK, and restart.
  2. Lower texture quality in-game. If you have 8GB of VRAM, setting textures to "Epic" can exceed VRAM in densely populated zones. Set Textures to High (or Medium for 4/6GB cards).
  3. Close background memory hogs. Ensure Chrome, Discord, and other heavy applications are closed before starting the game. Check Task Manager for memory usage.
  4. Run dxdiag and check for errors. Press Windows Key + R, type dxdiag, and click OK. On the System tab, confirm total memory is correct. On the Display tab, look for a "No problems found" result.
  5. Test your RAM with Windows Memory Diagnostic. Press Win + R, type mdsched.exe, choose "Restart now and check for problems." Let the test run its full cycle. If errors appear, your RAM is unstable—replace it or swap slots.
  6. Adjust NVIDIA Texture Quality via Control Panel. If you have an NVIDIA card, open the NVIDIA Control Panel, go to Manage 3D Settings, and set Texture Quality to "Quality" (not "High performance"). This reduces allocation spikes.

Warning: Do not over-allocate virtual memory on an SSD with low free space. You need at least 20GB free on the drive you assign the page file to, otherwise the game and OS will fight for space.

DirectX / Vulkan Compatibility Issues

NMRiH2 uses Unreal Engine 5, which defaults to DirectX 12 on Windows. Some systems—especially with older GPUs or unstable drivers—will perform better or crash less on Vulkan, though the selection between them is done via launch options.

Forcing DirectX 11 or Vulkan (if supported)

While the official release currently supports D3D12 and Vulkan (depending on the build), you can force the renderer through a command line argument.

  1. Open Steam, right-click No More Room in Hell 2 in your library.
  2. Click Properties > General > Launch Options.
  3. To force Vulkan, enter:
    -vulkan
  4. To force DirectX 12 explicitly, enter:
    -d3d12
  5. To run with DirectX 11 (in case of alpha/reworked versions), enter:
    -dx11
  6. Close the Properties window and launch the game.

If you were experiencing crashes with the default renderer, switching to the alternative API can often solve the problem—especially if your GPU driver has quirks with one API. For example, some users report that they crash on D3D12 during shader compilation but run flawlessly on Vulkan.

Disable DX12 Raytracing (if available)

In the game's settings, make sure Ray Tracing is set to Off. Ray tracing is a brand-new feature in the NMRiH2 engine and is a primary suspect for many instability issues, particularly on AMD GPUs where ray tracing performance and stability are not as mature.

Update Shader Cache with GPU Vendor Tools

  • NVIDIA: In the NVIDIA Control Panel, go to Manage 3D Settings > Global Settings and set Shader Cache Size to Unlimited. This prevents OS-level shader cache eviction, which can cause shader compilation stutter and eventual crashes.
  • AMD: In Adrenalin, go to Gaming > Graphics, and ensure Shader Cache is set to On. If the problem persists, use the Reset Shader Cache option in the same menu (or use the "Standard" profile).

After changing the shader cache settings, restart your PC before launching the game again.

Verify Game Files Integrity

Corrupted or incomplete game files are one of the most common—and easiest—crash fixes. If any of the game's core assets are missing or wrong, the game can crash at startup or during a save load.

  1. Launch Steam.
  2. Go to your Library.
  3. Right-click No More Room in Hell 2.
  4. Select Properties.
  5. Go to the Installed Files tab (or Local Files in older Steam UI).
  6. Click Verify integrity of game files...
  7. Wait for the process to complete. It will download any missing or damaged files automatically.

This process takes anywhere from a few minutes to half an hour, depending on your disk speed and the current size of the game. After verification, try launching the game. If it still crashes, perform a second verification—sometimes the Steam client itself has a hiccup and fails to fix everything on the first pass.

Tip: If you have manually placed files in the install directory (e.g., mods, custom shader caches), back them up before verifying, as Steam will remove them.

Clean Graphics Driver Reinstall

We touched on this in the GPU section, but it deserves its own heading because so many users skip it. A "dirty" install (just clicking "Update Driver" in Windows Update) can leave behind stale files that conflict with the game.

For the cleanest reinstall:

  1. Download Display Driver Uninstaller (DDU) .
  2. Download the latest driver for your GPU from NVIDIA or AMD.
  3. Disconnect from the internet (or disable Windows Update) to prevent Windows from reinstalling an old driver.
  4. Boot into Safe Mode.
  5. Run DDU, select "Clean and restart" (not "Clean and shutdown").
  6. After reboot, install the new driver using the Custom (Advanced) install, and uncheck every box except the main driver. Do not install GeForce Experience or Adrenalin's extra features for now.
  7. Restart again normally.

This process overwrites any leftover driver fragments and resets all GPU-related registry tweaks that might have been corrupted by an earlier crash.

Windows Game Mode and Optimizations

Windows 10 and 11 have a Game Mode and a Game Bar that can interfere with certain full-screen applications. Some users experience crashes because these features cause the GPU to switch between different rendering modes or because background capture is enabled.

Disable Fullscreen Optimizations (Windows 10/11)

  1. Navigate to your game's installation directory. The default path is usually:
    C:\Program Files (x86)\Steam\steamapps\common\No More Room in Hell 2\
  2. Find the game executable (e.g., NMRiH2.exe).
  3. Right-click it, select Properties.
  4. Go to the Compatibility tab.
  5. Check Disable fullscreen optimizations.
  6. Click Change high DPI settings and check Override high DPI scaling behavior, then select "Application" from the dropdown.
  7. Click OK and Apply.

Disable Windows Game Mode / Game Bar

  1. Press Win + I to open Settings.
  2. Go to Gaming > Game Mode.
  3. Toggle Game Mode to Off.
  4. Go to Gaming > Captures and turn off "Record in the background while I'm playing a game."
  5. In the same Gaming section, click Xbox Game Bar and turn it Off.

Disable Hardware-accelerated GPU Scheduling (optional)

Some users report that Hardware-accelerated GPU scheduling (a Windows 10/11 feature) causes crashes in Unreal Engine 5 games. To disable:

  1. Go to Settings > System > Display > Advanced graphics options (or Graphics).
  2. Scroll down to "Default graphics settings" and click Hardware-accelerated GPU scheduling.
  3. Toggle it Off.
  4. Restart your PC.

If the crash still occurs, you can re-enable it later; this is a low-probability fix but worth trying if all else fails.

Registry and Settings Resets

If none of the above worked, the problem lies in a corrupted configuration file or a broken registry entry related to the game. Resetting these back to defaults can clear up issues that stem from a previous crash, an unstable mod, or a manual setting that the game can no longer parse.

Reset the Game's Settings (Profiles/Config Files)

NMRiH2 saves your graphics and control settings in the following locations. Back up these files first if you care about your bindings.

  • For most installations:
    C:\Users\[YourUserName]\AppData\Local\NoMoreRoomInHell2\Saved\Config\Windows
    or
    ...\Documents\My Games\No More Room in Hell 2\Config\

Look for files like GameUserSettings.ini, Scalability.ini, or Engine.ini.

  1. Close Steam and the game completely.
  2. Rename the Config folder to Config_Backup (this is a non-destructive way to reset settings).
  3. Relaunch the game. It will generate fresh default config files.
  4. If the game runs without crashing, your old settings were corrupt. You can attempt to manually copy over only your control bindings from the backup or just reconfigure them in-game.

Clear Temporary Files

Steam's cache and your system's temp files can conflict with a fresh update.

  1. Press Win + R, type temp, and delete all files in the folder that opens (skip any that are in use).
  2. Do the same for %localappdata%\Temp.
  3. In Steam, go to Settings > Downloads > Clear Download Cache. This will require you to log in to Steam again.

Clean Windows Registry (use caution)

You should not need a third-party registry cleaner, but a broken Unreal Engine plugin registration can cause crashes. Proceed carefully:

  1. Press Win + R, type regedit, and press Enter.
  2. Navigate to:
    `HKEY_CURRENT_USER\Software
Previousconnection-issuesNextknown-issues
All Articles