Source-led route
A game that fails before you can play and one that closes during a battle are different reports. This checklist helps record which case occurred and points to Gaijin's published reporting guidance. It does not claim that any step makes the game stable.
Section 01
Sort the failure
| What happened | Record |
|---|---|
| The launcher or game fails before a session | Whether the launcher opened and the exact message shown |
| The game closes or freezes during a session | The time, what was happening and whether an error appeared |
| The game closes without a message | The symptom and any steps that reproduce it |
If an error appears, copy it exactly. Do not use instructions for a different message or infer a cause from a similar symptom.
Section 02
Startup failure
For an error shown at startup, record the full wording and use the matching Gaijin Support page. This article does not reproduce error-specific buttons, file names or repair steps that were not checked in the current client.
If the failure began after a Steam update, use the War Thunder Steam update checklist. If you are unsure whether the PC meets the published floor, compare it with the War Thunder PC requirements.
Section 03
Crash or freeze during a session
For a bug report, Gaijin asks for a clear title, a detailed description and steps to reproduce the issue when possible. It also asks for the platform, category, game version and files relevant to the issue.
Gaijin says client logs are recorded after the game closes. The latest .clog file is in the .game_logs folder inside the game directory. Client replays are stored in the Replays folder. The bug report page also links to instructions for creating a DxDiag file.
Record the game version as the client displays it, the approximate time of the crash, and what you were doing. Do not claim a cause based on one crash or one log.
Section 04
Crash with no error message
Gaijin has a separate support page for crashes without an error message. That page describes advanced diagnostics, including temporarily changing security settings, running the client with anti-cheat disabled and using a debugger.
This article does not instruct readers to make those changes. They are specific to Gaijin's no-message troubleshooting page, not general launch or stability settings. Review Gaijin's instructions and ask its support team before carrying out advanced steps.
Section 05
Report the issue
Gaijin says its support team does not manage bug reports. It directs players to the in-game report option or the War Thunder issue tracker. Include the exact message, a detailed description, steps to reproduce when possible, platform, category, version and the files relevant to the issue.
RigCircuit did not reproduce a crash, create a dump or submit a report for this article. No stability result is claimed.
Evidence record
Sources
- Taking necessary steps and collecting information in case of crashes without error messages, Gaijin Support, checked September 27, 2026.
- Bug reports, Gaijin Support, checked September 27, 2026.
Publication record
Keep the decision trace visible
This route passed its publication checks. Future reviews must reconfirm the source date, game build, media rights and reader action.
- Confirm the source. Recheck the linked primary or authoritative page.
- Confirm the media. Keep the approved WordPress path and rights note attached.
- Confirm the next move. Give the reader a clear action without inventing a test.
Evidence library
Sources checked for this article
This library preserves source titles, publishers and check dates. Original URLs remain in the editorial record.
- Taking necessary steps and collecting information in case of crashes without error messagesGaijin Support, War Thunder · Checked October 2, 2026Reference on file
- Bug reportsGaijin Support, War Thunder · Checked October 2, 2026Reference on file
Keep exploring
Related articles
Read next
Continue with the next route
