No More Room in Hell 2 Crash on Startup — PC Fixes

Match the fix to the crash stage

Before you start

Record the store (Steam or Epic), version 1.0.4.0, hardware, exact error text and whether the crash happens before the menu, while loading a map, during customization or in a live session.

Fix 1: Update the game and restart Windows

Hotfix 1.0.3.1 fixed two named customization and memory-related crashes, and 1.0.4.0 is the current official patch checked for this guide.

1. Close the game and launcher completely, restart Windows, then let Steam or Epic install every pending NMRIH2 update.
2. Launch once with the default startup options. Remove undocumented launch flags while diagnosing the crash.

Fix 2: Update Windows and the graphics driver

The official launch-week issue list says updating Nvidia drivers appeared to resolve reported hitching. Steam also recommends current Windows and device drivers for games that fail at launch.

1. Install pending Windows updates and restart the PC.
2. Install the current driver from Nvidia, AMD or Intel for the installed GPU, then restart before testing again.

Fix 3: Verify the installed game files

File verification is the platform-supported check for damaged or incomplete local files.

1. Steam: Library → NMRIH2 → Properties → Installed Files → Verify integrity of game files.
2. Epic: Library → three dots beside NMRIH2 → Manage → Verify.
3. Wait for verification to finish, then test one launch before changing another variable.

Fix 4: Check DirectX 12 hardware and memory pressure

Steam lists Windows 10 64-bit, DirectX 12, 12 GB RAM and a 4 GB GTX 1650, RX 570 or Intel Arc 580 as the minimum PC baseline.

1. Compare the PC with the current Steam minimum requirements.
2. Close non-essential overlays and memory-heavy background applications, then test at the game's default or lower graphics settings.
3. If the crash occurs only during heavy character customization, update first: the developer fixed a related memory crash in 1.0.3.1.

Fix 5: Use map-load recovery when it applies

Armageddon 1.0 added a Reconnect option specifically for crashes during map load.

1. After a map-loading crash, reopen the game and use Reconnect if the current session offers it.
2. Do not treat Reconnect as a startup-crash repair or as a guarantee that a Responder will always be restored.

Fix 6: Follow the Easy Anti-Cheat path only for an EAC error

Steam lists Easy Anti-Cheat for NMRIH2. Epic's official EAC guidance starts with the exact error, launching through the platform client, checking for blocked EAC connectivity, updating Windows, closing interfering background programs and verifying game files.

1. Photograph or copy the complete EAC error instead of treating every startup crash as an anti-cheat failure.
2. Launch NMRIH2 from Steam or Epic rather than directly from a copied executable or shortcut.
3. Close non-essential background utilities for one test, then verify the game files if the same EAC error remains.
4. Use the official EAC support article for the exact message; do not copy Fortnite-specific install commands into the NMRIH2 directory.

If it does not work

If the same crash remains, save the crash stage, error text, store, patch, GPU driver version and DxDiag details, then report it in-game, through the official Discord, or at the official support site.

Evidence boundary

The sources support the current patch, named crash fixes, DirectX 12 baseline, driver update, file verification, Easy Anti-Cheat's presence and map-load reconnect. They do not support a universal launch flag, registry edit, shader-cache deletion or guaranteed crash fix for every PC.

Sources

• Official Hotfix 1.0.4.0
• Official Hotfix 1.0.3.1
• Official launch-week known issues
• Steam store PC requirements
• Steam Support — games do not run after launch
• Epic Games Support — verify game files
• Epic Games Support — Easy Anti-Cheat game issues

Related guides