Guide

How to Fix Rust Crashing When Joining a Server

Kuma
Kuma
November 15, 2026 at 12:41 AM · 7 min read
Clan MemberMajor General
Two players in hazmat suits and tactical gear in a grassy field with a large monument.

Rust Crashing When Joining a Server: The Fix Order That Works

If Rust crashes when joining a server, the cause is usually on the player's PC, though a custom map or a server fault can be behind it too. Work this order: test a second server, raise your Windows page file, verify the game files in Steam, update your GPU drivers, then test whether Easy Anti-Cheat is involved. If Rust only closes on one particular server, the fault sits on that server, usually an outdated Oxide/uMod plugin or a custom map problem; Facepunch's server requirements, as checked in October 2026, are 12 GB free RAM and 15 GB free disk space. Easy Anti-Cheat timeouts look like crashes but are a separate failure with their own fix, and no Facepunch patch note or statement in the current update notes confirms a known crash-on-join bug or a hotfix for one.

That sequence is the spine of this guide. Every section below expands one step of it, and the closing checklist repeats the same five steps.

First-person view of a player aiming a bow at another player in a forest.
First-person view of a player aiming a bow at another player in a forest.

Does Rust close, or does the server drop you?

That single question splits every fix below. If the Rust process disappears entirely - no error, straight to desktop - work through the client steps. If you get bounced back to the main menu with an error string, you have a connection or anti-cheat problem instead, which Play Your Way treats as a separate problem with its own steps.

Some players report the crash at the very end of the loading sequence, on the "Done" or "Cleaning up" screen.

Which type of Rust crash you have

Match your symptom to a row, then use the matching section instead of grinding through the whole list.

Issue Type What It Looks Like Common Causes Typical Fixes
Crashes on Loading Game closes during startup or loading screen Corrupted game files, outdated GPU drivers, missing dependencies Verify files, update drivers, reinstall prerequisites
Asset Warmup Crashes Crash during texture/model/shader loading VRAM limits, shader cache corruption, GPU instability Lower graphics settings, clear shader cache, update GPU drivers
Crashes When Joining Servers Game crashes when entering specific servers Mod conflicts, server version mismatch, corrupted server data Switch servers, disable mods, verify files
EAC-Related Issues Kick or crash related to anti-cheat Easy Anti-Cheat corruption, blocked permissions, conflicting software Repair EAC, run as admin, close overlays/AV conflicts
Low-Memory Crashes Freeze or crash during gameplay or loading Insufficient RAM, low virtual memory, background apps Increase page file, close apps, lower settings

Step 1: Test a second server

Before you change anything, join a different server from the Rust server list. Crashing everywhere points at your PC or your install. Crashing on one server points at that server's plugins or map; Play Your Way's guide directs those cases to the server owner section.

Step 2: Raise the Windows page file

Loading into a server is the most memory-intensive moment in Rust. The client has to pull in the map image, world data and every asset around you before it hands over control, and hitting virtual memory limits is one of the documented causes of join-time crashes.

  1. Open Advanced System Settings and go to Advanced.
  2. Under Performance, click Settings, then the Advanced tab.
  3. In Virtual Memory, click Change.
  4. Untick Automatically manage paging file size for all drives.
  5. Set a custom size in both the initial and maximum fields. A Steam Community solution post reports 18000 or 30000 MB resolved the crash; Physgun's guide recommends an initial size of 1.5x and a maximum of 3x your installed physical RAM.
  6. Apply, restart Windows, launch Rust and rejoin.

Facepunch's own guidance frames the page file as a performance setting rather than a crash fix, but it notes Rust performs better on an SSD and that a very low page file should be ruled out. Treat this as a cheap early test rather than a guaranteed cure.

Step 3: Verify the game files and reinstall cleanly

Close Rust, right-click Rust in your Steam library, open Properties, go to Local files and press Verify integrity of game files. Facepunch notes this may take several minutes. Corrupted or missing files from an incomplete download, or a plugin touching the client, are a leading cause of crashes on loading.

If verifying changes nothing, do a fresh install. Steam's normal reinstall leaves files behind, so open Properties → Local files → Browse, delete the Rust folder, then install again from Steam.

Step 4: Update your GPU drivers

Nvidia users open GeForce Experience, go to the Drivers tab and check for updates. AMD users run the Auto Detect and Install tool, pick the Recommended Version and install. Outdated drivers are a documented cause of both loading crashes and asset warmup crashes, so do this before moving to the anti-cheat test.

Step 5: Test whether Easy Anti-Cheat is the cause

Launch RustClient.exe directly from your Rust folder. That runs the game without the EAC wrapper. It can only join servers that are not EAC-secure, so use the "Facepunch unsecure" server Facepunch names for the test.

