Jump to content
  • 0

Client.dll error.



Hi, I recently started having this problem while playing the game, the game crashes shortly after staying on a server for a certain time, sometimes even within a few seconds and it becomes quite annoying. I have reinstalled MTA several times and the problem continues, I scan my PC for a possible virus but everything is in order. What problem can it be? I have thought that maybe it is some incompatibility with Intel drivers, maybe that is it. Help!


Link to comment

3 answers to this question

Recommended Posts

  • 0
  • MTA Anti-Cheat Team

Well, only 2 other MTA users besides you are getting this crash on offset 0x0002A51C, it's rare. But when i analyzed the crash, it didn't make me much wiser:


CONTEXT:  (.ecxr)
eax=73f1824c ebx=00000101 ecx=2c67a1b0 edx=1b520820 esi=00000c20 edi=1d064a80
eip=2d617467 esp=0177f960 ebp=0177f978 iopl=0         nv up ei ng nz ac pe cy
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010297
2d617467 0000            add     byte ptr [eax],al          ds:002b:73f1824c=b0
Resetting default scope

ExceptionAddress: 2d617467
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 00000008
   Parameter[1]: 2d617467
Attempt to execute non-executable address 2d617467

PROCESS_NAME:  gta_sa.exe


2d617467 0000            add     byte ptr [eax],al

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.




IP_ON_HEAP:  2d617467
The fault address in not in any loaded module, please check your build's rebase
log at <releasedir>\bin\build_logs\timebuild\ntrebase.log for module which may
contain the address if it were loaded.

WARNING: Frame IP not in any known module. Following frames may be wrong.
0177f95c 73c7a51c     1b520820 107f44e8 73ca0d55 0x2d617467
0177f968 73ca0d55     1b520820 00000101 0177f99c client!CClientColManager::DoPulse+0x1c
0177f978 73c8e882     0177fa01 00000001 00186f00 client!CClientManager::DoPulse+0xc5
0177f99c 73c8f296     00000001 c5da3ec9 1b520820 client!CClientGame::DoPulses2+0x152
0177faf4 73c8e3bb     c5da3f4d 01acc9f8 01b701e8 client!CClientGame::DoPulses+0x9f6
0177fb70 74b0bc33     01acc9f8 06783f00 74ac40f2 client!CClientGame::DoPulsePostFrame+0x6eb
0177fb7c 74ac40f2     c36eed4a 067e2748 06783f00 core!CModManager::DoPulsePostFrame+0x53
0177fc6c 74b6de84     c36eed96 067e2748 00000000 core!CCore::DoPostFramePulse+0x8b2
0177fcb0 74b75070     06783f00 052a98f0 007f99b0 core!CDirect3DEvents9::OnPresent+0x164
0177fd14 007f9b12     067e2748 00000000 00000000 core!CProxyDirect3DDevice9::Present+0x30
0177fd38 007fb1c3     052a98f0 00100540 00000000 gta_sa+0x3f9b12
00000000 00000000     00000000 00000000 00000000 gta_sa+0x3fb1c3

SYMBOL_NAME:  unknown!printable+0

MODULE_NAME: unknown!

IMAGE_NAME:  unknown.dll

FAILURE_BUCKET_ID:  SOFTWARE_NX_FAULT_c0000005_unknown.dll!printable

All we can tell is that it might be related to collisions (i suggest that you make sure your game is clean, by re-installing a version without mods) or from something on your PC interfering with the game, as it's NX fault and that is a processor security feature, besides the exception being triggered from outside MTA. Because of the crash rarity, it's clearly not an MTA bug that results in NX fault.

Check all of your drivers, update them, scan your PC for viruses.. and if nothing helps, try disabling said security feature in your PC's BIOS, google for how to turn off "Intel NX / eXecute Disable bit / XD", its exact naming can vary per BIOS. Basically, it's the "Enter setup" key that you can press when most PC's are booting up. But it will be a security risk, especially if a virus is causing the problem, it can then cause an overflow in various software, opening up even more possibilities for the virus to control your system.

Edited by Dutchman101
  • Like 1
Link to comment
  • 0

@Dutchman101 I have found a solution, in the end it was not a problem with viruses or drivers, more than anything it was the processor. It was an overheating issue that caused this error to be seen frequently. A change of thermal paste and a little more ventilation was the best solution, the problem no longer appears to me. Thank you very much.

  • Thanks 1
Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...