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 ar...
Forum Discussion
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!
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
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.
- Hey man.. Today i put my windows virtualmemory to zero as an experiment and it stayed very long in that black screen then i got to matchmaking and origin crashed.. Can you try and see if you can get something in there working (i dont want to give yo some false hope it might work but obviously something happening when no virtual memory available).. I proceeded to turn of automatic page sizing and dedicated 4gb of virtual memory on my main drive and also 4gb of virtual memory for my second drive where i have apex installed..
Thanks @Konform103 , I tried that. I had a system allocated 4GB on my main drive so I removed the system allocation and added custom 4GB paging files to both the main OS drive and the drive where AL is installed. Still same behavior ☹️
EA Support had be run a system file scan, it repaired a few corruptions as well. Still no bueno.
Was this issue ever resolved for you?
I seem to have the same issue and have not had much luck with EA on fixing it. Apex Legends freezes up just like in your screenshot, after the Respawn screen and before the Intro or Title screen.
I seem to have the exact same issue with Titanfall 2. I don't own any other games on Origin, but I wonder if ALL Origin games are affected.
I can play any other game. Modern Warfare. Kingdom Come. MORDHAU. Minecraft with shader packs. Outer Worlds. All on high settings. I just can't play my two favorite shooters and I can't buy any more Origin games in good faith.
Edit: It was the stupid Radeon Overlay Software.I don't think this is ever going away. Same issue here anytime I first load the game for the day, or after I have not played for about 5 hours or so. Left click to enter game, black loading screen with Apex logo shows up bottom right, then after about 10 seconds you get " program not responding". Close it out, re start it, and it loads just fine. It is not a game breaker, but its stupid annoying.
Featured Places
