Need help. Today I wanted to play Rust, so I tried to launch it. When I launch it, I get bluescreen, writing me that bluescreen is because of EasyAntiCheat.sys. I tried to repair eac, reinstalled it, reinstalled Rust, and still I have a bluescreen view. What to do???
You ain't the only one - same thing happened to me today and it was working yesterday.
Opened request 50443 with Rust support. Hopefully they'll take a look at this.
let's hope for the best BlessRNG
Well - something new - so I'm posting this for completeness and to help anyone else out.
Yesterday, Microsoft update came out with some new fixes:
2019-01 Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2 for Windows 7 and Server 2008 R2 for x64 (KB4481480) Installation date: 1/17/2019
2019-01 Security Monthly Quality Rollup foWindows Malicious Software Removal Tool x64 - January 2019 (KB890830) Installation date: 1/17/2019
Windows Malicious Software Removal Tool x64 - January 2019 (KB890830) Installation date: 1/17/2019
Update for Microsoft Silverlight (KB4481252) Installation date: 1/17/2019
Which I installed on my computer
Today, I started rust and even though the anti-cheat splash screen seemed to stay longer, I didn't get the BSOD and eventually the Rust Configuration splash screen popped up which allows me to start the game. I'll see how it goes, and report any other problems - but it looks like an update from Microsoft has fixed my EAC problem.
What this means is that EAC is somehow in bed with Microsoft which allows them to actually monitor cheating from within the operating system itself - a BSOD should never happen unless you are touching something within the OS kernel itself. Either way, it's suspicious that after 500 hours of play, the EAC caused my BSOD one day, and the very day after an update from Microsoft comes out, then it goes away. The only thing which changed was a definition update to MS Security essentials - and this is what I believe caused EAC to break. Which means that EAC is not only embedded into the Microsoft kernel, but also into its antivirus and God knows what else in the OS layer. Pretty scary stuff - but I assume this is what is required for those morons who use hacks to cheat in video games.
At any rate - I'm going to post this in the ticket I sent to Rust eventually - since this isn't a problem with Rust itself. It's a problem with EAC which is a third-party software product that Rust pays to be allowed to use with their product (as do other software games). As such - if there is a problem with EAC, then Rust can do very little about it since it is so far down in the kernel. Only EAC and MS can solve these problems and tickets should be opened with them.
If anything, Rust should provide information on how we can open tickets with EAC directly.
Windows 10 is the most fucky OS Microsoft's released for years, and they release patches without thorough testing. EAC isn't "in bed with Microsoft", EAC just runs as a system service because it needs to be able to get behind the walls to watch what's happening inside the room, as it were. Antivirus and other security suites do the same thing -- they run at a higher access level because they need that higher access level to supervise lower levels of the system, like the programs the user is running. This doesn't require any formal cooperation from Microsoft because it's a thing Windows does.
Also BSODs happen all the time because of bad drivers, it's easy to make Windows fall over and die. It shouldn't be, but it is, because that's how Microsoft makes software. It's a coincidence that these two things happened so close to each other.
This is an unwarranted assumption and you clearly don't know what you're talking about. This is not how Windows works, and there is no capacity for EAC to "embed itself" into Windows system services like Microsoft Security Essentials. You could uninstall MSE and delete every file associated with it from your system and the EAC problem wouldn't change -- I'm not recommending that you do, but you could and nothing should be different.
Uh, they do?
First of all it was Windows 7 - not Windows 10. As the original poster posted.
Second of all - I didn't get a fix from EAC. I got several updates from Microsoft (which were listed) which made EAC start working again. That was the ONLY change! And sorry - there are no coincidences in software. If something is happening you can be dam sure that a programmer made it happen that way. Even failures such as BSODs. The fact that Microsoft changes solved a problem with a third party software seems to indicate that these programs are somehow dependent on one another. Which the OS shouldn't be.
Third EAC was dying on "PAGE_FAULT_IN_NON_PAGED_AREA". So if it was accessing it's own memory area - and having a problem - why did this problem go away when Microsoft provided new packages.
Look - I don't know who you are or why I'm getting attitude from you for my comments, but the one thing I learned about software going to production - when something breaks, the first thing you ask is "WHAT CHANGED?", after which the second question you usually ask is "CAN WE PULL THAT NEW CODE OUT OF PRODUCTION?" Before EAC started BSODing, my update history showed I had about 19 updates to MS security essentials (stretching back to December 29) and then the 4 new updates happened which made EAC stop BSODing and start working again. Now unless things got updated somewhere which wasn't recorded in history - well, that's not my fault for being misled by a lousy piece of software. At any rate, the ONLY change I could find before EAC started crashing the OS was the update to MS SE - which is why I will continue to blame MS Security Essentials for the break until I get some new information.
Thank you for the link to EAC, but as for your attitude, please stick it where the sun don't shine. If you can't provide any helpful new information on saying what exactly happened, I will stick to my original notion that this was a problem with EAC which was fixed by a Microsoft update. You might think it as being an unintentional fix - but if you do, you better show some evidence. My assumption for it being intentional is because I know nothing happens randomly in computer code. If only I could write random software to fix unknown bugs - life would be so much easier. Hasn't happened yet. I had situations where I've had to put loops in code to prevent run conditions in parallel processes, but this is a page fault - which is a different animal.
Oh - and btw - I've had my Windows 7 box for over 5 years now. This is the FIRST time it's BSODed and it wasn't because of a memory fault. I was actually quite impressed with how Windows 7 could recover from software crashes without the whole OS going down compared to XP. I've had thousands of apps (and services) crash on Windows 7 over the years and it never BSODed until now. My assumption is that all of these applications had there own protected memory area which prevented them from taking the OS down with it. The fact the EAC did BSOD means it's sharing memory that the OS is using - which is why Windows couldn't recover gracefully when a page fault happened. And again - please don't tell me "Windows doesn't work that way." If you want to be helpful and know how Windows works and how this BSOD happened, we're all ears, so please explain. Without the attitude if you can.
EAC gets updates silently and automatically from the EAC mothership without any kind of user notification. For all you know they updated something, it screwed up, and they pushed out another fix and it has absolutely nothing to do with Windows itself.
Windows does not crash because "something sharing memory with the OS" crashed, Windows BSODs when the kernel cannot recover from a bad state which could be caused by any driver or other high-level process with elevated permissions, meaning any device driver and EAC's primary functions. If something tries to share the same memory address with Windows that program is crashing immediately for memory protection violations.
Go talk to EAC if you're so sure you know what the problem is, no point in asking us if you already have the answer.
Sorry, you need to Log In to post a reply to this thread.
