. This error message—frequently appearing as Fatal error! QA_APPROVED_BUILD_JANUARY_2011 —is a legacy artifact from the game’s original Unreal Engine 3 compilation. It surfaces on modern platforms like Steam, GOG, and the Steam Deck.
Batman: Arkham City Document Type: Fatal Error Analysis & Verification Build Reference: QA Approved Build (January) Status: Verified / Confirmed Date of Report: [Current Date] Prepared By: [Your Name/Department]
: Navigate to your game's installation folder (typically Binaries\Win32 ). Right-click on both BatmanAC.exe and BMLauncher.exe , select Properties , go to the Compatibility tab, and check "Run this program as an administrator".
The most effective fix is to delete the game's configuration and save directory. Navigate to Documents \ WB Games . Delete the entire Batman Arkham City GOTY folder.
Tip: You can sometimes download a clean community save file online to replace your broken progress. Summary Checklist Target Root Cause Success Rate Engine instability Switch PhysX to CPU Driver conflict Verify Steam Files Missing/corrupt data Admin Permissions Windows restrictions It surfaces on modern platforms like Steam, GOG,
Delete the .ini files in this folder. The game will regenerate fresh defaults on next launch .
Even though this error has frustrated players for over a decade, the message itself is a clue. It simply refers to a "Quality Assurance Approved" version of the game that exists in the program's code. The lines that say "(filename not found)" are not typically the cause of the crash. Instead, they usually indicate that the game's retail version lacks the debugging symbols needed to identify the exact source of the crash.
Don’t worry. You don't need to be a forensic analyst at the GCPD to fix this. Follow these steps in order, and you will likely be back to breaking skulls in five minutes.
Navigate to:
: Disable any overlays (e.g., from Steam, NVIDIA, or Discord) as they can sometimes interfere with the game.
"
If the crash always happens at the exact same moment (e.g., loading a specific checkpoint or opening the map), your save file is likely corrupted.
If disabling PhysX doesn't solve the problem, forcing DX9 mode is a very effective fallback that often resolves the problem for good. The most effective fix is to delete the
Use a "GFWL Remover" tool found in the community forums to bypass the requirement. 2. Disable DirectX 11 Features (Use DX9) The game is much more stable using DirectX 9. Open the Batman: Arkham City Launcher . Click on Settings . Uncheck DirectX 11 Features . Launch the game. 3. Edit BmEngine.ini for Memory Stability Often, the fatal error is a memory allocation issue.
Search for in the Windows Start menu, go to Program settings , add BatmanAC.exe , and override/disable all protection settings for it.
A more recent cause on Windows 10 and 11 involves the game's incompatibility with a security feature called Address Space Layout Randomization (ASLR) . If your system forces this on BatmanAC.exe , it can cause a fatal error.