Dutchman101

No one likes hackers, we keep MTA free of them. Too bad for you as you underestimated MTA's anti-cheat strength And you are a hack developer yourself (currently banned, and all of your hacks were detected since day 1) so you ain't got no right to speak either. PM ccw with the source of your hack. You're just as bad, but it seems you don't like your fellow cheaters. Locked

Download RWAnalyze and use it to open the .dff file, then find "ZModeler lock" somewhere (usually around the bottom of list) and delete the node. You can also use Z2G DFF converter to automatically remove any lock. RWAnalyze: https://www.gta-modding.com/area/file-33-rw-analyze.html Z2G DFF converter: https://www.gta-modding.com/area/index.php?act=view&id=1251 (drag the DFF file into the .exe to start converting) If you cannot find a "Zmodeler lock" then the DFF has been locked in another way. You can try these tutorials: 1) https://www.youtube.com/watch?v=g54VneOeUVc (applies to a type of lock where you see only 1 clump and 1 struct in RWAnalyze) 2) https://www.youtube.com/results?search_query=dff+unlock (try to identify what type of lock it has and find a targetted unlocking tutorial). Please only use that procedure with models where you got permission of its authors to edit it, locks are often there for a reason. @Bozz

Please download and run MTADiag and follow the instructions. Post any Pastebin URL MTADiag gives you in this topic. Looks like something's wrong with your GPU (driver) judging from the crashing module. @Tawsif

Moved to the correct section, @StormxD Please review the regulations for this section. If you don't apply them within 24 hours your topic will be removed.

Specific to this issue, please read: https://forum.multitheftauto.com/topic/90196-cl33-error-mtasa/#comment-819400 and https://forum.multitheftauto.com/topic/96298-mta-error-cl33/?do=findComment&comment=862079 Your PC is probably infected, with this as result. Regardless, please post your log

Please download and run MTADiag and follow the instructions. Post any Pastebin URL MTADiag gives you in this topic. @wycked.

Make sure to also install the OEM drivers for Intel HD onboard graphics. Your laptop has both that and the dedicated AMD GPU. If the issue is related to this (as there's improvement) then it's a bad idea to use OEM AMD driver in combination with generic latest Intel HD drivers.

Several others with the same Error 5: access denied were running AVG anti-virus, just like you. AVG is probably causing it, whitelist MTA & GTA or disable/uninstall AVG. Inform us of the results, @Slammer

Ukrainian translations were added, download this build: https://nightly.multitheftauto.com/?mtasa-1.5-rc-latest Thanks for contributing.

Uninstall or completely disable any Razer software as much possible; for example Razer Gamebooster, Razer Gamecaster Engine (overlays, even passive, can interfere with your graphics driver), Razer Synapse, Razer Game Manager and preferably the whole Razer Cortex/Central package at once. Also delete "Driver Support AO" and anything related to it, this kind of software does more harm than good. I wonder how your primary GPU model has magically jumped from Radeon R5 M230 to showing as Radeon HD 8500M. Also while this is supposed to be the primary GPU (dedicated one), MTA seems to pick the weaker on-board Intel HD graphics as preferred GPU. After uninstalling the software I mentioned, enter both control panels of Intel and ATI/AMD and make sure to reset all configuration and settings to default, because said software may have modified it. After doing that, open up commandprompt (cmd) as Administrator and enter the following: dism /online /cleanup-image /restorehealth Reboot your PC when finished, open up cmd once again, and this time run: sfc /scannow and wait for it to complete. Now, zip up the most recent .dmp file from C:\Windows\Minidump and upload it to http://upload.mtasa.com (share the link here) as the BSOD you had recently can tell us more about your system issues which are related to the flickering problem. If you notice that before I respond to your new post, that none of these steps have worked, then you can proceed to install OEM drivers for your laptop model (Lenovo 20351, IdeaPad G50-70) from the manufacturer's driver support site. The reason is that just like with Nvidia optimus, sometimes generic latest drivers can cause severe problems because of OEM-specific modification incompatibility. This has been described for example on a Microsoft forum post, in which user "Th3r_365" discovered the problem. This is similar to your case with ATI, because once again, your weaker Intel HD graphics is picked as primary GPU for gaming, which shouldn't happen. So eventhough it's a shame, it's worth trying to use outdated drivers for both Intel HD and your Radeon GPU tailored for your specific laptop model. In your case you can get them from Lenovo driver page for G50-70 (model 20351)

Let's get back onto this topic after PM'ing back and forth with initial steps.. 1) download and extract https://www.wagnardsoft.com/DDU/download/DDU v17.0.8.4.exe 2) choose to delete Intel drivers in the DDU dropdown first, then after a reboot launch DDU again and also wipe ATI / AMD drivers. Now that all traces for both your GPU's drivers are completely gone, install the following drivers in sequence: - https://downloadmirror.intel.com/27267/a08/win64_154037.4835.zip - https://www2.ati.com/drivers/beta/win10-64bit-radeon-software-adrenalin-edition-18.3.4-march23.exe Let me know if this solves the problem, and if not, generate a fresh MTADiag log to post here, @-ffs-iRenox

What's the current server process memory usage? Please show a printscreen of that. Open each and every view in /ipb and make a screenshot compilation to upload, so we have everything possibly needed.

Show the "server" resources usage, not client.

There are servers on 1.5.5 with over 400 players on average that only collect just over 1GB in ram usage over several months. I have never heard of a server process using close to 16GB and still running, as you claim is the case. I don't think your problem relies on starting to use 1.5.5, it may be that something else on in your server environment has started interfering at that point though, as a result of the update. There must be something going on and it's a problem on your side. Are you running any custom modules? Also show us screenshots of the tables in performancebrowser

