Rust Crashing Fix (PC): Crashes, Startup Errors & Reshade

On this page

Rust usually crashes or fails to start on PC for one of four reasons Facepunch documents: leftover Reshade files (banned and blocked since 13 January 2025), damaged game files, a Steam client problem such as an opted-in Steam beta, or a Windows pagefile set too low. Fix them in that order: remove Reshade, verify Rust’s files, update Steam and leave its betas, set virtual memory to automatic, then do a fresh install. Every step below comes from Facepunch’s own support site (checked 21 November 2026).

Rust Crashing Fix (PC): Crashes, Startup Errors & Reshade

Quick fix order

#FixSolvesTime
1Remove Reshade files + verify”Failed to initialize” at launch5 min
2Verify Rust files”Unknown file version”, random crashes5–15 min
3Restart / update Steam, opt out of Steam betas”Steam not open?” and other startup errors5 min
4Set the pagefile to automaticCrashes or heavy hitching from low memory5 min + restart
5Fresh install (delete the folder)Anything the steps above didn’t fix30+ min
6Send the .dmp file to FacepunchRepeatable crashes with no clear cause10 min

1. “Failed to initialize”: remove Reshade

Rust has banned Reshade since 13 January 2025, and launching with any Reshade file in the game folder fails with a “Failed to initialize” error. Facepunch’s reason is fair play: Reshade can brighten dark scenes and change how the game looks in ways that give an advantage.

  1. In Steam, right-click Rust → Properties → Installed Files → Browse…
  2. Delete the Reshade files from that folder: dxgi.dll, d3d9.dll, d3d11.dll or opengl32.dll (whichever your setup used), reshade.ini and the reshade-shaders folder if present.
  3. Back in Properties → Installed Files, click Verify integrity of game files… so Steam restores anything you removed by mistake.
  4. Relaunch Rust.

2. Verify Rust’s files

Verifying makes Steam re-check every Rust file and re-download any that are missing or damaged, and Facepunch names it as the usual fix for “Unknown file version” errors.

  1. Close Rust.
  2. In your Steam library, right-click Rust → Properties.
  3. Open Local files (Installed Files in newer Steam builds) and click Verify integrity of game files.
  4. Wait for it to finish; it can take several minutes.

3. “Steam not open?” and other startup errors

Facepunch lists these in the order they most often work:

  1. Restart Steam. Close Rust, close Steam, open Steam, open Rust.
  2. Update Steam. Close Rust, then in Steam go to Steam → Check for Steam client updates, install, restart Steam.
  3. Opt out of Steam betas. Steam → Settings → Beta participation → Change, set the drop-down to NONE – opt out, apply any update, restart Steam.
  4. Verify Rust’s files (section 2).
  5. Fresh install (section 5).

The Steam beta matters beyond startup errors: Facepunch also lists an opted-in Steam beta as a cause of freezing or hitching when you use in-game voice, alongside the wrong microphone selected or third-party audio software such as RTX Voice or Voicemeeter.

4. Set the Windows pagefile to automatic

If Rust crashes or hitches badly under load, Facepunch’s advice is to check that the Windows pagefile has not been set to a very low size and to let Windows manage it. Rust is a memory-heavy game: Steam lists 12 GB RAM minimum and 16 GB recommended.

  1. Press the Windows key and type Advanced System Settings, then open View advanced system settings.
  2. On the Advanced tab, click Settings under Performance.
  3. On that window’s Advanced tab, click Change under Virtual memory.
  4. Tick Automatically manage paging file size for all drives and click OK.
  5. Restart your PC if you changed anything.

Facepunch also recommends running Windows and Rust from an SSD with free space for updates and logs. Steam’s requirements call an SSD “highly recommended” at minimum and required at the recommended tier.

5. Do a fresh install, not just a Steam reinstall

A fresh install deletes the entire Rust folder before installing again, which a normal Steam uninstall does not do; Facepunch says leftover files can keep causing problems.

  1. Find the folder: Steam library → right-click Rust → Properties → Local files → Browse. By default it is C:\Program Files (x86)\Steam\steamapps\common\Rust.
  2. Close Rust and delete the whole Rust folder.
  3. Launch Rust from your Steam library to reinstall it.

6. Frame drops while holding a weapon: try the GPU Skinning test branch

Not a crash, but often reported alongside one. Facepunch runs a GPU Skinning test branch for “unexplainable frame rate drops while holding a weapon”:

  1. Right-click Rust → Properties → Betas.
  2. Opt into GPU Skinning test from the drop-down.

You can stay on it if it helps. Opt back out if Rust later has trouble launching. For general server-side stutter, see the Rust stuttering fix.

7. Still crashing: send Facepunch the crash dump

Rust writes a .dmp file for each crash to C:\Users\USERNAME\AppData\Local\Temp\Facepunch Studios LTD\Rust\crashes. You can also type %AppData% in File Explorer and go to \Local\Temp\Facepunch Studios LTD\Rust\crashes from there (turn on View → Hidden items if AppData is hidden).

Sort by Date modified, take the newest .dmp that matches the crash time, and attach it to a ticket on Facepunch’s support site with a description of what you were doing. Support often also asks for output_log.txt from the Rust install folder.

Check the PC side too

If Rust is clean and still crashes, rule out the usual system causes:

Rust system requirements (Steam, November 2026)

MinimumRecommended
OSWindows 11 64-bitWindows 11 64-bit
CPURyzen 5 1400 / Core i5-6600Ryzen 7 3700X / Core i7-6700K
RAM12 GB16 GB
GPURX 470 / GTX 1060 / Arc A580RX 6600 XT / RTX 3060 / Arc B580
DirectX1112
Storage45 GB, SSD highly recommended45 GB, SSD required

If your PC is below minimum, no fix on this page will make Rust stable. For why large bases and busy servers cost so much performance, see why base building tanks FPS in survival games.

Frequently asked questions

Why does Rust keep crashing on PC?

Facepunch's support articles point to a short list of causes: leftover Reshade files (banned since 13 January 2025 and blocked at launch), damaged or mismatched game files, Steam client problems such as an opted-in Steam beta, and a Windows pagefile set too low. Work through them in that order: remove Reshade, verify files, opt out of Steam betas, set the pagefile to automatic, then do a fresh install.

What does "Failed to initialize" mean in Rust?

It is the error Rust shows when Reshade is present. Facepunch banned Reshade from 13 January 2025, so you must delete its files (dxgi.dll, d3d9.dll, d3d11.dll or opengl32.dll, reshade.ini and any reshade-shaders folder) from the Rust install folder, then verify the game files in Steam so any real game file you removed is restored.

How do I fix the "Steam not open?" error in Rust?

Facepunch's order of fixes is: restart Steam and Rust, update Steam (Steam > Check for Steam client updates), opt out of Steam betas (Steam > Settings > Beta participation > NONE), verify Rust's files, and finally do a fresh install. Most players are fixed by the first two or three steps.

Where are Rust's crash dump files?

Rust writes .dmp crash files to C:\Users\USERNAME\AppData\Local\Temp\Facepunch Studios LTD\Rust\crashes, where USERNAME is your Windows user name. Sort by Date Modified and attach the newest file that matches the crash time to a Facepunch support ticket, along with a description of what you were doing and your output_log.txt.

Is a Steam reinstall the same as a fresh install of Rust?

No. Facepunch says a normal Steam reinstall can leave Rust files behind that keep causing problems. A fresh install means deleting the whole Rust folder (by default C:\Program Files (x86)\Steam\steamapps\common\Rust) and then installing again from your Steam library.