What this tool does

When FiveM crashes, it generates a crash dump — a .zip file containing logs, metadata, and memory dumps. This tool reads that ZIP entirely inside your browser, parses the internal files, and presents a clear breakdown of what happened.

It extracts the crash hash (a unique identifier for the crash type), your system information (GPU, server details, OneSync status), any script errors from the log, and the last log lines leading up to the crash.

Understanding crash hashes

Every FiveM crash produces a crash hash — a combination of a word-key (like texas-mockingbird-two) and a DLL offset (like citizen-devtools.dll+2B4A6). The same crash type always produces the same hash.

This tool checks the hash against a built-in database of known FiveM crashes. If recognized, you'll see the cause and recommended fix. If not, the hash is still useful to search on the CFX forums.

Reading the analysis

Common crash types

These are the most frequent crash scenarios and what they typically mean.

How to collect crash data

1. 1When FiveM crashes, click Save crash information in the crash dialog.
2. 2Or find crash ZIPs in %localappdata%\FiveM\FiveM.app\crashes\.
3. 3Upload the .zip on the Crash Analyzer tab. Parsing is 100% local.

Each crash creates a new ZIP with a timestamped name like CfxCrashDumpـ .zip. Always use the most recent one.