MTA: San Andreas
MTA:SA crash codes and offsets
A crash code says what kind of failure happened, not why. These steps are what narrows a crash down.
What to do
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.
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.
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.
Update the graphics driver, then MTA
Install the current driver from your graphics card maker, then the current MTA from multitheftauto.com.
MTA crashes, freezes or closes unexpectedly: the full guide →
Still not fixed? Copy the whole message, not only the code, and check your log in the Fix tool. It is read on your own computer.
Nothing matches that. Try fewer letters, or only the code.
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.
| Code | Kind of failure | Name in MTA's source |
|---|---|---|
0xC0000005 | Access Violation: Invalid memory access | EXCEPTION_ACCESS_VIOLATION |
0xC000008C | Array Bounds Exceeded | EXCEPTION_ARRAY_BOUNDS_EXCEEDED |
0x80000003 | Breakpoint Hit | EXCEPTION_BREAKPOINT |
0x80000002 | Data Type Misalignment | EXCEPTION_DATATYPE_MISALIGNMENT |
0xC000008D | Floating Point: Denormal Operand | EXCEPTION_FLT_DENORMAL_OPERAND |
0xC000008E | Floating Point: Divide by Zero | EXCEPTION_FLT_DIVIDE_BY_ZERO |
0xC000008F | Floating Point: Inexact Result | EXCEPTION_FLT_INEXACT_RESULT |
0xC0000090 | Floating Point: Invalid Operation | EXCEPTION_FLT_INVALID_OPERATION |
0xC0000091 | Floating Point: Overflow | EXCEPTION_FLT_OVERFLOW |
0xC0000092 | Floating Point: Stack Check | EXCEPTION_FLT_STACK_CHECK |
0xC0000093 | Floating Point: Underflow | EXCEPTION_FLT_UNDERFLOW |
0xC000001D | Illegal Instruction | EXCEPTION_ILLEGAL_INSTRUCTION |
0xC0000006 | In Page Error: Page fault | EXCEPTION_IN_PAGE_ERROR |
0xC0000094 | Integer Divide by Zero | EXCEPTION_INT_DIVIDE_BY_ZERO |
0xC0000095 | Integer Overflow | EXCEPTION_INT_OVERFLOW |
0xC0000026 | Invalid Disposition | EXCEPTION_INVALID_DISPOSITION |
0xC0000025 | Non-Continuable Exception | EXCEPTION_NONCONTINUABLE_EXCEPTION |
0xC0000096 | Privileged Instruction | EXCEPTION_PRIV_INSTRUCTION |
0x80000004 | Single Step (Debugging) | EXCEPTION_SINGLE_STEP |
0xC00000FD | Stack Overflow | EXCEPTION_STACK_OVERFLOW |
0x80000001 | Guard Page Violation | EXCEPTION_GUARD_PAGE |
0xC0000008 | Invalid Handle | EXCEPTION_INVALID_HANDLE |
0xE06D7363 | C++ Exception | CPP_EXCEPTION_CODE |
0xC0000409 | Fail-fast / security termination | STATUS_STACK_BUFFER_OVERRUN_CODE |
0xC0000417 | Invalid C Runtime Parameter | STATUS_INVALID_CRUNTIME_PARAMETER_CODE |
0xC000041D | Fatal Exception in Windows Callback: Callback Exception Unhandled | STATUS_FATAL_USER_CALLBACK_EXCEPTION |
0xE03B10C0 | Out of Memory: Allocation Failure | CUSTOM_EXCEPTION_CODE_OOM |
0xE0000001 | Watchdog Timeout: Thread Freeze Detected | CUSTOM_EXCEPTION_CODE_WATCHDOG_TIMEOUT |
0xC0000374 | Heap Corruption Detected | STATUS_HEAP_CORRUPTION_CODE |
0xC0000420 | Assertion Failure | — |
0x40000015 | Fatal App Exit | — |
0xC00002C9 | Register NaT Consumption | — |
0xC0000194 | Possible Deadlock Condition | — |
0x80000029 | Unwind 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.
| Offset | Seen with | Seen in |
|---|---|---|
0x0000F64C | Custom model/shadow compatibility lead | module not recorded |
0x0000F663 | Custom model/shadow compatibility lead | gta_sa.exe, proxy_sa.exe |
0x0000F67C | Custom model/shadow compatibility lead | gta_sa.exe, proxy_sa.exe |
0x00016135 | Unverified build-specific localization claimunverified | module not recorded |
0x000193E6 | No cause explanation is published for this entry. | module not recorded |
0x0006A1E6 | Unverified build-specific cleanup claimunverified | module not recorded |
0x000A2CF3 | effects.fxp lead | gta_sa.exe, proxy_sa.exe |
0x000C9691 | Vehicle asset lead | gta_sa.exe, proxy_sa.exe |
0x000C9F98 | Skin/texture hypothesis | gta_sa.exe, proxy_sa.exe |
0x000CFCD6 | Animation allocation lead | gta_sa.exe, proxy_sa.exe |
0x000D68BA | Old water-script issue association | module not recorded |
0x000D7BD6 | Audio files, driver or device alternatives | module not recorded |
0x000DFE92 | Audio files, driver or device alternatives | gta_sa.exe, proxy_sa.exe |
0x000DFF90 | Audio files, driver or device alternatives | gta_sa.exe, proxy_sa.exe |
0x000E7ED0 | No cause explanation is published for this entry. | module not recorded |
0x000F0EBA | No cause explanation is published for this entry. | module not recorded |
0x0013388E | No cause explanation is published for this entry. | module not recorded |
0x00134134 | Model/collision lead | gta_sa.exe, proxy_sa.exe |
0x00137D6E | Allocation/address-space lead | gta_sa.exe, proxy_sa.exe |
0x0014F3B6 | Allocation/address-space lead | module not recorded |
0x0014F406 | Allocation/address-space lead | gta_sa.exe, proxy_sa.exe |
0x00165096 | Collision-data lead | gta_sa.exe, proxy_sa.exe |
0x00171A10 | Join-time asset hypothesis | gta_sa.exe, proxy_sa.exe |
0x0019BD39 | Nearby model during weapon use | gta_sa.exe, proxy_sa.exe |
0x001A49D4 | player.img/clothes lead | gta_sa.exe, proxy_sa.exe |
0x001B6B2F | DEFAULT.DAT/CARCOLS.DAT lead | gta_sa.exe, proxy_sa.exe |
0x001CD9AA | Unverified libcef ZIP claimunverified | module not recorded |
0x001D6E6A | Allocation or asset alternatives | gta_sa.exe, proxy_sa.exe |
0x001E26EE | Ped/object collision hypothesis | module not recorded |
0x002FE144 | Roadsign initialization hypothesis | module not recorded |
0x002FEC20 | Roadsign raster hypothesis | module not recorded |
0x0032F4DE | Memory allocation lead; domain or cause not proven | module not recorded |
0x00330D1F | Memory allocation lead; domain or cause not proven | module not recorded |
0x00332B2A | Old ped-health script reproduction | module not recorded |
0x00348CF4 | Game-folder D3D9 modification association; no accusation | gta_sa.exe, proxy_sa.exe |
0x00349B7B | Skin hierarchy lead | gta_sa.exe, proxy_sa.exe |
0x0034E85A | No cause explanation is published for this entry. | module not recorded |
0x003507FB | No cause explanation is published for this entry. | module not recorded |
0x00354B1C | No cause explanation is published for this entry. | module not recorded |
0x00357DEC | Memory allocation lead; domain or cause not proven | gta_sa.exe, proxy_sa.exe |
0x003C91CC | Graphics allocation lead | gta_sa.exe, proxy_sa.exe |
0x003C920C | Graphics allocation lead | gta_sa.exe, proxy_sa.exe |
0x003EC9DA | PED.IFP hypothesis | gta_sa.exe, proxy_sa.exe |
0x003F0BF7 | Vehicle asset lead | gta_sa.exe, proxy_sa.exe |
0x003F0C37 | Vehicle asset lead | gta_sa.exe, proxy_sa.exe |
0x003F18CF | Model lead | gta_sa.exe, proxy_sa.exe |
0x003F190F | Model lead | gta_sa.exe, proxy_sa.exe |
0x003F3A17 | Unverified CEF/SVG claimunverified | module not recorded |
0x003F5A3A | Memory allocation lead; domain or cause not proven | gta_sa.exe, proxy_sa.exe |
0x00423FD0 | GTA archive integrity lead | gta_sa.exe, proxy_sa.exe |
0x004A1ED4 | Memory allocation lead; domain or cause not proven | gta_sa.exe, proxy_sa.exe |
0x00771848 | Game data access lead | gta_sa.exe, proxy_sa.exe |
0x00BFFFFF | Collision-data lead | module not recorded |
0x01162FE3 | Collision-data lead | gta_sa.exe, proxy_sa.exe |
0x011630F2 | Collision-data lead | gta_sa.exe, proxy_sa.exe |
0x011630F8 | Collision-data lead | gta_sa.exe, proxy_sa.exe |
0x011630FE | Collision-data lead | gta_sa.exe, proxy_sa.exe |
Values shown with a connection timeout
These values appear with MTA's connection timeout message, not with a crash.
| Value | What the official page says about it |
|---|---|
00070000 | Possible malware-activity category. |
0A050000 | Possible malware-activity category. |
FF0B0000 | MTA update-guidance category; a distinct cause is unspecified. |
FF0B0121 | MTA update-guidance category; a distinct cause is unspecified. |
03040033 | Software 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. |
All fix guides · Every MTA:SA error code · CD08, connection timed out
Where this comes from
Every offset is a lead, in the same careful wording as its source. None of them is a proven cause, and a few are marked unverified.
- wiki.multitheftauto.com/wiki/Famous_crash_offsets_and_their_meaning
- wiki.multitheftauto.com/wiki/GTA_Crash_Codes
- help.multitheftauto.com/sa/trouble/connect-timed-out/
Read on 5 September 2026 and written in our own words here.