To understand the "unspecified error," you have to understand Medieval 2 ’s engine. Built on the bones of Rome: Total War , it was a miracle of mid-2000s ambition—thousands of units on screen, complex siege pathfinding, and a dynamic campaign map. But ambition has a price.
The "unspecified error" in Medieval 2: Total War is a notorious "catch-all" crash that typically indicates the game has run out of memory (RAM) or encountered a file it cannot read. Because the game was released in 2006, modern multi-core processors and 64-bit operating systems often struggle with its original 32-bit architecture. To understand the "unspecified error," you have to
Look for two files: descr_geography_new.txt and descr_geography_new.db. Delete them both. The "unspecified error" in Medieval 2: Total War
If the crash happens on the exact same turn every time, try toggling "Follow AI Character Movement" off in the options. Occasionally, the error is caused by a specific agent (like a diplomat or spy) performing an action that the engine can't render. Delete them both