This did work for me
@k10FA This worked for me. Thanks!
Removing mtihint.sys and mticache.sys in C>Windows>System32>drivers worked for me.
I created a new folder, moved those two files into the folder, while still in the DRIVERS folder and Apex started right up, gonna do some test runs and see if its stable
===This fix was stable on my PC, I played about 10 games, some long some short, no hiccups, stuttering or killing to desktop+++
I'm not sure what to tell you, when I was looking I was just hoping they'd be there so I could attempt the fix, now that they're they I just wish I knew what they are originally for
The solution first, works for me, but others might have a different fix depending on their setup:
1. Make a new folder in system32>drivers (I named it backup)
2. Cut and paste all the .sys files, ignore the folders
3. If they need administrator permission to move, continue
4. If they ask for second permission, skip all files (try again won't change a thing)
5. Then try to play Apex. If it works, then there's a problem with the moved drivers. If it doesn't work, unfortunately, you might need to wait for another solution.
Now, if you're skeptical, it's understandable, moving something in sys32 without knowing what it is is dangerous. But, the drivers that actually needed are all filtered on the 4th step, so the moved drivers should all be unused (but somehow Apex is trying to read/execute them in the latest update)
I fine-tuned the method by slowly moving back all the drivers from the backup folder (playing Skyrim with mods, combing files like this is like necessity). For me, there's a driver called MFWCtwl.sys which is from Samsung Electronics (I don't have any Samsung). There are people with mtihint.sys and mticache.sys, or others with ABD_something.sys. You might have different problem drivers too.
---
Thankfully you came back to check on this thread you made, even though there are a lot of people here already with their own problems.
Anyway, I searched for my problems and found out that you also have the same problems, hence why I'm here reading the thread.
I've also done the same troubleshooting as you did, but to no avail.
Funny enough, the solution @lasop123 worked for me.
Good luck.
I still can't play the game since last update at the end of july.
The trouble: the game launches, I see the first windows then nothing i get back to the desktop, and in the process, Apex is maked as running but with only 250 mo of RAM used.
config: windows 10, nvidia 3060 ti, AMD 3700x cpu,
I tried:
- get rid of Razer and cooler master soft and services about any rgb stuff
- repare, desinstall and reinstall apex, origin, even tried to install on steam (exactly same trouble)
- run as admin EasyAntiCheat_launcher.exe and r5apex.exe
- fix easyanticheat using EasyAntiCheat_Setup.exe
- closed all non-microsoft services and run a clean boot
- launch malwarebyte to try to find if some malwares interfering
...
so here i'm: still the exact same reproducible trouble: it launches easy-anticheat then nothing. It even replaced the Apex shortcut on my desktop but the easy anticheat icon.
My son on his PC: it works.
So, what can we do? No news and any communication? We are on holiday to benefit from gaming a bit and doesn't work
Really cool that we wwnt a whole * week and missed all but one day of the event because an update broke something. 🙂
Also stating it once again, this thread was made for the issue of the game being able to launch and then crashing after being open for a few minutes, not being unable to launch past EAC. Its hard to tell what people are trying to offer solutions for in here when everyone is talking about 2 different issues without saying which one they actually have. From what I can tell, everyone messing with BIOS or Sys32 are the ones suffering from EAC?
same thing for me. still not working and logo changed. its been a whole week without a word from them. They have robbed us of our money
