[Bug] Client Crash (CrashForExceptionInNonABICompliantCodeRange / game RVA 0xBF5986): no resource name or call stack trace; impossible to self-diagnose #373
Closed
skriptzip
started this conversation in
[BUG] FiveM for GTAV Enhanced
Replies: 2 comments 1 reply
|
Thanks, we are looking into it. |
0 replies
|
A fix for this bug has been implemented and is available in Hotfix 8. Please try again and let us know if the issue persists. Thanks for your help! |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
After migrating from FiveM (legacy) to FiveM for GTAV Enhanced, the client
crashes repeatedly. There seems to be no apparent reason, happen when traveling arround the map, so maybe releate to map loading but could be anything else (no additional maps etc are loaded). The crash dialog shows only "exception at game RVA 0xBF5986", no resource name, no Lua stack trace, no native call context.
WinDbg analysis with FiveM's symbol server (runtime.fivem.net/client/symbols/)
reveals the crash is handled by CrashForExceptionInNonABICompliantCodeRange. Even
with symbols loaded, the failure bucket resolves to "fivem-client.dll!Unknown".
The same resources run without crashes on the legacy client. There is currently
no way for a resource developer to identify which script, file, or native call
is responsible for the crash.
Issue type
Client
Repro rate
Always
Server build version
110
OS
Windows 11 Pro
CPU
25H2
GPU
NVIDIA RTX 5080
RAM
32 GB DDR5
Storage type
SSD NVMe
Connection type
Ethernet
ISP and bandwidth
DxDiag
No response
Network graph
No response
Platform
Docker
OS version / distribution
alpine:3.20
CPU
AMD Ryzen 7 9800X3D 8-Core Processor
RAM
32 GB DDR5
Using txAdmin?
None
Hosting provider
None
Machine type
None
/perf endpoint output
No response
DDoS protection
no
ulimit -n value (Linux only)
No response
Docker Compose file (Docker only)
Steps to Reproduce
Expected Behavior
When a crash is caused by a Lua resource, the crash report or client log should
contain at minimum:
( - if caused by gta native include )
Actual Behavior
Client crashes with:
"The game has crashed: [EXCEPTION]: exception at game RVA 0xBF5986"
Report codes:
c1f27c09-48e6-4fce-8e49-c80484b01770
59c8a337-0451-470a-99ad-d6b5824585d9
WinDbg analysis (dump: 0bcb646c-39b9-431d-9ecc-21642f763f33.dmp,
symbols: msdl.microsoft.com + runtime.fivem.net/client/symbols/):
FAILURE_BUCKET_ID: CPP_EXCEPTION_e06d7363_fivem-client.dll!Unknown
ExceptionCode: 0xE06D7363 (C++ EH exception)
ExceptionAddr: KERNELBASE!RaiseException+0x8a
Call stack:
KERNELBASE!RaiseException+0x8a
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x252a31b
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x1aadced
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x1aab847
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x1bea6ea
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x1a028e6
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x19f583d
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x19d6c3d
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x1c83f94
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x1aaea60
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x1aaf050
GTA5_Enhanced!Ordinal0+0x13d293c
GTA5_Enhanced!Ordinal0+0x13d2681
GTA5_Enhanced!Ordinal0+0x15c279
GTA5_Enhanced!Ordinal0+0x157029
GTA5_Enhanced!Ordinal0+0x338c
fivem_client!CrashForExceptionInNonABICompliantCodeRange+0x1a08904
GTA5_Enhanced!Ordinal0+0x278f
GTA5_Enhanced!Ordinal0+0x2524
GTA5_Enhanced!Ordinal0+0x156070
GTA5_Enhanced!Ordinal0+0x1f80
GTA5_Enhanced!Ordinal0+0x1003fe
GTA5_Enhanced!Ordinal0+0x1956
GTA5_Enhanced!Ordinal0+0x13871e
kernel32!BaseThreadInitThunk+0x17
ntdll!RtlUserThreadStart+0x2c
No Lua context, no resource name, and no native call site appear anywhere
in the dump or client log.
Evidence
Report codes:
c1f27c09-48e6-4fce-8e49-c80484b01770
59c8a337-0451-470a-99ad-d6b5824585d9
fivem-for-gtav-enhanced.log-2026-08-06_00-33-50.log
cef-2026-08-06_00-33-51.log
fivem-launcher-2026-08-06_00-33-11.log
56458233-33a3-4801-b4c5-5d9c6a5da609.dmp
Additional Context
No response
All reactions