RagePluginHook.log

Ill just be chilling and go to a call then boom random crash

[1/20/2026 10:04:50 PM.213] LSPD First Response: ==============================

[1/20/2026 10:04:50 PM.213] LSPD First Response: UNHANDLED EXCEPTION DURING GAME FIBER TICK

[1/20/2026 10:04:50 PM.213] LSPD First Response: ------------------------------

[1/20/2026 10:04:50 PM.213] LSPD First Response: Origin: Game fiber "CalloutManager".

[1/20/2026 10:04:50 PM.213] LSPD First Response: ------------------------------

[1/20/2026 10:04:50 PM.213] LSPD First Response: Exception type: System.NullReferenceException

[1/20/2026 10:04:50 PM.213] LSPD First Response: Exception message: Object reference not set to an instance of an object.

[1/20/2026 10:04:50 PM.213] LSPD First Response: ------------------------------

[1/20/2026 10:04:50 PM.213] LSPD First Response: Inner exceptions:

[1/20/2026 10:04:50 PM.213] LSPD First Response: ------------------------------

[1/20/2026 10:04:50 PM.213] LSPD First Response: Stack trace:

[1/20/2026 10:04:50 PM.213] LSPD First Response: at PUosvGKNfpuvZgwyRUaMTvFbFpLL.jitFUDhqaSGspaDkCZhXXHrMwZiAA() in D:\GTA V\LSPD First Response\LSPD First Response\Mod\Callouts\CalloutManager.cs:line 467

[1/20/2026 10:04:50 PM.213] at PUosvGKNfpuvZgwyRUaMTvFbFpLL.CxpiwnBDhpNTeGTQLoBZIclNUkKr() in D:\GTA V\LSPD First Response\LSPD First Response\Mod\Callouts\CalloutManager.cs:line 195

[1/20/2026 10:04:50 PM.213] at Rage.GameFiber.Main()

[1/20/2026 10:04:50 PM.213] LSPD First Response: ==============================

The issue seems to be with CalloutManager handling callouts. Either an issue with Callout Manager itself, or one of the callout plugins are not compatible.

You could disable CalloutManager first and see if it still crashes. If it doesn't crash, then you can either edit the CalloutManager.ini to find out which callout plugin is causing the issue, or alternatively, install one plugin at a time until it breaks

9 hours ago, Gan Ceann said:

The issue seems to be with CalloutManager handling callouts. Either an issue with Callout Manager itself, or one of the callout plugins are not compatible.

You could disable CalloutManager first and see if it still crashes. If it doesn't crash, then you can either edit the CalloutManager.ini to find out which callout plugin is causing the issue, or alternatively, install one plugin at a time until it breaks

The CalloutManager mentioned in the log is not the mod, but an internal function of LSPDFR that handles callouts, both vanilla and callout-pack ones.

12 hours ago, ThePurpleBat said:

Ill just be chilling and go to a call then boom random crash

Indeed, that seems like a pretty random crash. Before trying to figure out what exactly was the culpirt, I would reccomend to ''stabilize'' your game by updating 686 Callouts and MC Callouts, and removing the following DLL files (all unstable at best): RegularCallouts, VarietyCallouts, CountyCalls, KucheraCallouts, dlGlobal, Jurisdictions+, Lore Callouts

If after doing all that a session ends in a crash, send the log from it.

11 hours ago, Michael21107 said:

The CalloutManager mentioned in the log is not the mod, but an internal function of LSPDFR that handles callouts, both vanilla and callout-pack ones.

Are you sure? Because the path in the log doesn't exist in a normal LSPDFR installation

Yes, the path doesn't exist in a normal installation because it's the source code path the author uses.

17 minutes ago, Michael21107 said:

Yes, the path doesn't exist in a normal installation because it's the source code path the author uses.

I see. Makes sense