Jump to content
  • 0

MTA crash error code 0xC0000005 and direct3D error 8007000e


arielszz

Question

Posted

Since updating to version 23952, I've been experiencing constant crashes. I don't know exactly what's happening. I've already reinstalled MTA, switched to a completely original GTA version, and the crashes continue. I've tried windowed mode and fullscreen mode, and it crashes the same way. When I'm in windowed mode, the game freezes and closes, displaying the following error:

Version = 1.6-release-23953.0.000 Time = Sun Mar 8 17 08 2026 Module = C:\ProgramData\MTA San Andreas All\1.6\GTA San Andreas\gta_sa.exe Code = 0xC0000005 Offset = 0x00354D23 EAX=A2EC1846 EBX=0000000F ECX=0000002A EDX=00000005 ESI=0177FB10 EDI=00008843 EBP=0000002C ESP=0177FA1C EIP=00754D23 FLG=00210282 CS=0023 DS=002B SS=002B ES=002B FS=0053 GS=002B InvalidParameterCount = 0 CrashZone = 0 ThreadId = 7624 Precise crash time: 2026-03-08 17 08.175 Exception Type: SEH:AccessViolation Exception: Access Violation - Invalid memory access Resolved Module Path: C:\ProgramData\MTA San Andreas All\1.6\GTA San Andreas\gta_sa.exe Resolved Module Base: gta_sa.exe Resolved Module Offset: 0x00354D23 Additional Info: Allocation telemetry: requested=0 bytes (no tagged context available) CrashTelemetry::Scope annotations: none executed on this thread before crash; instrument entry points to capture context. Fatal Exception: Yes Stack trace: gta_sa.exe+0x354D23 [0x754D23] gta_sa.exe+0x3C9469 [0x7C9469] [Fallback Stack Trace] #00 0x754D23 [0x754D23] (gta_sa.exe+0x354D23) #01 0x7C9469 [0x7C9469] (gta_sa.exe+0x3C9469) Reason: Access Violation - Invalid memory access at gta_sa.exe+0x00354D23 (ThreadId=7624)

When I'm in full screen mode, the game typically crashes when I minimize or open MTA, and the following error appears:


spacer.png


Another thing I've noticed is that often, just before crashing, my game starts to have shader or DX glitches. For example, if there are custom maps like in F11 or the minimap, it starts to turn completely black as if it's not loading the information. Or, if there are DX panels, instead of having their background color, they become invisible, showing only the text but not the background images. If you can help me with this, I would appreciate it. I've already reinstalled DirectX 9 and the DirectX End-User Runtime, but it's still the same. I don't really understand what's happening or where the problem is.

2 answers to this question

Recommended Posts

  • 0
Posted

👋 @arielszz  The crash log and the graphical symptoms point more to a Direct3D / memory-related issue than to a broken GTA installation.

The important part here is the Direct3D error 0x8007000E, which usually means E_OUTOFMEMORY. Combined with the black minimap/F11 textures, missing DX panel backgrounds, and crashes when minimizing in fullscreen, it looks like the client is running into a rendering/device-reset problem, VRAM exhaustion, or something interfering with DirectX.

Since you already tested:
- a clean MTA reinstall
- a clean original GTA installation
- windowed and fullscreen
- DirectX 9 / End-User Runtime reinstall

then I would suggest checking these next:

1. Disable all overlays/injectors completely
   - Discord overlay
   - GeForce Experience / NVIDIA overlay
   - MSI Afterburner / RivaTuner
   - ReShade / ENB / graphics mods
   - Overwolf / recording overlays

2. Do a clean GPU driver reinstall
   Use a clean installation for your graphics driver, because this looks more like a rendering pipeline issue than a GTA file issue.

3. Reduce video memory usage
   - lower resolution
   - disable anti-aliasing
   - reduce draw distance
   - avoid heavy custom shader servers for testing
   - remove custom HUD/map resources temporarily if you are testing locally

4. Avoid minimizing in exclusive fullscreen
   Since it crashes very often when minimizing, borderless/windowed mode is safer for now.

5. Reset MTA client settings/cache
   Delete the local MTA cache/settings folder and let the client recreate it.

6. Test with another GPU driver version
   If the issue started exactly after updating to build 23952/23953, it may be a compatibility issue that only shows up with a specific driver version on your hardware.

7. Share MTADiag and full specs
   GPU model, driver version, RAM amount, Windows version, and MTADiag would help a lot. Without that, it is hard to tell whether this is a client regression or a local graphics/driver problem.

In short: this does not look like a simple corrupted GTA install. It looks more like Direct3D memory/device instability, especially because the DX elements start disappearing before the crash.

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