Rust crashing with no error message, randomly.

[Kikife]

Recently I've had an issue where Rust crashes with absolutely no error messages. The game will just stop, freeze for half a second then crash with no error log, no output, nothing. I have completely reinstalled windows, I've run everything on every forum I could find but absolutely nothing has worked. I've been in BIOS and I've tried to change settings in there, disabling XMP, removing any OC, etc. but to no avail.

Facepunch support is extremely slow at responding and seem to love to repeat their solutions, so I am turning to the community for help here.

My specs are as follows:
RTX 4080
64GB DDR5 5200mhz RAM
Kingston m.2 NVMe SSD 2TB (empty apart from Rust, Riot Games and Terraria along with Discord)
i7-13700kf (microcode patched)

Please, help

[VikingDork]

How often does it happen?

[Kikife]

Originally posted by VikingDork:

How often does it happen?

It happens extremely often. For example, I just booted the game and chilled in my base for 30 seconds doing absolutely nothing then it crashed. Sometimes I have 30 minutes, sometimes I have an hour, sometimes I have 10 minutes. It's random. Although, I will say, over the last 30 minutes it's been consistent for around 1 minute after loading into a game that it will crash within 1 minute or so.

[VikingDork]

Open your command prompt as an admin, then type these commands in order. You can copy and paste from here.

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

Restart your computer then run in command prompt:

sfc /scannow

Restart your computer once more.

[Kikife]

Originally posted by VikingDork:

Open your command prompt as an admin, then type these commands in order. You can copy and paste from here.

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

Restart your computer then run in command prompt:

sfc /scannow

Restart your computer once more.

I'll try this now. I've tried sfc /scannow before, but I'll try it again. I'll let you know the results.

[VikingDork]

Originally posted by Kikife:

Originally posted by VikingDork:

Open your command prompt as an admin, then type these commands in order. You can copy and paste from here.

Dism /Online /Cleanup-Image /CheckHealth

Dism /Online /Cleanup-Image /ScanHealth

Dism /Online /Cleanup-Image /RestoreHealth

Restart your computer then run in command prompt:

sfc /scannow

Restart your computer once more.

I'll try this now. I've tried sfc /scannow before, but I'll try it again. I'll let you know the results.

Dism /online /Cleanup-Image /StartComponentCleanup Might help as well.

Dism does all kinds of OS fixes and combined with SFC, it can find some issues that just one test couldn't find.

[Kikife]

Originally posted by VikingDork:

Originally posted by Kikife:

I'll try this now. I've tried sfc /scannow before, but I'll try it again. I'll let you know the results.

Dism /online /Cleanup-Image /StartComponentCleanup Might help as well.

Dism does all kinds of OS fixes and combined with SFC, it can find some issues that just one test couldn't find.

I have just done all of the suggested system tests. It came back with absolutely no errors and no missing files. I did just do a fresh and clean installation of Windows so I assumed nothing would be found.

[VikingDork]

Then it's a hardware issue somewhere.

[Kikife]

Originally posted by VikingDork:

Then it's a hardware issue somewhere.

I've done a full memtest and came back with no issues. My friend suggested disabling my cores one by one to see if one of them is faulty because of the microcode issue that 13th and 14th gen intel processors had. Do you think that could possibly be the case? No other games crash on my pc. I did have an issue with REPO crashing and so thought it may be an issue with Unity, but after reinstalling Windows REPO did not crash on my first time playing it on a large map and with 10 players.

[VikingDork]

Originally posted by Kikife:

Originally posted by VikingDork:

Then it's a hardware issue somewhere.

I've done a full memtest and came back with no issues. My friend suggested disabling my cores one by one to see if one of them is faulty because of the microcode issue that 13th and 14th gen intel processors had. Do you think that could possibly be the case? No other games crash on my pc. I did have an issue with REPO crashing and so thought it may be an issue with Unity, but after reinstalling Windows REPO did not crash on my first time playing it on a large map and with 10 players.

To my knowledge, at least the machines I witnessed with the microcode issue, you could not even use the machine. If it booted, it would run horribly. Most of the time though, it wouldn't even boot. So, I don't think it's related.

I will mention that I have experienced this, myself, every now and then. It's not constant or super frequent... maybe 1 time every 15 sessions. I can't really diagnose the issue, personally, but felt like mentioning that I have seen what you are experiencing.

