Is This Game Down
Error codes

Escape from Tarkov 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.

13 pages · last checked October 23, 2026

Things you can fix

Crashes, install faults and driver conflicts. Find your symptom, work the steps in order, stop when it launches.

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.

0Confirmed

Escape from Tarkov error 0: "no game with name eft" (fix)

The BSG Launcher or game refuses to start and shows a bare "Error: 0" dialog, often paired with the text 'There is no game with name "eft" Parameter name: game'.

614Reported

Escape from Tarkov error 614: "Matching is disabled"

Pressing Play or start matching shows "One or more errors occurred. 614 - Matching is disable..." straight away and every time. Restarting the launcher and the game doesn't change it.

213Confirmed

Escape from Tarkov error 213: auth server timeout (fix)

Launching the game or logging into the BSG Launcher fails with "Error 213", sometimes alongside error 0 in the same session.

1000Reported

Escape from Tarkov error 1000 (backend error): fix

A "1000 - Backend error" dialog interrupts login, a raid, or extraction, sometimes with the added line "Some error occurred on the backend, profile data could not be saved."

PROFILE-DATA-NOT-SAVEDReported

Escape from Tarkov "profile data not saved" error (fix)

After extracting or ending a raid, a dialog reads "Some error occurred on the backend, profile data could not be saved" — and the loot or progress from that raid doesn't show up afterward.

INVALID-MATCHMAKING-OPERATIONReported

Escape from Tarkov PvE "invalid matchmaking operation" (co-op)

In PvE co-op, joining a raid as a party member kicks you out of matchmaking or crashes the game, sometimes with "invalid matchmaking operation".

USER-ACTION-REQUIREDReported

Escape from Tarkov "User action required" error (fix)

The launcher or game stops with "User action required", either while the servers are down for maintenance or after the game crashes with "It appears the game has terminated with an error, do you wish to report it".

MATCHMAKING-ERRORS-OCCURREDReported

Escape from Tarkov "errors occurred during matchmaking"

Queuing for a raid hangs or kicks you back with "One or more errors occurred during matchmaking", sometimes freezing the PC or taking around 10 minutes to close.

CRASH-ON-CLOSEReported

Escape from Tarkov crash on exit: Windows restarts (BattlEye)

Closing Escape from Tarkov (or a failed raid load) is followed within seconds by a black Windows screen with a fatal-error message and an automatic restart. Some players only see the game itself crash.

AMBIGUOUS-MATCH-FOUNDReported

Escape from Tarkov PvE "EFT.MongoID Ambiguous match found" error

PvE will not load your existing character, or fails while loading into PvE, with "Error converting value "" to type 'EFT.MongoID'. Path '[1].Customization.Voice'. Ambiguous match found." PvP still works.

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.

Other games we track

← Back to Escape from Tarkov status