Mount Blade II Bannerlord Crashing: Fixes That Work
Mount & Blade II: Bannerlord crashing on launch, during battles, or on the campaign map is a common problem that usually stems from outdated mods, corrupted game files, or a driver conflict. This guide walks you through the most effective fixes in order, from quick checks to deeper system tweaks, so you can get back to conquering Calradia.
Why Bannerlord Crashes More Than Other Games
Bannerlord is built on a heavily modified engine that simulates thousands of AI actors simultaneously, from individual soldiers in a siege to entire caravans moving across the map. This constant simulation puts unusual stress on the CPU, memory, and storage. Unlike a linear shooter, a single corrupted save or a mod that changes a core mechanic can cause a crash only after hours of play, when a specific event triggers the faulty code. The game also has a large modding community, and even with the official mod tools, many popular mods are updated slowly after each patch, creating instability.
First Steps: Quick Checks That Fix Most Crashes
Before diving into complex troubleshooting, run these three checks. They resolve a surprising number of crash reports.
- Verify game files – In Steam, right-click the game, select Properties → Installed Files → Verify Integrity of Game Files. This finds and replaces any corrupted or missing files. On Epic Games Launcher, use the Verify option in the game’s settings menu.
- Update your graphics driver – Go to NVIDIA or AMD’s official website and download the latest driver for your GPU. Use the “clean install” option if available. Outdated drivers are a leading cause of crashes in DirectX 11 and 12 games.
- Remove all mods temporarily – Move the entire
Modulesfolder (default location:Steam\steamapps\common\Mount & Blade II Bannerlord\Modules) to your desktop. Launch the game. If it works, a mod is the culprit. Re-add mods one by one to find the offender.
Mod-Related Crashes: The #1 Cause of Mid-Game CTDs
Bannerlord’s modding tools are powerful, but they also mean that a mod written for version 1.2.0 can break the game after a 1.2.1 patch. The most common mod-crash scenario is using mods that are not updated for the current game version. Check the mod’s page on Nexus Mods or the Steam Workshop for the “Last Updated” date and the compatible game version. Also, pay attention to mod load order. Many mods require a specific order to work correctly, and a wrong order causes crashes on startup or when entering a town.
Another frequent issue is using mods that alter the same game files. For example, two different “troop overhaul” mods will conflict. Use a mod manager like Bannerlord Mod Manager (a free third-party tool) to see load order and detect conflicts. If you crash after loading a save, the save may be corrupted by a mod you removed. Keep a backup of your save folder (Documents\Mount and Blade II Bannerlord\Game Saves) before making major mod changes.
Performance and Memory Crashes: When Your PC Runs Out of Steam
Bannerlord is memory-hungry, especially with large battles. If you have 8GB of RAM or less, you will likely see crashes during sieges with 500+ troops. The game also has a known issue with memory leaks on the campaign map, where memory usage slowly increases until the game runs out of RAM and crashes. To mitigate this:
- Lower the Battle Size slider in Options → Performance. Default is 1000; try 500 or 600.
- Set Graphics Quality to Medium or High, not Ultra, if you have 8GB RAM.
- Close background programs like Chrome, Discord, or streaming software while playing.
- If you have 16GB or more, still check your RAM usage with Task Manager. If it hits 95% before a crash, you have a leak.
Another performance-related crash is due to the game’s “Unlimited” FPS setting. If you have a high-refresh-rate monitor (144Hz or more), the game can run at 300+ FPS in menus, causing GPU instability. Cap your FPS to 60 or 120 in the game’s video options.
Crash on Launch: Black Screen or Immediate CTD
If the game crashes before the main menu appears, the problem is usually not a mod. First, check that your system meets the minimum requirements (Windows 10 64-bit, 4GB RAM, but realistically 8GB, and a GPU with at least 2GB VRAM). Then try these:
- Run as administrator – Right-click the Bannerlord.exe (in the game’s bin folder) and select Properties → Compatibility → Run this program as an administrator.
- Disable fullscreen optimizations – In the same Compatibility tab, check “Disable fullscreen optimizations.” This fixes many Windows 10/11 launch crashes.
- Delete the game’s configuration files – Go to
Documents\Mount and Blade II Bannerlord\Configsand delete the entire folder. The game will recreate it with default settings. This fixes crashes caused by a corrupted config. - Check DirectX version – The game uses DirectX 11 by default. If you have an older GPU that only supports DX10, you need to update your hardware. Try running the game in “DX11” mode (it’s the only option).
Common Crash Points: Sieges, Towns, and the Campaign Map
Players often report crashes that happen at specific moments. Here’s what to do for each:
- Crash when entering a town or castle – This is almost always a mod conflict or a corrupted save. Try loading an earlier save, and if that works, the current save is corrupted. If no save works, disable mods.
- Crash during a siege battle – Reduce battle size, lower graphics settings, and update your GPU driver. Sieges are the most demanding part of the game.
- Crash when loading a save – The save may be from a different game version. Load a save from after the last patch, or use the “Load” menu’s “Show all saves” option to find an older one.
- Crash on the campaign map after a few minutes – This is the memory leak issue. Try setting the “Map” quality to Medium, and avoid leaving the game paused for long periods.
Advanced Fixes: Windows and Hardware Settings
If nothing above works, try these deeper system-level fixes. They are safe but take a few minutes.
- Update your chipset drivers – Go to your motherboard manufacturer’s website and download the latest chipset drivers. This can fix memory and PCIe issues.
- Disable fullscreen optimizations for the game launcher – The launcher (BannerlordLauncher.exe) can also cause crashes. Apply the same compatibility settings to it.
- Check for overheating – Use a free tool like MSI Afterburner to monitor your CPU and GPU temperatures. If they exceed 90°C, you have a cooling problem. Clean your PC’s fans and check your thermal paste.
- Run the game in windowed mode – In the game’s launch options (Steam: right-click → Properties → General → Launch Options), add
-windowedto see if that stops crashes.
Frequently Asked Questions
Why does Bannerlord crash to desktop without any error message?
This is typical of a memory leak or a mod conflict. The game doesn’t always write an error log. Check the Windows Event Viewer (under Windows Logs → Application) for an “Application Error” entry that mentions Bannerlord.exe. The faulting module will often point to a .dll file from a mod.
Will deleting my saves fix the crashing?
Only if the save itself is corrupted. Corrupted saves happen after a game update or a mod removal. Try loading an earlier save first. If no save loads, then yes, deleting the save folder will let you start a new game, but that’s a last resort.
Does Bannerlord have a 32-bit version that crashes less?
No. The game is 64-bit only. If you have a 32-bit Windows, the game won’t run at all.
Why does the game crash when I alt-tab?
This is a known issue with the game’s fullscreen mode. Set the game to “Borderless Window” in the video options. That allows alt-tabbing without crashing.
Can I play with mods after a new patch?
Yes, but you must wait for mods to be updated. Check the mod’s page for a “compatible with version” note. If you don’t want to wait, you can roll back the game version on Steam (Properties → Betas → select an older version).
Is there a way to get a crash log?
Yes. In the game’s folder, there is a file called crash_log.txt (or similar). It’s created in the same folder as the executable. You can also find it in Documents\Mount and Blade II Bannerlord\. This log lists the last actions before the crash, which helps modders identify issues.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.