Forum Discussion
11 Replies
- @Nalchic HP updated all drivers on Saturday via Windows Update and also went direct to NVIDIA to get their latest drivers. They also cleaned up any old ones that may have been laying around (unlikely since it was only re-imaged 10 days before), before installing and running the Heaven Graphics Benchmark.
- Nalchic12 months agoHero+@The_ultimate_GYT So my friend had exact same error message, what we did is formatted all SSD and installed win 10 from official site, then it worked fine.
- @Nalchic How did your friends system compare to mine (details in the attached msinfo file)?
Did they have the problem from the day they first installed FC24 or did it just stop working (My son had been using it for several months before getting the error)?
Any particular reason why your friend went to Win 10, is their machine not supported for Win 11?
As part of the debugging steps I disconnected both drives in my PC and connected another which I did an official Win 11 install on, but it still had the error. - Nalchic12 months agoHero+@The_ultimate_GYT The problem appeared on PC with r5 5600x and rtx2070 super. I would never use win 11 for fc24, seems to have much more problems with game. And yes at some point the game just stoped working, showing the message you mentioned.
- Nalchic12 months agoHero+Go into task manager -> details and set affinity for both faceitclient and faceitservice so that they work on only a single CPU (for example CPU 0) and do it every time you open up faceitAC.
Found this solution for faceitAC, may be it will work for ea ac as well. @NalchicThanks for the suggestions. Unfortunately the EA AntiCheat only starts up when the FC 24 game is launched so there's no time to set the Affinity before the crash happens.
I've also tried running Windows 10 but get the error the moment the FC 24 installation completes.
I really need to know what is failing in the AntiCheat so I can focus my attention in the correct area.@Nalchic Although the EA Anticheat doesn't run until you launch the game you did give me an idea of something else to look at.
So, I changed the boot configuration to reduce the total CPUs available from 16 down to 4.
After a restart I was running with only 25% of my CPU available but I didn't get the error and the game could launch.
It also worked with 50% of my CPU (8 processors) available at boot.
I'm definitely thinking I have a CPU issue now as problems with Valorant also go away with fewer CPUs.
The kicker was at 14 CPUs, the system does an immediate BSOD reporting a CRYPTO LIBRARY INTERNAL ERROR. Recovery mode and bcdedit is required to make the system usable after this.
So Valorant works fine until it goes above 12 CPUs and FC24 is fine up to 8. With 10 and 12 FC 24 fails to load but no Hardware error reported by the Anticheat.
Been in contact with HP again and waiting to hear back (discovered this just after they closed their help lines on Friday) but I think there could be light at the end of the tunnel.
Thanks for the inspiration.
- Nalchic12 months agoHero+@The_ultimate_GYT I had same problem with r5 3600, just gave me bsod. Changed cpu, no problem since then. Unfortunately cpu was the last thing I blamed, since I never had the problem with them before. But it appears, cpu now days are not that reliable.
Considering you managed to BSOD the operating system without any anticheat and a completely valid configuration, I think this is not an anticheat issue. It probably is CPU.
Regarding your initial post about the error message: Stating falsehoods in an error message is worse than being vague, and hardware errors can stem from really any component. So with such an error message, EA is probably playing it safe. They most likely suspect CPU issues are prevalent considering overclocking is explicitly called out as a possible cause, but you'd be more mad if it directly said it was a CPU problem and it turned out to be actually a RAM issue.Have you resolved it? I get the same error code "E0670A01" popping up when I try to launch EA FC. if you have could you tell me a bit about how I fixed it?
thanks.
Interesting thread because I’m having exactly the same error E0670A01.
My PC runs completely fine (Cyberpunk, Red Dead 2, Adobe Premiere Pro), but anything with EA Anti-Cheat refuses to launch.
Can you please update if changing out your CPU did indeed solve the problem?
I’ll also be trying to reduce the number of processors too to see if BF2042 will launch. Did you do this via msconfig?
Crazy thing is that both BF1 and BFV worked fine, but now they include Anti-Cheat too and now I can’t play them too!
Thanks for your help!
P.S. I have a AMD Ryzen 5700x and RTX 3060 Ti.
About FC 24 Technical Issues & Bugs
Recent Discussions
- 30 minutes ago
EA FC 24 disconnecting
Solved12 hours ago- 2 days ago
- 2 days ago