The CoD Mobile crash GameLoop admitted to has been open for seven months
Call of Duty Mobile crashes on the AOW 64-bit engine. GameLoop said so officially in December 2025 and told players to fall back to 32-bit — and has said nothing about a fix since.
If Call of Duty Mobile keeps closing on you in GameLoop, the problem is probably not your PC.
In its official announcement of 19 December 2025, GameLoop listed this among known issues: "Crash issue on AOW 64-bit while playing Call of Duty: Mobile in GameLoop." The recommended workaround: switch to AOW 32-bit. The same announcement carries a second known issue — "DMZ mode keymaps are not available yet" — with the suggested fix being to switch to the OB keymap and turn off auto-switching. (Source)
Seven months have passed. We have found no primary-source announcement saying the issue is resolved.
What to do
If you are hitting the crash, GameLoop's own advice still stands:
- Open Engine in GameLoop's settings.
- Select AOW 32-bit instead of AOW 64-bit.
- Close the emulator completely and restart it.
There is a cost to this. The 32-bit engine is limited by addressable memory, so it will not handle high graphics settings as comfortably as 64-bit does. This is a trade, not a fix.
And then there is the part we cannot verify
User comments underneath GameLoop's official posts carry a second recurring complaint: Call of Duty bans with no apparent cause. One user writes: "What is going on with GameLoop? Me and several friends are getting banned in Call of Duty for no reason." Some replies suggest moving to MSI App Player.
We are passing this on as a user claim, not as news. The reason is plain: there is no official statement, no verified case count, and no evidence tying the bans to the emulator. A repeated complaint in a comment thread is a signal, not proof.
Activision and TiMi's general policy is that bans apply to "unsafe emulators" and third-party helper software. But we could not find a 2026-dated official update listing approved emulators.
What it means for the version log
Because of this fault we treat the current 64-bit build as broken specifically for Call of Duty Mobile. The same does not apply to PUBG Mobile or other titles — the problem is game-specific.
The fact that GameLoop's last verifiable build dates to October 2025 sharpens the picture: nine months without a verified client update, and seven months with a crash report left open.
If an official announcement confirms a fix, we will update this article and note the change at the foot of the page.