ScriptsAboutBlogToolsKnowledge BaseReviewsFAQBasketDocsSupport
Clientcrash

Citizen.InvokeNative crash / game crashed (no dump)

Also seen as: game crashed no dump citizen invokenative crash fivem crash no error

What causes it

The FiveM client crashed with little or no error, often from a bad native call, a corrupt streamed asset, or an out-of-memory situation from too many/too-large stream assets.

How to fix it

Narrow down the offending resource and clear caches.

  1. Clear the client server cache (FiveM.app/data/cache/) and rejoin.
  2. Server owners: disable recently-added resources one at a time to find the culprit.
  3. Reduce oversized streamed assets (vehicles, MLOs) that can exhaust memory.
  4. Ensure client and server are on current builds.
  5. Check the CitizenFX.log / crash dumps for the last resource touched.

Related errors

Invalid native call in resource (game fatally closing)An unhandled exception (msgpack::type_error) caused FiveM to stop working

Related guides

Still stuck? We can help.

Optimized, dual-framework scripts for QBCore and ESX from Viper Development — escrow protected, delivered instantly to your Cfx portal.

Join DiscordBrowse Scripts →