Friday the 13th: The Game

Friday the 13th: The Game

View Stats:
MST3Claye Nov 6, 2017 @ 10:42pm
EasyAntiCheat.sys - BSoD MEMORY MANAGEMENT
I sent EasyAntiCheat an email on Friday (Oct 3) and still haven't heard back from them..

Windows 10 64-bit
DirectX 12
CPU Intel Core i5 4440 3.10ghz
nVidia GeForce GTX 750 Ti
8gb RAM

I apologize first off, because this is going to be talking a bit about Rust first, because that's what I've been able to play till I bought Friday the 13th on the Halloween sale. When I bought and installed it, this problem started, so bare with the Rust part of the explanation below.............................................

I've been playing Rust actively for months now and it has ran fine for what a GTX 750 Ti gpu and a Intel Pentium G3240 could run... (yes I switched CPUs, but days after the error/BSoD started).

I bought Friday the 13th when it was on sale Halloween weekend.. which also uses EAC.. and it seems that's where the problem started... I never ran Ft13, but Rust would BSoD MEMORY MANAGEMENT as soon as the launcher would finish.... and this has been the way for this game ever since. I still have yet to be able to play Ft13, because it does the same thing too.

I did get Rust to work for me one time on Halloween night. I had ran Tweaking.com's Windows Repair All-in-One. Not sure if that did something to make it work or not because I have ran that repair program two to three times after it working that night to see if it would work again to no avail.

I've read where it may be the memory or video drivers or hdd failures. All of which I have ran test after test and scan after scan. I've ran memtest86 its default 7 to 10 times. It ran clean. I've switched the RAM sticks. Nothing. I've run malware scans and scannow sfc and other things multiple times. Everything comes up fine.

bluescreenreview points to easyanticheat.sys and ntoskrnl.exe which makes me think it's EAC but I don't know how to fix that driver.

Also some odd occurence with EAC installs..

EAC directory in the Rust directory: EasyAntiCheat_Setup.exe, two DLL files (one x86 the other x64), Certificates directory, Launcher directory, Licenses directory, Localization directory.

EAC directory in c:\program files (x86): EasyAntiCheat.exe

nothing relating to EAC in the windows\system32 directory or its drivers dir.

nothing relating to EAC in the windows\SysWOW64 directory or it's drivers dir.

this is after I did a "repair" with the setup file in the Rust EAC dir. So no EasyAntiCheat.sys file to be found..

I try the EasyAntiCheat.exe file in the EAC dir in Program Files (x86) and it gives me an Error.. CopyFile fail 32.

I think the last time, I actually ran the .exe file and not the setup.exe file and it put the troubling sys file in the SysWOW64 directory.

here's a zip file of one crash mini dump that happened with the game after all the scans and AiO repairs that I did.

https://www.dropbox.com/s/dg2o20o39zhzj2c/110417-29875-01.rar?dl=0

I posted this to the Rust bug report discussion too fwiw. Would be nice to play these games (again).
< >
Showing 1-8 of 8 comments
MST3Claye Nov 7, 2017 @ 1:32pm 
Thank you for responding. I have sent the email with a .rar of my dxdiag and the dump error file of the recent attempt at trying to play Friday the 13th since I don't know where the game logs are for it.
MST3Claye Nov 8, 2017 @ 11:55am 
EAC got back with me and says that since ntoskrnl.exe is mentioned it's something deep in the system files or hardware and suggest deleting everything and re-installing Windows......... Ehhhhhhhhh....
Alt Nov 8, 2017 @ 12:40pm 
Have you tried updating your bios?
Alt Nov 8, 2017 @ 12:45pm 
Also, your RAM stick(s) might be faulty, this error is what comes up sometimes.
MST3Claye Nov 8, 2017 @ 2:45pm 
Yes, I updated my BIOS on Friday.. still the same error... I've ran my RAM through several memtest86 and memory diagnostic scans.. It's run the full 7 to 10 times scan on memtest86 and I think I've done that one twice over. I've taken my RAM out and even switched the sticks. Still nothing.
Alt Nov 8, 2017 @ 3:02pm 
Originally posted by MST3Claye:
Yes, I updated my BIOS on Friday.. still the same error... I've ran my RAM through several memtest86 and memory diagnostic scans.. It's run the full 7 to 10 times scan on memtest86 and I think I've done that one twice over. I've taken my RAM out and even switched the sticks. Still nothing.

Have you started the PC up and started a game up with only 1 RAM stick in?

Try doing that with each stick.

Also, it might be best to totally re-install windows.
Last edited by Alt; Nov 8, 2017 @ 3:04pm
MST3Claye Nov 9, 2017 @ 4:38pm 
UPDATE! I had a previous hard drive I was using till the first of August.. I plugged that in to figure out some stuff going on when I was checking my RAM.. because it did something weird with Windows on my current HDD... Rust ran FINE on it.. so did Ft13.. So I decided to do a clean install of Windows on a spare HDD I have while using the current drive just for important files and stuff.. loaded up Steam on the current drive while Windows was working on that spare HDD I have and tried Rust and Ft13.. They both ran fine without any issues.. In fact better than they'd been running....

Clean install of Windows did it.. or just a new install of Windows. Thanks for the replies and suggestions.
Alt Nov 9, 2017 @ 4:40pm 
Originally posted by MST3Claye:
UPDATE! I had a previous hard drive I was using till the first of August.. I plugged that in to figure out some stuff going on when I was checking my RAM.. because it did something weird with Windows on my current HDD... Rust ran FINE on it.. so did Ft13.. So I decided to do a clean install of Windows on a spare HDD I have while using the current drive just for important files and stuff.. loaded up Steam on the current drive while Windows was working on that spare HDD I have and tried Rust and Ft13.. They both ran fine without any issues.. In fact better than they'd been running....

Clean install of Windows did it.. or just a new install of Windows. Thanks for the replies and suggestions.

I've had some issues with windows where it stopped games from working, a completely clean install of windows usually fixes it.

Somehow files end up becoming missing on the current windowsOS and only way to fix it, is by reinstalling.
< >
Showing 1-8 of 8 comments
Per page: 1530 50

Date Posted: Nov 6, 2017 @ 10:42pm
Posts: 8