F5F Stay Refreshed Hardware Desktop Game freezes for 20 to 40 minutes with a black screen and missing UI, no crash message appears.

Game freezes for 20 to 40 minutes with a black screen and missing UI, no crash message appears.

Game freezes for 20 to 40 minutes with a black screen and missing UI, no crash message appears.

_
_Wild_Dog_
Member
170
05-22-2021, 03:41 PM
#1
I’ve been experiencing a peculiar problem in FiveM for about a week, and my usual fixes aren’t working. I’m seeking urgent assistance. Here’s what occurs: For 20–40 minutes, the game briefly flashes white before hiding hunger, thirst, and speech icons while the minimap remains visible. Then it abruptly switches to a black screen displaying only the FiveM logo. The game doesn’t close, players don’t leave, and my PC functions normally. I can still use Alt-Tab, the game is active, and even the in-game notes remain accessible. If I’m removed from the server later, I can simply type /do to inform others about the crash. It isn’t a GPU or Windows issue, nor a thermal fault—it feels like a partial rendering or UI malfunction. I’ve tried several solutions already: clearing the FiveM cache repeatedly, installing Windows 11 25H2, wiping all disks and reinstalling the game, updating drivers, disabling shader caches, adjusting graphics settings, using DDU, downgrading the NVIDIA driver, and even switching to Windows 10 22H2. Each attempt failed to resolve the problem. The new Windows 10 setup has stable specs, no dust, and normal temperatures. VRAM usage stays within limits, RAM is healthy, and FPS caps at 60 via the control panel. Hardware acceleration is disabled, and I’m still using 4K resolution. The issue persists across different settings—high, ultra, medium—and never occurred during my first season on the same server. It seems to happen gradually, sometimes with spikes in packet loss even when internet is solid. The F8 prompt occasionally reads “your PC is performing poorly” despite normal usage (GPU 40–55%, CPU low). VRAM stays under 8GB, GPU temps remain below 70°C, and VRAM temps under 90°C. During crashes, everything appears stable—clock speeds, temperatures, and system behavior remain consistent, indicating a render or UI pipeline problem rather than hardware failure.
_
_Wild_Dog_
05-22-2021, 03:41 PM #1

I’ve been experiencing a peculiar problem in FiveM for about a week, and my usual fixes aren’t working. I’m seeking urgent assistance. Here’s what occurs: For 20–40 minutes, the game briefly flashes white before hiding hunger, thirst, and speech icons while the minimap remains visible. Then it abruptly switches to a black screen displaying only the FiveM logo. The game doesn’t close, players don’t leave, and my PC functions normally. I can still use Alt-Tab, the game is active, and even the in-game notes remain accessible. If I’m removed from the server later, I can simply type /do to inform others about the crash. It isn’t a GPU or Windows issue, nor a thermal fault—it feels like a partial rendering or UI malfunction. I’ve tried several solutions already: clearing the FiveM cache repeatedly, installing Windows 11 25H2, wiping all disks and reinstalling the game, updating drivers, disabling shader caches, adjusting graphics settings, using DDU, downgrading the NVIDIA driver, and even switching to Windows 10 22H2. Each attempt failed to resolve the problem. The new Windows 10 setup has stable specs, no dust, and normal temperatures. VRAM usage stays within limits, RAM is healthy, and FPS caps at 60 via the control panel. Hardware acceleration is disabled, and I’m still using 4K resolution. The issue persists across different settings—high, ultra, medium—and never occurred during my first season on the same server. It seems to happen gradually, sometimes with spikes in packet loss even when internet is solid. The F8 prompt occasionally reads “your PC is performing poorly” despite normal usage (GPU 40–55%, CPU low). VRAM stays under 8GB, GPU temps remain below 70°C, and VRAM temps under 90°C. During crashes, everything appears stable—clock speeds, temperatures, and system behavior remain consistent, indicating a render or UI pipeline problem rather than hardware failure.