Jump to content
  • 0




2 answers to this question

Recommended Posts

  • 0
  • MTA Anti-Cheat Team

MTA is closing without crash handler, that makes it unlikely there'll be crash dumps, but please check anyways (in the folder C:\Program Files (x86)\MTA San Andreas 1.5\MTA\dumps\private). If there are dumps, zip them and upload to http://upload.mtasa.com/, then share the link in this topic.

But those dumps, if present, will only help us to understand the nature of corruption present on your PC, or which of your hardware is failing. The reason being that MTA cuts out with exception code 0xC0000409 which stands for "STATUS_STACK_BUFFER_OVERRUN" and that's usually caused by things like viruses or hardware damage (like RAM sticks - you could already go run memtest86 ahead of this) as other MTA users don't have such crashes, and neither did you until very recently.

So for the latter reason, you might find it useful to recount what changed lately on your PC (e.g installed software with viruses that potentially interfere with MTA.. hardware changes, such as replaced parts.. or game mods) and definately also run a full anti-virus & malware scan.

Furthermore, according to your MTADiag log, Windows Error Reporting has detected "bad_module_info" (according to the web, not rarely tied to hardware or RAM issues) fault on client.dll, an MTA file.. that goes along with the parameter 0xC0000409 so clearly it's affected by the same STATUS_STACK_BUFFER_OVERRUN issue, or it is what directly causes MTA to close. So please also follow Zango's advise, as corrupted data files of software that encounters said exception may also be the reason for it to happen.. and yeah, then viruses can be behind said corruption on files it sees fit to modify. So it's worth uploading "client.dll" from Program Files > MTA San Andreas 1.5\mods\deathmatch to https://www.virustotal.com/ before you re-install MTA, then share the link with us in case it raises detections, which would identify the virus that infected your PC.

Note that I didn't include suspecting "game mods" earlier for no reason.. something that's very incompatible with MTA and manipulating its execution too much can always cause weird things to happen. So again, really think of what you changed lately, and try with a clean, original GTA installation as well. Such as that you definately are having mod problems, as this WER entry is listed in your MTADiag log as well:

P1: gta_sa.exe
P3: 427101ca
P4: std.stream.dll_unloaded
P6: 5a5e2bf5
P7: 000616e8
P8: c0000005
P9: 00000008

std.stream.dll is a file from game mods and already caused your GTA to crash. So it's definately a point of attention.


Link to post

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