Forum Discussion

EA_Leeuw's avatar
EA_Leeuw
Icon for Community Manager rankCommunity Manager
3 years ago

Re: [PC][Steam] Error 10011 - (Failed to start the game (2))

@aelthain, what is your default game install location Drive?

Can you check if moving your game back to the C drive (where EAC is also installed on, so the default Steam games location) & verifying the game files does something? I also highly suspect that continuously moving the game between drives also causes some issues. Maybe it's better to perform a complete reinstall of the game on the C drive, in the default folder, and see if that does something?

17 Replies

  • @EA_Leeuw Just moved the game back to C: and it worked fine. However, even when the game is on C: it behaves strangely.

    For example, I have AIDA64 running in the background to monitor my system. Whenever BF42 launches, it stops updating all the counters (CPU, GPU temp etc.) when I quit the game sometimes it starts working again sometimes it remains frozen. If it's frozen after a few minutes the whole Windows crashes and I have to restart. 

    I've reinstalled the entire BF42 at least 3 times so far on both drivers X: and C: It mostly works when installed on C: almost never works from X: 

    When I move the gathe me around I get id_pc_corrupt_save_body error. When I get this, I have to delete the BF2042 profile from my documents and have to go through the entire "intro" of the game and set up my keybinds etc.

  • EA_Leeuw's avatar
    EA_Leeuw
    Icon for Community Manager rankCommunity Manager
    3 years ago

    @aelthain, cheers for the info, but I would like to go back to the main issue of this topic: the EAC "Failed to start the game ( 2 )" error. 🙂

    Will you maybe be able to give it a few more tries during the day and maybe tomorrow, to see if the situation changes and if error returns or not? I would really appreciate it.

  • Sure, moved the game back to X: and this is what I got. At least when I get this the game actually exits gracefully and I don't have to restart Windows. 

  • EA_Leeuw's avatar
    EA_Leeuw
    Icon for Community Manager rankCommunity Manager
    3 years ago

    @aelthain@samyhd I would like to request to stop continuously moving the game from drive A to drive B etc. This can cause issues as well if you continuously move files around, especially if you don't repair the files afterwards or perform a clean install of the game on the other drive. The most important thing right now is that we're trying to figure out if the main issue has solved itself when the game and either Steam, Origin, EA app etc. is installed on the same drive (Windows drive), as this seems to be the root cause of the issue; that the game and launcher are installed on different drives.

    So for you, @samyhd, I would also recommend installing the game on the same drive as where you have your launcher installed on (the Windows drive is most common), and see if this also solves the issue for you.

    What I would also like to point out is that if you own multiple copies of the same game, via Steam and via Origin/EA app, for example, it's best to install only one copy.

    If this indeed seems to be the cause of the issue, it's best to create a ticket for the EAC teams so they are aware of the issue: https://www.easy.ac/en-us/support/game/contact/tech/.

  • samyhd's avatar
    samyhd
    3 years ago
    @EA_Leeuw I have only installed the Steam copy of the game since that's the only copy I own. The game is installed in the same place as the steam launcher so the issue isn't fix by this step.

    I have opened a ticket to EAC to see if they can help me out with this issue.
  • Hi, I have the same issue and also followed the steps you have taken...Still does not work..so frustrating.

  • EA_Leeuw's avatar
    EA_Leeuw
    Icon for Community Manager rankCommunity Manager
    3 years ago
    Hey @OLDMozza666,

    Welcome in this thread. 🙂

    It's unfortunate to hear that the workaround hasn't worked for you.

    Just to double check; are you getting an error message from EAC when trying to launch the game?
  • EA_Leeuw's avatar
    EA_Leeuw
    Icon for Community Manager rankCommunity Manager
    3 years ago
    @OLDMozza666, hmm, alright. In that case I think it's a different issues than that is being described in this thread.

    Have you also tried the steps that are in the first post of this thread?
  • @EA_Leeuw Hi, yes ive done all this

    BF2042.exe and BF2042_launcher.exe were changed to run as administrator
    - Reinstalled the game via STEAM
    - Reinstalled / Repaired EAC (EasyAntiCheat) 
    - Allowed Origin to run as administrator
    - Updated Windows and GPU driver to the latest of the latest updates.
    - I've set EasyAntiCheat to run Automatically from Windows Services.

    I get the same symtoms as others just not seen an error code. After the black screen loader it just drops back to the Origin screen

  • samyhd's avatar
    samyhd
    3 years ago
    @OLDMozza666 Is the black screen loader from the EAC splash-screen or BF2042.exe itself?

    If it's BF2042 that is in black screen and then shuts down then u might not have a problem with EAC since u pass the loading phase of EAC.
  • Hey everyone,

    I have been having the exact same problem as you described it: 2 days of EAC error 10011 with no fix working for me.

    The EAC splash logo came on, blue bar filled up fast or slow depending if I tried to fix game 609, with a one second freeze at the end.

    The game failed to launch about 80% of the time and once in a full moon it launched without bricking my pc.

    I have done everything that could have been a possible solution, from graph driver rollback to reinstalling C++ and all that stuff.

    My steam and Battlefield game were on the same drive so I haven't moved it elsewhere. Reïnstalled the game twice to no avail. 

    My conclusion: it's a problem from EAC server side.

    Now this evening I tried to launch the game and it succeeded first try. Could they have fixed the issue?

    I'd like to hear your feedback.

    Kind regards.

    EDIT: Nope still getting error 10011. Guess first time I was lucky...

  • samyhd's avatar
    samyhd
    3 years ago
    @Kahuna169 I'm still pending a reply from EAC to my ticket opened 4-5 days ago... If I get any news/solutions from them I will make sure to come back here with their whole feedback.

    And yeah, the way you described the behavior of EAC is exactly how everyone here is experiencing it haha... 1 second freeze when the blue bar becomes full and then you just wait 15 seconds before you get the error and later on have your PC run slow, being forced to restart the PC to run ok again.

    I was able as well to get the game launch (before I made this thread) but I'm not into brute forcing the game to run.

    Hope the reply from EAC can show up soon, they're apparently slow in checking support tickets xD

    I saw similar threads as well created since this one:

    https://answers.ea.com/t5/Technical-Issues/eac-crashes-pc/td-p/11641795

    https://answers.ea.com/t5/Technical-Issues/BF-2042-will-not-start-at-all-Origin-or-EA/m-p/11637481#M27984

    Interesting enough is that some people get past the EAC and have the windowed game show up with a black screen, failing to launch afterwards, and then you have the rest of the playerbase that simply can play the game with no problems.

    I'm pretty sure the EAC update affects users based on some hardware version since I had a friend of mine update his GPU driver and windows to the same version as mine and they have no issues playing BF2042. Must be some conflict on a different scale that they need to fix
  • @samyhd its the EAC black screen that it crashes from, does not reach the BF screen at all.tried again this morning, still the same.

  • OLDMozza666's avatar
    OLDMozza666
    3 years ago

    this is the sequence of screens i get. each one about 10seconds.

About Battlefield 2042 Technical Issues & Bugs

Having issues with Battlefield 2042? Join here to report bugs, and find help with, crashes, connectivity and more.12,930 PostsLatest Activity: 17 hours ago