Multi Theft Auto: Wiki - User contributions [en]

Famous crash offsets and their meaning

2020-04-19T07:27:22Z

Tut: adding an explanation to vehicle-upgrade crashes

Example crash info:
<syntaxhighlight lang="xml">
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
</syntaxhighlight>

(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==
{| class="wikitable"
|-
!Offset(s)
!Meaning
|-
|<syntaxhighlight lang="lua">0x00134134</syntaxhighlight>
|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.
|-
|<syntaxhighlight lang="lua">0x00348CF4</syntaxhighlight>
|Caused by s0beit d3d9.dll
|-
|<syntaxhighlight lang="lua">
0x003F0C37
0x003F0BF7
</syntaxhighlight>
|Bad vehicle model. Use unmodded GTA install to check, or incase of server mods, ask server owner to identify and replace the corrupt mod.
|-
|<syntaxhighlight lang="lua">
0x003C91CC
0x003C920C
</syntaxhighlight>
|Out of video memory.
|-
|-
|<syntaxhighlight lang="lua">0x003F5A3A</syntaxhighlight>
|Out of video memory (probably).
|-
|-
|<syntaxhighlight lang="lua">0x004A1ED4</syntaxhighlight>
|Out of system memory (RAM)
|-
|-
|-
|<syntaxhighlight lang="lua">0x00137D6E</syntaxhighlight>
|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.
|-
|<syntaxhighlight lang="lua">0x00171A10</syntaxhighlight>
|Sometimes when joining a server, maybe related to bad server mods.
|-
|-
|<syntaxhighlight lang="lua">0x000C9F98</syntaxhighlight>
|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.
|-
|-
|<syntaxhighlight lang="lua">0x00349B7B</syntaxhighlight>
|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
|-
|-
|<syntaxhighlight lang="lua">0x00165096</syntaxhighlight>
|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.
|-
|-
|<syntaxhighlight lang="lua">
0x000DFE92
0x000DFF90
</syntaxhighlight>
|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.
|-
|-
|-
|<syntaxhighlight lang="lua">0x000CFCD6</syntaxhighlight>
|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.
|-
|-
|<syntaxhighlight lang="lua">
0x00771848
</syntaxhighlight>
|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
|-
|<syntaxhighlight lang="lua">
0x001B6B2F
</syntaxhighlight>
|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
|-
|<syntaxhighlight lang="lua">
0x003EC9DA
</syntaxhighlight>
|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
|-
|-
|-
|<syntaxhighlight lang="lua">
0x003F18CF
0x003F190F
</syntaxhighlight>
|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.
|-
|<syntaxhighlight lang="lua">
0x000C9691
</syntaxhighlight>
|Bad or missing vehicle model. This usually happens when you deleted a model from your GTA3.img without restoring the original or putting another model in its place. Or when the DFF isn't a valid model file at all.
Restore GTA3.img or use unmodded GTA install to check, and if that doesn't work then ask server owner to identify and replace the corrupt mod, since it can also still be a bad model (or a dodgy script, that, tell them this: deals with vehicle types, variants, upgrades etc, in an improper way)
|-
|<syntaxhighlight lang="lua">
0x0000F67C
0x0000F663
</syntaxhighlight>
|Custom models which are not working with volumetric shadows. Fix models or disable volumetric shadows in Settings->Video.
|-
|<syntaxhighlight lang="lua">
0x001A49D4
</syntaxhighlight>
|Bad mod (custom player.img in GTA San Andreas\models). Restore player.img to original or use unmodded GTA.
Note: this crash can also be triggered when a player with CJ model (or CJ clothes) appears on your screen, on a server you're playing on. Your custom player.img cannot handle that and will cause a crash.
|}

==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).

