FiveM for GTAV Enhanced — Reproducible client crash (6/6) while driving/moving
SUMMARY
Deterministic client crash reproduced 6 out of 6 times, always in a solo
session (no other players connected — ruled out a remote “crasher” client).
The crash happens after roughly 1-4 minutes of driving / moving around the
map. It is NOT tied to any specific vehicle (happens with stock/vanilla
vehicles too, not only addon ones), and — importantly — it also happens on
sessions where NO vehicle-handling warning appears in the console at all
(see below), which rules out vehicle data as the direct trigger.
CRASH SIGNATURE (identical in all 6 dumps)
Exception code : 0xC0000005 (STATUS_ACCESS_VIOLATION)
Module : GTA5_Enhanced.exe
Offset : +0x1D53D9C (one dump landed at +0x1D53D8E, 14 bytes off —
same code region)
Game build dir : gamecache_gen9\1158_16
Dump files included (dumps/):
- c34c0b63-e66a-4357-9826-f9ca5a702dc4.dmp (2026-09-23 19:17:20 local)
- 4e5f48ae-fb9c-456c-9196-47a815bc3939.dmp (2026-09-23 19:23:39 local)
- 061a6ade-5625-4d85-b14c-59b789626d03.dmp (2026-09-23 19:41:06 local)
- 5b5be6ad-77780962-05ef-4a86-9527-4fd6d2bcab18.dmp (2026-09-23 20:08:20 local)
- 6282492d-81ad51c1-ef6c-4210-9dfa-bc800a684032.dmp (2026-09-23 20:19:34 local)
- 9f1e12cd-e5ea3d5d-bd09-42ad-a423-6667536272ac.dmp (2026-09-23 20:53:48 local)
All six were parsed manually (minidump module list + exception stream) since
no debugger with GTA5_Enhanced.exe symbols was available locally. Happy to
provide the parsing script or raw stream dump if useful.
RELIABLE PRECURSOR: net thread stall, always immediately before the crash
In all 6 sessions, the client log shows this exact pattern right before the
crash, with no exceptions:
[warning] net thread warning: timer interval of Nms milliseconds
[warning] net thread warning: timer interval of Nms milliseconds
[critical] The application has crashed!
Observed N values across sessions: 494ms, 193ms, 209ms, 290ms, 302ms (normal
tick budget should be far below 100ms). This is the one consistent signal
across every single crash.
RULED OUT: vehicle handling data (initially suspected, now disproven)
In 2 of the 6 sessions, shortly (30-90s) before the crash, the console also
showed:
[error] Got invalid traction curve max X, min Y.
(e.g. “max 2.1625457, min 2.2830484”, “max 2.2704961, min 2.346”)
We initially suspected this was the trigger and investigated it heavily:
-
Audited every handling.meta on the server (89 files) for
fTractionCurveMax < fTractionCurveMin on disk. Found and fixed one
genuinely broken file (razor-thin 0.01 margin on a motorcycle, vs 0.1+ on
every other vehicle) plus two unrelated handlingName collisions between
resources (two different vehicle variants sharing the same handling
struct name) and one resource shipping a vehicles.meta that redeclared
~300 stock/vanilla vehicle models (very likely leftover from using the
base game’s file as a copy-paste template) it had no business touching.
All of these were real, independently worth fixing bugs. -
Confirmed no script other than our own vehicle-tuning job ever calls
SetVehicleHandlingFloat on those fields, and confirmed via session logs
that tuning job was never even invoked in the sessions where the crash
happened. -
Despite fixing all of the above, crash #6 reproduced identically with
ZERO mentions of “traction curve” anywhere in that session’s log, and
with the tuning job again unused. This proves the traction-curve warning
is a parallel/unrelated symptom, not a precondition for this crash.
Given this, our current best assessment is that this is a genuine engine-
level bug in the Enhanced early-access client, related to a main-thread
stall/hitch severe enough (200-500ms) to violate the network thread’s
timing budget, after which the client hard-crashes at a fixed internal
instruction — independent of vehicle content.
REPRODUCTION
- Join server solo (no other players).
- Drive/move around normally for 1-4 minutes.
- “net thread warning: timer interval of Nms” appears twice in console
immediately before the crash, every time. - Client crashes to desktop with report code shown, exception 0xC0000005 at
GTA5_Enhanced.exe+0x1D53D9C every time (6/6).
ATTACHMENTS
dumps/ → 6 .dmp files (raw Windows minidumps)
logs/ → full client session logs (fivem-for-gtav-enhanced.log-*.log)
containing the net-thread-warning + crash tail, and (for 2 of the
sessions) the traction curve warnings we ruled out as unrelated.
Happy to provide more sessions/dumps or run any diagnostic FiveM devs need —
this is very easy to reproduce on this server (6/6 so far).
fivem-for-gtav-enhanced.log-2026-09-23_20-16-46.log (176.7 KB)
fivem-for-gtav-enhanced.log-2026-09-23_19-37-42.log (173.7 KB)
28fd5ead-fivem-for-gtav-enhanced.log-2026-09-23_20-51-46.log (176.7 KB)
c34c0b63-e66a-4357-9826-f9ca5a702dc4.dmp (3.6 MB)
6282492d-81ad51c1-ef6c-4210-9dfa-bc800a684032.dmp (3.5 MB)
061a6ade-5625-4d85-b14c-59b789626d03.dmp (3.5 MB)
9f1e12cd-e5ea3d5d-bd09-42ad-a423-6667536272ac.dmp (3.6 MB)
