What is the issue you’re having?
FiveM consistently freezes between 19 and 21 minutes after launch (regardless of whether I’m in the menu, playing, or loading), and the process has to be force-killed after ~17 to 20 more minutes of unresponsiveness; this persists after exhaustively eliminating every local software cause I could test.
- Total freeze/hang of the
FiveM_b3570_GTAProcess.exeprocess, detected either by FiveM’s internal Watchdog (“FiveM has stopped responding”) or, in some cases, by an “Early-exit trap” occurring during engine initialization (before the FiveM menu even appears). - Across 19+ crashes analyzed in detail, the delay between game launch and the crash/watchdog trigger stayed remarkably constant: between 19.0 and 21.1 minutes, regardless of:
- time of day or day of the week (crashes at 2 AM as well as 5 PM or 7 PM)
- in-game activity at the moment of the freeze (spawning, phone calls, driving, resource cache loading, or simply sitting in the main menu without connecting to any server)
- the FiveM client build in use (observed on client versions 2.0.0.30388 and 2.0.0.31917)
- Two crash signatures observed:
citizen-devtools.dll+2CCD6(majority, ~15 occurrences) — generally occurs after connecting to a serverfivem.exe+1028(~4 occurrences) — sometimes occurs as early as engine initialization (before the menu), producing an “Early-exit trap” instead of the usual watchdog message
- The crashometry associated with
citizen-devtools.dll+2CCD6consistently shows: NVIDIA RTX 5080 GPU, OneSync Big enabled, 47 client resources/mods,hs_state: HS_HOSTED. - Windows history (Reliability Monitor / Event Viewer, event 1001 “AppHangTransient” and 1002/1000) shows this issue has occurred intermittently since June 28, 2026, with a complete lull between July 2 and July 4, then resuming systematically since July 5 (happening on almost every session since).
What have you tried already to fix the issue?
All of the following were tested individually — the freeze still occurred at ~19-21 minutes after every single one:
- Antivirus exclusions (Windows Defender) for the
FiveM.appfolder,FiveM.exe, andFiveM_b*_GTAProcess.exe - Fully disabling voice chat / Mumble
- Closing and disabling Razer Synapse (process +
Razer Game Manager Service 3) - Closing Medal (app +
MedalEncoder.exe, background clip-recording software) - Closing and stopping the Corsair iCUE service (
CorsairDeviceControlService) - Disabling Xbox Game Bar / Game DVR (
GameDVR_Enabledregistry key) - Stopping and disabling the Parsec service (
pservice.exe, virtual display adapter) - Disabling the Steam overlay specifically (while still launching through Steam)
- Fully deleting the FiveM resource cache (
data/server-cacheanddata/server-cache-priv, ~2.8 GB / 8225 files) to rule out cache corruption - Changing the system clock source (
bcdedit /set useplatformclock true, forcing HPET instead of TSC), followed by a full reboot — tested because a full AMD chipset driver reinstall happened on June 27, the day before the very first recorded freeze on June 28 - Local network checks: no packet errors/drops on the network adapter (0 errors, 0 discards), no Windows Firewall rule blocking FiveM, working DNS resolution, and successful TCP/443 connections to both
runtime.fivem.netandprod.ros.rockstargames.com - Reviewed Windows Update / driver / recently installed software history to find a correlated system change — found nothing installed between July 3 and July 5 that would explain the problem resuming
What server did you get this issue on?
game.flashbackfa.fr (FXServer master v1.0.0.31623, OneSync Big, ~47 client resources) — but the freeze/crash also occurs in the FiveM menu before connecting to this or any server, so it is likely not specific to this server.
Windows version
Windows 11 Home, version 10.0.26200 (build 26200), 64-bit
System specifications
- CPU: AMD Ryzen 7 9800X3D (8 cores / 8 threads)
- Motherboard: Gigabyte X870E AORUS PRO ICE
- GPU: NVIDIA GeForce RTX 5080 (driver 32.0.16.1062, dated 2026-06-11)
- RAM: 64 GB (61.6 GB reported by the system)
- Network: Realtek PCIe 2.5GbE (currently negotiated at 100 Mbps, no packet errors)
- Headset: Razer BlackShark V2 Pro
Antivirus software
Windows Defender (exclusions added for FiveM folders/executables, no effect on the issue)
CitizenFX crash zip file (‘Save information’ on a crash)
CfxCrashDump_2026_07_05_15_14_13.zip (1.82 MB)
CfxCrashDump_2026_07_05_04_27_34.zip (1.75 MB)
CfxCrashDump_2026_07_05_03_45_53.zip (1.67 MB)
CfxCrashDump_2026_07_05_03_13_24.zip (1.47 MB)
CfxCrashDump_2026_07_05_14_53_06.zip (2 MB)
CfxCrashDump_2026_07_06_14_48_06.zip (1.74 MB)
CfxCrashDump_2026_07_05_15_41_53.zip (1.83 MB)
Additional comments
- The fact that the crash occurs at a near-fixed delay (19-21 min) regardless of in-game activity, and that it was reproduced as early as the loading screen/menu (crash
fivem.exe+1028, “Early-exit trap”, occurring after only 47 seconds of actual engine activity but only detected/reported ~20 minutes later), strongly suggests an internal timeout mechanism (watchdog, heartbeat, or a blocking network wait) rather than something triggered by player action or third-party software. - AMD chipset drivers were fully reinstalled on 2026-06-27 (the day before the very first recorded freeze on 2026-06-28). The current NVIDIA driver was also installed on 2026-06-27 (dated 2026-06-11).
- Untested hypothesis (requires a physical network change I cannot perform remotely): an upstream network device (router/ISP box) silently expiring FiveM’s UDP connections after a fixed timeout close to 19-21 minutes. Since FiveM primarily uses UDP (ENet) for its live game connection, this kind of network “black hole” would produce no detectable error on the PC side (DNS, firewall, and HTTPS/TCP all tested fine) while still explaining why the issue is unaffected by any local software change.
- Available on request: the full
.dmp(minidump) files andCitizenFX_log_*.logfiles for each of the 19 crashes, all sharing the samecitizen-devtools.dll+2CCD6(orfivem.exe+1028) hash and the same characteristic timing window.
