Diagnose the failure before changing settings

First determine whether the issue affects one server, all servers, or the base game itself. Then capture the exact error and reproduce one action. A report with a time, a resource name, and reproducible steps is more useful than a list of random cache and graphics changes.

This page is for players and client-side developers. For an FXServer startup failure or network binding problem, use common server errors and server networking.

Separate the problem into one of three paths

A successful session elsewhere narrows the search; it does not prove a particular resource is defective. Keep other variables steady while testing.

Use the right console

F8 opens the client console. txAdmin’s live console is the server console. They are not interchangeable: ensure resource_name belongs on the server, while player connection and display diagnostics belong in F8.

These reversible F8 commands show and then hide performance information:

cl_drawperf true
cl_drawfps true

After reproducing the issue:

cl_drawperf false
cl_drawfps false

Record the activity alongside the readings. Low FPS, high latency, and packet loss are different observations; one number alone does not identify the root cause.

Developer-only resource measurements

On a development client with the appropriate developer-mode permissions:

resmon 1

Use resmon 0 afterward. An Access denied for command resmon message is a documented mode restriction, not evidence of a corrupt installation. Follow the official console-command documentation  for supported developer modes; players should not bypass a server’s restrictions.

For function-level investigation, follow recording and comparing profiler captures. A resource monitor is a starting point, not a complete diagnosis of GPU, asset-streaming, or network problems.

Send a report someone can reproduce

Copy the first relevant F8 error and the lines around it, not only the final cascade of follow-on failures. Preserve the corresponding client log locally when available. Use this template:

Observed at: 2026-09-22 14:30 Europe/Berlin
Client/game edition and build:
Affected server (share privately where appropriate):
Action: joined / opened menu / entered vehicle / visited location
Expected behavior:
Actual behavior:
First complete error and resource name:
Reproduction steps:
Does it happen on another server?:
Recent changes made before the issue:
Attachments: relevant log excerpt, screenshot, or requested profiler capture

The date is an example, not a timestamp generated by FiveM. Replace it with the actual occurrence. Remove account identifiers, IP addresses that should stay private, tokens, and unrelated chat before publishing a report. Keep an unedited local copy in case trusted support needs it.

Full crash dumps: only when requested

A full memory dump can contain private process data and can be very large. It is not an ordinary public log attachment. Use it when a trusted support contact specifically needs one, and arrange a private transfer.

The official full-dump procedure  uses this setting in the installation’s CitizenFX.ini:

EnableFullMemoryDump=1

Back up the file, enable the setting, reproduce the requested crash, and allow the dump to finish writing. Confirm that it is the same crash you are investigating. Remove the setting after collection so future crashes do not keep producing full dumps. Do not upload dumps to a public issue or paste their contents into a chat.

Avoid destructive default fixes

Do not delete application folders, system DLLs, or game files just because an unrelated post recommends it. Start from the exact error’s official support guidance , back up relevant configuration, and change one thing at a time. Return to the answer finder for resource, NUI, voice, and server-side investigations.