THE KEY POINT
A crash dump is evidence for investigation, not a fix. Match the newest relevant .dmp file to the time Rust closed and provide it through official support when requested.
01
Find the Windows client crash folder
Facepunch’s Windows 11 instructions point to C:\Users\USERNAME\AppData\Local\Temp\Facepunch Studios LTD\Rust\crashes, replacing USERNAME with your Windows account folder. In File Explorer, hidden items may need to be shown to see AppData. This path is for the client report described by that support article, not a universal location for a dedicated server.
The article’s alternative shortcut describes %AppData% followed by a Local folder, which can be confusing because %AppData% commonly opens Roaming. Use the explicit folder path above as the reference rather than appending folders to an unrelated location. If your installation has no matching folder, report that fact instead of inventing a dump.
02
Choose the file matching the crash
- Record the approximate time Rust closed and your time zone.
- Sort the files by Date modified and identify the recent .dmp corresponding to that incident.
- Keep a copy of that relevant report before cleaning temporary files.
- Note whether the failure happened before the menu, while joining a server or during play. Include the last visible message if there was one.
Finding a crash report does not diagnose or fix the cause.
03
Explain the event alongside the file
Facepunch asks for a description of what you were doing when the crash happened. Our suggested ticket also includes the game build, whether the problem repeats and any change immediately before it began. Separate an observation, such as Rust closing during loading, from an unverified explanation such as a bad graphics driver.
Send a dump through the official private support route when requested. Crash files can contain technical or account context; a public forum does not need the raw file, and a full Temp-folder archive is unnecessary. Do not execute a .dmp file or run a random repair tool to open it.
| Relevant .dmp found | Keep its timestamp and incident description together. |
|---|---|
| Several old reports | Select the one matching the reported incident instead of attaching every file. |
| No report at that location | State the missing-file result, system version and failure stage in the ticket. |
04
What this procedure does not establish
Finding a report does not identify the cause or guarantee a repair. Do not delete configuration, reinstall the game or disable anti-cheat simply because a dump exists. Preserve useful evidence first and follow a diagnosis tied to the actual failure.
BEFORE YOU CONTINUE
Quick checklist
- Use the explicit Windows client path.
- Match the report to the incident time.
- Describe the failure stage and what preceded it.
- Share only the necessary file through official private support.
Official sources
Facepunch's Windows client instructions were reviewed on 20 October 2026. No crash was reproduced or diagnosed during this review.
The explicit Windows path is retained; the source’s alternative AppData navigation is ambiguous. No crash cause was tested or inferred.