ScriptsAboutBlogToolsKnowledge BaseReviewsFAQBasketDocsSupport
Clientcrash

An unhandled exception (msgpack::type_error) caused FiveM to stop working

Also seen as: msgpack type_error unhandled exception FiveM client bad cast msgpack exception unhandled

What causes it

A client-side crash where data passed across the network couldn't be serialized/deserialized correctly, or a resource returned an unexpected type. Often triggered by a specific resource sending malformed data, or corrupted cached resource files on the client.

How to fix it

Clear the client's server cache and identify the resource sending bad data.

  1. On the client, delete the FiveM server cache (FiveM.app/data/cache/) and rejoin.
  2. If it persists on one server, a specific resource is likely sending malformed data — the server owner should check recent additions.
  3. Server owners: look for events passing wrong types across the network and validate payloads.
  4. Make sure the client's GTA V and FiveM are up to date.

Related errors

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.