NEED HELP with server crashing

Leave it to FiveM to take down your post and then delete it but not tell you why or where it should go, so maybe this section will work. Doubtful cause nothing else seems to work on here.

Can someone please help me out about whats going on here? This is getting frustrating. My system was fine before this new update and now I am constantly crashing. Thank you in advance for any help.

Description:
“crash_hash”: “fivem.exe+13DDD0C”,
“crash_hash_id”: 2781083131,
“crash_hash_key”: “xray-william-seventeen”,
“crashometry_did_render_backbuf”: “true”,
“crashometry_gpu_id”: “10de:1f10”,
“crashometry_gpu_name”: “NVIDIA GeForce RTX 2070 with Max-Q Design”,
“crashometry_hs_state”: “HS_HOSTED”,
“crashometry_last_server”: “185.223.28.55:30120”,
“crashometry_last_server_url”: “http://185.223.28.55:30120/”,
“crashometry_last_server_ver”: “master v1.0.0.7549”,
“crashometry_load_game_first_launch”: “true”,
“crashometry_onesync_big”: “true”,
“crashometry_onesync_enabled”: “true”
Server artifact version:
not the updated version. How does FiveM Update but not make everyone running a server update their artifact to match the new version. These crashes can be stopped.

Expected behavior:
Current behavior:
Error screenshot:

.dmp/crash files:
973abf5a-6bb4-456f-9cb3-63240414f719.dmp (7.7 MB)

Files/Code to reproduce bug:
Extra information:

It is the job of the server owner to manage their own server.

https://runtime.fivem.net/artifacts/fivem/build_server_windows/master/

Yeah, no duh; but I haven’t received a message back from them in over 20 days. I needed to know if it was my end or on theirs. FiveM continuing to show their prowess in customer support.

I’m not FiveM, and this isn’t customer support. This is you getting a response from a stranger on a community forum.

The warning in your first screenshot means the server is running an old version of FXServer.
The error in your second screenshot appears to make references to entity networking.
Older versions of FXServer (and thus older versions of OneSync) were known to have networking issues.
Thus it is likely the error is related to the server running an older artifact version, as opposed to something related to your client specifically.

If you would like any further help, I highly suggest filling out the entire Support Template, and taking the attitude down a notch.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.