7 years ago

Apex Legends - Crashes Before Load

100% Reproducible. Ever since the 2/13/19 patch, when I go to launch the game I get to what I call the "Landing Page". This is after the Respawn and EA splash videos. The only options on this page are "Left Click to Continue", "Exit To Desktop", and "Accessibility Options". After Left clicking, I am shown a black screen with an Apex Legends loading icon in the bottom right of the screen.

After 2 - 5s, the logo freezes and task manager shows Apex Legends not responding. I've contacted EA support and they aren't sure what's wrong, here's what I've done so far:

1. Rebooted Comptuer

2. Repaired Apex Legend Game Files

3. Uninstalled/Reinstalled Apex Legends

4. Moved Apex Legends to a variety of different HDDs and SSDs in my system

5. Updated Windows 10 fully

6. Updated Nvidia GFX 1070 to the latest driver version

7. Changed Origin Language from English to another language and back

8. Disabled Origin Overlay

9. Tried creating a new origin account and launching the game from a new account

10. Clean reinstall of Origin

11. Edit registry to disable GameDVR

12. Run in Administrator mode

13. Force EasyAntiCheat to relaunch after failures

14. Ensure my trace to EA servers is good

Event viewer and msinfo show no issues, and there are no visible errors. I've let the loading screen sit for 30minutes with no changes.

Nothing has worked, the behavior is exactly the same every time and it's 100% reproducible. I ran Apex Legends on the exact same system without any problems prior to the 2/13/19 patch.

Windows 10 64-bit

32GB Ram

Nvidia GTX1070 w/ latest driver.

Hopefully a new patch fixes things, but I'm willing to try another dozen fixes if it'll get me back playing sooner!

16 Replies

Konform103
7 years ago
Something to check if u are interested
CastleSeven
7 years ago
Thanks @Konform103
As long as the fact that x64 and x86 have the same version for a given year, and it doesn't necessarily matter that it matches the version you have in your screenshot, I think I'm OK here. It looks like the Apex Installer ships with redists for vc2010, 2012u4, and 2015.
Konform103
7 years ago
Well you need 2013 too (origin).. Be careful when you install games/software they often install older versions of visualc++ in the background, it would be best to only install the latest versions for every year you can find them on site of microsoft. Also make sure .net framework is latest update
CastleSeven
7 years ago
Sorry, should have clarified, I have 2005, 2008, 2010, 2012, 2013, 2017 installed, and in the cases you highlighted, I have x86 and x64 with the same versions, just not the exact same that you have.
For a given C++ release, is it best practice to install the latest from that particular year? E.g., if some other game installs a version of 2013, is it safe to install the latest of 2013 and assume that game will work with it? Or does the particular version matter? I have no idea how VC++ guarantees their APIs match from year-to-year and version-to-version.
Konform103
7 years ago
Well this configuration is offering me more stability on my pc i had a lot of issues with games which seems to have been solved by this.. I dont think you need exactly the latest version for every year i have but then again it wouldnt hurt to have it.. I'm no expert on the subject this is working for me.. But then again if you install some random software and it installs visual c++ 2010 10.0.1 in the background it could cause issues i believe.. I think it is best practice to keep it in mind when a game is not working to check your visual c++ installs and find if some app had installed an older version without you knowing.. Are you still not able to play the game?
CastleSeven
7 years ago
Yea, still not working for me. I've had random failure in a variety of games that are unexplainable. Just Cause 3, Dark Souls III, both are unplayable on my rig and installing them actually screws up other games. I've long suspected VC++ issues, but have no idea which versions to keep, which to update, and which to remove.
Konform103
7 years ago
Well i learned about it cause of the trouble installing apex legends.. Before i couldnt get Warface to run fullscreen (played window for over a year), fortnite would crash to desktop without error, ring of elysium would crash anytime.. Now i can run just about any game without crash
CastleSeven
7 years ago
@Konform103
Just wanted to let you know that I did try your recommendation, it unfortunately doesn't seem to have fixed anything in regards to Apex, but maybe other things will run more smoothly for me.
Here's what my C++ packages looked like before I started:
Notice there are several copies of 2013 (one of the duplicate x64's was japanese...?)
I tried to emulate your setup for what Apex cared about, and disregarding the 2008 stuff, I copied yours exactly, and this is what it looks like now:
Still a no-go, but at least it's cleaned up a little!
Konform103
7 years ago
This is something to keep in order.. BUt since i saw your screenshot.. You have double versions running of 2008.. I would delete the .4148 and the one without a last number.. If you install applications in the backgorund they might install older versions of visualc++.. It can become messy after a while
CastleSeven
7 years ago
Another update in case anyone else is following this thread -
I had noticed around the times I launched (and crashed) Apex Legends, I was getting the following in Event Viewer:
"Display driver nvlddmkm stopped responding and has successfully recovered."
Thinking that blip might cause a problem for Apex Legends, I followed the advice here to add 2 registry keys to change the Timeout Detection value.
After this change, Apex Legends still crashes, but after force-closing the application I see there has been a Windows Notification in the background:

"Application r5apex.exe is blocked from accessing the graphics hardware"
I tried a downgrade of my 1070 driver back to 417.71 as many people report this version is the most stable at the moment for Apex, but the behavior still persists (it took longer to crash on the first boot, but it still crashes before I even get to the main menu).
I'm still in contact with EA support, we'll see if I get any updates from their end.