Tomb Raider (2013) — Common Errors & How to Fix Them

The errors Tomb Raider (2013) players actually hit on PC, what causes each one, and the fix that works.

Last updated 2026-09-25 · evergreen reference

These are the failures that Tomb Raider (2013) players report most often, with the cause behind each one rather than a list of things to try at random.

Errors, causes and fixes

Start from the symptom that matches yours.

Severe frame-rate loss, especially on NVIDIA cards

What is happening: Two AMD-sponsored technologies in the menu: TressFX hair, and "Ultra" ambient occlusion, which is HDAO. Both hit non-AMD hardware hard.

Fix: Set hair to Normal to disable TressFX and set ambient occlusion to Normal rather than Ultra. These two changes are the largest single performance gain available.

Flickering and crashes on SLI or CrossFire

What is happening: Multi-GPU frame pacing plus tessellation.

Fix: Set VSync to Off in the launcher’s advanced settings and disable tessellation.

Crash to desktop and problems minimising the game

What is happening: Exclusive Fullscreen conflicts with "RAM optimiser" and game booster utilities.

Fix: Disable Exclusive Fullscreen and uninstall any RAM optimizer or game booster software — they are bloatware that actively destabilises the game.

Screen looks like broken glass at certain points

What is happening: A High Precision rendering bug that appears intermittently.

Fix: Change the High Precision setting to any other value and apply. The fix must be reapplied each time it appears, and you can set it back afterwards without retriggering it.

Static noise in music and ambient sound

What is happening: Sound card hardware acceleration.

Fix: Update your audio drivers, and in Control Panel > Sound > Audio > Advanced > Performance, set the hardware acceleration slider to None.

Large FPS loss on modern Windows with display scaling

What is happening: Exclusive Fullscreen is not applied correctly when system scaling is not at 100%.

Fix: Disable DPI optimisations for the executable in Compatibility settings, skip the launcher, or revert system scaling to its default.

The order to work in

Cheapest and most reversible first.

1. Rule out the universal causes

Verify game files, update the GPU driver with a clean install, and close overlays, recorders and RGB utilities. Across every engine, these three resolve the largest share of crashes before you touch anything game-specific.

2. Match the fix to the symptom

A crash that happens in the same place every time in Tomb Raider (2013) is usually asset or configuration damage — a cache, a config file or a mod. A crash that happens at random intervals is far more often a driver, an overlay, thermals or unstable memory tuning.

3. Change one thing, then retest

Load the same save, visit the same area and repeat the same action. If you change five settings at once you will never learn which one mattered, and you will end up reinstalling a game that did not need it.

Collecting evidence

What to gather before you ask anyone for help.

Logs beat descriptions

Most engines write a log you can attach: Warframe keeps EE.log in %LOCALAPPDATA%\Warframe, tModLoader writes client.log under Documents\My Games\Terraria\tModLoader\Logs, and Fallout 4 with Buffout 4 writes crash logs to My Games\Fallout4\F4SE. Find the equivalent for Tomb Raider (2013) before you post.

Note the trigger and the timing

Whether it crashes on launch, in a specific area, after a set number of minutes, or only online. That single distinction separates config damage from thermals from network faults, and it is the first thing any support agent will ask.

Related pages

This is an independent player reference and is not official documentation for Tomb Raider (2013). GameRulePro does not host or link to copyrighted assets. Modding guidance is for single-player use only — never use mods in online multiplayer. Verify current requirements, prices and policies with the publisher before acting.

Keep fixing

Related tools from our network

A focused set of free calculators and guides across related topics — no account required.