We could write a book about the real cause (which is that such servers have bad scripters, or those that don't know what optimization is, and that they add everything, including bloated models and textures, without reviewing it) but we won't do that here.

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/ 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.

Please note that in general, '''any crash''' with exception code '''0xE06D7363''' (on an MTA module, and not gta_sa.exe like this wiki page is focussed on) is also a memory-related issue, and comes back to the memory abuse by servers and mods described above.

==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.

In case you're only experiencing the crashes while playing on a certain server, there's a high chance that server is loading custom server models, and then we recommend you to contact the server owner so they can investigate and potentially identify & 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, and it's worth at least re-installing your GTA to try it out.

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.

Adding upgradable components (named "ug_upgradename") outside of chassis_dummy, will cause crashes once the vehicle has the respective upgrade component spawned.

User:Tut

2019-11-09T06:29:17Z

Tut:

User:Tut

2019-11-09T06:19:09Z

Tut: /* 2DFX - Particles */

User:Tut

2019-11-09T06:16:39Z

Tut: /* 2DFX - Particles */

User:Tut

2019-11-09T06:14:38Z

Tut: /* 2DFX - Particles */

User:Tut

2019-11-09T06:13:30Z

Tut: /* 2DFX - Particles */

User:Tut

2019-11-09T06:13:09Z

Tut: /* 2DFX - Particles */

User:Tut

2019-11-09T06:09:18Z

Tut: /* 2DFX - Particles */

User:Tut

2019-11-09T06:07:46Z

Tut:

User:Tut

2019-11-09T06:05:22Z

Tut:

File:2DFX gunflash.png

2019-11-09T05:53:52Z

Tut:

File:2DFX ws factorysmoke.png

2019-11-09T05:45:56Z

Tut:

File:2DFX waterfall end.png

2019-11-09T05:45:49Z

Tut:

File:2DFX water swim.png

2019-11-09T05:45:41Z

Tut:

File:2DFX water splsh sml.png

2019-11-09T05:45:33Z

Tut:

File:2DFX water splash big.png

2019-11-09T05:45:25Z

Tut:

File:2DFX water splash.png

2019-11-09T05:45:07Z

Tut:

File:2DFX water speed.png

2019-11-09T05:44:57Z

Tut:

File:2DFX water ripples.png

2019-11-09T05:44:47Z

Tut:

File:2DFX water hydrant.png

2019-11-09T05:44:37Z

Tut:

File:2DFX water fountain.png

2019-11-09T05:44:29Z

Tut:

File:2DFX water fnt tme.png

2019-11-09T05:44:17Z

Tut:

File:2DFX wallbust.png

2019-11-09T05:44:05Z

Tut:

File:2DFX vent2.png

2019-11-09T05:43:56Z

Tut:

File:2DFX vent.png

2019-11-09T05:43:44Z

Tut:

File:2DFX tree hit palm.png

2019-11-09T05:43:33Z

Tut:

File:2DFX tree hit fir.png

2019-11-09T05:43:22Z

Tut:

File:2DFX teargasAD.png

2019-11-09T05:43:09Z

Tut:

File:2DFX teargas.png

2019-11-09T05:42:54Z

Tut:

File:2DFX tank fire.png

2019-11-09T05:42:39Z

Tut:

File:2DFX spraycan.png

2019-11-09T05:42:26Z

Tut:

File:2DFX smoke50lit.png

2019-11-09T05:42:17Z

Tut:

File:2DFX smoke30m.png

2019-11-09T05:42:05Z

Tut:

File:2DFX smoke30lit.png

2019-11-09T05:41:54Z

Tut:

File:2DFX smoke flare.png

2019-11-09T05:41:45Z

Tut:

File:2DFX shootlight.png

2019-11-09T05:41:35Z

Tut:

File:2DFX riot smoke.png

2019-11-09T05:41:23Z

Tut:

File:2DFX puke.png

2019-11-09T05:41:01Z

Tut:

File:2DFX prt wheeldirt.png

2019-11-09T05:40:41Z

Tut:

File:2DFX prt watersplash.png

2019-11-09T05:40:29Z

Tut:

File:2DFX prt wake.png

2019-11-09T05:40:08Z

Tut:

File:2DFX prt splash.png

2019-11-09T05:39:57Z

Tut:

File:2DFX prt spark 2.png

2019-11-09T05:39:47Z

Tut:

File:2DFX prt spark.png

2019-11-09T05:39:31Z

Tut:

File:2DFX prt smokeII 3 expand.png

2019-11-09T05:39:18Z

Tut:

File:2DFX prt smoke huge.png

2019-11-09T05:39:09Z

Tut:

File:2DFX prt sand2.png

2019-11-09T05:38:59Z

Tut:

File:2DFX prt sand.png

2019-11-09T05:38:50Z

Tut:

File:2DFX prt gunshell.png

2019-11-09T05:38:27Z

Tut:

File:2DFX prt glass.png

2019-11-09T05:38:18Z

Tut: