GTA5_b3258.exe!sub_1413BF314 november-table-ink crash

[mori151]

What happened?

Randomly, a significant number of players are experiencing crashes. It seems to occur particularly around the Legion Square area. This happens regularly every day on a server with a concurrent player count of around 160 to 200.

[   8886156] [b3258_DumpServ]                20384/ Process crash captured. Crash dialog content:
[   8886156] [b3258_DumpServ]                20384/ GTA5_b3258.exe!sub_1413BF314 (0x89)
[   8886156] [b3258_DumpServ]                20384/ An error at GTA5_b3258.exe!sub_1413BF314 (0x89) caused FiveM to stop working. A crash report is being uploaded to the FiveM developers.
[   8886156] [b3258_DumpServ]                20384/ 
[   8886156] [b3258_DumpServ]                20384/ Legacy crash hash: november-table-ink
[   8886156] [b3258_DumpServ]                20384/ Stack trace:
[   8886156] [b3258_DumpServ]                20384/   GTA5_b3258.exe!sub_1413BF314 (0x89)
[   8886156] [b3258_DumpServ]                20384/   GTA5_b3258.exe!sub_1413BF8A8 (0xf3)
[   8886156] [b3258_DumpServ]                20384/   GTA5_b3258.exe!sub_1413A7AA8 (0x3a)
[   8886156] [b3258_DumpServ]                20384/   GTA5_b3258.exe!sub_1413E6B3C (0xca)
[   8886156] [b3258_DumpServ]                20384/   GTA5_b3258.exe!sub_1413E6E74 (0x52)
[   8886156] [b3258_DumpServ]                20384/   gta-core-five.dll!DrawModelGeometryHook (0x66) (CrashFixes.cpp:245)
[   8886156] [b3258_DumpServ]                20384/   GTA5_b3258.exe!sub_1413E6EFC (0x1ff)

We have introduced several MLOs, and just before the crashes, we see logs like the ones below. However, the connection between the crashes and these logs is unclear. Since there are already active players, it’s difficult to casually remove the MLOs or even confirm whether removing them would resolve the issue.

[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset lr_sc1_11_0.ybn.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 0 edge reference is invalid. It leads to vertex 81, when there are only 66 vertices.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset lr_sc1_11_0.ybn.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 222 edge reference is invalid. It leads to vertex 65386, when there are only 3454 vertices.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset lr_sc1_11_0.ybn.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 34 edge reference is invalid. It leads to vertex 65501, when there are only 627 vertices.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset lr_sc1_11_0.ybn.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 0 edge reference is invalid. It leads to vertex 65075, when there are only 2661 vertices.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset lr_sc1_11_0.ybn.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 2 edge reference is invalid. It leads to vertex 65027, when there are only 2940 vertices.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset lr_sc1_11_0.ybn.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 0 edge reference is invalid. It leads to vertex 63872, when there are only 1032 vertices.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset lr_sc1_11_0.ybn.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 0 edge reference is invalid. It leads to vertex 152, when there are only 112 vertices.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset lr_sc1_11_0.ybn.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 458 edge reference is invalid. It leads to vertex 65366, when there are only 6395 vertices.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset lr_sc1_11_0.ybn.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8749891] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 0 edge reference is invalid. It leads to vertex 12, when there are only 12 vertices.
[   8864656] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset hi@hei_dt1_12_0.ybn.
[   8864656] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8864656] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 2 edge reference is invalid. It leads to vertex 63788, when there are only 2788 vertices.
[   8880812] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset os_garagedoor_outlet.ydr.
[   8880828] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8880828] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 0 edge reference is invalid. It leads to vertex 65530, when there are only 8 vertices.
[   8881219] [b3258_GTAProce] ResourcePlacementThr/ Physics validation failed for asset os_showroom_carstand.ydr.
[   8881219] [b3258_GTAProce] ResourcePlacementThr/ This asset is **INVALID**, but we've fixed it for this load. Please fix the exporter used to export it.
[   8881219] [b3258_GTAProce] ResourcePlacementThr/ Details: Poly 0 edge reference is invalid. It leads to vertex 63730, when there are only 13296 vertices.

It would be great if we could identify the cause based on the logs.

Thank you for your support.

Expected result

should not crash

Reproduction steps

Random, not sure any way to reproduce.

Importancy

Crash

Area(s)

FiveM

Specific version(s)

FiveM 12110, Server 12092 linux

Additional information

No response

[ItzGoatATL]

Hey @mori151 do you use Gabz MLOs ? Also which artifacts and game build are you using ? I’m experiencing same issues.

[mori151]

Yes, I’m using Gabz MLOs.
The client version is b3258 (12110), and the server version is 12092 on Linux.

Here is a list of the Gabz MLOs being used.