Reasons for your last 4 crashes: 1) offset 0x003C91CC (gta_sa): out of video memory 2) offset 0x00349B93 (gta_sa): bad model (your gta3.img mod or server mods) 3: offset 0x001D23AC (core.dll): out of memory (RAM) 4: offset 0x0031F760 (client.dll): out of memory (RAM) As you do have a 64-bit OS: in cases like this it's either too low amount of RAM/too basic graphics card, bad memory (like damaged RAM sticks prone to faults) or playing intensively on servers with a myriad of inefficient, bloated models (those who typically have over 1GB client download) most of the times combined with a not too high-end PC. But in your case.. you have 8GB of RAM, and a pretty decent GPU. I would blame it on software system issues I can see in your log or otherwise playing in the type of servers that I described for hours. Download & run this file: https://mirror.multitheftauto.com/mtasa/utils/servicing.bat (rightclick > Run as Administrator) to try solve underlying system issues. Also removing those modded GTA sound files could help, some of them look corrupted (nearly empty, and one is missing entirely) which perhaps results in some kind of memory leak. What you can also do is monitor your memory usage while playing (use /showmemstat and take a screenshot every 20 minutes, then post it here creating a graph indicating the point it crashed) and tell us which servers you usually play and for how long at a time. Note: besides bloated mods, the memory usage resulting in this kind of crashes can also be caused by bad scripts (abusing certain functions, creating memory leaks..) a good example of that is https://bugs.mtasa.com/view.php?id=9833 where it's demonstrated how one of the crashes listed above that you experienced can be caused by a script. If you have one certain server where you constantly crash on, it's a good idea to also contact the server owner besides troubleshooting on your own.

Do never underestimate the speed we can patch new cheats with. We know what you have tried to use, ofcourse you're innocent. Tried to use the same as https://forum.multitheftauto.com/topic/103859-unban-request/

I had this issue myself (like in your video) a few years ago and because we could retrace to where it was related to, MTA made some improvements to how vertex buffer locking/flushing was done, as investigating the issue revealed shortcomings with that. However, the issue in that case wasn't solved, and much later I discovered it were GPU hardware problems, I had been experimenting with flashing different videocard BIOS (vbios) version onto my card, which tripped something. The GPU problems (or damage) that can cause this kind of graphical corruption can have more causes though. By writing this I assume your own troubleshooting (you said having re-intalled etcetera) was done properly, and in that case I'd have further advice for you: RMA your videocard under warranty. But again, that was my assumption, and I will still try to help you and see if the possibilities are really limited to GPU hardware problems; Please download and run MTADiag and follow the instructions. Post any Pastebin URL MTADiag gives you in this topic @-ffs-iRenox

Try with https://nightly.multitheftauto.com/?mtasa-1.5-rc-latest and let me know @LookaT

It's a bug in MTA triggered by your odd Windows username "ãðéàì", it hangs trying to draw a FFS lobby .jpg file because DirectX fails to copy it to a temp folder at a path under your username so that MTA can display it using DxDrawImage. MTA should be able to handle folders under usernames like yours, so it will be fixed and if you keep an eye on this topic, I will let you know when it's done. Side note: guess that username wasn't intended like that, it has possibly been corrupted by a virus in the past.. not to say MTA should be able to handle usernames composed of a mix out of several different language's unusual characters. @LookaT

Please download and run MTADiag and follow the instructions. Post any Pastebin URL MTADiag gives you in this topic @LookaT

It's either your net, that server or the latency or routing between you and the server. If you intended to imply it's MTA then you are wrong, since MTA has state-of-the-art sync that surpasses most commercial games. I will try to help you locate the problem though. Please download and run MTADiag and follow the instructions. Post any Pastebin URL MTADiag gives you in this topic.

Create a new text file (simply .txt with notepad) named "debug" in MTA installation folder (e.g C:\Program Files (x86)\MTA San Andreas 1.5 > debug.txt) Now when the game freezes, hold CTRL left + CTRL right simultaneously. This will force a crash, and if you provide us with the crashdump then we can retrace what caused the freeze. After it crashed, go to C:\Program Files (x86)\MTA San Andreas 1.5\MTA\dumps\private and zip up its contents (or just send the latest dated .dmp file). Upload it to https://upload.mtasa.com and share the link in this topic please @LookaT

I suppose you meant MTA 1.5.5, and the netcode is closed source so you'll have to take the net module(s) from the latest release. If you're building MTA from master (or master as base) you should take the net module from latest nightly. Just take it from the nightly release closest to where your modified repository is based on. @Neff Also if you're really trying to build 1.5.4 (don't really see a reason, the latest release would be recommended) then for the same reason you should get a 1.5.4 nightly and take the module from there, if you don't that error may result.

I see you have modded GTA sound files, this is the most likely culprit. Re-install with a clean GTA or else restore them to default. Also, update your sound driver: https://www.dropbox.com/s/wm0ofs2akbc4a2j/IDT_audio_drv.zip?dl=1 (follow the readme.txt instructions inside) If you still have the problem after taking these steps, then please create your own topic in Client support as I have asked before. To prevent further posting here, locking it. Anyone who reads this should also understand the instructions and driver links are tailored to that specific user and PC, as this seems to be the first result coming up in Google for MTA sound problems. Everyone is welcome to open up their own topic to get help.

Runcode isn't capable of making the edits to "admin" shown above, which have led to your problem. You have trusted someone to edit it, or gave access/have bad security. The only way of solving this issue is doing as I said; locate and remove the illegitimate edits or update to the latest admin panel.