Look for the line widescreen = 1 . If it is set to 0 , change it to 1 (or vice-versa if you are using an older 4:3 monitor).
Medieval 2 is a 32-bit application, meaning it can only access 2GB of RAM. High-resolution textures and large unit scales (especially in mods) will exceed this limit, causing an "unspecified error" crash.
You’re suddenly staring at your desktop, your army vanished into nothing, hours of progress lost. This infamous error message is the bane of Medieval II players, a generic, catch-all crash that offers no clues about what went wrong.
: If the crash happens when starting a campaign, find your mod's data folder (e.g., Medieval II Total War/mods/Stainless_Steel_6/data/world/maps/base ) and delete map.rwm . The game will automatically regenerate it. Troubleshooting Mods If the error occurs only with a specific mod: Look for the line widescreen = 1
By following these steps, you should be able to eliminate the unspecified error and enjoy one of the greatest strategy games ever made.
of RAM, leading to crashes in large battles or when playing mods with larger maps.
You groaned, feeling like you'd already tried that. But Old Bob was insistent. "Trust me, my lord. It's worth a shot." : If the crash happens when starting a
Delete or rename both files. The game will automatically regenerate clean versions. Day/Night Cycle Crash
To help narrow down the exact cause of your crash, please let me know: Are you playing the or using a specific mod ?
Total war encountered an unspecified error and will now exit. find your mod's data folder (e.g.
As of recent Steam updates (2024-2026), Valve has been updating the DRM wrapper for old games. This has introduced new "unspecified errors" related to the d3d8.dll (DirectX 8) wrapper.
Run the tool and select the medieval2.exe and kingdoms.exe files in your installation folder.
Download a trusted utility (such as NTCore's 4GB Patch). Run the executable as an administrator. Select medieval2.exe from your game installation folder.
