Step 4
Four Step Ultimate Troubleshooting Guide
Step 4. Disable your asi and root folder mods.
What are we doing? We are going to troubleshoot the root folder mods.
Why are we doing this? This last step is to ensure it is not an asi mod, or any root folder mod, that is causing issues.
It is very unlikely to be your trainer, but it could be an .asi script mod that is outdated, conflicting, or just not right for your system. Or something may have broken after a patch. It is also unlikely to be an essential file such as the heap and packfile mods, or ScriptHookVDotNet.asi, but anything is possible.
Instructions
Use the same process of renaming the mods, but go one by one. Don't rename OpenIV, it's not necessary. Also make sure to change the .asi extension to something like .bak, if you keep the extension as an .asi it will still try to be loaded by dinput8.dll and could cause issues. If you still can't find the problem, and if you're confident that it isn't a hardware, software, or folder structure issue, then you may want to check out these posts:
When All Else Fails - No Fix Works!
Recovering from a GTA 5 update
If you really want to become an expert at fixing mod issues, the following 2 articles are highly recommended. Following the advice there will help develop your troubleshooting skills.
Four Step Ultimate Troubleshooting Guide
Step 1. Disable all mods and test un-modded
Step 2. Disable your scripts folder
Step 3. Disable your mods folder
Step 4. Disable your asi and root mods
