Rust BSOD

[[1DoD] Dodge]

I am having an issue suddenly where Rust basically blue screens within 5-10 minutes of launching the game. I can enter a server, or stay at the main menu and it will suddenly crash my entire computer. I’ve mostly rules out power supply issues via benchmarking my GPU and CPU at the same time using separate benchmarking programs (Cinebench and Heaven benchmarks).

I have run the windows memory test to rule out RAM as an issue. I have reseated my GPU and RAM as well.

Verified integrity of game files.
Reinstalled Rust.
Reinstalled Windows to a blank state.
Updated and reverted GPU drivers.
Tried to run the game with only default Windows programs + Steam of course. Still crashes.

I cannot find a reason why it could be a hardware issue despite the symptoms seeming to lean towards hardware.

Latest bios update as well. No overclocking. And has been running the game just fine for a few days, suddenly it started doing this with no symptoms beforehand.


Hardware:

Intel i7 14700KF

Nvidia 4080 SUPER FE

32GB(16x2) DDR5 TForce 6000Mhz

Corsair 850w PSU

Any help is appreciated, thanks!

[thunder]

Same

i7 14700K
3080 12gb

[troy]

Same here. I think this is due to the recent update. I had done all of the baseline troubleshooting steps you can think of, and it's pointing to the game.

[[1DoD] Dodge]

Originally posted by troy:

Same here. I think this is due to the recent update. I had done all of the baseline troubleshooting steps you can think of, and it's pointing to the game.

Are you also using an intel 14th gen? It seems to be effecting those more than the rest.

[Syzo]

Happening to me aswell I have a Ryzen though

[Spill]

You seem to know what your doing. If you can try another PSUas you are saying ruling out PSU issues cant really be done.

Does indeed sound like hardware, Although this update mentioned something about changing unity version. Something that can trigger edge cases when enrolled to wide audience.

I would contact support and provide the dump files https://support.facepunchstudios.com/hc/en-us/articles/5060859342737-How-to-find-Rust-s-crash-dmp-files

and https://support.facepunchstudios.com/hc/en-us/articles/360019318117-Output-Log
outputlog is plaintext and can give you a clue to. but with bsd and insta turnoff it might not have gotten anything written

overheating could also be issue

been more similar reports lately, speaks against being a hardware issue on your end

how many of you have overclocked?

[~David~]

I get a black screen and then reboots pc..... and my base is decaying away.

[[1DoD] Dodge]

Originally posted by Spill:

You seem to know what your doing. If you can try another PSUas you are saying ruling out PSU issues cant really be done.

Does indeed sound like hardware, Although this update mentioned something about changing unity version. Something that can trigger edge cases when enrolled to wide audience.

I would contact support and provide the dump files https://support.facepunchstudios.com/hc/en-us/articles/5060859342737-How-to-find-Rust-s-crash-dmp-files

and https://support.facepunchstudios.com/hc/en-us/articles/360019318117-Output-Log
outputlog is plaintext and can give you a clue to. but with bsd and insta turnoff it might not have gotten anything written

overheating could also be issue

been more similar reports lately, speaks against being a hardware issue on your end

how many of you have overclocked?

Made a ticket with Facepunch as I cannot replicate the issue in any other way than just running Rust, they claimed to already have been looking into the issue since this morning and know about it. Seems to be in their hands now and all we can do is hope that they are speedy.

[[1DoD] Dodge]

Originally posted by Spill:

You seem to know what your doing. If you can try another PSUas you are saying ruling out PSU issues cant really be done.

Does indeed sound like hardware, Although this update mentioned something about changing unity version. Something that can trigger edge cases when enrolled to wide audience.

I would contact support and provide the dump files https://support.facepunchstudios.com/hc/en-us/articles/5060859342737-How-to-find-Rust-s-crash-dmp-files

and https://support.facepunchstudios.com/hc/en-us/articles/360019318117-Output-Log
outputlog is plaintext and can give you a clue to. but with bsd and insta turnoff it might not have gotten anything written

overheating could also be issue

been more similar reports lately, speaks against being a hardware issue on your end

how many of you have overclocked?

To be blatantly honest, no. I have no idea what I’m doing. I’m using basic logic with some experience diagnosing my own issues. I troubleshoot industrial manufacturing machinery for a living. Not computers.

[󠀡󠀡]

try this workaround:

Originally posted by 󠀡󠀡:

Sounds like the EAC crash error 30004 that hasn't been fixed for over 5 years.

Test in CMD with admin:

bcdedit.exe -set TESTSIGNING OFF
bcdedit.exe -set NOINTEGRITYCHECKS ON

it requires you to turn off secure boot in the bios in order to do these commands.
After doing those steps, go to "C:\Program Files (x86)\EasyAntiCheat_EOS" and delete the "EasyAntiCheat_EOS.sys" file. Then start the game and see if it stops crashing. It must be deleted every time you wish to open rust as something is happening on the kernel level that corrupts it after you close the game.

If you can do these exact steps every time you wish to open rust and it works, then thats the workaround.

If it doesn't work, then tell Facepunch to get their sh^t together to talk with EasyAntiCheat about it, thousands of people have this issue, no one should be BSODing in order to play your game.

[No_Quarter]

14 series intel CPU's have very high rate of defect so I would look into that.

[󠀡󠀡]

Originally posted by 󠀡󠀡:

try this workaround:

Originally posted by 󠀡󠀡:

Sounds like the EAC crash error 30004 that hasn't been fixed for over 5 years.

Test in CMD with admin:

bcdedit.exe -set TESTSIGNING OFF
bcdedit.exe -set NOINTEGRITYCHECKS ON

it requires you to turn off secure boot in the bios in order to do these commands.
After doing those steps, go to "C:\Program Files (x86)\EasyAntiCheat_EOS" and delete the "EasyAntiCheat_EOS.sys" file. Then start the game and see if it stops crashing. It must be deleted every time you wish to open rust as something is happening on the kernel level that corrupts it after you close the game.

If you can do these exact steps every time you wish to open rust and it works, then thats the workaround.

If it doesn't work, then tell Facepunch to get their sh^t together to talk with EasyAntiCheat about it, thousands of people have this issue, no one should be BSODing in order to play your game.

I must also mention, each BSOD carries the risk of damaging your SSDs when read writes are occurring and get disrupted, so this is not an issue you want to keep BSODing yourself with. Risk the BSOD at least 3 times to test if the workaround is consistent (assuming you've done the steps every time you wish to open rust), the results will be your answer.

[󠀡󠀡]

Originally posted by No_Quarter:

14 series intel CPU's have very high rate of defect so I would look into that.

I get it with my Ryzen too, so its definitely an EAC problem if we're talking about the same error code (EAC Error: 30004) which results in a BSOD kernel check error pointing to the "EasyAntiCheat_EOS.sys" file failing to work.

[[1DoD] Dodge]

Originally posted by No_Quarter:

14 series intel CPU's have very high rate of defect so I would look into that.

It’s a Rust only thing brother.

[No_Quarter]

Originally posted by 1DoD Dodge:

Originally posted by No_Quarter:

14 series intel CPU's have very high rate of defect so I would look into that.

It’s a Rust only thing brother.

yeah nah, big customers are reporting upwards of 25% failure rate for intel gen 13/14 CPU's.

[[1DoD] Dodge]

Originally posted by No_Quarter:

Originally posted by 1DoD Dodge:

It’s a Rust only thing brother.

yeah nah, big customers are reporting upwards of 25% failure rate for intel gen 13/14 CPU's.

Yes, I’m aware. But this problem is completely unrelated to that problem.