• cfx-gabz-mapdata
• cfx-gabz-scenarios
• cfx-gabz-pdprops
• cfx-gabz-247
• cfx-gabz-pizzeria
• cfx-gabz-pdm
• cfx-gabz-pillbox
• cfx-gabz-prison
• cfx-gabz-townhall
• cfx-gabz-impound
• cfx-gabz-mrpd
• cfx-gabz-sandypd
• cfx-gabz-davispd
• cfx-gabz-paletopd
• cfx-gabz-beanmachine
• cfx-gabz-tattoo
• cfx-gabz-bobcat
• cfx-gabz-vu
• cfx-gabz-binco
• cfx-gabz-triads
• cfx-gabz-suburban
• cfx-gabz-barber
• cfx-gabz-burgershot
• cfx-gabz-pearls
• cfx-gabz-ponsonbys
• cfx-gabz-pacificbank
• cfx-gabz-catcafe
• cfx-gabz-hayes
• cfx-gabz-bennys

[newjourneybot]

What gamebuild DLC do you use? @mori151

[mori151]

b3258, Bottom Dollar Bounties

[mori151]

Is it related? #2181

[Filcatalao]

Same here, ussing b3258 since August, but crashes only started a week ago with same maps as few months ago. (Some gabz maps, kiiya and nothing more) near phillbox and legionsquare

[RebelScripts]

Did anybody find the cause?

[RebelScripts]

What graphics card are you using when this crash happens? Everyone in my server experiencing the issue so far has an AMD card—Nvidia users don’t seem to be affected.

[BeloumiixGaming]

What graphics card are you using when this crash happens? Everyone in my server experiencing the issue so far has an AMD card—Nvidia users don’t seem to be affected.

Hello i have the same problem since 2 week, and me and my players use NVIDIA graphic card

[xPioSx]

We are also experiencing this in legion square and pillbox area with gabz mlo's

[RebelScripts]

It is most likely Gabz Otto's MLO. We removed it from our server and now the crash dissapeared.

[mori151]

I tried deleting all of Gabz's plugins, but the issue still occurred... Could you help triage this issue? Is the crash dump essential since the information we have might be insufficient?

[mori151]

For some reason, the number has been decreasing, but it still occurs frequently regardless.

[VIKTORGMD]

Experiencing the same issue in our server, I am trying to investigate it. I will stop the Otto's tonight and see if the issue gets resolved. Do you guys think it could be a car model as well tho ?

[mori151]

Additional Note: I have attached the crash dump obtained during normal gameplay. CfxCrashDump_2025_02_25_17_17_34.zip

[mori151]

Apologies for the multiple messages.

• On my server, we are not using Gabz's Otto's Autos (everything else is as described in this comment .
• We have also installed several MLOs from nteam, such as cfx-nteam-ccaffe.
• It seems that crashes are still occurring even after the patch was applied on the FiveM side, as indicated by the stack trace (CrashFixes.cpp:245). I was wondering if the development team is aware of this issue.
• The stack trace has been attached above. Since we are experiencing nearly 300 crashes daily, I can ask players to provide additional stack traces if needed.

We are struggling without any improvement. Could the developers kindly assist in investigating this issue?

Thank you very much for your support.

[VIKTORGMD]

Stopping Otto's solved it for us as well i would assume its another MLO that you have causing the same issue

[mori151]

Thank you.

I believe the crashes are likely caused by MLOs and are related to rendering.

However, isolating the issue has been extremely challenging. It often doesn’t reproduce locally, and the crashes didn’t start immediately after adding a specific MLO, making it even harder to pinpoint the cause.

It’s possible that the issue is related to downloads in progress or LOD (Level of Detail). It would be greatly appreciated if the SEGV point could be identified from the crash dumps and the root cause addressed...

[mori151]

Our server has been experiencing this crash since around December. While reviewing the commits, we started to suspect that some behavior might have changed around 4b75d9a . As reported, this issue frequently occurs around Legion Square, and we have also observed crashes happening when FiveM assets are being loaded. Additionally, we have confirmed that an error related to a duplicate archetype is occurring with encrypted paid assets.

@iridium-cfx Sorry for the mention, but do you have any information on this?

[crunchFiveM]

We have the same issue atm and we run ottos MLO. Guess we will stop it and see if it improves.

[crunchFiveM]

Removing Ottos and a few other gabz MLOs have totally eliminated this crash. We no longer have any issues. Id say Ottos was the issue for us.

[mori151]

We are still experiencing this issue at a similarly high frequency, and it has now persisted for over four months, which is causing us serious trouble.

Regarding MLO, we are not using gabz ottos, yet the issue continues to occur. We've also tried addressing potential problems on our end, such as duplicate archetypes including gabz (which is known to have quality concerns) and nteam, but nothing has resolved the issue.

Based on what we've heard from other servers as well, we suspect that the issue might lie in some kind of interaction involving "something from gabz." If you're using only gabz, the problem may stem from a combination of "something from gabz" and "gabz ottos," and the ottos themselves might not be the root cause.

Would it be possible to get some support from CFX? We would really appreciate any additional information you could provide!