Where to Find HOI4 Crash Reports: A Complete Guide for Hearts of Iron IV Players

Hearts of Iron IV is a deeply complex grand strategy game, and like any demanding piece of software, it can crash. When it does, it leaves behind a crash report — a log file containing technical details about what went wrong. Knowing where to find these files is the first step toward diagnosing the problem, whether you're troubleshooting yourself or reporting an issue to Paradox Interactive's support team.

What Is a HOI4 Crash Report?

A crash report is an automatically generated file that records the game's state at the moment it failed. It typically includes:

• Error codes and exception types — the technical reason the game stopped
• A stack trace — a sequential list of processes running at the time of the crash
• System information — your OS, memory state, and sometimes GPU/CPU activity
• Game version and mod list — which version of HOI4 was running and what mods were loaded

These files don't fix anything on their own, but they tell you — or a developer — exactly where the failure occurred.

Where HOI4 Stores Crash Reports 🗂️

Paradox games store their log and crash files in a consistent location depending on your operating system. HOI4 is no different.

On Windows

The most important folder is:

C:Users[YourUsername]DocumentsParadox InteractiveHearts of Iron IVlogs 

Inside this folder, look for:

• crash.dmp — a memory dump file created at the time of the crash
• error.log — a running log of game errors, warnings, and events
• system.log — records system-level information at launch and during play

The crash.dmp file is the most technically detailed. The error.log is often the most readable and useful for identifying mod conflicts or missing files.

On macOS

The path follows a similar structure:

~/Documents/Paradox Interactive/Hearts of Iron IV/logs/ 

macOS also generates its own crash reports through the Console app (found in Applications > Utilities). Under the "Crash Reports" section, look for entries labeled with hoi4 or hoi4game. These Apple-generated reports can supplement what Paradox's own logs capture.

On Linux

For Linux users running HOI4 through Steam (including Proton compatibility layer), the logs folder is typically:

~/.local/share/Paradox Interactive/Hearts of Iron IV/logs/ 

Note that Proton-based installations can sometimes scatter logs across additional locations depending on the Steam Play configuration. If the above path doesn't yield results, checking the Steam runtime folders may be necessary.

The Steam Overlay and Alternate Log Locations

If you launched HOI4 through Steam, there's an additional place worth checking. Steam occasionally writes its own crash information to:

C:Program Files (x86)Steamlogs 

Look for files like crash_[timestamp].dmp in this directory. These are less game-specific but can reveal issues related to the Steam client itself conflicting with the game.

How to Read a HOI4 Error Log 🔍

You don't need to be a programmer to get value from error.log. Open it with any plain text editor (Notepad, TextEdit, VS Code). The file reads chronologically, so scroll to the bottom — the most recent errors will be closest to the crash point.

Watch for lines beginning with:

• [Error] — a definite problem the game encountered
• [Warning] — a non-fatal issue that may have contributed to instability
• Script error — almost always points to a mod conflict or broken mod file

Common readable causes found in these logs include missing localisation files, incompatible mod versions, and out-of-bounds memory references.

Key Differences Between Log Files

The crash.dmp file requires specialized tools to interpret fully — such as WinDbg on Windows or crash analysis platforms used by developers. For most players, error.log will be the more actionable file.

Mods and Why They Complicate Crash Reports

If you're running mods, the error.log becomes significantly longer and more complex. Paradox's modding system is open-ended, and many community mods touch the same game files. When two mods modify the same national focus tree, event file, or unit definition, HOI4 can crash silently.

The log will usually flag these as Script errors referencing specific file paths. Those file paths often directly name the conflicting mod. This is why comparing your active mod list against the error entries is a reliable diagnostic step.

Submitting a Crash Report to Paradox Support

If you're opening a support ticket with Paradox Interactive, they will typically ask for:

1. Your error.log file
2. Your crash.dmp file
3. Your mod list (visible in the launcher)
4. Your system specifications

The logs folder location above covers everything they need. Compress the entire /logs/ folder into a .zip file for easy attachment.

What Shapes the Outcome From Here

Finding the crash report is straightforward — but what you do with it depends on several variables that differ from player to player:

• Whether you're running mods — vanilla crashes and modded crashes require completely different responses
• Your OS and hardware — some crashes are driver-related, others are memory or storage issues unrelated to the game itself
• HOI4 version — a crash in an older version may already be patched; a crash in a beta branch may be a known, reported issue
• Technical comfort level — reading a stack trace meaningfully requires a different skill set than simply identifying a mod conflict in error.log

The log files give you the raw data. Whether that data points to a simple mod disable, a driver update, a hardware issue, or a genuine game bug depends entirely on what's in your specific report — and that's something only your own files can reveal.