Parse errorlog.txt

Analyze DAOC’s crashes with Mojo.

When the DAOC client crashes on your computer, it stores information about the event in a file called errorlog.txt in its installation folder. Mojo can extract information from that file and print it in an easy-to-read format.

To open this window, go to “Debug” on Mojo’s main menu and select “Parse errorlog.txt”.

Here are some ways you can interpret the data:

Crashes that occur in module “game.dll” or “game.laa.dll” are happening in code published by Broadsword. If you see repeated crashes in these modules at the same address, they are caused by a software problem. If you see crashes at different addresses, they could be caused by a software problem or a hardware problem. Either way, you can try reinstalling the game. You can also report the problem to Broadsword.

Crashes that occur in modules with extension ‘.sys’ or that include “nvidia”, “logitech,” etc., in their names are occuring in device driver code. Updating the driver may fix the problem.

Crashes that occur in mojo_remote.dll or mojo_remote_cp.dll are caused by Mojo. If you see crashes of this sort, please contact me immediately.

Crashes that occur in ntdll.dll or another dll that belongs to the operating system are almost always caused by bugs in some other module. It’s extremely rare for a bug in the operating system to cause a crash.

If you see a module in the list that belongs to some program whose presence surprises you, consider not using that program anymore.

Technical notes

Mojo’s output only includes crashes caused by access violations. I have never seen any other kind of crash in errorlog.txt but they may sometimes occur.

Mojo’s output only includes crashes in game.dll or game.laa.dll (the live client). It does not include crashes in the Pendragon/Hector client.

This page was first published on March 21, 2021, last revised on March 21, 2021, and last republished on March 21, 2021.