Forum Discussion
Same here. Only difference being that I purchased the game this week through the EA app and had this issue from the get go. Also tried multiple solutions (Secure Boot, Digital Signature Enabling for the Game Service Launcher, Re-installing Anticheat, Re-Installing the EA app as well as the game, etc). Nothing seems to work. I looked at the dump file and it indicates the following:
EXCEPTION_RECORD: (.exr -1)ExceptionAddress: 00000188f9c75020 ExceptionCode: c0000005 (Access violation) ExceptionFlags: 00000000 NumberParameters: 2 Parameter[0]: 0000000000000008 Parameter[1]: 00000188f9c75020 Attempt to execute non-executable address 00000188f9c75020 PROCESS_NAME: EAAntiCheat.GameServiceLauncher.exe EXECUTE_ADDRESS: 188f9c75020
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.
EXCEPTION_CODE_STR: c0000005
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 00000188f9c75020
IP_ON_HEAP: 00000188f9c75020
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.
It seems like the EAAntiCheat_GameServiceLauncher is having issues at startup associated with trying to execute a file, but it's receiving an access violation error. This could be due to either the memory address not existing or the AntiCheat no having executable rights at the mentioned address. I've tried disabling firewall protections that could be impeding this (such as App & Browser Control under Windows Security Settings), but with no success.
The Windows version I'm using is Windows 11 23H2 Build 22631.
This doesn't seem like a trivial debugging process and I don't think we'll be able to debug it on our end. I'd assume EA will have to lunch an update to fix this issue.
About FC 24 Technical Issues & Bugs
Recent Discussions
- 13 hours ago
- 2 days ago
- 3 days ago