@Tavaro Denuvo is also partially used as anticheat software, though this information might just be a fluke from another error.
I've also had some users use Linux and open-source drivers, hasn't resolved their issues.
I'm getting the feeling that many issues like this seem to be related but might be completely different... that would be very bad.
We just need people from the dev team to analyze these .dmp files, they have the debug symbols which we lack.
It's most likely not even a memory leak anymore, it's just whack.
If i can help with additional infos/testing let me know.
Still no fix. Still no feedback from Respawn. Very annoying!
I installed Windows on another Drive and there apex works. But I wont reinstall my main windows to play apex. Very annoying!
@Tavaro I was one that faced the trouble exactly same as you're on;
same windbg error code, addresses, etc.
In my case, some driver that is "hated" by new anti-cheat system was a cause.
(It was Ctrl2Cap.sys, just in my case)
I resolved it by following:
1. Install Varolant(I'm not joking)
2. When Riot Vanguard (bundled with varolant) launches, it complains if there's a driver or some that "violates".
(It was Ctrl2Cap.sys in my case)
3. Uninstall the driver by certain procedure and of course, reboot the machine
try it if you're still out of outlands.
Thanks for the tip but Valorant is working fine. Its just apex. Still broken. I already tried removing all drivers.
