RuneScape 3 error codes and crash fixes
Every error, crash and connection failure we have a fix for, one page per code. Before the fix, each page says whether the problem is your machine or the studio's servers — because if it's theirs, no amount of verifying game files will help, and the only useful answer is whether it's happening right now.
Things you can fix
Crashes, install faults and driver conflicts. Find your symptom, work the steps in order, stop when it launches.
RuneScape 3 "Access Blocked" with a Ray ID: what to check
The website, the mobile app or the Jagex Launcher shows an "Access Blocked" message with a Ray ID and won't let you through.
RuneScape 3: "RuneScape has been updated!" restart error
Logging in shows "RuneScape has been updated! Please restart the game to retry" and the client won't let you sign in.
RuneScape 3 Jagex Launcher: "Could not authenticate"
The Jagex Launcher shows "Could not authenticate" when you open it, so you can't get to RuneScape.
RuneScape 3 stuck on "loading application resources"
The RuneScape client never gets past "loading application resources", or is stuck on "Loading resources", and never reaches the login screen.
RuneScape 3: client error during graphics initialisation
A pop-up says "The RuneScape client suffered from an error during graphics initialisation" and the desktop client won't load.
RuneScape 3 crash: "Error Code c0000409"
The RuneScape client crashes and shows "Error Code c0000409".
RuneScape 3: "Error_game_crash" (corrupted cache)
The client crashes with "Error_game_crash", often at startup or while playing.
RuneScape 3 on Mac: "The game cannot be opened"
On a Mac, opening RuneScape shows "The game cannot be opened" and the client does not start.
RuneScape 3: "Malformed login packet" (fix)
Logging in fails with "Malformed login packet".
RuneScape 3: "To access this free world, log into a members world"
Logging into a free-to-play world fails with "To access this free world, log into a members world and move your character to a non-members area".
Things you cannot
Queues, capacity limits and login failures. These are server-side — every page below links back to live status rather than a fix you can perform yourself.
RuneScape 3: "received an unexpected response (26)"
Logging in fails with "RuneScape received an unexpected response (26)", usually through the Steam client, and nothing else happens. Players in the same threads often say the Jagex client or the mobile app still let them in.
RuneScape 3: "Too many login attempts from your address"
Login fails with "Too many login attempts from your address", often during a busy period, and gets worse the more you retry.
RuneScape 3: "error loading the game configuration"
The client shows "There was an error loading the game configuration from the website" with a firewall hint and a code in brackets such as (6,200), (7,28) or (7,7), and won't start.
How these are graded
Every fix step carries a label. Confirmed means players demonstrably got back in with it, or the studio said so directly.Reported means it worked for some people and not others. Unconfirmed means it's circulating and there's no evidence either way yet. The distinction is the point — a page that lists five fixes with equal confidence costs you an evening.