#0x00F2232B error every day / League of Legends

1 messages · Page 1 of 1 (latest)

quartz osprey
#

Since the start of last week I've noticed a drastic increase in crashes when trying to start a session for League of Legends.

[Chromebook, Chrome OS]

Sometimes it's the client crashing with code 0xc000022 where the game client doesn't start, forcing me to restart the queue since I can't re-open the game client as a user.

Most of the times the crashes are because of error code 0x00F2232B, which happens after you enter your login information (after starting the session) at the start client and press "play", and this happens every time i start a session for the first time within a +10 hour delay. So if i play until 3 am, sleep, wake up and queue at 10pm it'll always crash with that code. If I however manage to start a game i can often play two to three more sessions (never went for more as the only time i can play is after 10pm when queue waiting times aren't ridiculous (mon-fri)) without it crashing.

I don't know why this happens and I already sent a question to https://nvidia.custhelp.com/app/ask 6 days ago with no response after seeing I don't have permission to enter live-chat [first image] (even though they specifically display that at https://nvidia.custhelp.com/app/home/).

Included [beside the first two images] are most of the screenshots(with date metadata) of almost every time it has crashed like mentioned in recent times. I looked online but most of the relevant searches direct to forums that've asked the same question for the past year. Will this issue ever be addressed? Especially now with huge waiting times for only 50 people (1-2 hour(s)) it feels like a cop out and bait for people who've started a queue, can't go to a different window because otherwise it says you've been inactive even though the queue is still halfway and when the finally go to start it they get shut out and forced to re-queue with no explaination whatsover.

alpine totem
#

To solve that Permission Denied, use a Incognito/InPrivate tab.

quartz osprey
#

included: The second attempt (1 hour later) often succeeds without any errors. It's always the first.

quartz osprey
#

Tried to go in today too. Started queue at 17 UTC, didnt help that I got force disconnected even with 5 bar+stable internet connection with nothing running in background or screen timeout. When i re-queue'd i just got the 0x00F2232B error when i entered my log in info whilst inside the session. Gonna restart the queue, lets see how long it takes until I join a game.... atleast they could put a goddamn note in the status website holy crap since this is apparently happening to others recently

quartz osprey
#

and again. Waited 3 hours with a queue of 221. Entered my login info and it "crashed"

quartz osprey
#

oh and here are some more btw just to keep the post going. I tried playing today and thrice did it happen, with the queue having been restarted three times. cool

#
  • not a single day has it been without atleast two of the 0x00F2232B warnings.
quartz osprey
#

nvm today's a rare "four times cancelled" type of day i guess

quartz osprey
#

update: keeps kicking me out with the error. Tried on different pc same network: still kicked with the "bug"

New feature: random chance of sessions with unusable streaming fps. After checking connection strength and speed after exiting session it shows nothing except 200mbs-down/150mbs-up and strong connection.

When I queue again and enter a new session immediately afterwards without changing anything it's perfectly fine as if nothings happened. Cool.