If Rust runs that way but not normally, EAC is the likely culprit. Repair EAC, close overlays and antivirus conflicts, and do not launch the game as administrator.

An error that names EAC and a timeout is a different problem entirely. "EAC Authentication Timeout", "EAC Disconnected" and "Client Integrity Violation" are disconnects at join time, not hard crashes, and have their own fix steps. The three error names come from Facepunch's EAC error guidance as summarised by Gamers Together, and the disconnect explanation from Lobbylink.

Server-side causes for owners

If you run the server, or you host for a group, these are the causes that get misdiagnosed as client crashes.

  • Plugins. Oxide/uMod plugins break after game updates and are a documented reason a server drops or hangs players at join. Update every plugin after each Rust patch.
  • Memory. Facepunch's server requirements, as checked against Facepunch's Rust wiki and support site in October 2026, are 12 GB free RAM and 15 GB free disk space. Large maps and plugin memory leaks can push a server past that.
  • Bad configuration. Changing the map seed without a full wipe, RCON misconfiguration and plugin memory leaks are all documented server crash causes, according to CoalHost's server crash guide. Check the Rust server wipe schedule before you assume a seed change is safe.
  • Diagnostics. Your hosting panel's Crashes tab logs each server start and how it ended - normal stop, crash, out of memory or stuck - with exit codes, as described in Loaf Hosts' Crashes tab guide. That is how you tell a server fault from a client one.

If people are being dropped for permissions or connection rules rather than memory, Rust admin commands cover the server-side settings that matter.

Cloud sessions and GeForce Now

Rust crashing specifically while loading into servers on GeForce Now rigs is a recurring case with its own causes, reported across NVIDIA's forums. The practical test is the same as step one: start a completely fresh cloud session and join a different server. If the crash follows one particular community server into the new session, the fault is on that server, not the cloud rig. Network instability on your own ISP has also been cited in GeForce Now threads, so rule that out before blaming the game.

Why the current build makes join crashes more likely

The "Printed and Polished" update moved Rust to Unity 6000.3.26f1 and focused on memory and VRAM optimisation, including freeing the server map image from VRAM about a minute after the connect screen closes. The same patch made the deep sea load only on entry, stopped workshop skin icons and textures keeping a RAM copy, fixed duplicated fonts and reduced UI managed memory.

The Printed and Polished changelog lists memory and VRAM optimisations, but no Facepunch statement links them to join-time crashes; treat the timing as an overlap rather than a proven cause. No Facepunch patch note or statement in the current update notes confirms a known crash-on-join bug or a hotfix for one.

Hardware floor matters too. Minimum specs, as listed on Steam and valid as of 20 October 2026:

Component Minimum
CPU Ryzen 5 1400 or Core i5-6600
RAM 12 GB
GPU GTX 1060-class
Storage 45 GB (SSD recommended)

Console crashes go somewhere else

Rust: Console Edition is a separate codebase maintained by Double Eleven, with its own status page and bug tracker. None of the PC fixes above apply to it. Report console crashes through Double Eleven's tracker at bugs.double11.com.

Getting back in without losing your wipe

Work the order honestly, and in this exact sequence:

  1. Join a second server.
  2. Raise the Windows page file.
  3. Verify the game files in Steam.
  4. Update your GPU drivers.
  5. Test with Easy Anti-Cheat bypassed via RustClient.exe.

Physgun's guide reports that verifying the game files is the fix "90% of the time". If the crash survives all five steps and only ever happens on one server, stop fixing your PC - the problem is the host's plugins or map, and the fix belongs in their panel, not yours.

Sources

  • Rust official news: Printed and Polished update notes (rust.facepunch.com)
  • Rust official site and devblog index (rust.facepunch.com)
  • Rust on Steam store and news feed (store.steampowered.com)
  • Facepunch Support: Launching Rust with EAC disabled (RustClient.exe)
  • Facepunch Support: EAC Authentication Timeout
  • Play Your Way: Fix Rust Crashing When Joining a Server
  • Physgun: How To Fix Rust Crashing When Joining A Server
  • LOW.MS: Rust Crash or Crashing when joining a server
  • Tradeit.gg: Rust Crashing When Joining Server Error Fix
  • Coalfosting: How to fix a Rust server that keeps crashing
  • Loaf Hosts: Rust server crashes guide
  • NVIDIA GeForce Now forums: Rust crash threads
  • Steam Community discussions: Rust crash on join
  • Double Eleven: Rust Console Edition status tracker (bugs.double11.com)
Last updated: November 15, 2026 at 12:41 AM

Comments

0 Comments

Join the Conversation

Share your thoughts, ask questions, and connect with other community members.

No comments yet

Be the first to share your thoughts!