The only other thing I can recommend is to stress test your cpu and/or gpu. There are a couple monitoring and stress testing programs available that should show if, maybe, one of your components is over heating, causing the crash.

IF you can try and play it again, get it to crash, then check Event Viewer, does it show anything to you?

[Kikife]

Originally posted by VikingDork:

Originally posted by Kikife:

I've done a full memtest and came back with no issues. My friend suggested disabling my cores one by one to see if one of them is faulty because of the microcode issue that 13th and 14th gen intel processors had. Do you think that could possibly be the case? No other games crash on my pc. I did have an issue with REPO crashing and so thought it may be an issue with Unity, but after reinstalling Windows REPO did not crash on my first time playing it on a large map and with 10 players.

To my knowledge, at least the machines I witnessed with the microcode issue, you could not even use the machine. If it booted, it would run horribly. Most of the time though, it wouldn't even boot. So, I don't think it's related.

I will mention that I have experienced this, myself, every now and then. It's not constant or super frequent... maybe 1 time every 15 sessions. I can't really diagnose the issue, personally, but felt like mentioning that I have seen what you are experiencing.

The only other thing I can recommend is to stress test your cpu and/or gpu. There are a couple monitoring and stress testing programs available that should show if, maybe, one of your components is over heating, causing the crash.

IF you can try and play it again, get it to crash, then check Event Viewer, does it show anything to you?

Hi,

I'll open event viewer and see if I can replicate the issue to give you more info. I have recently re pasted both my CPU and GPU, and so that can't be the issue. That was a few weeks ago and it's still holding up completely fine and not thermal throttling on the fur benchmark or any CPU stress test.

[Georgesk]

Hi, I have the same problem since yesterday, when I did a small update.
The following did not help to fix it:
- file integrity repair
- uninstall and then new install

This is my HW:
CPU: OctalCore AMD Ryzen 7 5800X
MB: Asus TUF Gaming B550-Plus WiFi II
RAM: DDR4 32GB
GPU: AMD Radeon RX 6600 (8176 MB)
DISK M2:
- Samsung SSD 970 EVO Plus 500GB
- Apacer AS2280P4U 2TB

[Kikife]

Originally posted by VikingDork:

Originally posted by Kikife:

I've done a full memtest and came back with no issues. My friend suggested disabling my cores one by one to see if one of them is faulty because of the microcode issue that 13th and 14th gen intel processors had. Do you think that could possibly be the case? No other games crash on my pc. I did have an issue with REPO crashing and so thought it may be an issue with Unity, but after reinstalling Windows REPO did not crash on my first time playing it on a large map and with 10 players.

To my knowledge, at least the machines I witnessed with the microcode issue, you could not even use the machine. If it booted, it would run horribly. Most of the time though, it wouldn't even boot. So, I don't think it's related.

I will mention that I have experienced this, myself, every now and then. It's not constant or super frequent... maybe 1 time every 15 sessions. I can't really diagnose the issue, personally, but felt like mentioning that I have seen what you are experiencing.

The only other thing I can recommend is to stress test your cpu and/or gpu. There are a couple monitoring and stress testing programs available that should show if, maybe, one of your components is over heating, causing the crash.

IF you can try and play it again, get it to crash, then check Event Viewer, does it show anything to you?

When it does inevitably crash, do you know where I should be searching in the event viewer? Can't say I've ever used it so I'm not sure what I'm looking for.

[VikingDork]

Should be Windows Logs -> Application

Look for the Error with the red !

[Kikife]

Originally posted by VikingDork:

Should be Windows Logs -> Application

Look for the Error with the red !

I've just replicated the issue. Was in the server for about 1 minute then it crashed. There's absolutely no logs except for EAC unloading from when I exited the game by crashing.

[Kikife]

Originally posted by Kikife:

Originally posted by VikingDork:

Should be Windows Logs -> Application

Look for the Error with the red !

I've just replicated the issue. Was in the server for about 1 minute then it crashed. There's absolutely no logs except for EAC unloading from when I exited the game by crashing.

I do have this one warning, though.

File System Filter 'EasyAntiCheat_EOSSys' (Version 10.0, ‎2025‎-‎03‎-‎25T11:13:55.000000000Z) does not support bypass IO.
Supported features: 0x4.