Famous crash offsets and their meaning

Example crash info:

Version = 1.5.6-release-14664.0.000
Time = Mon Oct  8 12:20:00 2018
Module = C:\Program Files (x86)\Rockstar Games\GTA San Andreas\gta_sa.exe
Code = 0xC0000005
Offset = 0x003C91CC

EAX=0F77A3C8  EBX=0F77A3B8  ECX=0177FAA0  EDX=00139700  ESI=00000000
EDI=00000001  EBP=0177FC50  ESP=0177FA80  EIP=007C91CC  FLG=00210202
CS=0023   DS=002B  SS=002B  ES=002B   FS=0053  GS=002B

(Note: always use the "Offset" value from the crash dialog to identify your crash and match it up with those listed on this wiki page)

Most MTA crashes are caused by something that the user is able to resolve because it depends on their system or game mods. This page seeks to be helpful for the aforementioned reason; you'll know where to look for when you get a certain type of crash.

For further advice on resolving issues, scroll down to the bottom of this page.

Module = gta_sa.exe or proxy_sa.exe

Offset(s)	Meaning
0x00134134	Bad model or corrupted GTA3.img. Use unmodded GTA install to check, or incase of server mods, ask server owner to identify and replace the corrupt mod. Note for server owners and modellers: if you open the crash dump (.dmp) as text with notepad and search for keyword `CEntity_GetBoundRect - No collision for model` you can often identify the bad model ID.
0x00348CF4	Caused by s0beit d3d9.dll
0x003F0C37 0x003F0BF7	Bad vehicle model. Use unmodded GTA install to check, or incase of server mods, ask server owner to identify and replace the corrupt mod.
0x003C91CC 0x003C920C	Out of video memory.
0x003F5A3A	Out of video memory (probably).
0x004A1ED4	Out of system memory (RAM)
0x00137D6E	Out of system memory (RAM). This co-incides with loading collisions; the risk to get this crash is high when joining a mod-heavy server with a weak PC and small amount of memory. To resolve this crash, mind the servers you're playing on (optimization) or get a faster PC. Sub-type of "Running out of memory": most often a direct result of running out of address space, so upgrading to 64-bit Windows installation is also an solution.
0x00171A10	Sometimes when joining a server, maybe related to bad server mods.
0x000C9F98	Possibly bad skin model or texture (clothes mods for multi-clump skins such as CJ). Use unmodded GTA install to check or incase of server mods, ask server owner to identify and disable mods on such skins, or any resource manipulating clothes or ped accesoires.
0x00349B7B	Bad skin model. Use unmodded GTA install to check or incase of server mods, ask server owner to identify and replace the corrupt skin mod. Information for modellers & server owners: corruption in the anim hierarchy in ped's skin DFF or bones configuration
0x00165096	Bad model (containing a corrupt collision model). Use unmodded GTA install to check or incase of server mods, ask server owner to identify and replace the corrupt mod. Information for modellers & server owners: corruption in one or multiple col spheres (or their radius) within the DFF model.
0x000DFE92 0x000DFF90	Bad sound mods or faulty audio driver/device. Use unmodded GTA install to check, or update your audio drivers. The problem is often known to be entirely missing or emptied/corrupted audio files (such as in \Rockstar Games\GTA San Andreas\audio > SFX or other subfolder), so you may alternatively be able to restore a targetted backup. Do not use 'compressed' GTA re-packs for this reason of cut-out audio files.
0x000CFCD6	Allocation failure as a result of (re-)connecting to servers after a lengthy playing session on a server with bad practise in their scripts (abusing RAM and anim functions). This crash may be 'fixed' (averted) by MTA in future, we're working on it! It's related to anims in memory and clearing them.
0x00771848	Crash because of issue with GTA data files (MTA fails to open them which could mean they are corrupted/modded & incompatible or missing) Use unmodded GTA install to check
0x001B6B2F	Crash because of issue with DATA\DEFAULT.DAT or DATA\CARCOLS.DAT file in your GTA installation folder (may be missing or modded/corrupted). Use unmodded GTA install to check
0x003EC9DA	Crash possibly because of issue with ANIM\PED.IFP file in your GTA installation folder (may be missing or modded/corrupted). Use unmodded GTA install to check
0x003F18CF 0x003F190F	Bad model. Use unmodded GTA install to check or in case of server mods, ask server owner to identify and replace the corrupt mod. This crash has been averted (fixed by MTA), but due to technical limitations will still occur for Windows XP users. Information for modellers & server owners: due to the nature of corruption, the model introduces a risk to crash, it could happen at any given moment while nearby.
0x0000F67C 0x0000F663	Custom models which are not working with volumetric shadows. Fix models or disable volumetric shadows in Settings->Video.

Resolving out-of-memory crashes

If you're experiencing crashes that, according to the table of common crashes, are related to any sort of running out of memory, then we advise you to;

- Mind the type of servers you're playing on, especially in combination with how powerful your PC is. There's lots of bloated, mod-heavy servers out there in MTA that demand the better of your PC and may also abuse memory through inefficient scripts besides custom mods (or even with the lack thereof). If you have a slow or older generation PC, then we advise you to avoid certain "fancy" servers with huge resource downloads and such.

- Install 64-bits version of Windows rather than x86 (32-bit)

If you still want to play on servers that may easily get upper hand on your system, then;

- Upgrade your PC's hardware for enhanced performance; consider replacing the videocard with one suitable for gaming, or adding additional system memory (RAM). Re-installing Windows can sometimes also help a bunch if your OS in general is slow and not well-maintained. Alternatively, perform some mainentance (consult someone with tech experience, or make a start by updating drivers and running various junk cleaners & renowned PC performance optimization tools)

- Follow the instructions listed at https://forum.mtasa.com/topic/78081-32-bit-windows-crashing/

- Remove any mods to your GTA installation (preferably re-install) because mods may take up video memory and RAM, enough to cause your high memory usage and subsequent crashes. Also you should definately try lowering streaming memory, by going into Settings->Advanced->Streaming memory-> and setting it to Min.

Resolving crashes related to custom models

If you're experiencing crashes that, according to the table of common crashes, are related to corrupt custom models, then we advise you to re-install GTA from the original game source (DVD or Steam, so no pre-modded repacks) or restore targetted file back-ups in case you understand which (type of) model may cause the crash. Incase you're only experiencing the crashes while playing on a certain server, there's a high chance that server is loading custom server models, in which case we recommend you to contact the server owner so they can investigate and potentially isolate & replace the corrupted model to stop the crashes. Until they take successful action, on that server you can try to avoid physically facing the mod you believe results in a crash (like not spawning said vehicle or using said skin). Let us remind you of the chance that the bad model is in your GTA3.img, but by coincidence you never physically come near that model on other servers, and the server you're crashing the most on happens to force usage of that model ID upon you (like as regularly used vehicle or skin); therefore it cannot be ruled out that it's possibly still your client mod, despite you only crashing on a single server.

If you are a server owner and wouldn't prefer letting go of your beloved (corrupt) model, then you can ask an experienced modeller to try fix the corruption by modifying/revising it. The alternative of crashing many players, potentially resulting in player loss for your server, isn't fine either way. For this reason, keeping a sharp eye on trends of players reporting (or shouting) that they crashed, and following up with them to get the crash details (to try match them up to model crashes from the table on this wiki page), may be a good idea.