Game crashes when I try to connect to online services

That's understandable. I was just noting someone else's solution that could possibly help. Here are some suggestions after reviewing your DxDiag.

1. Reinstall EA AntiCheat. Don't just repair it. Make sure it's fully reinstalled. Go to C:\Program Files\EA\AC\EAAntiCheat.Installer.exe. Run this as an admin and select FC 26. Then uninstall AntiCheat. Reboot, run the installer again, install AntiCheat and reboot again.
2. Disable all nonessential USB/HID devices before launch. 8BitDo controller, Logitech receiver, Razer Huntsman hooks, multiple HID virtual devices. Before you launch the game, unplug the controller and logitech receiver. Close synapse completely, disable Razer services temporarily and disable Steam input if using Steam. Test using only keyboard and mouse.
3. Clear the FC Online Profile Cache. Delete Documents\EA SPORTS FC 26\Settings and C:\Users\<you>\AppData\Local\EA SPORTS FC 26. Then, launch the game offline. If that works, launch it online.
4. Reset the Windows networking stack
   
   </>
   

   netsh winsock reset
   netsh int ip reset
   ipconfig /flushdns
   
   Reboot

5. Disable IPv6 temporarily. This can be done under the properties for your network adaptor
6. Skip the cloud sync. In the EA App go to settings > Disable cloud saves. Then, delete local FC profile/settings again. Launch offline once then try online
7. Use DDU to install a known stable driver. 24.8.1 or 24.5.1. Use DDU in Safe Mode to do this. Also, disable Windows automatic driver updates temporarily so it's not automatically updated. Reboot and try again.
8. Perform a clean boot. Hide all MS services and disable all remaining services. Startup tab > disable all startup apps. Reboot and try FC 26 online.
9. You can also try creating a new Windows user. Run the EA App from there and start the game. If this works, it's a corrupt profile issue.
10. If you still crash, check the Event Viewer and look for FC26.exe, EAAntiCheat, amdxx64.dll, ntdlll.dll, and kernelbase.dlll. Let me know what the faulting module name and exception code are.

Give these a shot and let me know what happens. Thanks!