RAGE error: UNKNOWN

Environment questions

GTA V version: 1.0.2944.0
Up to date: Yes
Legit or Pirate copy: Legit
Purchased where - Steam/Rockstar Launcher/Epic: Rockstar Launcher
Windows version: 11 pro
Did you try to delete content_index.xml and try again? No
System specifications: i7-12700k 12th gen, Nvidia 3060.
CitizenFX crash zip file (‘Save information’ on a crash):
logs/CitizenFX_log files:
.dmp files/report IDs:

If you can’t start the game at all

GTA V folder screenshot:

GTA V/update/x64/dlcpacks screenshot:

Filepath to FiveM folder: C:\Users\owner\AppData\Local\FiveM
FiveM client folder screenshot:
Which antivirus/firewall software are you using? MS defender
Did you try to disable/uninstall your Anti-virus? No

Important parts

What is the issue you’re having?
As the server owner, my members and I are experiencing RAGE error : Unknown crashes.
The basics are , we started seeing this issue back in June 2023, there was one or two every few days (out of 200+ playing on server), On July 20th, we suddenly experienced 29 Rage Error Crashes
in less than 15 hours. On July 21, 22nd and 23rd, we had only one total RAGE error: Unknown crash. On July 24th, we had 20 of them.

During our investigation, we have removed all resources, and attempted to rebuild the server again. On Friday (Sept 22), we had been 2 full days without a RAGE error crash,
when we continued to add server resources back in. while doing so, we suddenly started observing rage errors again. This add included 12 basic lua scripts that we had in and reviewed the files to ensure there was no corrupted code or errors.
Later Friday night, our members had several RAGE errors.

What are you trying to do?
Identify the corrupt resources, bad setting/config, and stop the RAGE error crash issue.

What have you tried already to fix the issue?

We have reviewed the firewall settings to determine if our server FW was blocking a port/service.
We have removed all resources and rebuilt the server.
We have collected cfx crash reports and reviewed the crash report with windbg, which did not clearly identify the issue.
We have worked diligently to get our members gaming PC’s up to date as much as possible (thinking the RAGE error may have been in reference to an out of date GPU driver or something).
We have went back and reviewed our current resources to observe any concerns with the folders, data files, etc. No issues were found.

Error screenshot (if any):

CfxCrashDump_2023_09_26_02_15_29.zip (2.0 MB)

What did you do to get this issue?
We are not sure.

What server did you get this issue on? Be specific and name some, ‘all of them’ by itself isn’t useful!
This has only been experienced on our server, FiveLAPD, an FXserver.


Additional comments

Hello, this is a friendly reminder because this is your first time creating a topic (or it has been a while since your last topic) in this category.

Please note that most of the support is provided by the Cfx.re community on a voluntary basis. We ask you to be patient; there is no guarantee we have a solution to your problem(s). To avoid unnecessary/duplicate topics, please browse the forums before creating a topic.

To improve your chances of your issue(s) being solved, please provide as much information as possible about the issue(s) you are having. Also —whenever possible— please use the template given to you when creating a topic.

Thanks for keeping these forums tidy!
:mascot:

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