Fix Black Screen Champ select [Read This - See if it helps you]

LuxuriousBinding·2/25/2017, 6:34:23 AM·4 votes·5,788 views

My post was being covered in the bug thread, there is a bug right now when you load into champ select it seems to lag and crash Or not load at all, or, take FOREVER to load, meanwhile showing a black screen.

Try deleting friends. I deleted 250 of my 300 friends and it loads fine for me now. Yesterdays patch allowed us with the beta client to view our friend lists while in game, this means, it loads up the list before each game, leading to the MASSIVE load times!

Hope this helps. Hope the GM's see this and put forth a fix that DOESN'T mean losing 250 friends in the process!

9 Comments

monkey 19922/26/2017, 12:29:15 AM3 votes

i don't think that is the problem i have 12 friends on my list and i still got this bug

Spixican2/25/2017, 4:40:50 PM1 votes

THANK YOU SO MUCH! THIS FIXED MY PROBLEM AND NOW I HAVE TIME BEFORE THE GAME STARTS! MY ARURF WEEKEND ISN'T RUINED ANYMORE! YOU HAVE NO IDEA HOW EXCITED I AM NOW! :D

Takanuvah2/25/2017, 4:49:42 PM1 votes

Hey i have the same problem and the friends list seems really glitchy so ima delete some friends and see if it works thanks a lot!

TrumpNukeYou2/25/2017, 9:57:21 AM1 votes

i have less than 50 friends and the bug still happens for me

Erikku2/26/2017, 12:48:15 AM1 votes

This worked for me. Thanks! I've been meaning to clean out my friends list anyways, lol

Silent Fury LvX2/27/2017, 1:18:45 AM1 votes

The Team From lolupdater.com found an solution. The Problem is coused by some overload from cclient, they updated some of their client components with faulty things, we found an workaround.

go to chatoptions and toggle group offline and also toggle group mobile, after that it should be fixed for some of ya guys.

but keep spamm support with this problem their new client is buggy as hell under the hoods, almsot all their components are fucked up and outdated.

THE TEH2/19/2018, 4:31:25 PM1 votes

I was having this issue in the new client and found out that doing a repair scan (in the client settings) fixed the bug !!