Rust crashing when loading into a server: fixes that actually work.

Joining a server is the heaviest moment in Rust. The client has to load the map, stream in every asset the server tells it about, and warm up shaders and textures, all at once. On a PC that is short of memory, running an old driver or fighting its anti-cheat, that spike is where it falls over. The symptoms are the ones everyone describes: the game closes to desktop at "loading assets" or "receiving data", freezes on the loading bar, or kicks back to the main menu with no error.

It is rarely the server. If other people are on it and you crash at the same point every time, the fix is on your side. If everyone is being disconnected at once, that is the server and the owner should check its console; the admin commands guide covers what to look at.

1. Restart the PC, not just Rust. A long session leaves memory fragmented. A clean boot clears it and fixes more loading crashes than anything else on this list.
2. Verify the game files in Steam. Right-click Rust in your library, Properties, Installed Files, Verify integrity. A single corrupt asset bundle will crash the load every time, and this is a five-minute check.
3. Close everything else. Browsers with many tabs, Discord's hardware acceleration and recording software all compete for the same RAM and video memory during the load.
4. Lower the graphics settings for one join. Drop texture quality, shadow quality and water quality, turn off "Max Gibs" and lower draw distance, join the server, then raise them back once you are in. The load spike is what crashes; the settings afterwards are fine.

Rust comfortably uses 12 to 16 GB of RAM while loading a large server, more on modded servers that push custom assets. On an 8 GB machine, or a 16 GB machine with a browser open, it runs out and Windows closes it.

• Check the page file. Windows uses the page file as overflow when RAM runs out. If it is disabled or capped small, Rust crashes instead of slowing down. In System, Advanced system settings, Performance, Advanced, Virtual memory, set it to "System managed" on your fastest drive, or a fixed size of at least 16 GB.
• Run Rust from an SSD. Asset streaming off a hard drive can time out on big servers, which shows up as a crash or a kick during loading.
• Watch Task Manager during the load. If memory hits 95 percent and Rust dies, you have your answer, and the page file change above is the fix until you add RAM.

• Update the GPU driver from NVIDIA or AMD directly, not through Windows Update. A clean install (the option is in the installer) removes old profiles that cause shader crashes.
• Disable fullscreen optimisations for Rust's executable: find Rust.exe in the install folder, Properties, Compatibility, tick "Disable fullscreen optimizations". Try the game in borderless window mode too.
• Turn off overlays. Steam, Discord, GeForce Experience and Xbox Game Bar overlays all hook into the game. Any one of them can crash the load after a driver update.
• Install pending Windows updates, then restart. Half-applied updates break DirectX components Rust relies on.

Rust runs Easy Anti-Cheat, and EAC failing to start shows up as a crash or an instant disconnect during loading rather than a clear error. Two fixes cover almost every EAC case:

1. Repair EAC. In the Rust install folder open the EasyAntiCheat folder, run EasyAntiCheat_Setup.exe or EasyAntiCheat_EOS_Setup.exe, choose Rust and click Repair.
2. Exclude Rust from your antivirus. Add the Rust install folder and the EasyAntiCheat service to your antivirus exclusions. Overzealous scanners quarantine EAC files mid-load.

If EAC complains about an untrusted file, it names it. Verifying the game files replaces it.

Two last steps when the above have not worked.

• Clear the shader and asset cache. Delete the cfg folder's cached files only if a guide for your specific error tells you to; the safer version is to let Steam rebuild shaders by setting Steam's shader pre-caching off and on again in Settings, Downloads.
• Launch options. In Steam, Properties, Launch options, -high raises the process priority. Some players also add -force-d3d11 if a newer DirectX path is crashing on an older card. Remove them again if they make no difference; launch options are not a performance setting.

If the crash only happens on one server, and that server is heavily modded, the server may be pushing a custom map or asset bundle that your client cannot load. Try a vanilla server to confirm, and tell the owner; our server list shows which servers are modded.

Server owners see the other side of this: everyone disconnects at once, or new players cannot load in while existing ones play fine. The usual causes are a server out of RAM (the console shows the save stalling or the process restarting), a plugin throwing errors on player connect, or a custom map that was uploaded incomplete. Restarting fixes the first for a while; the real fix is a plan with enough memory. RSH panel plans are sized at 16, 24 and 32 GB for exactly this reason, and the console in the panel shows the error that the player never sees.

Setting up a server from scratch, or moving one, is covered in how to host a Rust server.