Potionek

When GTA V receives a major title update, NVE modifies core archive files (like update.rpf, timecycle, and gameconfig.xml inside your mods folder). Because game updates change the internal memory layout and asset tables of GTA V, an unupdated mods folder containing an older NVE installation causes the game engine to hang or silently crash in the background before the window can even render.
Specifically, NVE relies on three components that break during game updates:
Outdated gameconfig.xml / dlclist.xml: NVE inserts custom DLC entries and asset modifications into your mods folder. When GTA V updates, the old gameconfig.xml inside your mods folder no longer matches the game's new build limits, forcing GTA5.exe to lock up instantly upon asset initialization.
NVE.asi / Custom Shaders: NVE uses its own script plugin (NVE.asi) and custom graphic overrides. When Script Hook V updates to support a new patch, older .asi files like NVE.asi can cause silent startup freezes until a patched build of NVE is released.
Modified Core .rpf Files: If NVE replaced or patched game archives inside your mods folder (like update.rpf), those modified archives tell the game to read outdated baseline data, leading to a silent background crash or endless loading.
How to use NVE again safely:
Re-create a clean mods folder in OpenIV.
Download and install the latest Gameconfig for Limit Adjuster, Heap Adjuster, and Packfile Limit Adjuster.
Re-download and reinstall the latest build of NVE that explicitly states support for your new GTA V version.

Yeah I can see the line relating to ELS. What I want you to do is remove whatever xml's you have in ELS/pack_default. Then add them one-at-a-time and test after each addition. See if there are any problems.

Computer+ is out dated and known to cause crashes.