Charlie686

That's because RageNativeUI isn't causing the crash at all.
However, an out of date copy of LSPDFR certainly is! Update it by reinstalling LSPDFR.

Wait a minute!
Removing dinput8.dll is a diagnostic step to determine whether you have an issue with your .asi scripts (dinput8.dll is your ASI Loader).
To further help diagnose this issue, please move all .asi files in your main directory, to your desktop. Then, please re-add dinput8.dll to your main directory. Re-add your .asi files individually, and test if your game runs. Once you've identified which .asi file is causing the issue, please let me know. 🙂 

😉

Hiya,
Arrest Manager, Interaction+ & Traffic Policer are outdated. This means they have not been updated by the developers for the latest LSPDFR API versions, and can cause instability.
You should look at Bejoijo's plugins as an alternative. 

Increase your Plugin Timeout Threshold to 60,000 in the RPH settings & retry.
 

Hi there, here are some things I noticed:
 
Code 3 callouts is out of date Random Calls is out of date Typical Callouts needs an update Increase your Plugin Timeout Threshold to 60,000 in RAGE settings It is really important you keep your plugins up to date otherwise they can cause random crashes like the one you experienced. Let me know if you have anymore issues 🙂

Update RageNativeUI.
Link: https://github.com/alexguirre/RAGENativeUI/releases

Set Main.DisableGameBlipHiding to true in your lspdfr.ini 🙂 

It looks like you have ENB installed; this affects how RagePluginHook hooks with GTAV.
Therefore you need to load GTAV without RAGE; only once you are in story mode can you ALT + TAB out and launch, letting it hook.

Sweet!
I just realise I recognise your name I think, so hello again. 😄 
 
Your mp_m_freemode_01 didn't load. You could try again as it may've been a one off, but if not try disabling your mods folder for me.

In regards to your force duty crash please disable game blip hiding in your lspdfr.ini & give it another shot.
 

You should get in contact with the developer, usually through a link on their file page, to ensure it can be looked at. 😄
 

Hiya,
This crash is specifically caused by Code3Callouts, it is outdated and so I would advise its removal.
In addition the following message maybe useful:
 
The following plugins are outdated. This means they are not updated for the latest LSPDFR version.
I'd suggest their removal for the smoothest experience as they may cause issues.
However, if you find this fixes the issue, you are welcome to try re-adding them.
Though if an issue does reappear, then the plugin(s) should not be kept.
Assorted Callouts
Code Red Callouts
Crazy Callouts
Federal Callouts
HighWayCallouts
TaccoHighwayCallouts
Traffic Control
Wilderness Callouts
 
The following plugins are likely to be due an update.
Download their latest versions if they are available.
BasicCallouts

Howdy,
 
Issue is definitely not with Door Control.
Rather, you want to update RageNativeUI. 
Reviewing the stack trace is how this conclusion can be drawn.
 
Hope this helps! 😄 

I would go to OpenIV -> tools -> ASI Manager. Reinstall those. Then give your PC a restart, boot up GTAV and give it another shot.

Please rename your mods folder to _mods & give it another shot.
This is so we can confirm the issue lies there.

Hi there,
You need to increase your Plugin Timeout Threshold to 60,000 in the RAGE settings. 
Hope this helps. 😄 

Big red banner.

Check out this document and try a more appropriate handling ID.

That's a new police tactic employed by the LSPD to keep Los Santos safe!
Only kidding - make sure Everyone Ignore Player / Cops Ignore Player is set to false in your trainer. 😄 

LSPDFR does not require the internet. 😄 

The verifying your version should not come on after it has already verified that game session. 

You'd want to change the HandlingID defined in the vehicles.meta entry for said vehicle(s) to something more appropriate; GRESLEY is an example. 🙂 

CompuLite: Problem on Loading Citations.xml: System.Xml.XmlException: An error occurred while parsing EntityName. Line 10, position 38.
Hmm, give that a check!

The log is contradicting the latest version, but that could be an issue the developer needs to address.
You should report this to the developer to ensure it is actually fixed! @Officerporci may want to look at this directly here.
To provide further information as well, OfficerPorciPlugin seems to be requiring Ultimate Backup - you don't have it & that's why you are crashing.