Forum Discussion
7 years ago
I have this too. Using an Intel Xeon E5450 3.0Ghz. A lot of people encountered this same issue in For Honor when the last update dropped on the 31st of January, mostly people with Xeon and Core 2 Quad CPUs are affected by it (although there were some i5s and i7s with the same problem too). It's most likely caused by EasyAntiCheat but no one's sure yet. I can only recommend sending a support ticket as it seems to be a pain in the * to fix for developers and it doesn't seem we can fix it by ourselves.
- 7 years agoRunning Win7 and a Core 2 Quad CPU, like you mentioned. It does seem to be the EasyAntiCheat, because it always throws the error up after a few seconds of it running. Were the issues resolved with For Honor yet? Are we looking at a long time until we can expect a fix, if ever? FeelsBadMan
- 7 years ago
I love installing 3rd party stuff, sniffing on my personal data even if i don't cheat, breaking games.
developer: "we play our games." sure and i'm unicorn.