The Last of Us Part I PC Errors

The Last of Us Part I's PC port is single-player, so its errors are crashes rather than server codes — the 0xc0000005 access-violation crash on launch, freezes and crashes during the long first-run shader compilation, crashes from a corrupted cloud save, and out-of-memory crashes when VRAM runs out on high presets. Almost all trace back to drivers, corrupt files, or graphics settings. Here's what each means and the fastest fix.

Error codes

0xc0000005 (access violation) on launch The game tried to access protected memory and was closed by Windows

Cause: An unstable/outdated GPU driver, corrupt game files, an overclock, or an overlay/anti-cheat conflict at startup.

Fix:
  1. Clean-install the latest GPU driver with DDU and install the latest Visual C++ Redistributables (x86 and x64).
  2. Verify integrity of the game files in Steam/Epic to replace corrupted data.
  3. Remove any GPU/CPU/RAM overclock and disable overlays (Steam, Discord, GeForce Experience), then relaunch.
Crash during shader compilation / 'Building shaders' The game hangs or crashes during the one-time shader-build step

Cause: Outdated drivers, insufficient VRAM, or a corrupt shader cache interrupting the build.

Fix:
  1. Update your GPU driver and let 'Building shaders' finish without alt-tabbing — it can take many minutes.
  2. Lower the graphics preset from Ultra to High to reduce VRAM pressure during compilation.
  3. If it keeps crashing at the same percent, verify the game files or delete the shader cache and let it rebuild.
Crash from a corrupted save The game crashes on load because the save/cloud data is corrupt

Cause: A bad Steam Cloud sync or a corrupted local save file.

Fix:
  1. Disable Steam Cloud for the game, then delete the local save/storage folder (back it up first — this clears progress).
  2. Relaunch so the game rebuilds a clean save, then re-enable Cloud once stable.
  3. Verify the game files afterward to confirm nothing else is damaged.
Out-of-memory / VRAM crash The game runs out of video memory and crashes, often after minutes of play

Cause: Texture/preset settings exceeding your card's VRAM, especially at higher resolutions.

Fix:
  1. Lower Texture Quality and overall preset until the VRAM meter in Settings stays below your card's limit.
  2. Cap the frame rate and disable other GPU-hungry apps to free VRAM.
  3. Update to the latest game patch — several fixes reduced VRAM use over time.

Fixes that work for most The Last of Us Part I (PC — Steam, Epic) errors

  1. Verify/repair the game files (Steam: Properties -> Installed Files -> Verify integrity; Ubisoft Connect/Epic: Manage -> Verify files) — this replaces corrupted files behind most crashes and connection faults.
  2. Update your GPU driver with a clean install (use DDU), and install the latest Microsoft Visual C++ Redistributables (x86 and x64) plus the DirectX End-User Runtime — missing runtimes and stale drivers cause most launch crashes.
  3. Flush your DNS and reset the network stack (ipconfig /flushdns; netsh winsock reset; netsh int ip reset), switch to Google (8.8.8.8) or Cloudflare (1.1.1.1) DNS, and prefer a wired connection over Wi-Fi to cut packet loss.
  4. Disable overlays (Steam, Discord, GeForce Experience) and any VPN, and add the game to your firewall and antivirus exceptions.
  5. Check the game's official server/status channels (X, Discord, Downdetector) before assuming a local problem — many named connection errors are a maintenance window or outage and clear on their own.

FAQ

How do I fix error 0xc0000005 in The Last of Us Part I?

0xc0000005 is an access-violation crash where the game touched protected memory and Windows closed it, usually from an unstable or outdated GPU driver, corrupt files, an overclock, or an overlay conflict. Clean-install the latest GPU driver with DDU, install the latest Visual C++ Redistributables, verify the integrity of the game files, remove any overclock, and disable overlays like Steam, Discord and GeForce Experience before relaunching.

Why does The Last of Us Part I crash during shader compilation?

The one-time 'Building shaders' step can hang or crash if your GPU driver is outdated, VRAM is tight, or the shader cache is corrupt. Update your driver and let it finish without alt-tabbing (it can take many minutes), lower the preset from Ultra to High to ease VRAM pressure, and if it crashes at the same percentage each time, verify the game files or delete the shader cache so it rebuilds cleanly.

Other games