To fix stuttering, low FPS, and crashing in Mount & Blade II: Bannerlord on PC, start with a clean mod-free launch, verify the game files, clear Bannerlord's shader and configuration caches, then use a CPU-friendly graphics profile capped to a stable frame rate. Bannerlord is unusually sensitive to battle size, AI simulation, driver shader compilation, and mod load order, so lowering every setting at random rarely solves the real problem.
Follow the sections below in order. Test the same scene after every major change, especially a siege or a battle with 500-plus troops. That gives you useful evidence instead of a vague feeling that the game is “better.” Also check the current official Steam page for the latest build notes and system requirements before blaming your hardware.
Start With a Clean Bannerlord Installation
Before changing graphics settings, separate a game problem from a mod problem. Bannerlord's official modules, including Native, SandBoxCore, Sandbox, StoryMode, and CustomBattle, should load without third-party additions. A broken Harmony dependency or an outdated overhaul can crash during startup, loading screens, campaign-map transitions, or the first battle.
Use this isolation sequence
- Exit the game and disable every third-party mod in the launcher. If you use a mod manager, disable profiles there too.
- In Steam, open Library > Bannerlord > Properties > Installed Files > Verify integrity of game files.
- Launch a new campaign with the same graphics settings, not an old modded save. Test the tutorial battle or a Custom Battle first.
- If the clean game works, re-enable mods in small groups. Put framework mods such as Harmony, ButterLib, UIExtenderEx, and Mod Configuration Menu before the mods that depend on them.
- Do not load a save that depends on a removed overhaul. Bannerlord may reach the campaign map and still crash later when it requests missing troop, item, or quest data.
For a stubborn installation, back up your saves and remove Bannerlord's user configuration folder under Documents\Mount and Blade II Bannerlord\Configs, then let the game rebuild it. Keep the save backup separate; deleting configuration files is useful, while deleting saves is not. If the launcher itself behaves strangely, reinstalling only the game may not remove old mod files, so inspect the game's Modules folder and remove abandoned manual installs.
| Symptom | Most Likely Cause | First Test |
|---|---|---|
| Crash before the main menu | Broken module, dependency, or config | Disable all mods and delete rebuilt configs |
| Crash when loading a save | Removed mod or incompatible campaign data | Launch a new unmodded campaign |
| Stutter only in battles | CPU simulation, troop count, or shader compilation | Run Custom Battle at 200 troops |
| Random desktop crash after hours | Memory pressure, unstable overclock, or driver issue | Return CPU/GPU/RAM to stock settings |
Use the general PC crash and FPS troubleshooting steps if other games are failing too. If only Bannerlord crashes, keep your investigation focused on modules, files, shaders, drivers, and the specific save.
🎮 Mount & Blade
Looking to experience this game? Grab your digital key directly on our store for $9.99.
View on Steammoz Store →Fix Stuttering by Targeting CPU Bottlenecks
Bannerlord is not just rendering a picture. It is tracking formations, pathfinding, morale, ranged attacks, cavalry movement, hit detection, ragdolls, and campaign AI. That workload makes the Battle Size slider one of the most important performance settings in the game. A powerful graphics card cannot rescue a CPU that is trying to simulate 1,000 agents during a siege.
Open Options > Video and begin with Battle Size at 400. If frame time still spikes during clashes, drop to 300 or 200. This changes the number of troops active in a battle, not the total size of your army or the campaign's maximum party size. Players chasing a locked 60 FPS often get a smoother experience at 400 troops than at 1,000, even when average FPS looks similar.
Watch the difference between GPU and CPU limitation. If GPU usage sits near 95–99% while lowering resolution increases FPS, the graphics card is the limit. If GPU usage falls to 60–80% during a crowded melee while FPS collapses, the CPU and simulation are the problem. An on-screen monitor such as MSI Afterburner with frame-time graphs makes this obvious: a flat 16.7 ms frame time equals 60 FPS, while long spikes reveal stutter that an average FPS counter hides.
CPU-focused changes that actually matter
- Reduce Battle Size before destroying image quality. It has a much larger impact on large engagements than lowering texture quality.
- Set ragdolls to Low or Medium. High ragdoll counts add CPU and physics work after clashes.
- Lower Character Detail and Number of Corpses if sieges produce repeated frame-time spikes.
- Close browsers, RGB utilities, recording tools, and launchers that compete for CPU time or memory.
- Use Windows Best performance power mode on a desktop or when plugged into a gaming laptop.
- Keep the game on an SSD. An SSD will not magically raise average FPS, but it reduces asset-streaming pauses and campaign loading friction.
Do not set Bannerlord's process priority to Realtime. That can starve audio, input, or Windows services and make a crash harder to diagnose. Normal priority is fine; High may help in rare cases, but it is not a substitute for a stable frame cap and sensible battle size.
| Profile | Battle Size | Target Hardware | Expected Experience |
|---|---|---|---|
| Competitive smooth | 200–300 | Older six-core CPU or gaming laptop | Best frame pacing in sieges and dense melee |
| Balanced | 400–600 | Modern six-core or eight-core CPU | Strong visual scale with manageable CPU spikes |
| Large battles | 800–1,000 | Modern high-end CPU | Most dramatic battles, but unstable lows are normal |
Use a Graphics Profile That Holds Its Frame Rate
Once the CPU side is under control, tune the GPU. Bannerlord's Render Resolution, Shadow Quality, Texture Quality, Lighting Quality, and Screen Space Reflections affect performance differently. The goal is not “all Low”; it is preserving the settings that make Calradia readable while cutting expensive effects that are hard to notice during combat.
Start at your monitor's native resolution with V-Sync Off if you have G-Sync or FreeSync. Cap the game through your GPU control panel to a number your system can actually sustain: 60 FPS for a 60 Hz display, 90 or 117 FPS for common high-refresh panels, or a steady 45 FPS when large battles refuse to hold 60. A consistent 45 FPS feels dramatically better than bouncing between 60 and 28.
Set Texture Quality to High if your GPU has at least 6 GB of VRAM, and Medium for 4 GB cards. Textures mainly consume VRAM, so lowering them will not cure a CPU-bound siege unless the card is paging assets. Reduce Shadow Quality to Medium first; large outdoor shadows are costly and the visual difference from High is minor during fast combat. Set Particle Quality to Medium if fire, dust, and arrows cause dips.
| Setting | Recommended Value | FPS Impact | Visual Trade-Off |
|---|---|---|---|
| Render Resolution | Native; 90% if needed | High | Lower values soften the image |
| Texture Quality | High with 6 GB+ VRAM | Low to Medium | Mostly affects surface detail and VRAM |
| Shadow Quality | Medium | Medium to High | Less detailed cast shadows |
| Lighting Quality | Medium | Medium | Flatter lighting in towns and battles |
| Screen Space Reflections | Low or Off | Medium | Less convincing water and glossy reflections |
| Particle Quality | Medium | Low to Medium | Reduced dust, smoke, and impact effects |
| Anti-Aliasing | High, then Medium | Low to Medium | More jagged edges when reduced |
| Foliage Quality | Medium | Low to Medium | Thinner grass and less dense vegetation |
If the game crashes while changing settings, close it and edit the rebuilt configuration rather than repeatedly launching into the same failing state. Also update your GPU driver through NVIDIA, AMD, or Intel's official support pages, then restart Windows. A clean driver install is worth trying when crashes began immediately after a driver update, but do not combine it with five other unknown changes.
For comparison, our Far Cry 6 FPS settings guide covers the same principle: protect frame pacing first, then spend your performance budget on effects you can actually see.
Stop Crashes Caused by Drivers, Memory, and Overlays
Bannerlord can run for hours before exposing an unstable overclock or a memory problem. If crashes appear during saves, scene transitions, or after extended sieges, test the system at stock settings. Disable GPU overclocks, CPU undervolts, XMP or EXPO temporarily, and any aggressive laptop performance profile. If stability returns, reapply changes one at a time rather than assuming the game is at fault.
Work through the common Windows causes
- Update Windows and install the latest stable graphics driver. Choose a clean installation option when available.
- Disable Steam Overlay, Discord Overlay, GeForce Experience or AMD recording overlays, and Xbox Game Bar for one test session.
- Add Bannerlord's executable to your antivirus exception list only if security software is visibly blocking files. Do not disable antivirus permanently.
- Check free space on the Windows and game drives. Keep at least 15–20 GB available for shader caches, updates, and temporary files.
- Use Windows Memory Diagnostic or MemTest86 if crashes affect several games. Faulty RAM often masquerades as a Bannerlord-specific crash.
- Check Event Viewer or the game's crash files for repeating module names. A graphics driver module points in a different direction from a mod DLL.
Shader compilation can cause brief stutters after a driver update or a fresh installation. Let the game sit at the main menu for a few minutes, load a small Custom Battle, and avoid judging performance from the first 30 seconds. Repeatedly deleting shader caches can make this worse because the game must rebuild them again. Clear a cache only after a driver change, corrupted visuals, or a persistent crash that survives file verification.
Borderless mode is usually the easiest choice for multitasking, while exclusive fullscreen can reduce some desktop interference on older systems. Test both. Disable Motion Blur if camera movement feels smeared, but remember that it has little effect on raw FPS. Likewise, changing field of view can improve comfort without solving a CPU bottleneck.
Repair Mod Load Orders Without Sacrificing Your Campaign
Mods are one of Bannerlord's greatest strengths and its most common crash trigger. Major overhauls such as Calradia Expanded, Realm of Thrones, and Prophecy of Pendor-style projects can alter troops, settlements, quests, and campaign systems. They are not interchangeable with a vanilla save, and an update to one dependency can break an otherwise stable profile.
Use the game's launcher to check warnings, but do not treat a green launch as proof that the load order is correct. Framework libraries generally belong above the mods that use them. Keep the official modules in their expected order, place libraries next, then UI, gameplay, troop, map, and patch modules according to each project's documentation. The official TaleWorlds Bannerlord page and the mod author's documentation should be your source of truth for version compatibility.
| Test Stage | Modules Enabled | What It Proves | Next Action |
|---|---|---|---|
| Stage 1 | Official modules only | Base game and hardware are stable | Add framework libraries |
| Stage 2 | Harmony, ButterLib, UIExtenderEx, MCM | Dependencies load correctly | Add one gameplay mod |
| Stage 3 | Half of remaining mods | Narrows the faulty group quickly | Split the failing half again |
| Stage 4 | Full profile | Confirms final interaction | Lock versions and back up the profile |
When a modded save crashes, do not remove random modules while standing in a town or during a quest. Make a backup first, then test on a copied profile. A safer recovery path is restoring the exact mod versions used when the save was created. If a campaign is permanently damaged, a new unmodded save is the clean confirmation that your PC and installation are healthy.
For large mod packs, keep a written load order and save a copy of the Modules folder before updates. Steam Workshop can silently update a dependency, so disabling automatic updates or using a mod manager with version control may be worthwhile. The same disciplined approach helps with other demanding games; see our crashing and low-FPS troubleshooting guide for a useful diagnostic mindset.
Use This Final Bannerlord Performance Checklist
After making changes, test three repeatable situations: a Custom Battle with 200 troops, a busy settlement such as Marunath or Epicrotea, and a siege with the highest troop count your system can handle. Record average FPS and the lowest frame-time behavior. If the small battle is smooth but the siege is not, your machine is probably CPU-limited rather than broken.
- Verify files and launch with Native, SandBoxCore, Sandbox, StoryMode, and CustomBattle only.
- Clear or rebuild configuration files only after backing up saves and settings.
- Set Battle Size to 200–400 for stable frame pacing, then increase it gradually.
- Use Medium shadows, Medium particles, Low reflections, and High textures when VRAM allows.
- Cap FPS to a stable target instead of chasing an inconsistent maximum.
- Update drivers, disable overlays, and test stock CPU, GPU, and RAM settings.
- Add mods in groups and never assume a modded save will survive an overhaul update.
Bannerlord performance is a balancing act between battlefield scale, CPU simulation, GPU effects, and mod complexity. The biggest win usually comes from reducing Battle Size and fixing the installation before touching resolution. Once the game is stable, raise one setting at a time and keep the first profile that delivers smooth frame pacing in the battles you actually play. For hardware context, our PC requirements guide explains how to judge minimum specifications without confusing “launches” with “runs well.”
If you still crash after a mod-free verification, stock hardware testing, driver reinstall, and a fresh campaign, report the reproduction steps through the official Bannerlord Steam discussions. Include your game version, GPU driver version, crash location, battle size, enabled modules, and whether a new campaign reproduces it. That information is far more useful than simply saying the game “keeps crashing,” and it gives other players a real chance to identify the fix.