Game crashes mid match for more than one player (files attached)

:arrow_forward: GAME INFORMATION

:point_down: These details are CRITICAL; DO NOT skip them or your issue may not be reviewed.

  • GAME BUILD #: 101.101.46295.0
  • OPERATING SYSTEM: Windows 10

:arrow_forward: ISSUE EXPERIENCED

Was playing ranked TG with my friend and the game stopped in the middle of the match (reaching castle age). It happened to me (the grey ethiopian) and to my friend (the green player who picked Byzantines) at the same time.
The game stopped responding and the notification that the program has stopped appeared.
First time this bug popped to us

:arrow_forward: FREQUENCY OF ISSUE

:point_down: How often does the issue occur? CHOSE ONE; DELETE THE REST!

  • Less than 25% of the time / matches I play (RARELY)

:arrow_forward: REPRODUCTION STEPS

:point_down: List CLEAR and DETAILED STEPS we can take to reproduce the issue ourselves… Be descriptive!

Here’s the steps to reproduce the issue:

  1. Play a ranked TG game
  2. Wait for the crash in a couple of minutes

:arrow_forward: EXPECTED RESULT

:point_down: What was SUPPOSED to happen if the bug you encountered were not present?
The game should not crash

:arrow_forward: IMAGE

:point_down: ALWAYS attach a PICTURE (.jpg, .png, .gif) or VIDEO (.mp4, YouTube link) that highlights the problem.

:arrow_forward: GAME FILES (SAVE / RECORDING)

:point_down: Attach a SAVE GAME (.aoe2spgame) or GAME RECORDING (.aoe2record) of the match where you encountered the issue. Link it below if using an external file service.

I include the log file and the recorded game

EDIT: replaying the replay causes the game to crash

1 Like


my game crashed aswell in a 1v1 at around 30 min of game time. After I restarted the game, I was watching the replay to analyse the match up to the point of the crash. Surprisingly, my game crashed once again at the same point of the game. @Hectornauta: Does your replay crash your game aswell?

Here is my replay file:
MP Replay v101.101.46295.0 @2021.04.24 120041 (1).aoe2record (1,7 MB)

1 Like

Your replay crashes also on my system.

2021.04.24-14.53.19.txt (20.9 KB) I have also a crash to desktop even re-watching the replay leads to the crash to desktop. Here is my replay and the log
Relevant information in the log states:
Exception type 0xc0000005 occurred at 00007ff7097ae7a5 (both in my and your replay)

MP Replay v101.101.46295.0 @2021.04.24 160912 (2).aoe2record (1.2 MB) 2021.04.24-14.53.19.txt (20.9 KB)

1 Like

Yes, did not noticed but I’ve just tested it and the replay also crashes my game.

1 Like

Check the newest log files for AOE, its located like below:

C:\Users[your name]\Games\Age of Empires 2 DE\logs

Look at the last few entries after a crash.

Exceptions cause the game to crash, something like Exception type 0xc0000005 indicates something wrong with memory apparently… increasing RAM or having a massive pagefile.sys might help :rofl:

1 Like

Sync is being logged
[rlink - error] 2021/04/30 06:25:20.148 (UTC) Unknown presenceID entered

[rlink - error] 2021/04/30 06:29:36.732 (UTC) subscribe to notifications error:

[rlink - error] 2021/04/30 06:51:13.809 (UTC) TelemetryRow::addString : Value (61) is larger than Column (32)

Exception type 0xc0000005 occurred at 00007ff6b0fce7a5
Writing crash record file.
Writing out log

I got this message in the logs. Does it mean that is a RAM issue? But why does it happen since March 24 update which didn’t happen to me before?

Try closing other apps. When the game starts, close apps like Chrome or Edge as they use a lot of Ram (change the setting to continue where left off). Also, change Game Graphics to low or medium can improve game stability.

How to determine apps memory usage on Windows 10 | Windows Central

I still have the error and the exact same issue. Log is identical. And also for other players it crashes.

this is a common problem since the latest update which devs haven’t addressed for some reason, maybe they don’t know what they screwed up?

I reported a bug but they want me to play the Public beta and see if problem exists there
But: The problem is not easy to trigger, I do not want to play the beta for that long to trigger the error