Errors and Crashes

Star Citizen log and error doctor

Check the log from the session that crashed

Drop Game.log, gpu_error.log or the launcher's log.log here, or choose it below. The page finds the crash, explains the likely cause and lists what to try.

Your log never leaves your computer. It is read by your browser, checked, and thrown away - nothing is uploaded or saved. Your Windows username, RSI handle, account and player IDs and IP addresses are hidden from what is shown.

Game log: ...\Roberts Space Industries\StarCitizen\LIVE\Game.log
Launcher log: %appdata%\rsilauncher\logs\log.log

Error code lookup

Type a code from the launcher or the game - matching codes appear as you type. Codes are checked in your browser and not recorded.

Every code in the list

Star Citizen error codes (44)

  • Error 19000 - login server authentication failed - 19000, 19004, and 19005 mean the client failed to authenticate with the Cloud Imperium login servers.
  • Error 15011 - account login locked - 15011 means the account login is locked and the client will not start a session.
  • Error 10000 - game servers not found - 10000 means the client cannot locate the game servers. This is a client-side connection block, not a crash.
  • Error 10001 - authentication service - 10001 means the client could not connect to the authentication service.
  • Error 10003 - persistence cache - 10003 means authentication connected, but the persistence cache is corrupted or unreachable.
  • Error 10004 - CIG services timeout - 10004, 50000, and 50001 are CIG services connection timeouts.
  • Error 20028 - disconnected for inactivity - 20028, 20030, and 30028 mean the session was closed because the client was idle.
  • Error 30003 - connection error or bad token - 30003 is a connection error, often with a bad token file left on disk.
  • Error 30004 - package or entitlement - 30004 and 30005 mean the game package or entitlement check failed.
  • Error 30011 - socket error - 30011 and 30012 are socket errors. The client could not send data to the server.
  • Error 30013 - kicked - 30013 means the session was kicked.
  • Error 40026 - version mismatch - 40026 means the client and server builds do not match.
  • Error 40014 - region routing - 40014 is a connection or region routing error.
  • Error 41070 - backend or patch availability - 41070 and 41013 are known backend or patch-availability errors.
  • Error 60015 - session full - 60015 means the session you tried to join is full.
  • Error 5009 - cannot create game files - 5009 is an I/O error. Windows blocked the launcher from creating files in the game directory.
  • Error 5021 - installer error - 5021 is an installer failure while writing the game files.
  • Error 8001 - manifest or patch download failed - 8001 and 8004 mean the launcher could not download the manifest or the patch.
  • Error 16007 - cannot reach CIG services - Error 16007, often paired with 16008, means the game cannot reach or connect to the authentication and CIG backend services for your region.
  • Error 4000 - cannot retrieve update manifest - 4000 means the launcher could not download the update manifest.
  • Bad token - <=BAD TOKEN=> in location select is a stale session, usually right after a 30k.
  • Easy Anti-Cheat code 0 / untrusted file - EAC code 0 or Untrusted System File means anti-cheat rejected a file or an injector.
  • Error 30000 - connection timeout - Star Citizen error 30000 (the 30k) is a general connection timeout. The game client lost contact with the game server, either because the server crashed or the network session timed out. You can still be connected to the hub.
  • Error 15006 - authentication timeout - 15006 and 15009 mean the client could not finish authentication with the game servers.
  • Error 15007 - account login failed - 15007 means the account login failed. It is also reported with 15006 and 16007 when a local profile or user config is stuck.
  • Error 15008 / 16008 - account data update failed - The game cannot reach the authentication servers for your region.
  • Error 30007 - connection timeout - 30007 is a connection timeout, sometimes caused by the GPU stalling while the client is trying to connect.
  • Error 6000 - generic crash - 6000 is a catch-all. The game or launcher stopped without a more specific code.
  • Access violation - 3221225477 (0xC0000005) is the most common crash. The game touched memory it was not allowed to use.
  • GPU crash - STATUS_CRYENGINE_GPU_CRASH. The graphics device failed.
  • DXGI device removed - 0x887A0005 means the GPU device was suspended or removed.
  • DXGI device hung - 0x887A0006 means a GPU command ran too long and Windows reset the card.
  • DXGI device reset - 0x887A0007 means the graphics device reset mid-frame.
  • Out of system memory - STATUS_CRYENGINE_OUT_OF_SYSMEM. The game ran out of virtual memory, even if installed RAM looks free.
  • Engine watchdog - STATUS_CRYENGINE_WATCH_DOG. The engine stopped answering.
  • Fatal engine error - STATUS_CRYENGINE_FATAL_ERROR. A generic engine halt. The line above it names the real trigger.
  • Breakpoint - 2147483651 (0x80000003) is a deliberate stop. It does not name a subsystem.
  • Overlay crash - 3489660927 is commonly reported after a crash to desktop when an overlay is injected.
  • Easy Anti-Cheat - 70xxx codes mean an Easy Anti-Cheat check failed.
  • Launcher process failed - 2000 means the launcher failed while installing, updating, or launching. It is generic.
  • Download failed - 5007 means the download failed because of the connection.
  • P4K file corrupt - 5010 means the game data archives are damaged.
  • Installer exception - 5013 is an installer exception in log.log. RSI has no single confirmed cause.
  • GPU blocked the game - The graphics driver blocked StarCitizen.exe.

Obsidian Squad's own guide, not official Cloud Imperium support. If nothing here helps, the Star Citizen support site and Issue Council are the places to report it.