Register
Login
Merry Christmas and Happy New Year to all players!
Advanced Crash Codes & Fixes - Part 2
Kazuha's Blogs
Acceonit
20/06/2022
Hi again this the part 2 of advanced crash codes & fixes, I couldn't complete it in the first part because the limit for words is 50.000, anyways here goes nothing... press CTRL + F at the same time to find a specific code in this blog post, anyways I made this blog post for the players who can't play with modifications that makes their game better in graphics, vehicles, skins, etc. well... here goes nothing.
below are some advanced and probably rare client crash addresses that usually pop out when you use corrupted/unconfigured modifications... which you can use to help trace the problem and prevent it from occurring in the future. In most cases, client crashes occur because of a problem in the script.
0x004CE15C
Problem: Error loading pedestrian animations. Possibly the "datapeds.ide" is misconfigured.
Solution: Fix the wrong line in peds.ide, thus correcting the animation placed on that pedestrian. If you don't know how to do this, ask the mod author. If you edited it yourself, review what you did better or go back up.
0x0057FAAD
Problem: Possibly caused by Widescreen Fix ...
0xC000007B
Problem: Missing some .dll, runtimes, etc
Solution: Check the root folder of your GTA SA, if any .dll is missing there, a good tip is to copy all the .dll's from a backup GTA SA folder and paste them into GTA with the problem, but without replacing so only paste the that are missing.
Solution 2: Click here to download the .dll's and runtimes that are missing from your PC.
0x006FD525
Problem: Vehicle.txd, more specifically, car license plate textures. Also possible to be related to ImVehFt, board textures in ImVehFtPlates folder.
Solution: Back up or install another mod that replaces Vehicle.txd or reinstalls ImVehFt, there is a problem related to loading these textures.
0x0046504E
Problem: Related to some object, create, get it while it no longer exists, and do something with it. Possibly caused by some badly done or poorly installed Cleo script etc.
0x0059F8B4
Problem: Failed to load collision from .dff. The .col file is possibly not installed or the name inside the.COL file is different from the name of the .dff related to it, or there is simply no model .dff name inside the.COL
Solution: Check if there is a .COL file for the .dff properly installed and working in the game, as well as look in modloader.log looking for if the.COL was loaded etc. Or check yours.COL file to see if everything is in order.
0x00734E5A
Problem: TXD missing or incomplete or buggy or some mod tried to load some texture or some model that doesn't exist.
0x007F0875
Problem: Some poorly modeled cars.
Solution: Find and remove the car (if you can, notify the creator of the car). Test Car Load will help find the buggy car.
0x006A65F6
Problem: Related to processing the suspension of a car, the problem with its collision.
Solution: Look for which car has this problem and remove it, notify the creator.
0x007C94E7
Problem: Some buggy model or graphic mod that messes with the models. Models of people/pedestrians.
Solution: Has already been fixed by removing Normal Map from DK22Pac while using Insanity Peds and Insanity Weapons Items. Remember that using these mods without DK's Normal Map mod will work, but it won't have the effect of Normal Map. The same crash has already occurred in other mods that use Normal Map, even without having SkyGfx installed.
0x004082B1
Problem: Invalid handle/reference of a person from the script.
Solution: SCRLog can help you find out exactly which script caused the problem.
0x005A3280
Problem: Loading objects into the object.dat file
Solution: Identify the mod and uninstall, or if you have 2 or more "object.dat" files in ModLoader, take the changes from one and put them in the other. This site can be helpful. Several mods use object.dat files, like Overdose Effects, and some map mods like INSANITY Construction Site by Ezekiel.
0x006F7524
Problem: Starting train tracks, possibly problem with "tracks*.dat" files in datapaths folder
0x007FFF12
Problem: Get the image format (usually mods that load .png, .bmp images, etc.). This crash has been caused when trying to use ImVehFt on Windows 10
Solution: It was already fixed when reinstalling the mod folder, but the problem kept coming back.
Problem 2: Similar to the case above, such image (.png, .bmp, etc) could not be loaded for some reason, including lack of it.
Solution 2: Identify and verify that mods that use images are correctly installed, for example, the GTA V Hud.
0x006D867A
Problem: Wind speed. Possibly some mod that controls the game's wind? Like mods that edit rain or the Wind Mod created by me (if misconfiguring the .ini can cause this crash, I believe).
0x005725BF
Problem: Catch the distance between two zones (game areas such as neighborhoods)
Solution: Did you change any files that control anything about the zones? like .zon files or some other?
0x004946A4
Problem: Caused when using GTA V Skybox
Solution: Remove it, very poorly done
0x00757D6E
Problem: Possibly some modeling of something (like a vehicle) or graphical mods (like enb series). It has already been caused by selecting a part in Tuning Mod, so the problem is with that part
.
0x007F5D85
Problem: Possibly some modeling of something (like a vehicle).
0x00416C0B
Problem: Collision problem (collision model, coll) of something.
0x00731C93
Problem: .TXD file limit
Solution: Download and install Fastman92 Limit Adjuster; Open fastman92limitAdjuster_GTASA.ini; In "FILE_TYPE_TXD" remove the "#" from the beginning of the line and increase the value. It can increase a lot, 500 or 1000 more.
0x0E0748C5, 0x0E3E9AD1 and 0x0FE75A1F (in the "Backtrace" at the end of the log will have 0x006A7770)
Problem: Caused when using do not blow up the car while overturned mod (created by LINK/2012)
Solution: Remove the mod, in the case of MixSets, disable the "VehFlpDontBurn" function within the Mix Sets.ini
Solution 2: Using NoDEP.asi may not help, but if it does, let me know!
0x08265E39 and 0x0E2656F3 (in the "Backtrace" at the end of the log will have 0x006ADB85)
Problem: Caused when using reverse gear mod together with MixSets, as MixSets already has this mod included (BrakeReverseFix inside .ini).
Solution: Delete the mod...
0x006CAC47
Problem: Has been caused using Enhanced Functions with cars added without replacing.
Solution: Stop using Enhanced Functions, it's an obsolete mod, replaced by VehFuncs.
0x004AA134
Problem: Particle-related (special effects)
Solution: Try removing your special effects mods. This issue has been caused when using a xenon mod (not xenon in Cleo as it is just a Cleo and does not change your game effects)
0x004F02D3
Problem: Related to playing a sound. It has been caused in SAMP when shooting close to someone
Solution: If you haven't changed your game sounds, it could be any other related issue, including your PC's audio drivers
0x004C53A6
About: Usually caused by some vehicle having the node name (basically, the name of the part) with a name that is too long (the limit is 23 characters, 25 or more causes serious problems in your game). With VehFuncs installed, this crash is automatically corrected. The information remains in the .log in case you want to know which vehicle is causing the problem. Without VehFuncs, with or without this crash, the problem that leads to this crash also leads to other bugs and crashes in the game.
0x00571A10 and 0x00571A00
About: This can be caused by hundreds of different reasons.
Backtrace: 0x00490B77
Problem: Some mod applied too many tasks to the game's peds/NPCs, thus hitting the limit.
Solution 1: Identify and remove this mod Cleo. You can use SCRLog for that, but it's some mod that controls NPCs. Notify the mod author to fix it.
Solution 2: Raise the task limit.
0x909090C3
Problem: This crash can happen due to several reasons, but it is usually caused by a conflict between 2 mods that used the game's system memory patch.
0x005A5A47
Problem: Related to textures (from player.img).
Solution: Remove such edits, if you didn't do any of this, try to inform/find out what you did to give this problem too
0x0040F64C
Problem: Possibly your special effects mods (effects.fxp)
Solution: Uninstall it. You can also try using the game's graphics at Low which may also fix the problem.
0x004C9239
Problem: Some problems with the handling line. Not installed? Wrong configured? Did you hit or miss setting the limit? Anything like that. More specifically the flags of the model.
Solution: Check-in total, this crash has been caused when trying to add a car without replacing it.
0x0064F8C3
Problem: Some .ifp file (from anims) is buggy; missing anims; badly converted, etc.
Solution: Identity which .ifp is causing this and remove it. If it was right when you started the game, it was probably some ped.ifp you have installed.
0x004C9691 and 0x00732924, 0x00749B7B
Problem: SRT3 / RoSA Project (or maybe any other texture mod, or anything that uses .txd). Caused by using non-power 2 textures in .txd. As taught in the Magic.TXD tutorial here on the blog, it is necessary that the resolution of the textures has a power number of 2, such as 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, etc...
Solution: If the crash was in the SF hospital, download the fix found here on MixMods in the SRT and/or RoSA Project post. If not in this location, let us know, if you don't use such mods then this is not the problem, but it can still be caused by another mod that modifies .txd and is correctable by recreating the .txd (if you identify which .txd it gave the problem there) — exporting everything with txd workshop and recreating the .txd with magic txd. The solution may also be simply to change the resolution of the textures to power of 2, which in addition to correcting such a crash, corrects other visual bugs and improves the processing of the video card.
Problem 2: In the case of 0x00749B7B, get the models inside a model. It can happen for many reasons, such as some script trying to create a person whose model hasn't been loaded yet.
Solution 2: If you think this was caused by a script someone created, remove this script and contact the author, possibly the SCRLog.log will show which script caused the problem.
Problem 3: It could be due to a model (usually cars and skins?) being poorly adapted, converted, or saved in another GTA format (eg GTA VC format)
Solution 3: In this case, identify which model mod is giving this error (it will give the error when loading to appear in the game), uninstall, inform the author, etc.
Problem 4: When loading the game after it has already loaded?
Solution 4: Disable the MixSets VehLODdist and/or DelayToRead function (DelayToRead seems to have fixed it and does virtually no harm to disable it). If it does solve it and you're sure, I ask you to let me know so I can try to fix it.
Problem 5: It has been caused using mod "town_adjuster.asi", which is from Cops Bikers Overhaul. Because I had the .asi installed without the .dff and .txd files from the police skins.
Solution 5: Reinstall the mod, make sure the cops .dff and .txd are actually loading, or simply delete the "town_adjuster.asi".
0x006A4523
Problem: When closing a car door, possibly non-existent.
Solution: If it was during Tuning Mod, be aware that in v1.5 or newer it has been fixed. If you weren't using the Tuning Mod, Scrlog.log will be able to tell you the problem (or not), some Cleo mod that controls the car doors.
0x00469FBC
Problem: Initialization of game scripts
Solution: Delete the folder "cleocleo_saves"
0x00822527
Problem: shopping.dat with errors.
Solution: Back up the shopping.dat, remove this file from the Mod Loader or replace it with the original in the Data folder.
0x004C8F24
Problem 1: This crash has been caused when using Stream Memory Fix 2.0, which is an extremely old and disused mod.
Solution 1: Stop using it and use MixSets and/or Open Limit Adjuster.
Problem 2: Some car limit problems.
Solution 2: Has already been fixed by installing the Open Limit Adjuster.
Problem 3: Related to a car model.
Solution 3: Find and remove the car (if you can, notify the creator of the car). Test Car Load will help find the buggy car.
0x00532B82
Problem: Apparently lack of collision (.col) in a model
Solution: Check the installation of the mods you have that use .col, it may be missing .col or with the wrong .col (missing the collision model inside the .col)
0x004CE15C
Problem: Error loading pedestrian animations. Possibly the "datapeds.ide" is misconfigured.
Solution: Fix the wrong line in peds.ide, thus correcting the animation placed on that pedestrian. If you don't know how to do this, ask the mod author. If you edited it yourself, review what you did better or go back up.
0x004F0E1C
Problem: Something related to sounds.
Solution: Are you using a sound pack? Try uninstalling it to see if it works.
0x0070AA31
Problem: Something related to the game's shadows.
Solution: If you are using a shadow extender, you can try uninstalling it.
0x007F5A3A
Problem 1: If you have "0x006A2C29" in the "Backtrace" at the end of the log: Bad modeling of some vehicles.
Solution 1: Try to find out which vehicle and uninstall it.
0x006A65EF
Problem: Some vehicles without collision
Solution: Check your vehicles, if you don't know which one it is, test to see if they are working and stop looking for which one is faulty or manually uninstall, or all, some of them have .dff with errors. That should help you find.
0x0072837D
Problem: Related to on-screen sprites (anything added to the hud, images, texts)
Solution: Try to figure out which mod and delete it, be it any mod that added such things to the screen during the crash.
0x00405CB6
Problem: Lack of an IPL file or bad written IPL.
Solution: Check if any IPL is missing to be loaded, either original from the game or one installed. Usually, gta.dat files or in some readme come with IPL load-lines inside, so reinstall such mods or delete them entirely.
0x00801D58
Problem: Usually some mods do give this error, I don't know why and which ones.
0x006FEC20 and 0x0D3C1FA0 (0x006FECF5)
Problem: When rendering the text of traffic signs (those saying city names etc, roadsigntext).
Solution: Problem with the texture of the letters in particle.txd, did you use compression on this texture in particle.txd? Are you using .cs to increase the resolution of those cards? Some of these things may have caused the problem and you should of course check the particle.txd you are using, not adding compression ("compressed") to the roadsignfont texture, leaving Raster Raw.
0x0040FB80
Problem: Collision related (coll), possibly hitting the game's collision limit or another issue about .col.
Solution 1: It has already been fixed due to some bad configuration of the fastman92 limit adjuster.
Solution 2: If you are trying to start SAMP, probably samp.exe has a different compatibility mode than gta_sa.exe or some other reason why SAMP cannot open gta_sa.exe (bad configuration, there is already some gta_sa. exe in Task Manager, some program preventing startup (you can try restarting the PC), etc).
0x006D1080
Problem: Failure to handle a vehicle, quite possibly the vehicle disappeared from the game and some bad mod ended up trying to handle a non-existent car
Solution: Possibly it was a Cleo and possibly won't generate SCRLog.log for you to know which Cleo... you will have to look for which script manually gave this error, unfortunately. If it was a MixMods mod, let me know.
0x005B6B2F
Problem 1: Two identical IDs are being used in data/vehicles.ide
Solution 1: Check your vehicles.ide or lines of it, must have a duplicate line or id already used, etc, things like that. It can even be a line with a badly configured model, missing, etc.
Problem 2: Error in carcols.dat, number of color variations, possibly some car has more than 16 colors in its carcols line or vehicles.ide is misconfigured.
Solution 2: Delete the number of color variations of the car to make it less than 16, or use some mod that increases the limit of color variations. It is also possible that you installed the colors in the wrong places, placing the lines of 2 colors where they are for 4 or vice versa, if you do not know, install by Mod Loader, it will install the lines correctly for you.
The problem can also be because of the badly configured vehicles.ide, review the models and IDs if they are all correct, etc.
0x00563289
About: With VehFuncs installed, in case this crash happens, the mod will give information about which vehicle model caused this. However, this particular crash is usually not about cars.
Problem 1: Error removing an object from the map, possibly an object stuck in the save game
Solution 1: Try to see if another save game or new game doesn't crash at that location, if it didn't, then you must have saved the game with some script mod that adds an object to the map. Click here to download a mod that will enable you to fix this crash, just look for the bugger object on the spot and delete it. Or click here to download a new save game and see some tips.
Problem 2: It can also be any type of model, such as poorly made vehicles (there is still a slight possibility of being skins and clothes).
Solution 2: Try to uninstall all your vehicles or try to find which one. If the crash is while you are playing, try using Test Car Load to find out which of the vehicles caused the problem.
Problem 3: Any necessary mods (object-related?) are missing from your game. Possibly you will have this problem only in a save, and right after uninstalling some mods.
Solution 3: Replace the mod you uninstalled, possibly the game needs it.
0x004A2CF3
Problem: Related to special effects, you probably have an effect (.fxp or .fxs) installed but you are using an unsupported "effectsPC.txd" without any texture there.
Solution: Check your .fxp and effectsPC.txd files in modloader, it might be a conflict.
0x007F120E
Problem: Frame not found. It can be caused by 40 reasons such as a buggy model or a script controlling something from a car. This also happens in MixSets version 4.0.5 or older when blowing up lots of cars, it has already been fixed in new versions.
Solution: If you use MixSets 4.0.5 or older, please update it as this crash has been fixed. It has been caused trying to tune a car is unprepared for tuning. Possibly the crash can also happen when arriving near a garage with a car with unsupported tuning parts inside. Check your mods and models. In case of a crash due to some tuning in a car that doesn't have support, simply don't tune or try to configure the line of carmods.dat of it correctly because the lines are incorrect. It was also caused by using the windshield remove the mod, on motorcycles, which had no windshield (as it can be any other mod that removes vehicle parts)
0x004D41C5
Problem: Problem with the animation of getting into a vehicle, it could have been you or another player on the street (if the crash was during the game without you getting into one)
Solution: Try to find out which vehicle (if you don't know) and check the vehicle.ide and/or .ifp lines (if you edited an .ifp, it may lack some animation). This crash has even been caused when using the F-14 plane, but apparently due to a problem with the plane itself, where you need to enter it from the right side otherwise this crash occurs here.
0x007F3737
Problem: Loading textures from a TXD
Solution: Check your TXD
0x007F39FB
Problem 1: You have a .img file open.
Solution 1: Close any IMG Editor program.
Problem 2: Loading a texture (inside TXD). An original ModLoader bug has a hud.txd installed on it. It can happen when starting the game, and next time it works.
Solution 2: Delete all hud.txd that are installed inside ModLoader. If you have more than 1, try to uninstall and leave only 1 of them.
Problem 3: Failed to load any clothing .txd or vehicle.txd. Or else some paint job from a car.
Problem 4: Some CLEO scripts tried to load a sprite texture into some .txd ("models/txd") but didn't load the .txd file before. For example in an old version of ATP.
Solution 4: Identify the mod CLEO, note that the .txd file may even exist (if the .txd file does not exist but CLEO tries to load, the problem is another one), the problem may be direct as an error of some CLEO mod that needs .txd but forgot to load it.
About: It could be anything related to "loading a texture from a .txd file", so it could be caused by hundreds of different reasons, but one thing is certain: There's some .txd wrong there, possibly buggy or missing some important texture, things like that.
0x004D464E
Problem: Animation problem in some animgroup, either weapons or walking styles.
Solution: Could have been caused by editing weapon.dat and changing the weapon's .ifp file, but not also changing the default.ide file (which is the file where the weapon and its .ifp are loaded). Just as it may have been caused by a script that tried to put the gun on someone, but the gun was not loaded, and so this crash. The same error can be caused by a misconfigured animgroup in the ifp part (animgrp.dat). It is best to identify which mod is giving this (following the details I just said) and contact the author of this mod to fix it by having the necessary .ifp file loaded for that weapon (or the weapon itself is loaded) in-game memory).
Problem 2: A new line of weapon.dat without having a fastman92 limit adjuster installed and configured.
Solution 2: If this is your case, identify, check if you have any weapon lines installed (either weapon.dat or .txt files containing lines from it), remove or install fastman92 limit adjuster, configure it correctly, etc.
0x0080D5EF
Problem: Transforming a 3D point
Solution: It may or may not be reasons for car models or explosion systems of some mod (usually asi). Try starting the game in admin mode and with Windows XP SP3 compatibility (this has already solved one person's problem)
0x00405CA4
Problem: Error with binary IPLs. Wrong ID.
Solution: Fix or remove (if new) your binary IPLs (inside .img or Modloader)
0x0053C1F5 and 0x0053E986
Problem: Missing NewOpcodes.Cleo? Some mod asks for it and you don't have it?
About: Try downloading it and installing it in your Cleo folder.
0x004F0E67
Problem: Possibly sound problem from your PC, DirectPlay, or is using Mobile sounds mod.
Solution: Read Error: DSOUND.dll below
0x004AA4C8
Problem: Special effect (effects.fxp) not found or missing.
Solution: Check your effects.fxp, possibly you replaced it with one that is missing an effect or you are using some mod that uses an effect that is missing inside your effects.fxp.
0x00705D48
Problem: Related to the processing of dynamic shadows.
Solution: Uninstall any mod that messes with them, disable them with MixSets or SkyGfx, or simply leave the game at the Low setting.
0x00826360
Problem: When trying to read some text, the text did not exist. It could be for several reasons.
Solution: Invalid timecyc.dat file, it happens because there is some error (for example, some line is missing) in your timecyc.dat or you are using the mod Timecycle 24H with some timecyc.dat installed in the modloader (just uninstall the timecyc.dat from the modloader ).
0x005381A5
Problem 1: Incorrect IPL or buggy model (crash when trying to load a stanza from an IPL). By reports, this also has to do with mods and saved game
Solution 1: Check the IPLs or models. If the problem is not saved, try using Delete Objects
Issue 2: It has been caused using Open Limit Adjuster not configured for Project2dfx.
Solution 2: In case, Project2DFX comes with an Open Limit Adjuster properly configured for it, you need to use it, remove another Open Limit Adjuster from your GTA (if you have two) and leave Project 2DFX's own.
0x00553F71
Problem: Related to map rendering.
0x00534134
Problem 1: The same ID being loaded on different models, is very common in installing different map mods with authors who don't care about compatibility. If you had this crash after installing a part in Tuning Mod, it is because two parts (or some other different mod) are using the same ID, inform the author and/or follow this tutorial to fix the incompatibility.
Solution 1: Review your new IDE files, one might be using the same ID as the other. In most mods (not scripts) you can just open and change the id to some free one (click here for a list or use this tutorial to fix the incompatibility).
Problem 2: Inappropriate (or missing) COL
Solution 2: COL: Review whether the COL is being loaded on the IMG or Mod Loader, if IMG, also reviews whether the IMG is being loaded on gta.dat or Mod Loader. To install a COL in Mod Loader correctly, follow the Mod Loader Tutorial in the part where it talks about installing.COL
Problem 3: The object with LOD was removed.
Solution 3: Remove a map object that contains LOD, it is necessary to use both the *_stream*.ipl file (inside gta3.img) and the .ipl file from the data/maps folder. If you for example remove an object only in the *_stream*.ipl file but not also remove it from the .ipl from the data/maps folder, it will cause this crash. What can also happen when installing a mod, for example, you already have a mod that changes the same .ipl file, so the necessary file will not be loaded and will cause this crash. You will have to check that the files are all installed and loading (you can check modloader.log to see if it is loading if you already have another file installed etc). Alternatively, if you're creating a map mod, you can move the object underground instead of deleting it, so you'll avoid problems like this but you'll also have to do the same with the LOD (which is in the .ipl of the data folder/maps).
Problem 4: You have some game .img open in some program, like Alci's IMG Editor.
0x0040E179
Type: The game freezes when looking at an object
Problem: TXD (or other feature (except DFF)?) is not present in IMG.
Solution: Add the TXD to the IMG or remove the IDE/IPL from the related object.
0x005DC425
Problem 1: Incorrect collision material (Inappropriate material ID).
Solution 1: Fix the material ID within the COL file. A tip is after you identify exactly which model and which .col file is causing the problem, open the .col in Coll Editor, select the model with the problem, or that you think has the problem, go to Edit Mode, in Face, and Select All to select all, and see in "Material" the number that appears. If you just created the .col then everything will probably be "0", which is the default, but if you have any invalid IDs, it will be with another bug number and so will not show any numbers there. Changing the Material to 0 with all faces selected will change everything to 0, including the bug face, and fix the problem. This is probably caused by Coll Editor merging differently.col files, probably some Coll Editor bug.
Problem 2: Strangely, a time-cycle-related issue (timecyc.dat).
Solution 2: It happened in the "lite" version of Real Linear Graphics, it has already been fixed. Strangely, the solution was to lower the intensity value of the 7 pm line of the San Fierro fog climate, as the crash was in Los Santos, it is not known for sure how this happened.
0x006E9248
Problem: Water-related (incorrect water.dat?) (in water rendering). Division by 0.
Solution: Fix the water.dat.
0x006F5702
Problem: Too many objects? Some unknown boundaries.
0x007ECABB
Stack: 0x4CDCDE > Error
Problem: Corrupt texture format (problem with low-resolution textures). This could be caused by the WTD2TXD tool.
Solution: Fix the TXD. Check if low-resolution textures are marked with compression (compressed, DXT).
Files Problems
Error: CLEO.asi
Problem: Some CLEO/SCM script.
Solution: The SCRLog mod can tell you exactly which script caused the problem and contact the author.
Error: CLEO+.cleo
Problem: Algum script CLEO/SCM que use CLEO+.
Solution: The SCRLog mod can tell you exactly which script caused the problem and contact the author.
Error: modloader.asi
Problem 1: In extreme cases where you install any file in modloader and it already causes several crashes, including in modloader. asi just by opening the game, probably all your modloader got into a mess and stopped working.
Solution 1: So, try to reinstall the modloader and delete all its cache in your user's AppData folder, that is, in my case it would be "C:UsersJuniorDjjrAppDataLocalmodloader", go in there and delete everything and try again. If you're having trouble finding your AppData folder, please Google it.
About 1: If it crashes after a few minutes of playing: Usually this problem is caused not by Mod Loader, but by ImVehFt. The error is not Mod Loader, but how ImVehFt was created, try to uninstall it or use IVF version 2.0.8 to see if it solves, if it doesn't or you don't use IVF then the problem is different. ..
About 2: You may also have the wrong Mod Loader, misconfigured, etc, review these questions if you configured it.
About 3: Send the modloader.log to see, by the .dll shown at the end of the crash codes you can also get a sense of what kind of file the modloader failed when trying to load. That's if you have the .dll... So, send it, but there is no promise that it will fix it, modloader crashes can be many and many reasons that are difficult to know exactly why...
Error: std.bank.dll
Problem 1: Some sound. This DLL is Mod Loader, but it cannot necessarily be a Mod Loader problem.
Solution 1: If you've edited your game's sounds, whatever the mode, back it up, and as always, if it doesn't help, move the GTA folder to Documents and try again.
Problem 2: Possibly your PC's sound problem, DirectPlay.
Solution 2: Read the Error: DSOUND.dll below...
Error: D3DXAPI.asi
Type: Loading failure or crash
Solution 1: Download and install DirectX End-User Web Installer (in this download will come to update for all DirectX of your PC, so it can fix other problems as well)
Solution 2: Download and install Visual C ++ 2013 Redistributable
Solution 3: If you have plugin.dll in your GTA, delete it. If you say that plugin.dll is missing, update the mods that need it, as they have been updated and you should no longer use plugin.dll in your GTA.
Error: TM.asi
Type: Loading failure
Solution: Download and install Visual C++ 2013 Redistributable
Error: KERNELBASE.dll
Problem 1: It has been caused when using ped pack in HD
Solution 1: If you are using the mod "Load Whole Map" with the "Peds Pack in HD", go to .ini (from Load Whole Map) and the "LoadPeds" function if you have "1" " put "0" because apparently some pedestrian(s) of this pack is having a problem and when loading it(s) it gives an error. If the problem persists giving errors while playing, it may be exactly because some model is buggy and so it's good to look for which one or remove the entire pack.
Problem 2: Possibly your PC's sound problem, DirectPlay. It could also be a ModLoader cache problem. Go to the folder "C:UsersTommyAppDataLocalmodloader" where "Tommy" is your username, and delete all content. Next time your game will take a while to open, but it will work.
Solution 2: Read Error: DSOUND.dll below...
Problem 3: Incompatibility of Grass Models.
Solution 3: Disable "ps2grassFiles" from SkyGfx1.ini (and other .ini of it)
Problem 4: Some problems related to ReShade (d3d9.dll/dxgi.dll).
Error: bass.dll
Type: Any error message related to it, or it is missing from your GTA after uninstalling SAMP.
Solution: Download bass.dll by clicking here, and install x86 (32 bits). I recommend downloading even if you don't have the problem, because some mods that use sounds or the SAMP .dll may have problems etc.
Error: quartz.dll
Problem 1: Incompatibility with new versions of Windows.
Solution 1: Enable Windows XP Compatibility Mode (Service Pack 2) in the game's .exe properties.
Problem 2: Related to Plugin LAV Video
Solution 2: (uploaded by Guto Rocha) In Start Menu > Programs > K-Lite Codec Pack > Configuration. Click on LAV Video. In the "Formats" tab, clear the boxes corresponding to MPEG1, MPEG2, and MPEG3 formats. Apply and ok. (tested on Windows XP and Windows 10).
Problem 3: It has been caused when installing mods in the Mod Loader root folder instead of installing folders inside it, which is an error.
Solution 3: Do not install mod files by leaving in "GTA San Andreas / modloader /", always install the files in "GTA San Andreas / modloader / some folder". There is more information right in the Modloader download post.
Error: colormod.asi
Problem: It has been caused by incompatibility with Project2DFX. Even if it doesn't make much sense and even though I used them both together a lot and I never saw a problem: you can try to uninstall either one to see if it corrects. As well as it can also be incompatible with some other mod or even bad installation of Color Mod.
Error: igdumd32.dll
Problem: This .dll is from Intel Graphics (your video card). It could be a problem with your PC's graphics drivers, simply a conflict between graphics mods, or a problem model or texture mod. It's hard to know the exact reason since it's about graphics in general.
Error: DSOUND.dll
Problem: DirectPlay
Solution 1: Use SilentPatch
Solution 2: Install DirectPlay by going to Control Panel > Programs and Features > Turn Windows features on or off (on the left of the window) > go to legacy components and check the DirectPlay box > install and restart the computer (tested on Windows 8.1 and fixed).
Error: normalmap.asi or NORMAL~1.ASI
Problem: Video card not supported? If your video card is very old, this is possibly the problem.
Error: colormod.asi
Problem: Incompatibility with Project2DFX
Solution: Uninstall it or it or Project2DFX.
Error: d3d9.dll
Problem 1: As you may already know, it's the .dll used for a lot of things, especially enb series, so everything sets it to WHAT you used it (where 99% of people use it as enb series or it already came in game installation ). It may be that your PC doesn't support the enb series or another graphical mod that uses this dll, but some mods are made using this dll, super old mods from the GTA SA release where they ended up using this .dll to create the mod, completely obsolete now, stop using such mods. If you don't use in series or other mods of this dll, it should be correctable by updating your DirectX Runtime, and then, if you have this dll installed in your game, delete it (or not).
Problem 2: If a crash in the Advanced menu of the game graphics and you are using 90s AVP Reborn, it was caused by his Super GT and the solution is simply to change this car. In the same way, you might not be using the 90s AVP but you might have this same car, or another car with the same problem, that is if this dll crashes in this menu, it could be a car installed in your GTA.
Problem 3: During an explosion? Using some mod like Remastered Effects? If you have any 0x007FDE14 and/or 0x007FE7DC and/or 0x004A140A in the "Backtrace" at the end of the log, it may be caused by IgnoreWater from MixSets (or even FreezeHour). So, if enabled, set these functions to -1 in MixSets.
Error: ntdll.dll
Problem: Difficult to know the exact reason as it is a very common Windows .dll. But it's more likely something to do with uploading files.
First of all, if the crash occurred when opening the game, simply try to open it one or two more times that should work. It's weird and I still don't know why yet. But this same error can be caused by other things:
Solution 1: At the end of "modloader.log", in the top line of the crash address, you will have the last file read, for example: "Loading default object types "datamapsveh_modsveh_mods.ide", in this example, possibly crashed when trying to read the veh_mods.ide file, check it. If the last file was a .txd, it was quite possibly not a problem with it. Also often it can't have anything to do, if you enter a store it will appear that "shopping.dat" was loaded last, but that doesn't mean that the crash was in this file too, so I'm not sure, but still try to check them, especially if the crash was when trying to open the game.
Solution 2: Check Windows permissions and file reads, it can be any file, whether from the data folder or some mod. I always recommend using GTA in Documents and not Program Files, to fix this and other problems.
Solution 3: If it crashed when selecting the radio "User Tracks", delete the file "sa-utrax.dat" from the folder "Documents/GTA San Andreas User Files". It is also possible that some .mp3 there is with the wrong encoding, GTA SA only accepts the MP3 LAME format. in this case, you can identify and remove such a CLEO mod that uses the CHDIR command, or change the radio by pause menu.
Solution 4: If SAMP crashed, check if "SAMP Fix" is marked in the ImVehFt .ini. Or if any files needed for SAMP to work are missing (in this case reinstalling SAMP will help)
Solution 5: If you see followed an error window "std.asi: translator.SteupASI failed to identify caller ASI", it is because it was the incompatibility of one .asi with another, mods .asi that modify the same thing as the other. I believe this was once due to vehlightsfix.asi along with silentpatch.asi, as they both fix some of the same things, but that was just a guess and also just an example.
Problem 6: Action_x86.dll incompatible with ntdll.dll.
Solution 6: Switch to 32-bit color resolution.
Solution 7: Uninstall HiDefCam.asi.
Problem 8: After minimizing the game?
Solution 8: Pause the game before minimizing, or if you have already paused it, it could be the mod SAGrading (colorcycle).
Solution 9: Try installing an Improved Fastloader.
Solution 10: The stream.ini file is missing from the game folder.
Solution 11: Don't use special characters (no punctuation etc) in the game folder name or somewhere along the path. Also, don't go too long. Has already been fixed after removing characters [ and . of the game folder name, but it is not exactly known if this was the problem, if the path was too long if it was some Windows bug, etc.
Other problems:
Freeze (usually flying with Hydra)
Solution: Open the game in administrator mode and Windows XP SP2 compatibility mode. It could be some mod, you don't know which one.
Game not re-installing
About: Trying to use the installer but it already identifies that the game is installed?
Solution: Open the start menu, type regedit and open regedit.exe. Go to HKEY_LOCAL_MACHINE -> SOFTWARE, there will be a "folder" Rockstar Games, and inside GTA San Andreas with a "key" inside it. Delete the key or the "GTA San Andreas" folder itself.
If not, look inside HKEY_CURRENT_USER.
Error: Message "Runtime Error!" "This application has requested the Runtime to terminate it unusually."
About: It could be caused by an error in some .asi mod. The modloader.log[b] or another crash dump can give a hint of what the mod was (even if not 100% correct).
During gameplay: In addition to .asi, it may have been caused by high memory usage if you configured the game to use 2GB of stream memory without using [b]largeaddress
When trying to start the game: In addition to .asi, it may be ModLoader's cache problem. Go to the folder "C:UsersTommyAppDataLocalmodloader", and delete all content. Next time your game will take a while to open, but it will work.
it took time to write all this, if you have something to suggest/discuss drop a comment in the comments section.
Other useful blogposts:
Arcade Games | Custom Fonts | Stalls Location | Forum Titles | Website BBCode | Random Packages | Fish Species | Shell Game | Kitty Claw | Epsilon Program | Computer sites | Storage Lockers & Pawn Shop | Drug Base | Datacenter | Mafia Money | Drug Plane | SF | Drug Plane | LV & Airfield | Drug Plane | LS | Drug Delivery | SF | Drug Delivery | LS | Newspaper Events | Contacts | Diploma + Benefits |
Fixes & Methods for Problems in-game:
Advanced Crash Codes & Fixes - Part 1 | Basic Crash Codes & Fixes | Crashes Solutions | Game Freeze Solutions | Common Problems Solutions | Solution to 'unable to excute' error |
below are some advanced and probably rare client crash addresses that usually pop out when you use corrupted/unconfigured modifications... which you can use to help trace the problem and prevent it from occurring in the future. In most cases, client crashes occur because of a problem in the script.
0x004CE15C
Problem: Error loading pedestrian animations. Possibly the "datapeds.ide" is misconfigured.
Solution: Fix the wrong line in peds.ide, thus correcting the animation placed on that pedestrian. If you don't know how to do this, ask the mod author. If you edited it yourself, review what you did better or go back up.
0x0057FAAD
Problem: Possibly caused by Widescreen Fix ...
0xC000007B
Problem: Missing some .dll, runtimes, etc
Solution: Check the root folder of your GTA SA, if any .dll is missing there, a good tip is to copy all the .dll's from a backup GTA SA folder and paste them into GTA with the problem, but without replacing so only paste the that are missing.
Solution 2: Click here to download the .dll's and runtimes that are missing from your PC.
0x006FD525
Problem: Vehicle.txd, more specifically, car license plate textures. Also possible to be related to ImVehFt, board textures in ImVehFtPlates folder.
Solution: Back up or install another mod that replaces Vehicle.txd or reinstalls ImVehFt, there is a problem related to loading these textures.
0x0046504E
Problem: Related to some object, create, get it while it no longer exists, and do something with it. Possibly caused by some badly done or poorly installed Cleo script etc.
0x0059F8B4
Problem: Failed to load collision from .dff. The .col file is possibly not installed or the name inside the.COL file is different from the name of the .dff related to it, or there is simply no model .dff name inside the.COL
Solution: Check if there is a .COL file for the .dff properly installed and working in the game, as well as look in modloader.log looking for if the.COL was loaded etc. Or check yours.COL file to see if everything is in order.
0x00734E5A
Problem: TXD missing or incomplete or buggy or some mod tried to load some texture or some model that doesn't exist.
0x007F0875
Problem: Some poorly modeled cars.
Solution: Find and remove the car (if you can, notify the creator of the car). Test Car Load will help find the buggy car.
0x006A65F6
Problem: Related to processing the suspension of a car, the problem with its collision.
Solution: Look for which car has this problem and remove it, notify the creator.
0x007C94E7
Problem: Some buggy model or graphic mod that messes with the models. Models of people/pedestrians.
Solution: Has already been fixed by removing Normal Map from DK22Pac while using Insanity Peds and Insanity Weapons Items. Remember that using these mods without DK's Normal Map mod will work, but it won't have the effect of Normal Map. The same crash has already occurred in other mods that use Normal Map, even without having SkyGfx installed.
0x004082B1
Problem: Invalid handle/reference of a person from the script.
Solution: SCRLog can help you find out exactly which script caused the problem.
0x005A3280
Problem: Loading objects into the object.dat file
Solution: Identify the mod and uninstall, or if you have 2 or more "object.dat" files in ModLoader, take the changes from one and put them in the other. This site can be helpful. Several mods use object.dat files, like Overdose Effects, and some map mods like INSANITY Construction Site by Ezekiel.
0x006F7524
Problem: Starting train tracks, possibly problem with "tracks*.dat" files in datapaths folder
0x007FFF12
Problem: Get the image format (usually mods that load .png, .bmp images, etc.). This crash has been caused when trying to use ImVehFt on Windows 10
Solution: It was already fixed when reinstalling the mod folder, but the problem kept coming back.
Problem 2: Similar to the case above, such image (.png, .bmp, etc) could not be loaded for some reason, including lack of it.
Solution 2: Identify and verify that mods that use images are correctly installed, for example, the GTA V Hud.
0x006D867A
Problem: Wind speed. Possibly some mod that controls the game's wind? Like mods that edit rain or the Wind Mod created by me (if misconfiguring the .ini can cause this crash, I believe).
0x005725BF
Problem: Catch the distance between two zones (game areas such as neighborhoods)
Solution: Did you change any files that control anything about the zones? like .zon files or some other?
0x004946A4
Problem: Caused when using GTA V Skybox
Solution: Remove it, very poorly done
0x00757D6E
Problem: Possibly some modeling of something (like a vehicle) or graphical mods (like enb series). It has already been caused by selecting a part in Tuning Mod, so the problem is with that part
.
0x007F5D85
Problem: Possibly some modeling of something (like a vehicle).
0x00416C0B
Problem: Collision problem (collision model, coll) of something.
0x00731C93
Problem: .TXD file limit
Solution: Download and install Fastman92 Limit Adjuster; Open fastman92limitAdjuster_GTASA.ini; In "FILE_TYPE_TXD" remove the "#" from the beginning of the line and increase the value. It can increase a lot, 500 or 1000 more.
0x0E0748C5, 0x0E3E9AD1 and 0x0FE75A1F (in the "Backtrace" at the end of the log will have 0x006A7770)
Problem: Caused when using do not blow up the car while overturned mod (created by LINK/2012)
Solution: Remove the mod, in the case of MixSets, disable the "VehFlpDontBurn" function within the Mix Sets.ini
Solution 2: Using NoDEP.asi may not help, but if it does, let me know!
0x08265E39 and 0x0E2656F3 (in the "Backtrace" at the end of the log will have 0x006ADB85)
Problem: Caused when using reverse gear mod together with MixSets, as MixSets already has this mod included (BrakeReverseFix inside .ini).
Solution: Delete the mod...
0x006CAC47
Problem: Has been caused using Enhanced Functions with cars added without replacing.
Solution: Stop using Enhanced Functions, it's an obsolete mod, replaced by VehFuncs.
0x004AA134
Problem: Particle-related (special effects)
Solution: Try removing your special effects mods. This issue has been caused when using a xenon mod (not xenon in Cleo as it is just a Cleo and does not change your game effects)
0x004F02D3
Problem: Related to playing a sound. It has been caused in SAMP when shooting close to someone
Solution: If you haven't changed your game sounds, it could be any other related issue, including your PC's audio drivers
0x004C53A6
About: Usually caused by some vehicle having the node name (basically, the name of the part) with a name that is too long (the limit is 23 characters, 25 or more causes serious problems in your game). With VehFuncs installed, this crash is automatically corrected. The information remains in the .log in case you want to know which vehicle is causing the problem. Without VehFuncs, with or without this crash, the problem that leads to this crash also leads to other bugs and crashes in the game.
0x00571A10 and 0x00571A00
About: This can be caused by hundreds of different reasons.
Backtrace: 0x00490B77
Problem: Some mod applied too many tasks to the game's peds/NPCs, thus hitting the limit.
Solution 1: Identify and remove this mod Cleo. You can use SCRLog for that, but it's some mod that controls NPCs. Notify the mod author to fix it.
Solution 2: Raise the task limit.
0x909090C3
Problem: This crash can happen due to several reasons, but it is usually caused by a conflict between 2 mods that used the game's system memory patch.
0x005A5A47
Problem: Related to textures (from player.img).
Solution: Remove such edits, if you didn't do any of this, try to inform/find out what you did to give this problem too
0x0040F64C
Problem: Possibly your special effects mods (effects.fxp)
Solution: Uninstall it. You can also try using the game's graphics at Low which may also fix the problem.
0x004C9239
Problem: Some problems with the handling line. Not installed? Wrong configured? Did you hit or miss setting the limit? Anything like that. More specifically the flags of the model.
Solution: Check-in total, this crash has been caused when trying to add a car without replacing it.
0x0064F8C3
Problem: Some .ifp file (from anims) is buggy; missing anims; badly converted, etc.
Solution: Identity which .ifp is causing this and remove it. If it was right when you started the game, it was probably some ped.ifp you have installed.
0x004C9691 and 0x00732924, 0x00749B7B
Problem: SRT3 / RoSA Project (or maybe any other texture mod, or anything that uses .txd). Caused by using non-power 2 textures in .txd. As taught in the Magic.TXD tutorial here on the blog, it is necessary that the resolution of the textures has a power number of 2, such as 2, 4, 8, 16, 32, 64, 128, 256, 512, 1024, 2048, 4096, etc...
Solution: If the crash was in the SF hospital, download the fix found here on MixMods in the SRT and/or RoSA Project post. If not in this location, let us know, if you don't use such mods then this is not the problem, but it can still be caused by another mod that modifies .txd and is correctable by recreating the .txd (if you identify which .txd it gave the problem there) — exporting everything with txd workshop and recreating the .txd with magic txd. The solution may also be simply to change the resolution of the textures to power of 2, which in addition to correcting such a crash, corrects other visual bugs and improves the processing of the video card.
Problem 2: In the case of 0x00749B7B, get the models inside a model. It can happen for many reasons, such as some script trying to create a person whose model hasn't been loaded yet.
Solution 2: If you think this was caused by a script someone created, remove this script and contact the author, possibly the SCRLog.log will show which script caused the problem.
Problem 3: It could be due to a model (usually cars and skins?) being poorly adapted, converted, or saved in another GTA format (eg GTA VC format)
Solution 3: In this case, identify which model mod is giving this error (it will give the error when loading to appear in the game), uninstall, inform the author, etc.
Problem 4: When loading the game after it has already loaded?
Solution 4: Disable the MixSets VehLODdist and/or DelayToRead function (DelayToRead seems to have fixed it and does virtually no harm to disable it). If it does solve it and you're sure, I ask you to let me know so I can try to fix it.
Problem 5: It has been caused using mod "town_adjuster.asi", which is from Cops Bikers Overhaul. Because I had the .asi installed without the .dff and .txd files from the police skins.
Solution 5: Reinstall the mod, make sure the cops .dff and .txd are actually loading, or simply delete the "town_adjuster.asi".
0x006A4523
Problem: When closing a car door, possibly non-existent.
Solution: If it was during Tuning Mod, be aware that in v1.5 or newer it has been fixed. If you weren't using the Tuning Mod, Scrlog.log will be able to tell you the problem (or not), some Cleo mod that controls the car doors.
0x00469FBC
Problem: Initialization of game scripts
Solution: Delete the folder "cleocleo_saves"
0x00822527
Problem: shopping.dat with errors.
Solution: Back up the shopping.dat, remove this file from the Mod Loader or replace it with the original in the Data folder.
0x004C8F24
Problem 1: This crash has been caused when using Stream Memory Fix 2.0, which is an extremely old and disused mod.
Solution 1: Stop using it and use MixSets and/or Open Limit Adjuster.
Problem 2: Some car limit problems.
Solution 2: Has already been fixed by installing the Open Limit Adjuster.
Problem 3: Related to a car model.
Solution 3: Find and remove the car (if you can, notify the creator of the car). Test Car Load will help find the buggy car.
0x00532B82
Problem: Apparently lack of collision (.col) in a model
Solution: Check the installation of the mods you have that use .col, it may be missing .col or with the wrong .col (missing the collision model inside the .col)
0x004CE15C
Problem: Error loading pedestrian animations. Possibly the "datapeds.ide" is misconfigured.
Solution: Fix the wrong line in peds.ide, thus correcting the animation placed on that pedestrian. If you don't know how to do this, ask the mod author. If you edited it yourself, review what you did better or go back up.
0x004F0E1C
Problem: Something related to sounds.
Solution: Are you using a sound pack? Try uninstalling it to see if it works.
0x0070AA31
Problem: Something related to the game's shadows.
Solution: If you are using a shadow extender, you can try uninstalling it.
0x007F5A3A
Problem 1: If you have "0x006A2C29" in the "Backtrace" at the end of the log: Bad modeling of some vehicles.
Solution 1: Try to find out which vehicle and uninstall it.
0x006A65EF
Problem: Some vehicles without collision
Solution: Check your vehicles, if you don't know which one it is, test to see if they are working and stop looking for which one is faulty or manually uninstall, or all, some of them have .dff with errors. That should help you find.
0x0072837D
Problem: Related to on-screen sprites (anything added to the hud, images, texts)
Solution: Try to figure out which mod and delete it, be it any mod that added such things to the screen during the crash.
0x00405CB6
Problem: Lack of an IPL file or bad written IPL.
Solution: Check if any IPL is missing to be loaded, either original from the game or one installed. Usually, gta.dat files or in some readme come with IPL load-lines inside, so reinstall such mods or delete them entirely.
0x00801D58
Problem: Usually some mods do give this error, I don't know why and which ones.
0x006FEC20 and 0x0D3C1FA0 (0x006FECF5)
Problem: When rendering the text of traffic signs (those saying city names etc, roadsigntext).
Solution: Problem with the texture of the letters in particle.txd, did you use compression on this texture in particle.txd? Are you using .cs to increase the resolution of those cards? Some of these things may have caused the problem and you should of course check the particle.txd you are using, not adding compression ("compressed") to the roadsignfont texture, leaving Raster Raw.
0x0040FB80
Problem: Collision related (coll), possibly hitting the game's collision limit or another issue about .col.
Solution 1: It has already been fixed due to some bad configuration of the fastman92 limit adjuster.
Solution 2: If you are trying to start SAMP, probably samp.exe has a different compatibility mode than gta_sa.exe or some other reason why SAMP cannot open gta_sa.exe (bad configuration, there is already some gta_sa. exe in Task Manager, some program preventing startup (you can try restarting the PC), etc).
0x006D1080
Problem: Failure to handle a vehicle, quite possibly the vehicle disappeared from the game and some bad mod ended up trying to handle a non-existent car
Solution: Possibly it was a Cleo and possibly won't generate SCRLog.log for you to know which Cleo... you will have to look for which script manually gave this error, unfortunately. If it was a MixMods mod, let me know.
0x005B6B2F
Problem 1: Two identical IDs are being used in data/vehicles.ide
Solution 1: Check your vehicles.ide or lines of it, must have a duplicate line or id already used, etc, things like that. It can even be a line with a badly configured model, missing, etc.
Problem 2: Error in carcols.dat, number of color variations, possibly some car has more than 16 colors in its carcols line or vehicles.ide is misconfigured.
Solution 2: Delete the number of color variations of the car to make it less than 16, or use some mod that increases the limit of color variations. It is also possible that you installed the colors in the wrong places, placing the lines of 2 colors where they are for 4 or vice versa, if you do not know, install by Mod Loader, it will install the lines correctly for you.
The problem can also be because of the badly configured vehicles.ide, review the models and IDs if they are all correct, etc.
0x00563289
About: With VehFuncs installed, in case this crash happens, the mod will give information about which vehicle model caused this. However, this particular crash is usually not about cars.
Problem 1: Error removing an object from the map, possibly an object stuck in the save game
Solution 1: Try to see if another save game or new game doesn't crash at that location, if it didn't, then you must have saved the game with some script mod that adds an object to the map. Click here to download a mod that will enable you to fix this crash, just look for the bugger object on the spot and delete it. Or click here to download a new save game and see some tips.
Problem 2: It can also be any type of model, such as poorly made vehicles (there is still a slight possibility of being skins and clothes).
Solution 2: Try to uninstall all your vehicles or try to find which one. If the crash is while you are playing, try using Test Car Load to find out which of the vehicles caused the problem.
Problem 3: Any necessary mods (object-related?) are missing from your game. Possibly you will have this problem only in a save, and right after uninstalling some mods.
Solution 3: Replace the mod you uninstalled, possibly the game needs it.
0x004A2CF3
Problem: Related to special effects, you probably have an effect (.fxp or .fxs) installed but you are using an unsupported "effectsPC.txd" without any texture there.
Solution: Check your .fxp and effectsPC.txd files in modloader, it might be a conflict.
0x007F120E
Problem: Frame not found. It can be caused by 40 reasons such as a buggy model or a script controlling something from a car. This also happens in MixSets version 4.0.5 or older when blowing up lots of cars, it has already been fixed in new versions.
Solution: If you use MixSets 4.0.5 or older, please update it as this crash has been fixed. It has been caused trying to tune a car is unprepared for tuning. Possibly the crash can also happen when arriving near a garage with a car with unsupported tuning parts inside. Check your mods and models. In case of a crash due to some tuning in a car that doesn't have support, simply don't tune or try to configure the line of carmods.dat of it correctly because the lines are incorrect. It was also caused by using the windshield remove the mod, on motorcycles, which had no windshield (as it can be any other mod that removes vehicle parts)
0x004D41C5
Problem: Problem with the animation of getting into a vehicle, it could have been you or another player on the street (if the crash was during the game without you getting into one)
Solution: Try to find out which vehicle (if you don't know) and check the vehicle.ide and/or .ifp lines (if you edited an .ifp, it may lack some animation). This crash has even been caused when using the F-14 plane, but apparently due to a problem with the plane itself, where you need to enter it from the right side otherwise this crash occurs here.
0x007F3737
Problem: Loading textures from a TXD
Solution: Check your TXD
0x007F39FB
Problem 1: You have a .img file open.
Solution 1: Close any IMG Editor program.
Problem 2: Loading a texture (inside TXD). An original ModLoader bug has a hud.txd installed on it. It can happen when starting the game, and next time it works.
Solution 2: Delete all hud.txd that are installed inside ModLoader. If you have more than 1, try to uninstall and leave only 1 of them.
Problem 3: Failed to load any clothing .txd or vehicle.txd. Or else some paint job from a car.
Problem 4: Some CLEO scripts tried to load a sprite texture into some .txd ("models/txd") but didn't load the .txd file before. For example in an old version of ATP.
Solution 4: Identify the mod CLEO, note that the .txd file may even exist (if the .txd file does not exist but CLEO tries to load, the problem is another one), the problem may be direct as an error of some CLEO mod that needs .txd but forgot to load it.
About: It could be anything related to "loading a texture from a .txd file", so it could be caused by hundreds of different reasons, but one thing is certain: There's some .txd wrong there, possibly buggy or missing some important texture, things like that.
0x004D464E
Problem: Animation problem in some animgroup, either weapons or walking styles.
Solution: Could have been caused by editing weapon.dat and changing the weapon's .ifp file, but not also changing the default.ide file (which is the file where the weapon and its .ifp are loaded). Just as it may have been caused by a script that tried to put the gun on someone, but the gun was not loaded, and so this crash. The same error can be caused by a misconfigured animgroup in the ifp part (animgrp.dat). It is best to identify which mod is giving this (following the details I just said) and contact the author of this mod to fix it by having the necessary .ifp file loaded for that weapon (or the weapon itself is loaded) in-game memory).
Problem 2: A new line of weapon.dat without having a fastman92 limit adjuster installed and configured.
Solution 2: If this is your case, identify, check if you have any weapon lines installed (either weapon.dat or .txt files containing lines from it), remove or install fastman92 limit adjuster, configure it correctly, etc.
0x0080D5EF
Problem: Transforming a 3D point
Solution: It may or may not be reasons for car models or explosion systems of some mod (usually asi). Try starting the game in admin mode and with Windows XP SP3 compatibility (this has already solved one person's problem)
0x00405CA4
Problem: Error with binary IPLs. Wrong ID.
Solution: Fix or remove (if new) your binary IPLs (inside .img or Modloader)
0x0053C1F5 and 0x0053E986
Problem: Missing NewOpcodes.Cleo? Some mod asks for it and you don't have it?
About: Try downloading it and installing it in your Cleo folder.
0x004F0E67
Problem: Possibly sound problem from your PC, DirectPlay, or is using Mobile sounds mod.
Solution: Read Error: DSOUND.dll below
0x004AA4C8
Problem: Special effect (effects.fxp) not found or missing.
Solution: Check your effects.fxp, possibly you replaced it with one that is missing an effect or you are using some mod that uses an effect that is missing inside your effects.fxp.
0x00705D48
Problem: Related to the processing of dynamic shadows.
Solution: Uninstall any mod that messes with them, disable them with MixSets or SkyGfx, or simply leave the game at the Low setting.
0x00826360
Problem: When trying to read some text, the text did not exist. It could be for several reasons.
Solution: Invalid timecyc.dat file, it happens because there is some error (for example, some line is missing) in your timecyc.dat or you are using the mod Timecycle 24H with some timecyc.dat installed in the modloader (just uninstall the timecyc.dat from the modloader ).
0x005381A5
Problem 1: Incorrect IPL or buggy model (crash when trying to load a stanza from an IPL). By reports, this also has to do with mods and saved game
Solution 1: Check the IPLs or models. If the problem is not saved, try using Delete Objects
Issue 2: It has been caused using Open Limit Adjuster not configured for Project2dfx.
Solution 2: In case, Project2DFX comes with an Open Limit Adjuster properly configured for it, you need to use it, remove another Open Limit Adjuster from your GTA (if you have two) and leave Project 2DFX's own.
0x00553F71
Problem: Related to map rendering.
0x00534134
Problem 1: The same ID being loaded on different models, is very common in installing different map mods with authors who don't care about compatibility. If you had this crash after installing a part in Tuning Mod, it is because two parts (or some other different mod) are using the same ID, inform the author and/or follow this tutorial to fix the incompatibility.
Solution 1: Review your new IDE files, one might be using the same ID as the other. In most mods (not scripts) you can just open and change the id to some free one (click here for a list or use this tutorial to fix the incompatibility).
Problem 2: Inappropriate (or missing) COL
Solution 2: COL: Review whether the COL is being loaded on the IMG or Mod Loader, if IMG, also reviews whether the IMG is being loaded on gta.dat or Mod Loader. To install a COL in Mod Loader correctly, follow the Mod Loader Tutorial in the part where it talks about installing.COL
Problem 3: The object with LOD was removed.
Solution 3: Remove a map object that contains LOD, it is necessary to use both the *_stream*.ipl file (inside gta3.img) and the .ipl file from the data/maps folder. If you for example remove an object only in the *_stream*.ipl file but not also remove it from the .ipl from the data/maps folder, it will cause this crash. What can also happen when installing a mod, for example, you already have a mod that changes the same .ipl file, so the necessary file will not be loaded and will cause this crash. You will have to check that the files are all installed and loading (you can check modloader.log to see if it is loading if you already have another file installed etc). Alternatively, if you're creating a map mod, you can move the object underground instead of deleting it, so you'll avoid problems like this but you'll also have to do the same with the LOD (which is in the .ipl of the data folder/maps).
Problem 4: You have some game .img open in some program, like Alci's IMG Editor.
0x0040E179
Type: The game freezes when looking at an object
Problem: TXD (or other feature (except DFF)?) is not present in IMG.
Solution: Add the TXD to the IMG or remove the IDE/IPL from the related object.
0x005DC425
Problem 1: Incorrect collision material (Inappropriate material ID).
Solution 1: Fix the material ID within the COL file. A tip is after you identify exactly which model and which .col file is causing the problem, open the .col in Coll Editor, select the model with the problem, or that you think has the problem, go to Edit Mode, in Face, and Select All to select all, and see in "Material" the number that appears. If you just created the .col then everything will probably be "0", which is the default, but if you have any invalid IDs, it will be with another bug number and so will not show any numbers there. Changing the Material to 0 with all faces selected will change everything to 0, including the bug face, and fix the problem. This is probably caused by Coll Editor merging differently.col files, probably some Coll Editor bug.
Problem 2: Strangely, a time-cycle-related issue (timecyc.dat).
Solution 2: It happened in the "lite" version of Real Linear Graphics, it has already been fixed. Strangely, the solution was to lower the intensity value of the 7 pm line of the San Fierro fog climate, as the crash was in Los Santos, it is not known for sure how this happened.
0x006E9248
Problem: Water-related (incorrect water.dat?) (in water rendering). Division by 0.
Solution: Fix the water.dat.
0x006F5702
Problem: Too many objects? Some unknown boundaries.
0x007ECABB
Stack: 0x4CDCDE > Error
Problem: Corrupt texture format (problem with low-resolution textures). This could be caused by the WTD2TXD tool.
Solution: Fix the TXD. Check if low-resolution textures are marked with compression (compressed, DXT).
Error: CLEO.asi
Problem: Some CLEO/SCM script.
Solution: The SCRLog mod can tell you exactly which script caused the problem and contact the author.
Error: CLEO+.cleo
Problem: Algum script CLEO/SCM que use CLEO+.
Solution: The SCRLog mod can tell you exactly which script caused the problem and contact the author.
Error: modloader.asi
Problem 1: In extreme cases where you install any file in modloader and it already causes several crashes, including in modloader. asi just by opening the game, probably all your modloader got into a mess and stopped working.
Solution 1: So, try to reinstall the modloader and delete all its cache in your user's AppData folder, that is, in my case it would be "C:UsersJuniorDjjrAppDataLocalmodloader", go in there and delete everything and try again. If you're having trouble finding your AppData folder, please Google it.
About 1: If it crashes after a few minutes of playing: Usually this problem is caused not by Mod Loader, but by ImVehFt. The error is not Mod Loader, but how ImVehFt was created, try to uninstall it or use IVF version 2.0.8 to see if it solves, if it doesn't or you don't use IVF then the problem is different. ..
About 2: You may also have the wrong Mod Loader, misconfigured, etc, review these questions if you configured it.
About 3: Send the modloader.log to see, by the .dll shown at the end of the crash codes you can also get a sense of what kind of file the modloader failed when trying to load. That's if you have the .dll... So, send it, but there is no promise that it will fix it, modloader crashes can be many and many reasons that are difficult to know exactly why...
Error: std.bank.dll
Problem 1: Some sound. This DLL is Mod Loader, but it cannot necessarily be a Mod Loader problem.
Solution 1: If you've edited your game's sounds, whatever the mode, back it up, and as always, if it doesn't help, move the GTA folder to Documents and try again.
Problem 2: Possibly your PC's sound problem, DirectPlay.
Solution 2: Read the Error: DSOUND.dll below...
Error: D3DXAPI.asi
Type: Loading failure or crash
Solution 1: Download and install DirectX End-User Web Installer (in this download will come to update for all DirectX of your PC, so it can fix other problems as well)
Solution 2: Download and install Visual C ++ 2013 Redistributable
Solution 3: If you have plugin.dll in your GTA, delete it. If you say that plugin.dll is missing, update the mods that need it, as they have been updated and you should no longer use plugin.dll in your GTA.
Error: TM.asi
Type: Loading failure
Solution: Download and install Visual C++ 2013 Redistributable
Error: KERNELBASE.dll
Problem 1: It has been caused when using ped pack in HD
Solution 1: If you are using the mod "Load Whole Map" with the "Peds Pack in HD", go to .ini (from Load Whole Map) and the "LoadPeds" function if you have "1" " put "0" because apparently some pedestrian(s) of this pack is having a problem and when loading it(s) it gives an error. If the problem persists giving errors while playing, it may be exactly because some model is buggy and so it's good to look for which one or remove the entire pack.
Problem 2: Possibly your PC's sound problem, DirectPlay. It could also be a ModLoader cache problem. Go to the folder "C:UsersTommyAppDataLocalmodloader" where "Tommy" is your username, and delete all content. Next time your game will take a while to open, but it will work.
Solution 2: Read Error: DSOUND.dll below...
Problem 3: Incompatibility of Grass Models.
Solution 3: Disable "ps2grassFiles" from SkyGfx1.ini (and other .ini of it)
Problem 4: Some problems related to ReShade (d3d9.dll/dxgi.dll).
Error: bass.dll
Type: Any error message related to it, or it is missing from your GTA after uninstalling SAMP.
Solution: Download bass.dll by clicking here, and install x86 (32 bits). I recommend downloading even if you don't have the problem, because some mods that use sounds or the SAMP .dll may have problems etc.
Error: quartz.dll
Problem 1: Incompatibility with new versions of Windows.
Solution 1: Enable Windows XP Compatibility Mode (Service Pack 2) in the game's .exe properties.
Problem 2: Related to Plugin LAV Video
Solution 2: (uploaded by Guto Rocha) In Start Menu > Programs > K-Lite Codec Pack > Configuration. Click on LAV Video. In the "Formats" tab, clear the boxes corresponding to MPEG1, MPEG2, and MPEG3 formats. Apply and ok. (tested on Windows XP and Windows 10).
Problem 3: It has been caused when installing mods in the Mod Loader root folder instead of installing folders inside it, which is an error.
Solution 3: Do not install mod files by leaving in "GTA San Andreas / modloader /", always install the files in "GTA San Andreas / modloader / some folder". There is more information right in the Modloader download post.
Error: colormod.asi
Problem: It has been caused by incompatibility with Project2DFX. Even if it doesn't make much sense and even though I used them both together a lot and I never saw a problem: you can try to uninstall either one to see if it corrects. As well as it can also be incompatible with some other mod or even bad installation of Color Mod.
Error: igdumd32.dll
Problem: This .dll is from Intel Graphics (your video card). It could be a problem with your PC's graphics drivers, simply a conflict between graphics mods, or a problem model or texture mod. It's hard to know the exact reason since it's about graphics in general.
Error: DSOUND.dll
Problem: DirectPlay
Solution 1: Use SilentPatch
Solution 2: Install DirectPlay by going to Control Panel > Programs and Features > Turn Windows features on or off (on the left of the window) > go to legacy components and check the DirectPlay box > install and restart the computer (tested on Windows 8.1 and fixed).
Error: normalmap.asi or NORMAL~1.ASI
Problem: Video card not supported? If your video card is very old, this is possibly the problem.
Error: colormod.asi
Problem: Incompatibility with Project2DFX
Solution: Uninstall it or it or Project2DFX.
Error: d3d9.dll
Problem 1: As you may already know, it's the .dll used for a lot of things, especially enb series, so everything sets it to WHAT you used it (where 99% of people use it as enb series or it already came in game installation ). It may be that your PC doesn't support the enb series or another graphical mod that uses this dll, but some mods are made using this dll, super old mods from the GTA SA release where they ended up using this .dll to create the mod, completely obsolete now, stop using such mods. If you don't use in series or other mods of this dll, it should be correctable by updating your DirectX Runtime, and then, if you have this dll installed in your game, delete it (or not).
Problem 2: If a crash in the Advanced menu of the game graphics and you are using 90s AVP Reborn, it was caused by his Super GT and the solution is simply to change this car. In the same way, you might not be using the 90s AVP but you might have this same car, or another car with the same problem, that is if this dll crashes in this menu, it could be a car installed in your GTA.
Problem 3: During an explosion? Using some mod like Remastered Effects? If you have any 0x007FDE14 and/or 0x007FE7DC and/or 0x004A140A in the "Backtrace" at the end of the log, it may be caused by IgnoreWater from MixSets (or even FreezeHour). So, if enabled, set these functions to -1 in MixSets.
Error: ntdll.dll
Problem: Difficult to know the exact reason as it is a very common Windows .dll. But it's more likely something to do with uploading files.
First of all, if the crash occurred when opening the game, simply try to open it one or two more times that should work. It's weird and I still don't know why yet. But this same error can be caused by other things:
Solution 1: At the end of "modloader.log", in the top line of the crash address, you will have the last file read, for example: "Loading default object types "datamapsveh_modsveh_mods.ide", in this example, possibly crashed when trying to read the veh_mods.ide file, check it. If the last file was a .txd, it was quite possibly not a problem with it. Also often it can't have anything to do, if you enter a store it will appear that "shopping.dat" was loaded last, but that doesn't mean that the crash was in this file too, so I'm not sure, but still try to check them, especially if the crash was when trying to open the game.
Solution 2: Check Windows permissions and file reads, it can be any file, whether from the data folder or some mod. I always recommend using GTA in Documents and not Program Files, to fix this and other problems.
Solution 3: If it crashed when selecting the radio "User Tracks", delete the file "sa-utrax.dat" from the folder "Documents/GTA San Andreas User Files". It is also possible that some .mp3 there is with the wrong encoding, GTA SA only accepts the MP3 LAME format. in this case, you can identify and remove such a CLEO mod that uses the CHDIR command, or change the radio by pause menu.
Solution 4: If SAMP crashed, check if "SAMP Fix" is marked in the ImVehFt .ini. Or if any files needed for SAMP to work are missing (in this case reinstalling SAMP will help)
Solution 5: If you see followed an error window "std.asi: translator.SteupASI failed to identify caller ASI", it is because it was the incompatibility of one .asi with another, mods .asi that modify the same thing as the other. I believe this was once due to vehlightsfix.asi along with silentpatch.asi, as they both fix some of the same things, but that was just a guess and also just an example.
Problem 6: Action_x86.dll incompatible with ntdll.dll.
Solution 6: Switch to 32-bit color resolution.
Solution 7: Uninstall HiDefCam.asi.
Problem 8: After minimizing the game?
Solution 8: Pause the game before minimizing, or if you have already paused it, it could be the mod SAGrading (colorcycle).
Solution 9: Try installing an Improved Fastloader.
Solution 10: The stream.ini file is missing from the game folder.
Solution 11: Don't use special characters (no punctuation etc) in the game folder name or somewhere along the path. Also, don't go too long. Has already been fixed after removing characters [ and . of the game folder name, but it is not exactly known if this was the problem, if the path was too long if it was some Windows bug, etc.
Freeze (usually flying with Hydra)
Solution: Open the game in administrator mode and Windows XP SP2 compatibility mode. It could be some mod, you don't know which one.
Game not re-installing
About: Trying to use the installer but it already identifies that the game is installed?
Solution: Open the start menu, type regedit and open regedit.exe. Go to HKEY_LOCAL_MACHINE -> SOFTWARE, there will be a "folder" Rockstar Games, and inside GTA San Andreas with a "key" inside it. Delete the key or the "GTA San Andreas" folder itself.
If not, look inside HKEY_CURRENT_USER.
Error: Message "Runtime Error!" "This application has requested the Runtime to terminate it unusually."
About: It could be caused by an error in some .asi mod. The modloader.log[b] or another crash dump can give a hint of what the mod was (even if not 100% correct).
During gameplay: In addition to .asi, it may have been caused by high memory usage if you configured the game to use 2GB of stream memory without using [b]largeaddress
When trying to start the game: In addition to .asi, it may be ModLoader's cache problem. Go to the folder "C:UsersTommyAppDataLocalmodloader", and delete all content. Next time your game will take a while to open, but it will work.
it took time to write all this, if you have something to suggest/discuss drop a comment in the comments section.
Other useful blogposts:
Arcade Games | Custom Fonts | Stalls Location | Forum Titles | Website BBCode | Random Packages | Fish Species | Shell Game | Kitty Claw | Epsilon Program | Computer sites | Storage Lockers & Pawn Shop | Drug Base | Datacenter | Mafia Money | Drug Plane | SF | Drug Plane | LV & Airfield | Drug Plane | LS | Drug Delivery | SF | Drug Delivery | LS | Newspaper Events | Contacts | Diploma + Benefits |
Fixes & Methods for Problems in-game:
Advanced Crash Codes & Fixes - Part 1 | Basic Crash Codes & Fixes | Crashes Solutions | Game Freeze Solutions | Common Problems Solutions | Solution to 'unable to excute' error |
3959
Comments (11)
Recent contributors
Latest post
Request your own Forum Signature
Popular blogs
Mano's Blog
Latest post
sensfix [NO CLEO]
The Player Guide
Latest post
Pickpocketing - FiveM
Unusual blog
Latest post
Vehicle colors ID ULTIMATE BLOG POST
Kazuha's Blogs
Latest post
Request your own Forum Signature
© 2008 - 2024 GTA-MULTIPLAYER.CZ. All rights reserved.
good job