CITMTA & CIT FixCIT Tools

MTA: San Andreas

MTA:SA crash codes and offsets

When MTA closes with a crash message it shows a version, a module, an offset and an exception code. Two of those are worth looking up, and both of them describe the kind of failure rather than the reason for it. This page lists every exception code and offset the Fix tool knows, in the same careful wording as its sources.

The exception code

The exception code is a Windows value that says what sort of failure happened. 0xC0000005, an access violation, covers most game crashes and appears for dozens of unrelated causes. Use it to confirm the kind of crash, not to find the cause.

Every one of these describes a kind of failure. None of them names a cause, and there is no fix that belongs to a code on its own: what narrows a crash down is the module, the offset and what you were doing when it happened.

CodeKind of failureName in MTA's source
0xC0000005Access Violation: Invalid memory accessEXCEPTION_ACCESS_VIOLATION
0xC000008CArray Bounds ExceededEXCEPTION_ARRAY_BOUNDS_EXCEEDED
0x80000003Breakpoint HitEXCEPTION_BREAKPOINT
0x80000002Data Type MisalignmentEXCEPTION_DATATYPE_MISALIGNMENT
0xC000008DFloating Point: Denormal OperandEXCEPTION_FLT_DENORMAL_OPERAND
0xC000008EFloating Point: Divide by ZeroEXCEPTION_FLT_DIVIDE_BY_ZERO
0xC000008FFloating Point: Inexact ResultEXCEPTION_FLT_INEXACT_RESULT
0xC0000090Floating Point: Invalid OperationEXCEPTION_FLT_INVALID_OPERATION
0xC0000091Floating Point: OverflowEXCEPTION_FLT_OVERFLOW
0xC0000092Floating Point: Stack CheckEXCEPTION_FLT_STACK_CHECK
0xC0000093Floating Point: UnderflowEXCEPTION_FLT_UNDERFLOW
0xC000001DIllegal InstructionEXCEPTION_ILLEGAL_INSTRUCTION
0xC0000006In Page Error: Page faultEXCEPTION_IN_PAGE_ERROR
0xC0000094Integer Divide by ZeroEXCEPTION_INT_DIVIDE_BY_ZERO
0xC0000095Integer OverflowEXCEPTION_INT_OVERFLOW
0xC0000026Invalid DispositionEXCEPTION_INVALID_DISPOSITION
0xC0000025Non-Continuable ExceptionEXCEPTION_NONCONTINUABLE_EXCEPTION
0xC0000096Privileged InstructionEXCEPTION_PRIV_INSTRUCTION
0x80000004Single Step (Debugging)EXCEPTION_SINGLE_STEP
0xC00000FDStack OverflowEXCEPTION_STACK_OVERFLOW
0x80000001Guard Page ViolationEXCEPTION_GUARD_PAGE
0xC0000008Invalid HandleEXCEPTION_INVALID_HANDLE
0xE06D7363C++ ExceptionCPP_EXCEPTION_CODE
0xC0000409Fail-fast / security terminationSTATUS_STACK_BUFFER_OVERRUN_CODE
0xC0000417Invalid C Runtime ParameterSTATUS_INVALID_CRUNTIME_PARAMETER_CODE
0xC000041DFatal Exception in Windows Callback: Callback Exception UnhandledSTATUS_FATAL_USER_CALLBACK_EXCEPTION
0xE03B10C0Out of Memory: Allocation FailureCUSTOM_EXCEPTION_CODE_OOM
0xE0000001Watchdog Timeout: Thread Freeze DetectedCUSTOM_EXCEPTION_CODE_WATCHDOG_TIMEOUT
0xC0000374Heap Corruption DetectedSTATUS_HEAP_CORRUPTION_CODE
0xC0000420Assertion Failure—
0x40000015Fatal App Exit—
0xC00002C9Register NaT Consumption—
0xC0000194Possible Deadlock Condition—
0x80000029Unwind Consolidate (Frame consolidation)—

The offset

The offset is the place in the program where it stopped. MTA's community keeps a list of offsets that have been seen often, with the thing each one was associated with at the time. Those are leads, not diagnoses: the same offset appears for different reasons, and an offset alone has never been a proof of cause.

Read an offset as a lead

Every line below is kept as a reference, in the same careful wording as its source. None of them is a proven cause, several offsets have no published explanation at all, and a few are marked unverified because the claim behind them was never established.

OffsetAssociated withSeen in
0x0000F64CCustom model/shadow compatibility leadmodule not recorded
0x0000F663Custom model/shadow compatibility leadgta_sa.exe, proxy_sa.exe
0x0000F67CCustom model/shadow compatibility leadgta_sa.exe, proxy_sa.exe
0x00016135Unverified build-specific localization claimunverifiedmodule not recorded
0x000193E6No cause explanation is published for this entry.module not recorded
0x0006A1E6Unverified build-specific cleanup claimunverifiedmodule not recorded
0x000A2CF3effects.fxp leadgta_sa.exe, proxy_sa.exe
0x000C9691Vehicle asset leadgta_sa.exe, proxy_sa.exe
0x000C9F98Skin/texture hypothesisgta_sa.exe, proxy_sa.exe
0x000CFCD6Animation allocation leadgta_sa.exe, proxy_sa.exe
0x000D68BAOld water-script issue associationmodule not recorded
0x000D7BD6Audio files, driver or device alternativesmodule not recorded
0x000DFE92Audio files, driver or device alternativesgta_sa.exe, proxy_sa.exe
0x000DFF90Audio files, driver or device alternativesgta_sa.exe, proxy_sa.exe
0x000E7ED0No cause explanation is published for this entry.module not recorded
0x000F0EBANo cause explanation is published for this entry.module not recorded
0x0013388ENo cause explanation is published for this entry.module not recorded
0x00134134Model/collision leadgta_sa.exe, proxy_sa.exe
0x00137D6EAllocation/address-space leadgta_sa.exe, proxy_sa.exe
0x0014F3B6Allocation/address-space leadmodule not recorded
0x0014F406Allocation/address-space leadgta_sa.exe, proxy_sa.exe
0x00165096Collision-data leadgta_sa.exe, proxy_sa.exe
0x00171A10Join-time asset hypothesisgta_sa.exe, proxy_sa.exe
0x0019BD39Nearby model during weapon usegta_sa.exe, proxy_sa.exe
0x001A49D4player.img/clothes leadgta_sa.exe, proxy_sa.exe
0x001B6B2FDEFAULT.DAT/CARCOLS.DAT leadgta_sa.exe, proxy_sa.exe
0x001CD9AAUnverified libcef ZIP claimunverifiedmodule not recorded
0x001D6E6AAllocation or asset alternativesgta_sa.exe, proxy_sa.exe
0x001E26EEPed/object collision hypothesismodule not recorded
0x002FE144Roadsign initialization hypothesismodule not recorded
0x002FEC20Roadsign raster hypothesismodule not recorded
0x0032F4DEMemory allocation lead; domain or cause not provenmodule not recorded
0x00330D1FMemory allocation lead; domain or cause not provenmodule not recorded
0x00332B2AOld ped-health script reproductionmodule not recorded
0x00348CF4Game-folder D3D9 modification association; no accusationgta_sa.exe, proxy_sa.exe
0x00349B7BSkin hierarchy leadgta_sa.exe, proxy_sa.exe
0x0034E85ANo cause explanation is published for this entry.module not recorded
0x003507FBNo cause explanation is published for this entry.module not recorded
0x00354B1CNo cause explanation is published for this entry.module not recorded
0x00357DECMemory allocation lead; domain or cause not provengta_sa.exe, proxy_sa.exe
0x003C91CCGraphics allocation leadgta_sa.exe, proxy_sa.exe
0x003C920CGraphics allocation leadgta_sa.exe, proxy_sa.exe
0x003EC9DAPED.IFP hypothesisgta_sa.exe, proxy_sa.exe
0x003F0BF7Vehicle asset leadgta_sa.exe, proxy_sa.exe
0x003F0C37Vehicle asset leadgta_sa.exe, proxy_sa.exe
0x003F18CFModel leadgta_sa.exe, proxy_sa.exe
0x003F190FModel leadgta_sa.exe, proxy_sa.exe
0x003F3A17Unverified CEF/SVG claimunverifiedmodule not recorded
0x003F5A3AMemory allocation lead; domain or cause not provengta_sa.exe, proxy_sa.exe
0x00423FD0GTA archive integrity leadgta_sa.exe, proxy_sa.exe
0x004A1ED4Memory allocation lead; domain or cause not provengta_sa.exe, proxy_sa.exe
0x00771848Game data access leadgta_sa.exe, proxy_sa.exe
0x00BFFFFFCollision-data leadmodule not recorded
0x01162FE3Collision-data leadgta_sa.exe, proxy_sa.exe
0x011630F2Collision-data leadgta_sa.exe, proxy_sa.exe
0x011630F8Collision-data leadgta_sa.exe, proxy_sa.exe
0x011630FECollision-data leadgta_sa.exe, proxy_sa.exe

What actually narrows a crash down

  1. Keep the whole crash message

    The version, module, offset and exception code together are worth far more than any one of them. Copy all of it before you close the window.

  2. Note what you were doing

    A crash that happens at the same place every time is the easy kind. Write down where you were, what you were driving, wearing or shooting, and whether it repeats.

  3. Play with a clean GTA folder

    Mods in the game folder are the most common cause of repeated crashes. Move .asi files, d3d9.dll and modded archives aside and try again.

  4. Update the graphics driver, then MTA

    Install the current driver from your graphics card maker, then the current MTA from multitheftauto.com.

  5. Check the log on this site

    The Fix tool reads MTA's core.log on your own computer and points at the entries that matter.

Values shown with a connection timeout

These hexadecimal values appear with MTA's connection timeout message, not with a crash. A number that looks like one of these in a crash window is an address, not one of these values.

ValueWhat the official page associates with it
00070000Possible malware-activity category.
0A050000Possible malware-activity category.
FF0B0000MTA update-guidance category; a distinct cause is unspecified.
FF0B0121MTA update-guidance category; a distinct cause is unspecified.
03040033Software interference attributed to Evolve.
4D0?????Audio-library repair guidance category; a distinct cause is unspecified.
4E0?????Audio-library repair guidance category; a distinct cause is unspecified.
4F0?????Audio-library repair guidance category; a distinct cause is unspecified.

Still stuck? The Fix tool reads MTA's own log on your computer and points at the matching steps. Nothing is uploaded.

Open the Fix tool

Every MTA:SA error code · CD08, connection timed out

Where this comes from

Meanings read from these sources on 5 September 2026 and written in our own words here.