Las Venturas Playground
Crash addresses: Reasons and Solutions - Printable Version

+- Las Venturas Playground (https://forum.sa-mp.nl)
+-- Forum: Main Talk (https://forum.sa-mp.nl/forum-3.html)
+--- Forum: Development (https://forum.sa-mp.nl/forum-16.html)
+--- Thread: Crash addresses: Reasons and Solutions (/thread-28383.html)

Pages: 1 2

Crash addresses: Reasons and Solutions - Jay - 11-06-2011

List of client crashes along with their cause and solution. To be updated. Will be published here and on SA:MP forums when a significantly sized list is compiled.


Rare

0x00000000 - SA-MP is not initializing. Solution:: Re-install the game, ensure singleplayer works. If you have any mods installed, remove them.

0x006E3D17 - Skin related. Often occurs when changing the skin of a player who is in a vehicle, or is just entering or exiting one. Solution: Ensure the player is on foot before changing their skin.

0x0058370A - Vehicle related. Occured when the script attempted to put the player in a vehicle. The vehicle the player is being teleported into is not yet available and/or rendered in the world. Solution: Wait a few milliseconds before teleporting a player into a vehicle that is newly created. Another solution would potentially be to use SetCameraBehindPlayer prior to teleporting them to the vehicle.

0x0040F64C - Issue with Windows 7. Solution: Update to SA:MP 0.3d. If it still occurs, rename your GTASA directory.

0x0059F8B4 - Occurs when client fails to load SA-MP objects. Solution: Click

0x00746929 OR 0x0081214A - Badly configured client side setting. Solution: Click

Frequent

0x007F0BF7 -> Related to vehicle upgrades. Often caused when the server attempts to put an invalid upgrade on a vehicle (EG nos or spoilers on a motorbike). Other causes could be bad client side vehicle mods.

0x00544BC8 - Object related. Too many objects are showing for the player. Solution: Use a streamer to fix this and lower the maximum amount of visible objects for players at a time.

0x00415D47 - Object related. Occurs when the client has a lot of objects on show. It's somehow related to collisions but extremely hard to trace and fix. Solution: It occurs randomly depending on the object. Remove groups of objects and use the process of elimination to establish which objects are causing it and remove them from your script.



Ingame warning codes

Warning(s007) Exception: 0x0000005 at 0x534134 - This is an issue in Windows 7 / Vista.  Solution: Run SA-MP as administrator

Warning(s007): Exception 0xC0000005 at 0x5E5815 - Difficult to trace. The method this address points to does a whole load of things.  It processes animation blending based on the surface the ped is standing on and then deals with audio, and is called right after a function which *gives* you weapons... Perhaps what happened here is that some script-invoked event occurred right at the moment that you were entering a vehicle (e.g. receiving a weapon, teleporting or something similar).

Warning(opcode 0x107): Exception 0xC0000005 at 0x544BC8 - See 0x00544BC8
Warning(opcode 0x107): Exception 0xC0000005 at 0x536DF4 - See 0x00544BC8

Re: Crash addresses: Reasons and Solutions - Peter - 11-06-2011

0x58370A
This is a function which determines the player's camera facing-direction prior to rending the radar in the HUD. If the camera mode is 16, presumably something vehicle-related, it retrieves the Entity which the camera is tracking and fetches it's location matrix. As the Entity, for whatever reason, could not be retrieved, there is a null pointer exception. In human talk: the vehicle the player is being teleported into is not yet available and/or rendered in the World.

Potential fix is to call SetCameraBehindPlayer() just after the player has teleported in or out a vehicle.

0x415D47
This is some deep function in GTA's collision resolving system. Hard to triage, but definitely object related. Only plausible solution is to bisect the offending object.

Re: Crash addresses: Reasons and Solutions - Pedro - 11-06-2011

Rare (Occurs one time in 50)

0x0058370A - This bug's not new, it used to happen on the previous gamemodes as well. It occurs when the player reaches the last checkpoint of a race or when exports a vehicle. In this case I was exporting vehicles, I'm not sure if the cause of the race's bug can be the same, but since both happen exactly after reaching a checkpoint, it may be.

Re: Crash addresses: Reasons and Solutions - Jay - 11-06-2011

Thanks, updated! :>

Pedro: That crash address you posted is the same one that Peter just explained :+

Re: Crash addresses: Reasons and Solutions - Pedro - 11-06-2011

LOL right, sorry then. :+ When I started writing my post Peter hadn't posted his post yet, and then I didn't compare the adresses ahah

Re: Crash addresses: Reasons and Solutions - Richard - 01-03-2012

Bit of a bump, but I suppose this is a good place.

We were playing robbery and I was on defend. I went to the hunter and when I was about to get in (I pressed my enter vehicle key), I crashed. I didn't think anything of it and rejoined without checking my logs.
New game, attack this time. I spawn, and crash right away.

This is what I got:

Quote:[22:20:42] * Use the ! prefix to talk to your team.
[22:20:42] Enter the casino via either the roof or main entrance to begin.
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x4D1750
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x5E5815
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x5E5815
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x5E5815
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x5E5815
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x5E5815
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x5E5815
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x5E5815
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x5E5815
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x5E5815
[22:20:43] Warning(s007): Exception 0xC0000005 at 0x5E5815

Pedro crashed with me, but he didn't get any errors.

Re: Crash addresses: Reasons and Solutions - Peter - 01-04-2012

0x5E5815 is located a function called by in CPed::ProcessControl (0x5E8CD0) right after a call to RpAnimBlendClumpGetFirstAssociation, which requests RpAnimBlendAssociation->sAnimID. Given that RpAnimBlendClumpGetFirstAssociation returns a pointer and sAnimID is requested on the [tt]eax[/tt] object (return value), and RpAnimBlendClumpGetFirstAssociation may return NULL if RpAnimBlendClumpIsInitialized equals false, Rockstar failed to add a NULL-check here and assumed that a proper value would be returned.

The method does a whole load of things. It processes animation blending based on the surface the ped is standing on and then deals with audio, and is called right after a function which *gives* you weapons. What I think happened here is that some script-invoked event occurred right at the moment that you were entering a vehicle (e.g. receiving a weapon, teleporting or something similar).

Re: Crash addresses: Reasons and Solutions - Richard - 01-04-2012

In other words, nothing we can do about it?

Re: Crash addresses: Reasons and Solutions - Richard - 01-05-2012

And another.. this happened when the robbery ended. I got spawned back around ship and crash. Nothing in my log this time, just the crash report:

Quote:SA-MP 0.3d-R2
Exception At Address: 0x0081214A

Registers:
EAX: 0x00000002 EBX: 0x00000079 ECX: 0x0000001C EDX: 0x00000000
ESI: 0x00000002 EDI: 0x0D3A0AB0 EBP: 0x004C88B0 ESP: 0x0027FB7C
EFLAGS: 0x00010287

Stack:
+0000: 0x004C88BB  0x00000002  0x0000000C  0x0074C7B7
+0010: 0x00000002  0x00000079  0x181A9190  0x126F467C
+0020: 0x004C9430  0x00000079  0x004C9448  0x00000010
+0030: 0x004C88B0  0x00000079  0x126F4400  0x00749B93
+0040: 0x126F467C  0x00000079  0x0000001A  0x0AC3C658
+0050: 0x76882AE6  0x00000000  0x004C9834  0x181A9188
+0060: 0x004C9430  0x00000079  0x006D64E9  0x3DF98197
+0070: 0x0AC3C658  0x3DF98197  0x006AAB76  0x0000001A
+0080: 0x00000044  0x76882AE6  0x00000000  0x00542D86
+0090: 0x399AC11D  0x3F7FFF84  0xBB7B25FA  0x0AC3B228
+00A0: 0xBD9D46E1  0x3B7BE469  0x3F7F3DFA  0xBAC7A020
+00B0: 0x00000000  0x00000000  0xBAE60E32  0x80000000
+00C0: 0x1254BF10  0x00000000  0x3C4B4A74  0x3F1FBBD3
+00D0: 0x3BAC6023  0x110D9110  0x3C4B4A74  0x3F1FBBD3
+00E0: 0x3BAC6023  0x00000000  0x44FFB440  0x44B6F0F2
+00F0: 0x00000000  0x3E8D2057  0xBF76153F  0x0B53E680
+0100: 0x3CABC6BE  0x3F7FC251  0xBD1B8954  0x3FEC8B44
+0110: 0xBE10624E  0xBE20C49C  0x3CABB465  0x3F7FC254
+0120: 0xBD1B8959  0x80000000  0xB3CFBD54  0x34B51E55
+0130: 0x3F800000  0x3F800000  0x35351E55  0x344FBD54
+0140: 0x00536B7D  0xB5351E55  0x3F800000  0xA992F97A
+0150: 0x00000000  0xB44FBD54  0xA992F97A  0x3F800000
+0160: 0x00000000  0x00000000  0x00000000  0x00000000
+0170: 0x00000000  0x0027FD40  0x00000000  0x3F800000
+0180: 0x35351E55  0x344FBD54  0x00542D86  0xB5351E55
+0190: 0x3F800000  0xA992F97A  0x0AC3B228  0xB44FBD54
+01A0: 0xA992F97A  0x3F800000  0xBAC7A020  0x00000000
+01B0: 0x00000000  0x00000000  0x80000000  0x00000000
+01C0: 0x00000000  0x3F800000  0x35351E55  0x344FBD54
+01D0: 0x4501BC94  0xB5351E55  0x3F800000  0xA992F97A
+01E0: 0x44B2FC7C  0xB44FBD54  0xA992F97A  0x3F800000
+01F0: 0x00000000  0x00000000  0x00000000  0x00000000
+0200: 0x00000004  0x0027FF78  0x008480D6  0xFFFFFFFF
+0210: 0x0055394D  0x0000001A  0x00000001  0x00000000
+0220: 0x0053EA03  0x44200000  0x44000000  0x0053ECC2
+0230: 0x00000001  0x00619B71  0x0000001A  0x00000001
+0240: 0x00000001  0x0000000A  0x00748DA0  0x0000001A
+0250: 0x00000001  0x75021D07  0x00000000  0x0027FF88
+0260: 0x7EFDE000  0x012C0000  0x4F7E37C1  0x002C1128
+0270: 0x00000008  0x00000100  0x00000008  0x0000011A

SCM Op: 0x6BD, lDbg: 0

Game Version: US 1.0

State Information: Ped Context: 0
P0 (0,0) P1 (0,0) P2 (0,0) P3 (0,0)
P4 (0,0) P5 (0,0) P6 (145,0) P8 (192,0) P9 (0,0) P10 (192,0) P11 (145,0)
P12 (0,0) P13 (145,0) P14 (147,1094) P15 (145,0)
P17 (0,0) P18 (0,0) P19 (0,0)
P20 (147,33) P21 (147,34) P22 (145,0) P23 (0,0)
P25 (0,0)


Re: Crash addresses: Reasons and Solutions - Jay - 05-03-2012

Updated \o
Few more and I'll publish it :)