[CLIENT] Unable to load into game after match making

HeartCapturer·9/11/2018, 7:47:35 AM·3 votes·1,530 views

I'm able to join matchmaking and chose my champion, runes, and other items. But once it's time to load in, the second launcher containing the game never loads. I can't even reconnect since the client believes I'm loading in. (Notice there's no second launcher where the game would be.) I tried exiting the client and re-logging in but the same issue happens where it just says "Game is still in progress" with no reconnect button.

After the match ended (notified by my duo partner), we created a custom match to see if the same thing would happen again. Now a new message popped up along with the second launcher saying there was a "critical error". However, I still can't see the second launcher containing the game I only know it is running because of my task manager.

I am then asked for a "full memory dump to troubleshoot". When done doing so it sends back to the original client with the reconnect button. I tried to reconnect and it sends me back to the "critical error" message asking for ANOTHER "full memory dump troubleshoot". I'm basically being sent in an endless loop with no actual way to load into the game.

5 Comments

savagejen9/11/2018, 5:35:23 PM1 votes

Same issue here. I get past champ select, it looks like it's launching the game, and I end up back in the client with a Reconnect button. Clicking reconnect does nothing. Windows application error logs show the application faulted.

savagejen9/12/2018, 1:26:49 AM1 votes

I did notice a bunch of errors in the RADS logs related to chrome, which seemed odd to me. So I updated chrome and relaunched League and it significantly reduced the errors created in the RADS log, but did not fix the issue.

savagejen9/12/2018, 12:03:19 PM1 votes

Still having the issue after the patch. Submitted a bugsplat with a link to my logs.

egirlwins9/12/2018, 8:48:23 PM1 votes

I AM ON 20MIN LEAVERBUSTER BECAUSE OF THIS SAME PROBLEM HAPPINING TO ME ONLY WHEN I START RANKED MATCH.

savagejen9/13/2018, 2:35:40 PM1 votes

OK so it seems like it's related to the windows insider build I was on. If you can grab update 18237.1000, the Microsoft blog post says it will fix it.